|
Re: [Veritas-bu] Backing up SQL and Transaction logs?
2009-10-14 09:00:05
|
Folks,
Here' s my take on it. You can use DATABASE $ALL but this won't
truncate your log files if you're using 'Full recovery' mode in
SQL.
You can create 2 scripts, and it works but one is obviously dependant on
the other having completed, or do as i do and specify each DATABASE individually
in the script and then each transaction log seperately, see
below:
Works for us and
have proven recovery. One slight cavaet, when your dba creates new databases he
better tell you, otherwise they won't be getting backed
up
| GROUPSIZE 15 |
| OPERATION BACKUP |
| DATABASE "YOURNAME" |
| SQLHOST "sqlhost" |
| NBSERVER "master" |
| MAXTRANSFERSIZE 0 |
| BLOCKSIZE 7 |
| BROWSECLIENT "clientname" |
| ENDOPER
TRUE |
| GROUPSIZE 15 |
| OPERATION BACKUP |
| DATABASE "YOURNAME" |
| SQLHOST "sqlhost" |
| NBSERVER "master" |
| MAXTRANSFERSIZE 0 |
| BLOCKSIZE 7 |
| BROWSECLIENT "clientname" |
| OBJECTTYPE TRXLOG |
|
ENDOPER TRUE
Mike
|
Hello Simon,
Thanks for the reply and yes it does answer my
question.
While reading through the
admin guide I think I've come to the same conclusion.
Can I ask why you run the log backup's 12 hours after
and not sooner? I would think that I would want to grab the logs ASAP after a
"Full" in order to truncate and file away.
Thanks again.
Regards,
John Keating
Information Technology
Tachi-S
Engineering U.S.A. Inc.
| "WEAVER, Simon
(external)" <simon.weaver AT astrium.eads DOT net>
10/14/2009 02:18 AM
|
|
To
| <J.Keating AT tachi-s DOT com>,
<VERITAS-BU AT mailman.eng.auburn DOT edu>
|
|
cc
|
|
|
Subject
| RE: [Veritas-bu] Backing up SQL
and Transaction logs? |
|
John
Maybe I
am doing it wrong, but this is what I do ...
1) Single .bch
file called "SQL_Backup.bch" with the following:
OPERATION BACKUP
DATABASE $ALL
SQLHOST
"<CLIENT>"
NBSERVER "<MASTER_NBU>"
MAXTRANSFERSIZE
0
BLOCKSIZE 7
ENDOPER TRUE
This is created for a policy called
"SQL_FULL_BACKUPS". This allows me to do a FULL Online SQL DB Backup of all
DB's
Now for the Transaction logs, I do the following:
1) Single .bch file called
"SQL_Backup_TXLogs.bch" with the following:
OPERATION BACKUP
DATABASE $ALL
SQLHOST
"<Client>"
NBSERVER "<MASTER_NBU>"
MAXTRANSFERSIZE
0
BLOCKSIZE 7
OBJECTTYPE TRXLOG
ENDOPER TRUE
This is then created for a second policy called
"SQL_TX_LOGS" and runs AFTER the full SQL Backup has run (usually 12 hours
after the SQL Full Backup Window starts).
I have had to
restore SQL from the Full and Logs, and the DBA's have never
complained.
I read through the
SQL Admin guide to get most of this done.
Does this make sence, or answer your questions?
Simon
From:
veritas-bu-bounces AT mailman.eng.auburn DOT edu
[mailto:veritas-bu-bounces AT mailman.eng.auburn DOT edu] On Behalf Of
J.Keating AT tachi-s DOT com
Sent: Tuesday, October 13, 2009 3:11
PM
To: VERITAS-BU AT mailman.eng.auburn DOT edu
Subject:
[Veritas-bu] Backing up SQL and Transaction logs?
Hello All,
I've been backing up several
SQL servers for quite some time now and through re-creating a "disaster
recovery" situation and reading through SAP section of the NetBackup SQL Admin
guide I notice the section for backing up transaction logs.
After going through the SQL
transaction log creation wizard, I verified the changes in that batch file to
my original "Full" SQL batch file that I've been using.
The changes were these 2
lines:
BROWSECLIENT "CLIENT_NAME"
OBJECTTYPE TRXLOG
Am I correct to think that without
these 2 lines in my batch file that a complete restore of the databases for
SAP or otherwise would not happen?
Should I simply add these 2 lines to my original
batch file?
Thanks for your help.
Regards,
John Keating
Information
Technology
Tachi-S Engineering U.S.A. Inc.
This email (including any
attachments) may contain confidential
and/or privileged information
or information otherwise protected
from disclosure. If you are not
the intended recipient, please
notify the sender immediately, do not
copy this message or any
attachments and do not use it for any
purpose or disclose its
content to any person, but delete this
message and any attachments
from your system. Astrium disclaims any
and all liability if this
email transmission was virus corrupted,
altered or falsified.
-o-
Astrium Limited, Registered in England
and Wales No. 2449259
Registered Office:
Gunnels Wood Road,
Stevenage, Hertfordshire, SG1 2AS,
England |
**************************************************************************************
This e-mail (including any attachments) is intended for the above-named person(s). It is confidential and may contain legally privileged information. Any opinions expressed are not necessarily those of the company. If you receive it in error please delete it, inform the sender and do not copy, distribute or take any action in reliance upon it.
We may monitor all incoming and outgoing emails in line with current legislation. We have taken steps to ensure that this email and attachments are free from any virus, but it remains your responsibility to ensure that viruses do not adversely affect you.
Orange Personal Communications Services Limited is an English company (registered no. 2178917) with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ.
Orange Retail Limited is an English company (registered no. 2439104) with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ.
Orange Home UK Limited is an English company (registered no. 3014367) with its address at St James Court, Great Park Road, Almondsbury Park, Bradley Stoke, Bristol BS32 4QJ.
.
**************************************************************************************
*********************************
This message and any attachments (the "message") are confidential and intended solely for the addressees.
Any unauthorised use or dissemination is prohibited.
Messages are susceptible to alteration.
France Telecom Group shall not be liable for the message if altered, changed or falsified.
If you are not the intended addressee of this message, please cancel it immediately and inform the sender.
********************************
_______________________________________________
Veritas-bu maillist - Veritas-bu AT mailman.eng.auburn DOT edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
|
|
|
