The Greatest Guide To veritas

The Greatest Guide To veritas

Blog Article

There was no disk pool down And that i cross checked it. I found in a tech Take note that any backup task to DataDomain fails with mistake 2074 - Disk volume is down when you can find already Energetic Work producing to exactly the same volume. I had been getting the error right until several Work opportunities were managing but when there was just one job working, I ran the command nbdelete -allvolumes –pressure on learn server which executed effectively.

1.five) Get Credential on VCenter for Netbackup to make use of at time of backup( if you desire to to use the Esxi also for backups obtain the Credential on ESxi also)

-> in order to use this Digital Equipment server for Focused backup host, that may be chosen from “ For backup host” solution Otherwise go away it default.

Nevertheless I considering that found out that all other customers Have a very -bkup extension to their title and also have entries inside their hosts file and over the learn server equipment which point towards the -bkup name and to use the netbackup vlan IP as opposed to the conventional host IP. I now have equally entries stated during the console less than Host properties, customers. I get "the vnetd proxy encountered an error" information After i click both of these.

Equally storage units are accessible and backup Employment are working fantastic on them. What could possibly be the result in and achievable options of this mistake?     

I get the subsequent mistake on my Windows File Level backup plan purchasers for randemly, so as to solve this concern i usually 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 illustrations or photos with bpimage -cleanup –allclients because of to increase in sizing of impression catalog and got mistake.

I suppose it might be the cert really should be regenerated for hostname-bkup periksa di sini as an alternative to 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 , decide on “Virtual Device server type” with the drop down listing

After that I ran bpimage -cleanup –allclients and this time the graphic cleanup command ran fully successful. So eventually problem obtained resolved.

see the down below tech Notice to understand the various out there “Virtual Device server” and job of each

Observe:- Credential can get additional properly only when the grasp server or precise backup host has the communication with “Virtual Device server”  nevertheless port quantity 443.

I put in the Home windows client on an SQL server. I was over a aid contact along with the agent reported it was ok to skip the cert era since it would not join. Afterwards I couldn't obtain the customer to attach thoroughly. on Investigation I found 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, a single neighborhood push as primary disk storage device stu-03 and various a person is data area community travel dd670backup