SQL Clone
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 


Log shipping between SQL Server 2000 and SQL 2008R2


Log shipping between SQL Server 2000 and SQL 2008R2

Author
Message
Simha24
Simha24
SSC-Addicted
SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)

Group: General Forum Members
Points: 404 Visits: 319
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
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54516 Visits: 17691
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" ;-)
Simha24
Simha24
SSC-Addicted
SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)

Group: General Forum Members
Points: 404 Visits: 319
I didnt get you....They wanted to have backups of logshipping database aswell.
Perry Whittle
Perry Whittle
SSC Guru
SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)SSC Guru (54K reputation)

Group: General Forum Members
Points: 54516 Visits: 17691
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" ;-)
Simha24
Simha24
SSC-Addicted
SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)SSC-Addicted (404 reputation)

Group: General Forum Members
Points: 404 Visits: 319
no
happycat59
happycat59
SSCrazy Eights
SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)SSCrazy Eights (8.7K reputation)

Group: General Forum Members
Points: 8725 Visits: 3281
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 ?



GilaMonster
GilaMonster
SSC Guru
SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)SSC Guru (226K reputation)

Group: General Forum Members
Points: 226361 Visits: 46325
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

We walk in the dark places no others will enter
We stand on the bridge and no one may pass


Go


Permissions

You can't post new topics.
You can't post topic replies.
You can't post new polls.
You can't post replies to polls.
You can't edit your own topics.
You can't delete your own topics.
You can't edit other topics.
You can't delete other topics.
You can't edit your own posts.
You can't edit other posts.
You can't delete your own posts.
You can't delete other posts.
You can't post events.
You can't edit your own events.
You can't edit other events.
You can't delete your own events.
You can't delete other events.
You can't send private messages.
You can't send emails.
You can read topics.
You can't vote in polls.
You can't upload attachments.
You can download attachments.
You can't post HTML code.
You can't edit HTML code.
You can't post IFCode.
You can't post JavaScript.
You can post emoticons.
You can't post or upload images.

Select a forum

































































































































































SQLServerCentral


Search