What is the correct procedure to migrate Vault Pro 2011 x86 to Vault Pro 2012 x64 in a fully replicated environment?
From what I recall, you have to do a backup & restore, there is no way around it!
However, how is this done on a fully replicated environment?
Thanks, Dave
Solved! Go to Solution.
Solved by paul.gunn. Go to Solution.
Hi Dave,
You are right that a backup should always be done first off - this is always a good safety measure. However it is not necessary to perform a restore to do the upgrade unless you are planning on changing machines or something as part of your upgrade process. ADMS will perform a migration of the replicated environment when you first run ADMS console on the publisher after upgrade.
A few things to keep in mind:
- Replicated migration requires that all subscribers be running and accessible. This is to ensure all data has been replicated before migrating and to prevent data changes on the subscribers during migration
- 2012 does require SQL 2008 or higher, so if you are running SQL 2005 you should update SQL prior to upgrading ADMS
Hope this is helpful,
Paul
Thanks Paul, that does help. I also remember now that the problem we had before was because we were migrating fron SQL 2005 x86 to SQL 2008 x64 - and that required a backup & restore!
In this case, would we best migrate the publisher first followed by the subscribers?
At what point do the vaults actually migrate?
Dave
Hi Dave,
The vaults are migrated when you first run ADMS console on a publisher site. So what you could do is upgrade all the ADMS servers [without running ADMS console] and then run ADMS console on a publisher site to do the migration.
After publisher migration is done, it will take a little while for the new snapshot to be created and migration changes replicated to the subscribers. You can watch the replication status of the subscribers via 'replication status' on the publisher's adms console.
Paul