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 there are actually previously Lively Work opportunities creating to the exact same volume. I was receiving the mistake until finally various Employment ended up running but when there was only one career running, I ran the command nbdelete -allvolumes –power on grasp server which executed correctly.

1.5) Get Credential on VCenter for Netbackup to work with at some time of backup( if you want to make use of the Esxi also for backups receive the Credential on ESxi also)

-> if you wish to use this Virtual Device server for Committed backup host, which might be selected from “ For backup host” choice if not depart it default.

On the other hand I since found that every one other clients have a -bkup extension to their name and also have entries within their hosts file and about the grasp server equipment which issue to the -bkup name and to use the netbackup vlan IP as an alternative to the traditional host IP. I now have both of those entries listed in the console under Host Homes, purchasers. I get "the vnetd proxy encountered an mistake" information After i click both of them.

The two storage units are accessible and backup Work are operating good on them. What could possibly be the result in and achievable options of this mistake?     

I get the subsequent error on my Windows File Level backup plan purchasers for randemly, so as to solve this concern i often unistall and install the NBU shopper with reissue token opption...immediately after reinstall the NBU customer, backup operates good.

All the backup Careers which include catalog backup Positions are working effectively. I made an effort to cleanup all expired photographs with bpimage -cleanup –allclients because of to increase in dimensions of picture catalog and bought mistake.

I presume it'd be the cert needs to be regenerated for hostname-bkup instead of just hostname but I am Uncertain how To achieve this of if this genuinely is my problem.

-> Then It will eventually open up the window comparable to beneath , select “Virtual Equipment server variety” in the fall down list

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

see the underneath tech note to be aware of the different readily available “Virtual Device server” and role of each and every

Be aware:- Credential can get included productively only if the grasp server or unique backup host has the conversation with “Digital Equipment server”  although port variety 443.

I mounted the windows consumer on an SQL server. I used to be with a assistance phone as well as agent stated it had been Alright to skip the cert technology mainly because it would not connect. Afterwards I couldn't receive the customer to attach properly. on Investigation I found Di Sini that somone had taken out the netbackup VLAN. I've extra The brand new NIC assigned IP and ran the command to deliver a cert effectively.

The media server pointed out while in the down below position details has two storage units, 1 regional travel as essential disk storage device stu-03 and other 1 is information domain network drive dd670backup