Transcript
00:00
[MUSIC PLAYING]
00:04
Autodesk recommends that when upgrading or migrating a complex environment,
00:09
you work with a Value-Added Reseller or your Autodesk Account Team.
00:13
First, let's take a look at Vault Replication in 2022.
00:16
Vault Replication in 2022 is replacing SQL merge replication technology with transactional replication, SQL technology.
00:25
So the data synchronizes almost instantly.
00:27
As part of this, all your read operations will continue occurring on the subscriber,
00:32
but your write operations, such as your check-ins, will only occur on the publisher.
00:36
File replication remains unchanged.
00:39
So planning to do your upgrade to 2022,
00:45
as mentioned in the beginning, Autodesk recommends you test your upgrade prior to go-live.
00:50
In a multi-site environment, it is best if you have both a subscriber and a publisher.
00:56
If you already have a test server, you could do a backup from production, restore it to the test server.
01:01
You can create a separate test server if you wish to have it after the upgrade,
01:05
installing the same version and restoring the backup.
01:09
Once you have the server set up,
01:10
you will follow the same steps outlined below on your test server and document it for your go-live and production day.
01:18
On go-live day,
01:20
make sure your SQL and Windows version on the current server will support the version of Vault that you are upgrading to.
01:27
Document the current version and patch level of Vault in case you need to roll back.
01:31
Ensure that the server meets the minimum hardware and software requirements.
01:35
You will need to know the impersonation account and the SA account.
01:39
If your organization doesn't use the SA account or doesn't allow use of the SA account,
01:43
you will need a SQL server account that has been set up as a sysadmin and know that password.
01:49
Make sure you have all the required software and patches.
01:53
Know your serial number, product key, network license, server model, and network license server name.
02:00
Have a plan in place for high latency.
02:03
If you have a slow connection between two locations,
02:07
subscriber and publisher, using the alternate snapshot method, which you can find information on in the resources PDF.
02:14
If you do have to roll back,
02:16
you will need to reinstall the server with the version that was originally on there and restore the backup.
02:24
When you're upgrading a multi-site environment to 2022,
02:27
or any multi-site environment for that matter, the publisher has to be done first.
02:32
Choose your upgrade window.
02:33
If you're working with an Autodesk representative, let them know your planned upgrade window.
02:37
Have all users log out of the system and do an IISRESET.
02:41
Make sure that your application is synced.
02:44
You can do this by checking the replication monitor on the SQL server,
02:48
and verify that it says "It's been polling for 60 seconds."
02:51
At that point, you are ready to backup your existing Vault at the publisher.
02:56
You will then upgrade, install Vault on all servers, publishers and subscribers.
03:02
Apply Hotfixes on all servers, publishers, and subscribers.
03:06
And then on the publisher, you will start your ADMS console.
03:09
You're going to disable replication when prompted.
03:13
You're going to then migrate your databases.
03:15
If the step does not start automatically, you may need to do a manual B2B migration.
03:19
And you can find information on that in the resources PDF.
03:23
Verify that the subscriber's version does match, that they have been upgraded.
03:28
And once you've verified that the subscribers are upgraded,
03:32
you're going to need to manually recreate each subscriber. And then when you migrate the subscribers,
03:37
you will allow the snapshot to be consumed.
03:40
You will then open the ADMS console on the subscriber.
03:44
You will enable the Vaults.
03:46
And then you would repeat this for each new subscriber.
03:49
Once you're done, backup the publisher and the final working state.
03:53
If you have slow connection, again,
03:55
consider using the alternate snapshot method if you feel that it is taking too long for the snapshot to be consumed.
04:01
Quick look at some of the steps you're going to see when you go through 2022 multi-site upgrade.
04:06
So currently this is what your migration looks like under a merge replication.
04:10
There's a two-way connection between each subscriber and a publisher, and they upgrade two ways.
04:15
Any action that you do on the subscriber will upgrade the publisher.
04:19
And any action you do on the publisher will upgrade the subscriber.
04:23
And then the publisher will upgrade the other subscribers.
04:26
Now, 2022 - the first step when you run the install is replication, is disabled.
04:32
It's going to turn the publisher into a single site.
04:35
The ADMS console will offer to disable replication.
04:38
It gives you some information and tells you what's happening.
04:40
There's a checkbox where it will document all of your subscribers for you.
04:44
And then you would click "Proceed."
04:47
And then it's going to confirm.
04:49
It's going to give you some warnings,
04:51
and it's going to confirm that you do want to move forward and that you are removing existing replication.
04:56
Once that is done, you can use the information that's documented to re-add the replication.
05:01
And this is what you end up with -- the publisher in the middle talking to all the subscribers.
05:07
And the publisher is the only server that has write operations happening to it.
05:12
For those of you who've been using replication for any length of time,
05:15
I'm sure at some point in time you've had some kind of ownership issues.
05:18
This is a long way toward eliminating anything because the publisher will own everything.
05:24
So replication is manually re-established using transactional replication.
05:29
So, again, using that information that you documented, you're going to recreate each subscriber.
05:34
Things to know when you're doing a multi-site upgrade --
05:37
You will not be able to restore if SQL Server and Vault are not the same or higher version.
05:43
You need to make sure that your users are out of Vault from the point where you are going to backup the production server,
05:48
until the point that you are going live, after the final backup and after test.
05:54
Autodesk does recommend that every Vault upgrade starts with a validated backup.
05:58
Testing does allow you to validate your backup.
06:01
Before migrating any live production environment, restore the latest ADMS console backup to a similar but non-production environment,
06:09
in other words, a test system.
06:11
And a test upgrade gives you the confidence that the backup is valid,
06:14
and identifies any potential pitfalls while having no impact on production.
06:20
If re-establishing replication is taking too long, consider using the alternate snapshot method to speed it up.
06:26
Information on that can be found in the resources PDF.
06:30
And this process will be different than any previous multi-site upgrade.
06:34
And last but not least, the subscribers will not be created automatically.
06:39
Once everything is completed, you will need to create them manually.
00:00
[MUSIC PLAYING]
00:04
Autodesk recommends that when upgrading or migrating a complex environment,
00:09
you work with a Value-Added Reseller or your Autodesk Account Team.
00:13
First, let's take a look at Vault Replication in 2022.
00:16
Vault Replication in 2022 is replacing SQL merge replication technology with transactional replication, SQL technology.
00:25
So the data synchronizes almost instantly.
00:27
As part of this, all your read operations will continue occurring on the subscriber,
00:32
but your write operations, such as your check-ins, will only occur on the publisher.
00:36
File replication remains unchanged.
00:39
So planning to do your upgrade to 2022,
00:45
as mentioned in the beginning, Autodesk recommends you test your upgrade prior to go-live.
00:50
In a multi-site environment, it is best if you have both a subscriber and a publisher.
00:56
If you already have a test server, you could do a backup from production, restore it to the test server.
01:01
You can create a separate test server if you wish to have it after the upgrade,
01:05
installing the same version and restoring the backup.
01:09
Once you have the server set up,
01:10
you will follow the same steps outlined below on your test server and document it for your go-live and production day.
01:18
On go-live day,
01:20
make sure your SQL and Windows version on the current server will support the version of Vault that you are upgrading to.
01:27
Document the current version and patch level of Vault in case you need to roll back.
01:31
Ensure that the server meets the minimum hardware and software requirements.
01:35
You will need to know the impersonation account and the SA account.
01:39
If your organization doesn't use the SA account or doesn't allow use of the SA account,
01:43
you will need a SQL server account that has been set up as a sysadmin and know that password.
01:49
Make sure you have all the required software and patches.
01:53
Know your serial number, product key, network license, server model, and network license server name.
02:00
Have a plan in place for high latency.
02:03
If you have a slow connection between two locations,
02:07
subscriber and publisher, using the alternate snapshot method, which you can find information on in the resources PDF.
02:14
If you do have to roll back,
02:16
you will need to reinstall the server with the version that was originally on there and restore the backup.
02:24
When you're upgrading a multi-site environment to 2022,
02:27
or any multi-site environment for that matter, the publisher has to be done first.
02:32
Choose your upgrade window.
02:33
If you're working with an Autodesk representative, let them know your planned upgrade window.
02:37
Have all users log out of the system and do an IISRESET.
02:41
Make sure that your application is synced.
02:44
You can do this by checking the replication monitor on the SQL server,
02:48
and verify that it says "It's been polling for 60 seconds."
02:51
At that point, you are ready to backup your existing Vault at the publisher.
02:56
You will then upgrade, install Vault on all servers, publishers and subscribers.
03:02
Apply Hotfixes on all servers, publishers, and subscribers.
03:06
And then on the publisher, you will start your ADMS console.
03:09
You're going to disable replication when prompted.
03:13
You're going to then migrate your databases.
03:15
If the step does not start automatically, you may need to do a manual B2B migration.
03:19
And you can find information on that in the resources PDF.
03:23
Verify that the subscriber's version does match, that they have been upgraded.
03:28
And once you've verified that the subscribers are upgraded,
03:32
you're going to need to manually recreate each subscriber. And then when you migrate the subscribers,
03:37
you will allow the snapshot to be consumed.
03:40
You will then open the ADMS console on the subscriber.
03:44
You will enable the Vaults.
03:46
And then you would repeat this for each new subscriber.
03:49
Once you're done, backup the publisher and the final working state.
03:53
If you have slow connection, again,
03:55
consider using the alternate snapshot method if you feel that it is taking too long for the snapshot to be consumed.
04:01
Quick look at some of the steps you're going to see when you go through 2022 multi-site upgrade.
04:06
So currently this is what your migration looks like under a merge replication.
04:10
There's a two-way connection between each subscriber and a publisher, and they upgrade two ways.
04:15
Any action that you do on the subscriber will upgrade the publisher.
04:19
And any action you do on the publisher will upgrade the subscriber.
04:23
And then the publisher will upgrade the other subscribers.
04:26
Now, 2022 - the first step when you run the install is replication, is disabled.
04:32
It's going to turn the publisher into a single site.
04:35
The ADMS console will offer to disable replication.
04:38
It gives you some information and tells you what's happening.
04:40
There's a checkbox where it will document all of your subscribers for you.
04:44
And then you would click "Proceed."
04:47
And then it's going to confirm.
04:49
It's going to give you some warnings,
04:51
and it's going to confirm that you do want to move forward and that you are removing existing replication.
04:56
Once that is done, you can use the information that's documented to re-add the replication.
05:01
And this is what you end up with -- the publisher in the middle talking to all the subscribers.
05:07
And the publisher is the only server that has write operations happening to it.
05:12
For those of you who've been using replication for any length of time,
05:15
I'm sure at some point in time you've had some kind of ownership issues.
05:18
This is a long way toward eliminating anything because the publisher will own everything.
05:24
So replication is manually re-established using transactional replication.
05:29
So, again, using that information that you documented, you're going to recreate each subscriber.
05:34
Things to know when you're doing a multi-site upgrade --
05:37
You will not be able to restore if SQL Server and Vault are not the same or higher version.
05:43
You need to make sure that your users are out of Vault from the point where you are going to backup the production server,
05:48
until the point that you are going live, after the final backup and after test.
05:54
Autodesk does recommend that every Vault upgrade starts with a validated backup.
05:58
Testing does allow you to validate your backup.
06:01
Before migrating any live production environment, restore the latest ADMS console backup to a similar but non-production environment,
06:09
in other words, a test system.
06:11
And a test upgrade gives you the confidence that the backup is valid,
06:14
and identifies any potential pitfalls while having no impact on production.
06:20
If re-establishing replication is taking too long, consider using the alternate snapshot method to speed it up.
06:26
Information on that can be found in the resources PDF.
06:30
And this process will be different than any previous multi-site upgrade.
06:34
And last but not least, the subscribers will not be created automatically.
06:39
Once everything is completed, you will need to create them manually.
