There was no disk pool down And that i cross checked it. I present in a tech Take note that any backup position to DataDomain fails with mistake 2074 - Disk quantity is down when you will find presently Energetic Work opportunities crafting to the exact same quantity. I had been getting the error till various Employment had been working but when there was just one occupation jogging, I ran the command nbdelete -allvolumes –force on master server which executed efficiently.
1.5) Get Credential on VCenter for Netbackup to utilize at enough time of backup( if you would like to use the Esxi also for backups obtain the Credential on ESxi also)
-> if you need to use this Virtual Machine server for Devoted backup host, which can be chosen from “ For backup host” solution if not go away it default.
Having said that I since discovered that each one other shoppers have a -bkup extension to their identify and also have entries inside their hosts file and around the grasp server equipment which stage to your -bkup identify and to use the netbackup vlan IP as opposed to the conventional host IP. I now have both equally entries mentioned within the console beneath Host Houses, purchasers. I get "the vnetd proxy encountered an mistake" concept Once i click on possibly of them.
Each storage units are available and backup Work opportunities are running good on them. What could possibly be the lead to and doable alternatives of the error?
I get the next error on my Windows File Degree backup policy customers for randemly, in an effort to solve this situation i often unistall and install the NBU customer with reissue token opption...immediately after reinstall the NBU customer, backup performs wonderful.
Each of the backup Employment such as catalog backup Work are running correctly. I made an effort to cleanup all expired photographs with bpimage -cleanup –allclients because of to increase in sizing of impression catalog and received mistake.
I think it would be the cert ought to be regenerated for hostname-bkup rather than just hostname but I am Uncertain how To achieve this of if this seriously is my difficulty.
-> Then It'll open up up the window much like below , decide on “Virtual Equipment server sort” in the fall down checklist
Following that I ran bpimage -cleanup –allclients and this time the graphic cleanup command ran fully successful. So eventually periksa di sini concern bought settled.
begin to see the under tech note to grasp the several out there “Virtual Equipment server” and part of each and every
Be aware:- Credential can get included efficiently only in the event the master server or distinct backup host has the interaction with “Virtual Device server” though port amount 443.
I mounted the windows consumer on an SQL server. I had been on the guidance get in touch with as well as agent mentioned it absolutely was Okay to skip the cert generation because it would not join. Afterwards I couldn't have the client to connect correctly. on Investigation I uncovered that somone experienced removed the netbackup VLAN. I've included the new NIC assigned IP and ran the command to create a cert properly.
The media server mentioned inside the under career particulars has two storage units, a single community travel as basic disk storage unit stu-03 along with other one particular is facts area community push dd670backup