Multi-Site Upgrade; Clarification Request

[tbronzel]

When upgrading a multi-site using "in-place upgrade", which of these is the correct process;

•  Option A - Install Vault Server at all sites and then open ADMS console at Main site to perform migration (therefore, DB migration does not occur until all sites are running the same Vault server build)
•  Option B - Install Vault Server at main site, open ADMS Console to perform migration and then upgrade vault server at remaining sites

My suspicion is Option A is the correct one given that readme's for SP's and hotfixes indicate you should not open ADMS Console to migrate until all sites are at the same product/patch.  Please confirm.

Thanks!

Tyler

[paul.gunn]

Hi Tyler,

You are right - option A would be the recommended approach.

Paul

[tbronzel]

Paul,

 Is Option A also preferred when the upgrade is a "Connected Workgroup" in which both SQL and Filestore are replicated?

  The confusion for me is that the documentation seems, correction IS, contradictory; according to the upgrade PDF, specifically page 15 (http://wikihelp.autodesk.com/Vault/enu/Help/Help/0305-Vault_In305/0364-Upgrade_364) the process would be to COMPLETELY upgrade the Publisher (including opening ADMS to migrate) and only then move onto the subscriber but again, if I look to the service pack readme's they emphasize the point that you should never migrate unless all ADMS's have been updated!   Which one is it?

  I still lean towards Option A because it just "seems" right that you wouldn't want to Open ADMS to migrate until all servers are at the same level but would appreciate confirmation.

  My plan then would be;

1. Verify Publisher and Subscriber are online and no replication pending
2. Publisher; Uninstall ADMS
3. Publisher: Upgrade SQL (to comply with system requirements)
4. Publisher: install New ADMS
5. Publisher: install service packs and hotfixes
6. Subscriber: repeat steps 2 through 6
7. Now that Publisher and Subscriber are running exact same SQL, ADMS and Service packs and hotfixes, open ADMS Console at the Publisher to complete the migration.

Thank-you!

[paul.gunn]

Hi,

My suspicion is that the upgrade doc was speaking more to cases where there might be intermediary migrations (e.g. 2010 -> 2012 -> 2014). In that case it is mentioned in the doc that only the publisher would need 2012 installed.

The primay consideration in connected workgroups (which you reference) is making sure the replication environment is sound before upgrading. ie. all SQL servers are online and accessible, replication is in a steady state.

In general I see no problems with your plan. Only suggestions would be to always take a backup of the system before upgrading. And (if you have a test machine available) do a restore of a recent backup into the new ADMS version just to ensure ahead of time there will be no migration issues.

Paul