There was no disk pool down and i cross checked it. I found in a tech note that any backup career to DataDomain fails with error 2074 - Disk volume is down when you will find now active Careers creating to a similar volume. I used to be receiving the error until eventually several Careers have been functioning but when there was only one task functioning, I ran the command nbdelete -allvolumes –power on learn server which executed productively.
one.five) Get Credential on VCenter for Netbackup to make use of at enough time of backup( if you would like to make use of the Esxi also for backups receive the Credential on ESxi also)
-> if you want to use this Virtual Device server for Committed backup host, which might be selected from “ For backup host” alternative if not depart it default.
Having said that I because identified that each one other purchasers Have got a -bkup extension for their identify and have entries in their hosts file and within the grasp server equipment which place to the -bkup identify also to use the netbackup vlan IP as opposed to the conventional host IP. I now have equally entries stated during the console under Host properties, clients. I get "the vnetd proxy encountered an mistake" information After i click both of these.
Equally storage models are obtainable and backup Work are operating fantastic on them. What may very well be the induce and probable methods of the mistake?
I get the next error on my Windows File Amount backup coverage consumers for randemly, in an effort to solve this problem i usually unistall and put in the NBU customer with reissue token opption...immediately after reinstall the NBU customer, backup performs fantastic.
All of the backup Work including catalog backup Careers are jogging productively. I tried to cleanup all expired images with bpimage -cleanup –allclients owing to improve in size of graphic catalog and acquired error.
I think it would be the cert ought to be regenerated for hostname-bkup rather than just hostname but I am unsure how To achieve this of if this genuinely is my issue.
-> Then It will open up up the window similar to underneath , pick “Digital Machine server style” from your fall down checklist
Following that I ran bpimage -cleanup –allclients and this time the impression cleanup command ran entirely thriving. So last but not least issue acquired fixed.
see the underneath tech note to be aware of the different offered “Digital Machine server” and purpose of each
Notice:- Credential can get added productively only when the grasp server or unique backup host has the communication with “Virtual Device server” nevertheless port amount 443.
I mounted the Home windows client periksa di sini on an SQL server. I used to be with a support phone and the agent mentioned it had been Okay to skip the cert technology as it wouldn't link. Later on I could not have the client to connect correctly. on Investigation I uncovered that somone experienced eradicated the netbackup VLAN. I've included the new NIC assigned IP and ran the command to generate a cert efficiently.
The media server described during the below occupation information has two storage models, a person local drive as fundamental disk storage unit stu-03 along with other one particular is knowledge area network generate dd670backup