01-16-2014 07:57 AM
Hi all,
We have recently started testing the NBU SQL DB agent with some very encouraging results so far. However, I still have a couple of questions that I was hoping some of you might be able to answer as I haven't been able to find a definitive answer elsewhere:
Solved! Go to Solution.
01-16-2014 08:40 AM
first one is easy: see the Symantec NetBackup™ for Microsoft SQL Server Administrator's Guide for details
The database move redirects the restore of a SQL Server database to a different
location. The new location can be a different instance on the same host, a different
host, or a different file path. The move operation also lets you restore the database
under a different name than the original one.
http://www.symantec.com/business/support/index?page=content&id=DOC5173
second one is better asked on Microsoft forum
01-16-2014 09:02 AM
It's better to avoid a full+log backups situation, bad things can happen :)
https://serverfault.com/questions/13099/sql-transaction-log-backups-conflicting-with-full-backups
01-17-2014 09:19 AM
1. Perfectly supported. Steps are described in NetBackup for Microsoft SQL Server Administrator's Guide http://www.symantec.com/docs/DOC5173
2. Specify both scripts in the same policy. First script (Full backup) will complete before 2nd (Transaction log) script starts.
See https://www-secure.symantec.com/connect/forums/it-supported-run-sql-backup-script-follow-transaction...
01-16-2014 08:40 AM
first one is easy: see the Symantec NetBackup™ for Microsoft SQL Server Administrator's Guide for details
The database move redirects the restore of a SQL Server database to a different
location. The new location can be a different instance on the same host, a different
host, or a different file path. The move operation also lets you restore the database
under a different name than the original one.
http://www.symantec.com/business/support/index?page=content&id=DOC5173
second one is better asked on Microsoft forum
01-16-2014 09:02 AM
It's better to avoid a full+log backups situation, bad things can happen :)
https://serverfault.com/questions/13099/sql-transaction-log-backups-conflicting-with-full-backups
01-17-2014 09:19 AM
1. Perfectly supported. Steps are described in NetBackup for Microsoft SQL Server Administrator's Guide http://www.symantec.com/docs/DOC5173
2. Specify both scripts in the same policy. First script (Full backup) will complete before 2nd (Transaction log) script starts.
See https://www-secure.symantec.com/connect/forums/it-supported-run-sql-backup-script-follow-transaction...
01-20-2014 04:09 AM
Thanks for the info, much appreciated.
Marianne, your suggestion of having both scripts in one policy would be ideal, but would that mean I couldn't do nightly full backups and hourly transaction logs due to the schedule configuration?
01-20-2014 05:24 AM
You can have 2 policies - One for nightly backups as per my suggestion above with night-time backup window.
One for daily log backups that only includes log backup script with day-time backup window.
Or else only database backup script in night-time window, and another log backup policy that will only have open window during day time. You should carefully monitor database backup to know more or less when database backups end, and then only open log backup window when you know that database backups are done.
Most of our customers have day-time schedules for log backups with a Frequency of 1 hour.
01-24-2014 02:37 AM
Thanks for the help!