Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
AskSQLTeam
Ask SQLTeam Question
0 Posts |
 Posted - 2003-03-20 : 07:23:13
|
| Alex writes "I have two servers - one live and one standby.Every night the backup of the live is transferred to the standby and restored in the state of STANDBY (thus read-only access, and allows extra transactions to be applied).We then have a transaction backup every 20 mins. If the live server goes down at around 11:00am, the transaction log can be copied to the warm standby and then applied up to 10:40am.However my problem is that as there is no backup history on the warm standby server, I have to apply each transaction in order. Since the transaction starts from about 6:00am till 12:40am (then there is an incremental), that could mean doing 15+ restores of the log. In SEM You can normally tick the latest backup you want to restore to, and all the preceding log backups are also ticked, and hence restored. This doesn't happen on the warm standbyI can't just transfer msdb as the warm standby has other uses.Therefore I was thinking I could run something like RESTORE HEADERONLY FROM 'Logback' on the live server, then from the data returned insert into the relevant tables in msdb on the warm standby server - to create the history that can be used by SEM. But I am wary on doing this for obvious reasons. Is this possible, sensible and reasonable? Many thanks" |
|
|
chadmat
The Chadinator
1974 Posts |
Posted - 2003-03-20 : 11:52:29
|
| This is what logshipping is for.-Chad |
 |
|
|
AGP
Starting Member
2 Posts |
Posted - 2003-03-20 : 12:22:45
|
| Thanks.Log shipping - very American term, no wonder I didn't spot it! Would have been better if it was Log Transfer............... |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-20 : 12:37:34
|
| The backup history has nothing to do with being able to apply transaction logs. Backup history is just purely history and nothing else. You are going to buy yourself anything if you transfer the history over because it really isn't used for anything. You will always have to apply each transaction in order, always.Tara |
|
|
|
AGP
Starting Member
2 Posts |
Posted - 2003-03-21 : 07:17:05
|
| TaraI know I have to apply Transaction logs in order. However by using the Backup history in SEM you can select the latest one you require, and all the previous ones are selected and restored in order automatically.Without that history on the warm standby, I have to restore each transaction log in order, manually. But you are saying that transferring the history wouldn't help me anyway. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2003-03-24 : 13:06:58
|
| Why don't you just write a script to do this for you? That's what we do when we need to apply lots of transaction logs. The script would write out all of the RESTORE statements that you would need.Tara |
|
|
|
|
|
|
|
|
Transferring the backup history to another server (without replacing the msdb)