Status 96 : Error unable to allocate new media for backup, storage unit has none available (96) even when tapes are available in scratch pool / NBU status: 96, EMM status: No media is available unable to allocate new media for backup, storage unit has none available (96)

Netbackup job failing to write data on the tape media with following error message

NBU status: 96, EMM status: No media is available
unable to allocate new media for backup, storage unit has none available (96)

Things to check :
–> status on tape library management console , make sure all green,
–> make you have empty tape available to write the data or add new tape media
–> make sure scratch pool was created correctly
–> make sure driver was up from Netbackup console
–> make you tape drivers are able to performed move operation or clean-up job
—> restart the service if required.
–> run the netbackup tape library configuration wizard.
–> most of the time issue is mainly related to tape media so make sure you have correct media available or run the expire of media


bpmedialist -U -m (media ID)  — to check the media status

bpexpdate -d 0 -m (Media ID) –> to expire media


Thanks !

Azure Virtual Machines Availability Zone and Availability set

Configure and Manage Public cloud with Azure is piece of cake same way configuring high availability for virtual machine is very simple with feature availability zone and availability set. With the availability zone we can manually select the Datacenter option from 1 to 3 in the same building or region. availability set provide a group of two or more vm to ensure that at least one is available during planned or unplanned events. availability option must need to configure while create a virtual machine as it can’t be changed after creation. Availability option expressly tell virtual machine that is identical or related such as webserver behind load balancer

Availability Zone :-

As we can see from below , we have option to select VM placement from Datacenter from 1 to 3  in same building or region.



Availability Set :-

with availability set azure is going to make an attempt to physically separate those machine so that something that would take down one VM won’t take down others and those might be bad power supply or a windows update or some kind of a patch so any unintended or intended downtime is minimized and it only works for two or more virtual machine.

Fault domain

FD is mainly related to physical problem such as power supply, network issues or switch issue, so if you deploy two VM across two FD then a single power supply or single network switch is not going to bring down VM. Fault domain maximum can be increased to 3 and default is 2.



Update Domains :-
there are 20 maximum update domains , so if we have 20 vms we cloud deploy 20 update domains and MS is going to roll out the patches from 1st to all the way up to 20 so vm can rebooted one at a time , default is 5

Visit also :- 


Azure File Sync Cloud Tiering

Azure Cloud tiering is most effective feature to provide extra fixability to the azure file share , with the help of cloud tiering unused or unassessed data stored on the local file server endpoint can directly ingest to the cloud with intelligent method. it is kind of data archiving solution. unlike other archiving solution where they replaced actual files in to shortcut same way  fingerprint will left for that particular files .when you need to access file it will download from contain in  azure cloud.

  1. Least used content is cloud tiered
  2. Before removing the files server from the file sync group make sure you pull down all data first otherwise you will loss data.  all data can be pull back with the help of PowerShell
  3. File smaller than 64KB will never be cloud tiered, ,must be more that in size
  4. Cloud tiering file server is server based not the sync group based
  5. works based on the free space available on the file server endpoint


For More information :-