There was no disk pool down And that i cross checked it. I found in a tech note that any backup job to DataDomain fails with mistake 2074 - Disk quantity is down when you will find currently Lively Work writing to exactly the same quantity. I had been getting the mistake right up until several jobs have been operating but when there was just one work managing, I ran the command nbdelete -allvolumes –power on grasp server which executed effectively.
1.5) Get Credential on VCenter for Netbackup to implement at enough time of backup( if you want to to utilize the Esxi also for backups receive the Credential on ESxi also)
-> in order to use this Virtual Device server for Committed backup host, which might be picked from “ For backup host” possibility Otherwise go away it default.
On the other hand I given that uncovered that every one other shoppers have a -bkup extension to their identify and also have entries in their hosts file and within the grasp server appliance which issue towards the -bkup name and to utilize the netbackup vlan IP as opposed to the normal host IP. I now have both entries listed inside the console below Host Houses, shoppers. I get "the vnetd proxy encountered an error" message Once i click either of these.
Each storage models are accessible and backup Careers are jogging good on them. What could be the cause and possible alternatives of this mistake? situs web
I get the subsequent mistake on my Home windows File Amount backup coverage shoppers for randemly, in an effort to take care of this situation i usually unistall and set up the NBU shopper with reissue token opption...soon after reinstall the NBU shopper, backup functions high-quality.
All of the backup Positions including catalog backup Employment are running efficiently. I made an effort to cleanup all expired images with bpimage -cleanup –allclients due to boost in measurement of impression catalog and bought error.
I presume it might be the cert must be regenerated for hostname-bkup instead of just hostname but I'm unsure how to do this of if this truly is my issue.
-> Then It is going to open up up the window much like underneath , select “Virtual Equipment server style” from the fall down listing
After that I ran bpimage -cleanup –allclients and this time the image cleanup command ran completely effective. So at last difficulty obtained settled.
see the underneath tech Notice to be aware of the several obtainable “Virtual Device server” and function of each and every
Observe:- Credential will get added productively only once the learn server or specific backup host has the conversation with “Digital Equipment server” nevertheless port amount 443.
I mounted the windows customer on an SQL server. I used to be on the guidance contact and the agent mentioned it absolutely was Alright to skip the cert technology as it wouldn't hook up. Later on I could not have the consumer to connect correctly. on Investigation I found out that somone experienced removed the netbackup VLAN. I've added The brand new NIC assigned IP and ran the command to create a cert properly.
The media server mentioned inside the under work information has two storage units, 1 neighborhood drive as basic disk storage unit stu-03 and various one is facts domain community push dd670backup