08-17-2012 06:36 AM
Hi All,
We have recently taken a VMware backup of 4 windows clients under a common policy. Now where one client is showing the both VMDK and folders view while selecting the "flash backup windows" as policy type and "Normal backup" as policy type....the other is displaying only the VMDK files. It is giving an error: unable to obtain list of files using specified search criteria....It is showing the backup that has happened today but not able to fetch.
Any ideas please where i could be going wrong?
Thanks, Anish
Solved! Go to Solution.
09-13-2012 06:48 AM
Hi Stuart,
Thanks for your suggestions. This is how the issue got resolved.
We checkedt he server disk properties and found that there was corrput disk path which could not be removed.
With some special priviledges, Server team, removed the path and readded it.
Restores were successful after that.
Cheers
Anish
08-17-2012 08:48 AM
I would look at logs, as I presume your backups are all successful of these VM's. Status 0. If not review the activity monitor of these jobs.
Your problem is around browsing the backup images, from within the BAR gui.?
So review the directory on the master server logs\bprd\
08-20-2012 04:49 AM
Thanks Stuart,
getting hold of the server team to check the encryption stuff and all.
info that you desire are as follows:
the backups are all VCB backups
Netbackup version is: 7.1.0.2
08-20-2012 06:58 AM
I would recommend you start to plan in a move over to vstorage api. Has several advantages over VCB and the fact support for VCB is being withdrawn by VMware.
vstorage api compatibility with netbackup would result in checking your ESX version (if on vsphere ESX(i)4 then your OK) If on ESX(i)3.5 make sure you are at the latest Update I believe vstorage api came in after update 2 or 3.
But you get change block tracking and much more features when move to vstorage api. Block level incremental backups too.
09-13-2012 06:48 AM
Hi Stuart,
Thanks for your suggestions. This is how the issue got resolved.
We checkedt he server disk properties and found that there was corrput disk path which could not be removed.
With some special priviledges, Server team, removed the path and readded it.
Restores were successful after that.
Cheers
Anish