October 18, 2010 at 2:08 am
Hi,
I have configured Log-Shipping. All databases are now in standyby/read only mode in the secondary server.
I would like to know about the backup procedure. That is, now my only backup is on the secondary server(Log Shipping). My question is..
1) If I take Weekly Full, Daily Differential, Hourly T-Log Backups (onto the primary server itself), Will it affect the Log Shipping in anyway ?
2) Is the above backup plan good?
Thanks in advance.
October 18, 2010 at 2:40 am
ovonelmonk (10/18/2010)
I would like to know about the backup procedure. That is, now my only backup is on the secondary server(Log Shipping). My question is..1) If I take Weekly Full, Daily Differential, Hourly T-Log Backups (onto the primary server itself), Will it affect the Log Shipping in anyway ?
The weekly full and daily diff will have no effect.
When you are log shipping, the ONLY log backups must be the ones taken by the log shipping job. If you take manual ones, the log shipping will break and the manual log backups will also be useless as both will be partial log chains.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
October 18, 2010 at 5:05 am
thanks 🙂
Another related question..
so i will take full and diff on the primary server, and incase I want point in time restore, Can I use the T-Logs that has been shipped to the secondary server?
October 18, 2010 at 8:26 am
@ ovonelmonk...
You just need to take full backups daily night....
The transaction logs are already there from log shipping, on the primary server ..(the LSbackup jobs on primary server)..
I dont think you need more.
Regards,
Sushant
Regards
Sushant Kumar
MCTS,MCP
October 20, 2010 at 8:57 am
The transaction log backups made for log shipping are identical to the ones that would be produced from a transaction log maintenance plan and can be used in exactly the same way. Think of logshipping as a transaction log backup maintenance plan with two extra steps (copy and restore).
Since you've already performed the log backup, you cannot manually produce the same one. Any log backups performed now form part of the logshipped backup chain and need to be "shipped".
Full and diff backups should still be performed in the normal manner however you now have a warm standby database server which is being logshipped so the criticality of these backups is less so. You still couldnt rely on the logshipped server to act as a production box in the event of a failure though. You need some sort of scheduled process to copy jobs, logins, master db procs etc...
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply