04-01-2014 05:58 PM
Hi,
I've got quite a few SQL instances with many databases. Some are set to SIMPLE recovery mode. This means I cannot run a transaction log backup without an error being raised in NetBackup logs.
This thread indicates you can use the NB_SQL_DATABASE_EXCLUDE environment variable to exclude databases.
https://www-secure.symantec.com/connect/forums/nbsqldatabaseexclude-not-work
OP is now excluding master and msdb from ALL backups using the $ALL token. At least that's how I read the documentation. Probably not a good thing, even though symantec seems to keep restore history in it's own catalog.
What's the standard way to handle this very common situation in a large environment?
Thanks,
Sam
07-18-2014 08:43 AM
You are at risk for data loss. Consider using the full recovery model.
From Microsoft:
"Important
The simple recovery model is inappropriate for production systems for which loss of recent changes is unacceptable. In these cases, we recommend that you use the full recovery model. For more information, see Backup Under the Full Recovery Model."
http://technet.microsoft.com/en-us/library/ms191164%28v=sql.105%29.aspx
07-18-2014 01:31 PM
Not all DBs need to use full recovery. What we've done is include only specific DBs in the transaction log backup Policy, instead of using $ALL and NB_SQL_DATABASE_EXCLUDE environment variable.