There was no disk pool down and i cross checked it. I present in a tech note that any backup position to DataDomain fails with error 2074 - Disk quantity is down when there are actually presently Lively Work opportunities composing to the same volume. I used to be getting the error right until numerous Work opportunities were managing but when there was just one work running, I ran the command nbdelete -allvolumes –force on grasp server which executed properly.
1.5) Get Credential on VCenter for Netbackup to work with at some time of backup( if you would like 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” alternative if not depart it default.
On the other hand I since identified that each one other purchasers have a -bkup extension to 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 then the traditional host IP. I now have both entries outlined within the console below Host Qualities, clientele. I get "the vnetd proxy encountered an error" message when I click on either of them.
Both storage models are obtainable and backup Work opportunities are jogging high-quality on them. What may very well be the bring about and doable remedies of this error?
I get the subsequent mistake on my Home windows File Degree backup policy clients for randemly, so that you can take care of this situation i often unistall and install the NBU shopper with reissue token opption...immediately after reinstall the NBU customer, backup operates good.
Every one of the backup Employment such as catalog backup jobs are jogging productively. I tried to cleanup all expired visuals with bpimage -cleanup –allclients owing to improve in size of graphic catalog and acquired mistake.
I believe it might be the cert should be regenerated for hostname-bkup in lieu of just hostname but I'm Doubtful how To accomplish this of if this truly is my issue.
-> Then It's going to open up the window just like under , pick out “Virtual Equipment server kind” within the drop down record
After that I ran bpimage -cleanup –allclients which time the image cleanup command ran fully successful. So last but not least problem obtained resolved.
see the down below tech Be aware to be familiar with the various readily available “Virtual Device server” and purpose of each
Notice:- Credential can get added productively only in the event the master server or distinct backup host has the interaction with “Virtual Machine server” however port number 443.
I set up the windows customer on an SQL server. I had been on a assist connect with and also the agent explained it absolutely was ok to skip the cert generation since it would not join. Later on I could not have the client to connect adequately. on Investigation I discovered that somone had taken out the netbackup VLAN. I have extra The brand new NIC assigned IP periksa di sini and ran the command to generate a cert effectively.
The media server described from the down below occupation specifics has two storage units, one particular community travel as basic disk storage unit stu-03 and also other just one is data area community travel dd670backup