February 15, 2013 at 9:49 am
I am going to implement log shipping between 2000 (primary ) and 2008 R2 (secondary).
I found there are regular backups are running in primary server .....I told them to stop regular backups when logshipping configured (beacuse when regaular backups are running on primary server secondary server will catchup proper logfiles ) but my customer asking bellow set off Questions to answers.
1. Why they want to exclude the DB’s from the regular backups?
2. How long will it take to complete the logshipping?
3. When will this DB’s be included in the regular backups and when the backup’s for these database will be available.?
I have a answers for Question 1 and 2....Can someone answer for Question 3....
Is it possible to take backups in secondary server which is stanby mode
February 15, 2013 at 9:56 am
Simha24 (2/15/2013)
I am going to implement log shipping between 2000 (primary ) and 2008 R2 (secondary).
Why???
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 15, 2013 at 9:57 am
I didnt get you....They wanted to have backups of logshipping database aswell.
February 15, 2013 at 10:04 am
why do you want to log ship between 2000 and 2008, do you understand the ramifications of doing this?
-----------------------------------------------------------------------------------------------------------
"Ya can't make an omelette without breaking just a few eggs" 😉
February 15, 2013 at 7:37 pm
no
February 17, 2013 at 8:20 pm
You can restore a backup to a more recent version of SQL but you CANNOT go the other way. This means that any backup done on your secondary (SQL 2008) server CANNOT be restored to the SQL 2000 server. This is by design - there are significant differences between the versions of SQL Server and the restore process makes those changes on the fly as the restore is executing.
Why are you wanting to implement log shipping between SQL 2000 and SQL 2008 ?
February 18, 2013 at 2:32 am
While this will work, it is not a recommended configuration.
Two reasons.
- You can only restore WITH NORECOVERY, hence you can't use the logshipping secondary for reporting
- If you ever fail over to the secondary (the primary fails), it's a one-way failover and you will NOT be able to fail back to the primary without upgrading that to SQL 2008 R2 first. Hence any DR usage is essentially a permanent move of the production DB.
Since log shipping is usually used for reporting or failover in the case of a disaster, a up-version log shipping is a rather poor idea since it works for neither.
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
Viewing 7 posts - 1 through 6 (of 6 total)
You must be logged in to reply to this topic. Login to reply