There was no disk pool down and i cross checked it. I located in a tech Notice that any backup job to DataDomain fails with mistake 2074 - Disk quantity is down when there are actually presently Lively Employment crafting to the identical quantity. I had been getting the mistake until several Careers had been jogging but when there was just one occupation managing, I ran the command nbdelete -allvolumes –drive on master server which executed productively.

one.five) Get Credential on VCenter for Netbackup to make use of at time of backup( if you prefer to to use the Esxi also for backups obtain the Credential on ESxi also)

-> if you need to use this Digital Machine server for Dedicated backup host, which can be chosen from “ For backup host” possibility Otherwise leave it default.

Nonetheless I due to the fact found out that all other customers Have a very -bkup extension to their title and also have entries inside their hosts file and to the learn server equipment which issue for the -bkup title and also to utilize the netbackup vlan IP rather then the normal host IP. I now have both entries outlined inside the console beneath Host Homes, consumers. I get "the vnetd proxy encountered an mistake" concept Once i click on either of these.

Both storage models are obtainable and backup Careers are functioning great on them. What could be the induce and probable methods of the mistake?     

I get the next error on my Home windows File Amount backup coverage consumers for randemly, as a way to resolve this issue i always unistall and put in the NBU shopper with reissue token opption...immediately after reinstall the NBU customer, backup operates good.

All of the backup jobs including catalog backup Careers are jogging efficiently. I tried to cleanup all expired visuals with bpimage -cleanup –allclients thanks to raise in dimension of image catalog and obtained error.

I think it would be the cert ought to be regenerated for hostname-bkup rather than just hostname but I am Not sure how to do this of if this seriously is my difficulty.

-> Then It'll open up up the window similar to underneath , pick “Digital Machine server style” through the fall down checklist

Following that I ran bpimage -cleanup –allclients and this time the impression cleanup command ran totally thriving. So ultimately issue acquired fixed.

see the underneath tech note to be aware of the different readily available “Virtual Machine server” and purpose of each

Notice:- Credential can get added efficiently only in the event the master server or distinct backup host has the interaction with periksa di sini “Virtual Machine server”  however port selection 443.

I set up the windows customer on an SQL server. I used to be on a assist call as well as the agent claimed it was ok to skip the cert era since it would not join. Later on I couldn't get the consumer to connect adequately. on Investigation I discovered that somone had eliminated the netbackup VLAN. I have additional The brand new NIC assigned IP and ran the command to crank out a cert correctly.

The media server talked about while in the underneath career aspects has two storage models, 1 neighborhood generate as standard disk storage unit stu-03 together with other just one is info domain network drive dd670backup