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 error 2074 - Disk volume is down when you will find now active jobs composing to a similar volume. I used to be receiving the error until eventually multiple Positions were working but when there was only one career running, I ran the command nbdelete -allvolumes –power on grasp server which executed successfully.

1.5) Get Credential on VCenter for Netbackup to implement 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” solution Otherwise go away it default.

Nevertheless I considering that learned that every one other clients Possess a -bkup extension to their name and have entries within their hosts file and about the grasp server equipment which place into the -bkup identify and to use the netbackup vlan IP instead of the normal host IP. I now have the two entries detailed while in the console underneath Host Houses, purchasers. I get "the vnetd proxy encountered an mistake" concept Once i click on either of them.

Both storage models are obtainable and backup Work opportunities are running fine on them. What could be the cause and possible solutions of the mistake?     

I get the next error on my Home windows File Stage backup coverage clientele for randemly, as a way to resolve this problem i always unistall and put in the NBU customer with reissue token opption...soon after reinstall the NBU consumer, backup works great.

Many of the backup Work opportunities like catalog backup Work are running properly. I attempted to cleanup all expired pictures with bpimage -cleanup –allclients thanks to raise in dimension of graphic catalog and acquired error.

I believe it might be the cert need to be regenerated for hostname-bkup in lieu of just hostname but I'm Not sure how To do that of if this definitely is my dilemma.

-> Then It'll open up up the window much like down below , choose “Digital Machine server form” in the fall down list

Following that I ran bpimage -cleanup –allclients which time the picture cleanup command ran completely prosperous. So lastly challenge received fixed.

see the underneath Di Sini tech note to grasp the different offered “Digital Machine server” and position of each and every

Be aware:- Credential can get included productively only in the event the master server or unique backup host has the communication with “Virtual Equipment server”  though port amount 443.

I mounted the windows client on an SQL server. I used to be with a assistance phone and the agent mentioned it had been ok to skip the cert generation because it wouldn't hook up. Later on I could not get the consumer to connect appropriately. on Investigation I found out that somone had taken out the netbackup VLAN. I have extra The brand new NIC assigned IP and ran the command to crank out a cert efficiently.

The media server pointed out in the down below task specifics has two storage models, a person nearby drive as basic disk storage device stu-03 and other one is data area community drive dd670backup