08-29-2013 12:37 AM
Hello everyone!
I have 2 question on configuring MS-SQL Backup
1) I created 2 scripts in client: first for full backup of my databases, second for transaction logs backup for the sames databases. Can I Configure it in one policy? I need to execute full backup once at week, and transaction log once at hour. How do I need to configure policy and schedules? Do I need to create a new policy for transaction logs?
2) My backup executes correctly, when it's initiated by master server during the backup window. But I can't execute manual backup, it fails. How to configure it correctly?
Thanks!
P.S. Master, media, client are 7.5.0.6 running on Win 2008 R2, MS SQL 2008
Solved! Go to Solution.
08-29-2013 01:47 AM
You need at least two policies.
First for the full backup - note that it actually runs using the Default Application backup schedule so this needs a full single window and to have its retention period set to what you want it to be
Second for the transaction logs - again with the Default Application Backup schedule having the retention you need
If you do Monthly and Annual backups you will also need additional policies for those as you can only have one default application backup schedule in a policy and the jobs retentention period is taken from that schedule
Hope this helps
08-29-2013 01:47 AM
You need at least two policies.
First for the full backup - note that it actually runs using the Default Application backup schedule so this needs a full single window and to have its retention period set to what you want it to be
Second for the transaction logs - again with the Default Application Backup schedule having the retention you need
If you do Monthly and Annual backups you will also need additional policies for those as you can only have one default application backup schedule in a policy and the jobs retentention period is taken from that schedule
Hope this helps
08-29-2013 01:59 AM
Ok, I need to back up logs every hour, and default setting is 1 week. I can't configure frequency in default-application backup schedule.
08-29-2013 02:09 AM
The Automatic backup schedule is what will kick off the hourly backup.
The Default Application Backup schedule is what is backing up the actual client-initiated streams and determines the retention period.
Please go through the NBU for SQL manual: http://www.symantec.com/docs/DOC5173
It contains detailed steps as well as explanation of the different schedule types.
08-29-2013 03:23 AM
As Marianne says .. it is "Your" schedule that decides when it runs - the only thing you need to change on the Default one is your retention period
Yours will set to every 1 hour without a problem
To clarify (as as pointed out it is worth going through the manual) ...
When you create a policy it has a Default Application Schedule - this is like a user backup window so leave this as it is apart from setting the retention period
You then create your Automatic schedule - this decides when the job will actually run. When it does run it calls the bch script on the client which then does a "User" backup, one at a time, for each database. When this runs it used the Default application schedule which is why this is where the retention is decided and why it needs a full backup window (as it has when you create the policy)
Hope this clarifies things
08-29-2013 04:40 AM
HI,
1. You may need to create two different policies one for FULL back up with a scheduler of weekly and one for transaction log with the scheduling to run hourly.
2. You mean to say Manual backup from NBU console Or from the NBU database extension GUI?
Regards
Ajin
08-29-2013 05:07 AM
08-29-2013 05:09 AM
During a SQL backup the client talks directly to the Master Server even though it passes its data to the Media Server
Ensure that the SQL client is resolving the Master Server by the correct name and IP address (FQDN and short host name) and vice - versa, use Hosts files in needs be
08-29-2013 05:47 AM
and after few minutes I have succesfully executed job (in attach)
08-29-2013 05:59 AM
That did finish with a Status of 1 so check the logs - if you selected All Databases in your logs bch file then re-create it to exclude the Master database as you cannot do logs for that one - other wise the logs on the client will tell you which database could not have its logs backed up (probably in the wrong mode but the ogs do tell you)
When happy dont forget to close the thread by marking the advice that helped the most using the "Mark as solution" option - this helps other searching for similar details in the future
08-29-2013 07:11 AM
I'm Sorry, what logs in client I need to check?
In my bch file I selected some needed DBs - not all. All selected DBs are in FULL mode, not simple.
08-29-2013 07:28 AM
If a job fails it will get logged on the client under program files\veritas\netbackup\logs\mssql_backup_failures
If it is partly successful it will log under program files\veritas\netbackup\logs\user_ops\mssql\ or similar - you will see the structure it uses
If you want it all stored in one place the create program files\veritas\netbackup\logs\dbclient\ and it will there
08-30-2013 12:10 AM
Mark, log from \dbclient\ is in attach. Errors are same.
In addition I suspect that there is a confusion in FQDN and DNS names in settings.
I tried to indicte FQDN everywhere: in policy -> clients, on BAR on client, on Netbackup MS SQL Client
But in logs sometime a see a DNS name....
THanks!
08-30-2013 01:23 AM
Lots of issues in that log by the looks of it
Have you set the NetBackup Client Service and NetBackup Legacy Network Service on the client to use an account that has sysadmin rights to all databases? - This is needed for the version and O/S of your SQL Server
Try that first, restart the services on the client to register the logon accounts and try the backup again and then send the new logs if it doesn't work
09-01-2013 11:41 PM
I changed accounts for this services, errors are same (in attach).
Thanks
09-02-2013 03:11 AM
Another couple of questions then ...
1. Is that account also a local admin on the SQL Server
2. Are you running this from a policy or from the client
Could you also post your bch files for checking (which i assume you created on the client itself using the NBU SQL GUI?)
09-02-2013 04:24 AM
09-02-2013 05:22 AM
Domain admin is not likely to be enough - it must be an account that has sysadmin rights to all SQL Databases - your SQL Admin needs to provide that or give your Domain Admin account such rights within SQL
I asked about that account having local admin rights as i saw this line in the log file:
<16> readCommFile: ERR - timed out after 900 seconds while reading from C:\Program Files\Veritas\NetBackup\Logs\user_ops\mssql\logs\0902113000057-4012-3856-000-000-prg
However, you have also set a grouping of 5 on the job (was there a reason for that?) so it may be taking longer to get the file list togeter and you may need to increase the client read timeout settings on the Master and Media Servers to get this to work
I would try tesing it with a simple basic bch file first - just one database and no additions specification in it which could hold things up:
OPERATION BACKUP
DATABASE "CitrixXenDesktopDB"
SQLHOST "CDC01-DISQL--01.DC-DEVELOP.TN.CORP"
NBSERVER "CDC01-PINTBAK01.DC-PROD.TN.CORP"
MAXTRANSFERSIZE 6
BLOCKSIZE 7
BROWSECLIENT "CDC01-DISQL--01.DC-DEVELOP.TN.CORP"
NUMBUFS 2
ENDOPER TRUE
09-02-2013 07:00 AM
My domain administrator have sysadmin rights in SQL. Additionally I gave him rights on all my databases.
I configured policy with your script and second for logs. I will try it this night. Tomorrow i'll notify you.
Additionally I forgot to mention that SQL is in MS fileover cluster services. Agent is installed on both nodes. In policy and client settings there is a FQDN of clustered service.
Thanks you for your help!
09-02-2013 10:50 PM
Hi!
Some backups with test script finished successfully (at 8-34), and the seconf (at 9-34) fails with timeout
Logs in attach