June 22, 2010 at 6:21 pm
Hi,
We have A/P cluster setup for SQL Server 2005 with SP3 and Log shipping is configured. Now All the databases in Secondary server are in restore state.
And now we need to peform in-place upgrade to SQL Server 2008. I read the below steps from SQL2008UpgradeTechnicalReferenceGuide.docx document and makes NO sense for me.
Below are the steps copied from SQL2008UpgradeTechnicalReferenceGuide.docx document
1.Disable the copy and restore jobs on the secondary.
2.Disable the alert job on the monitor (if it is used).
3.Upgrade the SQL Server 2005 instance containing the secondary database. As noted earlier, because the database is in a state where it is restoring transaction logs, it will not be upgraded to SQL Server 2008 yet.
4.Manually copy over and restore (WITH NORECOVERY) all transaction log backups generated during the SQL Server 2008 upgrade from the primary to the secondary.
5.On the primary, stop all incoming traffic and verify that there are no connections to ensure that, at this point, the data cannot be changed. To do this, consider using single-user mode.
6.Disable the transaction log backup job on the primary.
7.On the primary database, manually make a final transaction log backup (also known as the tail of the log) using the WITH NORECOVERY option. This will put the SQL Server 2005 database in the RESTORING state. If this instance will not be the primary again, do not use the WITH NORECOVERY clause of the BACKUP LOG command.
8.Copy and restore the tail WITH RECOVERY on the secondary database, which has not yet been upgraded. Once the restore is done and the database is online, it will be considered upgraded to SQL Server 2008.
9.Synchronize any logins and ensure that all jobs and objects residing outside the database are restored via scripts.
10.It is recommended that you run all the necessary health checks, including DBCC CHECKDB, at this point to ensure the well-being of the newly upgraded databases.
11.Configure administration such as backup jobs for the database.
12.Set the database compatibility level of upgraded databases to 100.
13.Delete the old copy and restore jobs on the former secondary database.
14.Upgrade the monitor instance to SQL Server 2008.
15.Delete the alert job from the monitor instance.
16.Upgrade the original primary to SQL Server 2008. Because there is a new primary, to save time during the upgrade, consider dropping the old primary database so that it will not go through the upgrade process.
17.If the old primary is going to become the new secondary, make a new full backup of the new primary database, copy it, and restore it on the old primary server.
18.Configure log shipping from the new primary to the new secondary.
19.Redirect all users and applications to the newly upgraded SQL Server 2008 log shipped primary database. The old secondary is now the new primary database.
Questions:
1.
Step 4 says, upgrade to SQL Server 2008 is performed on Primary. But in
Step 7 says, 7.On the primary database, manually make a final transaction log backup (also known as the tail of the log) using the WITH NORECOVERY option. This will put the SQL Server 2005 database in the RESTORING state
Please clarify me the above 2 steps?
2.
In step 16, it again says to upgrade the Primary to SQL Server 2008
Step 16. Upgrade the original primary to SQL Server 2008. Because there is a new primary, to save time during the upgrade, consider dropping the old primary database so that it will not go through the upgrade process
Please clarify the above?
Here anyway we are bringing the secondary online and reconfiguring the log shipping from scratch (By taking full backup, copy & restore with NORECOVERY & then configure log shipping), then:
1. Why all these steps required?
2. Simply disable the logShipping, delete the databases on Secondary, upgrade the Secondary to SQL Server 2008.
3. Upgrade the Primary to SQL Server 2008, take the full backup, copy to secondary & the restore with Norecovery
4. Configure the log shipping.
In conclusion, I did NOT find any use going for 1) Upgrade log shipping with a role change or 2) Upgrade log shipping without a role change. Because anyway at the ned we are reconfiguring the log shipping doing all these extra steps.
Please provide your inputs
June 22, 2010 at 10:26 pm
I think Your points are absolutely right, the above steps are not clear and proper. Some time it is easier to upgrade the instances and then configure the log shipping from scratch.
This will save time and troubleshooting efforts.:-)
"More Green More Oxygen !! Plant a tree today"
June 23, 2010 at 11:16 am
I'm also looking for the same and want some experts opinion and guidelines for the same.
I just posted the same in the below link.
http://www.sqlservercentral.com/Forums/Topic941489-391-1.aspx
Thanks
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply