Log in
::
Register
::
Not logged in
Home
Tags
Articles
Editorials
Stairways
Forums
Scripts
Videos
Blogs
QotD
Books
Ask SSC
SQL Jobs
Training
Authors
About us
Contact us
Newsletters
Write for us
Recent Posts
Recent Posts
Popular Topics
Popular Topics
Home
Search
Members
Calendar
Who's On
Home
»
SQL Server 2008
»
SQL Server 2008 - General
»
transaction log backup - point in time...
transaction log backup - point in time recovery
Rate Topic
Display Mode
Topic Options
Author
Message
chewychewy
chewychewy
Posted Tuesday, January 15, 2013 8:56 PM
Valued Member
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:15 AM
Points: 72,
Visits: 286
Hi Guys,
Just curious will point in time recovery work in this case?
(1) Monday 2am - Transaction log backup via maintenance plan to disk
(2) Monday 7pm - full backup via maintenance plan to disk
(3) Monday 10pm - full backup to tape via 3rd party backup software, eg: backup exec, arc serve
(4) Tuesday 2am - Transaction log backup via maintenance plan to disk
Tuesday 3am - Users complain and want us to perform point in time recovery till tuesday 2am due to some data error.
If this is the case, can i use the full backup (2) with the transaction log taken at (4) to perform point in time recovery? I can't get (3) as the tape has some problem.
thanks
Post #1407562
Lynn Pettis
Lynn Pettis
Posted Tuesday, January 15, 2013 9:00 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 12:11 AM
Points: 21,602,
Visits: 27,431
chewychewy (1/15/2013)
Hi Guys,
Just curious will point in time recovery work in this case?
(1) Monday 2am - Transaction log backup via maintenance plan to disk
(2) Monday 7pm - full backup via maintenance plan to disk
(3) Monday 10pm - full backup to tape via 3rd party backup software, eg: backup exec, arc serve
(4) Tuesday 2am - Transaction log backup via maintenance plan to disk
Tuesday 3am - Users complain and want us to perform point in time recovery till tuesday 2am due to some data error.
If this is the case, can i use the full backup (2) with the transaction log taken at (4) to perform point in time recovery? I can't get (3) as the tape has some problem.
thanks
Yes, you should. Full backups should not break the log chain.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1407565
chewychewy
chewychewy
Posted Tuesday, January 15, 2013 9:11 PM
Valued Member
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:15 AM
Points: 72,
Visits: 286
thanks Lynn.
Have u used backup exec or arc serve before?
1. Daily full backup via backup exec to tape at 9pm.
This tape will be send offsite for safe keeping.
2. Daily full db backup to filesystem via SQL Maintenance Plan at 9pm
3. 5 hourly interval db transaction logs backup via backup exec to tape.
This tape will be onsite
I heard with this, I can't do point in time recovery using option 2 and 3.
Seems like backup exec doesn't have an option to restore the transaction logs to file system, for us to
using it with option 2.
Any idea?
thanks
Post #1407573
Lynn Pettis
Lynn Pettis
Posted Tuesday, January 15, 2013 9:14 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 12:11 AM
Points: 21,602,
Visits: 27,431
chewychewy (1/15/2013)
thanks Lynn.
Have u used backup exec or arc serve before?
1. Daily full backup via backup exec to tape at 9pm.
This tape will be send offsite for safe keeping.
2. Daily full db backup to filesystem via SQL Maintenance Plan at 9pm
3. 5 hourly interval db transaction logs backup via backup exec to tape.
This tape will be onsite
I heard with this, I can't do point in time recovery using option 2 and 3.
Seems like backup exec doesn't have an option to restore the transaction logs to file system, for us to
using it with option 2.
Any idea?
thanks
You will have to use the native RESTORE WITH NORECOVERY to restore the full backup and backup exec's RESTORE LOG (with norecovery if more than one log file) to restore the log files directly to the database. Backups directly to tape are not like a backup to disk and then a backup of that file to tape.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1407574
Lynn Pettis
Lynn Pettis
Posted Tuesday, January 15, 2013 9:16 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 12:11 AM
Points: 21,602,
Visits: 27,431
Note, it the above does not work, you may want to revisit your backup scheme and use either native backups to disk then backup those files to tape, or use backup exec for all your backup needs.
Personally, I prefer the first over the latter.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1407575
chewychewy
chewychewy
Posted Tuesday, January 15, 2013 9:16 PM
Valued Member
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:15 AM
Points: 72,
Visits: 286
thanks for ur kind advise.
Post #1407576
chewychewy
chewychewy
Posted Tuesday, January 15, 2013 9:31 PM
Valued Member
Group: General Forum Members
Last Login: Wednesday, May 15, 2013 2:15 AM
Points: 72,
Visits: 286
Hi Lynn,
What do u think of this article?
http://www.symantec.com/business/support/index?page=content&id=TECH58674
==
This issue occurs because the Log Sequence Number (LSN) for SQL is reset by the other backup application. So subsequent differential or log backups performed by BEWS are relative to the other backup application instead of the original BEWS Full backup. The subsequent differential or log backups are thus rendered unrecoverable by BEWS, because it is unable to use the backup sets created by the other backup application.
==
thanks
Post #1407578
Lynn Pettis
Lynn Pettis
Posted Tuesday, January 15, 2013 9:54 PM
SSC-Insane
Group: General Forum Members
Last Login: Today @ 12:11 AM
Points: 21,602,
Visits: 27,431
chewychewy (1/15/2013)
Hi Lynn,
What do u think of this article?
http://www.symantec.com/business/support/index?page=content&id=TECH58674
==
This issue occurs because the Log Sequence Number (LSN) for SQL is reset by the other backup application. So subsequent differential or log backups performed by BEWS are relative to the other backup application instead of the original BEWS Full backup. The subsequent differential or log backups are thus rendered unrecoverable by BEWS, because it is unable to use the backup sets created by the other backup application.
==
thanks
Looks like Backup Exec doesn't play nice. If this is true, you need to decide how you want your backups done, either use the native backup process (Full/Diff/T-Log) or use Backup Exec for them all.
Personally, I have always insisted on running the native backups (even used it with HyperBac) and then I would have the backup files copied to tape. I also preferred to have all backups done to local disk (or SAN disk allocated to the server) then move the files to other network resources for storage and archival to tape.
Lynn Pettis
For better assistance in answering your questions, click here
For tips to get better help with Performance Problems, click here
For Running Totals and its variations, click here
or
when working with partitioned tables
For more about Tally Tables, click here
For more about Cross Tabs and Pivots, click here
and
here
Managing Transaction Logs
SQL Musings from the Desert
Fountain Valley SQL
(My Mirror Blog)
Post #1407582
« Prev Topic
|
Next Topic »
Permissions
You
cannot
post new topics.
You
cannot
post topic replies.
You
cannot
post new polls.
You
cannot
post replies to polls.
You
cannot
edit your own topics.
You
cannot
delete your own topics.
You
cannot
edit other topics.
You
cannot
delete other topics.
You
cannot
edit your own posts.
You
cannot
edit other posts.
You
cannot
delete your own posts.
You
cannot
delete other posts.
You
cannot
post events.
You
cannot
edit your own events.
You
cannot
edit other events.
You
cannot
delete your own events.
You
cannot
delete other events.
You
cannot
send private messages.
You
cannot
send emails.
You
may
read topics.
You
cannot
rate topics.
You
cannot
vote within polls.
You
cannot
upload attachments.
You
may
download attachments.
You
cannot
post HTML code.
You
cannot
edit HTML code.
You
cannot
post IFCode.
You
cannot
post JavaScript.
You
cannot
post EmotIcons.
You
cannot
post or upload images.
Copyright © 2002-2013 Simple Talk Publishing. All Rights Reserved.
Privacy Policy.
Terms of Use.
Report Abuse.