Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Log shipping between SQL Server 2000 and SQL 2008R2 Expand / Collapse
Author
Message
Posted Friday, February 15, 2013 9:49 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, 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




Post #1420638
Posted Friday, February 15, 2013 9:56 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:15 AM
Points: 6,182, Visits: 13,329
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"
Post #1420643
Posted Friday, February 15, 2013 9:57 AM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, Visits: 319
I didnt get you....They wanted to have backups of logshipping database aswell.

Post #1420644
Posted Friday, February 15, 2013 10:04 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Today @ 10:15 AM
Points: 6,182, Visits: 13,329
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"
Post #1420652
Posted Friday, February 15, 2013 7:37 PM
SSC Journeyman

SSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC JourneymanSSC Journeyman

Group: General Forum Members
Last Login: Tuesday, May 14, 2013 6:45 AM
Points: 94, Visits: 319
no
Post #1420844
Posted Sunday, February 17, 2013 8:20 PM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Today @ 9:48 PM
Points: 2,923, Visits: 2,526
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 ?



Post #1421024
Posted Monday, February 18, 2013 2:32 AM


SSC-Forever

SSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-ForeverSSC-Forever

Group: General Forum Members
Last Login: Today @ 4:58 PM
Points: 42,466, Visits: 35,532
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 2008, MVP
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

Post #1421106
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse