08-05-2015 07:41 PM
We recently noticed backups made of primary mirror pair databases (not secondary) which show in the client status as having been successfully backed up are not enumerated in the list of databases available for restore using a client restore from the same server. Effectively this means our databases are not backed up as they are currently unavailable for restore.
Has anyone else noticed this behaviour?
Screenshots showing successful backup of a db named ADBC_OTEN then the database not being enumerated for restore are attached below. This seems to be occuring across all our mirror primaries on SQL2008R2 except a few on SQL2012 - the environment is large and we are still checking but I wanted to get this out there to see if anyone has a quick answer.
Netbackup server view shows the primary mirrors are in the catalogue/contents list for the server meaning they were backed up, as shown in the last screengrab.
TIA, Danielle.
Excuse me if this is vague, this is my first question on this topic and we are the database administrators not the primary backup admins.
The mirror dbs are in yellow.
Solved! Go to Solution.
08-06-2015 10:47 PM
Have you checked out the NBU admin guide for MSSQL?
http://www.symantec.com/docs/DOC6479
In page 152~153, it stated that you need to create the a file (No.Restrictions) in master server, this is usually needed for restore & browse to work properly. That file is not required for a successful backup. To create that file, contact your Netbackup admin.
08-05-2015 09:01 PM
Have you checked the same from the other server (mirrored one)? It might have moved.
08-06-2015 10:06 PM
Yes, that the mirror was still the primary was checked - and shows in the first picture as well (Principal, Synchronised)
08-06-2015 10:47 PM
Have you checked out the NBU admin guide for MSSQL?
http://www.symantec.com/docs/DOC6479
In page 152~153, it stated that you need to create the a file (No.Restrictions) in master server, this is usually needed for restore & browse to work properly. That file is not required for a successful backup. To create that file, contact your Netbackup admin.