There was no disk pool down And that i cross checked it. I present in a tech note that any backup career to DataDomain fails with mistake 2074 - Disk quantity is down when you will discover already active jobs producing to exactly the same quantity. I had been getting the mistake until a number of Careers had been functioning but when there was only one work jogging, I ran the command nbdelete -allvolumes –pressure on grasp server which executed properly.
1.5) Get Credential on VCenter for Netbackup to work with at some time of backup( if you want to to utilize the Esxi also for backups have the Credential on ESxi also)
-> in order to use this Virtual Device server for Focused backup host, that can be selected from “ For backup host” alternative if not depart it default.
Having said that I because uncovered that each one other shoppers Have got a -bkup extension for their name and have entries in their hosts file and within the grasp server appliance which position to your -bkup identify also to utilize the netbackup vlan IP rather than the normal host IP. I now have each entries stated in the console beneath Host properties, purchasers. I get "the vnetd proxy encountered an error" information when I click on both of them.
Both equally storage models are accessible and backup Work are operating good on them. What might be the trigger and feasible solutions of the mistake?
I get the next error on my Home windows File Stage backup coverage clientele veritas for randemly, as a way to resolve this difficulty i generally unistall and set up the NBU consumer with reissue token opption...following reinstall the NBU shopper, backup will work wonderful.
Each of the backup Work including catalog backup Careers are jogging efficiently. I tried to cleanup all expired visuals with bpimage -cleanup –allclients because of to boost in sizing of impression catalog and received mistake.
I suppose it might be the cert really should be regenerated for hostname-bkup as an alternative to just hostname but I'm Doubtful how To do that of if this really is my challenge.
-> Then It's going to open up up the window much like down below , decide on “Digital Device server type” through the drop down listing
Following that I ran bpimage -cleanup –allclients and this time the graphic cleanup command ran entirely thriving. So ultimately difficulty obtained fixed.
see the underneath tech Be aware to be aware of the different readily available “Virtual Machine server” and purpose of each
Notice:- Credential can get added productively only in the event the master server or certain backup host has the interaction with “Digital Machine server” however port selection 443.
I installed the windows customer on an SQL server. I had been on a help connect with and also the agent explained it absolutely was Okay to skip the cert era because it wouldn't link. Afterwards I couldn't receive the shopper to connect adequately. on Investigation I uncovered that somone had removed the netbackup VLAN. I have added the new NIC assigned IP and ran the command to make a cert properly.
The media server outlined in the down below work facts has two storage models, 1 nearby push as fundamental disk storage device stu-03 along with other 1 is facts domain network travel dd670backup