Integrated BIM tools, including Revit, AutoCAD, and Civil 3D
Professional CAD/CAM tools built on Inventor and AutoCAD
Any referenced datasets can be downloaded from "Module downloads" in the module overview.
Transcript
00:00
[MUSIC PLAYING]
00:05
Please note, Autodesk recommends that when you are upgrading or migrating a complex environment in Vault,
00:10
that you work with a Value-Added Reseller or your Autodesk Account Team.
00:15
When upgrading a multi-site environment and an in-place server, as mentioned earlier,
00:22
Autodesk does recommend that you test your upgrade prior to go-live and in a multi-site environment.
00:27
If you can, it's best to have both a publisher and a subscriber.
00:31
If you already have a test server,
00:32
you can do a backup from production and restore it to the test server and then you can perform the process on the test server.
00:39
To create a test server, you're going to build a server as close to the same as your production,
00:45
with the same version and patch level as your existing Vault server.
00:48
You're going to want a backup from production and restore to that new test server.
00:52
And again at that point, you're ready to perform and document the steps that are going to be required on go-live day.
00:58
Preparation for go-live for SQL and check your SQL in your Windows version,
01:03
make sure you document your current version in case you have to roll back.
01:07
So you want to know both the Vault version and the patch level.
01:10
Ensure that the server that you are using does meet the minimum hardware and software requirements.
01:16
In case you need to upgrade either SQL server or Windows, you'll need to the impersonation account and the SA account.
01:24
And if your organization doesn't allow access to an SA account,
01:28
you will then need a SQL account that has been set up as a sysadmin and have the password for that.
01:33
It can be disabled after the install.
01:36
It is only needed during install and updates.
01:40
Make sure you have all the required software and patches,
01:43
that you know the serial number, product key, network license,
01:46
server model, and the name if roll back is required.
01:50
In case you need to reinstall the older version for any reason,
01:53
make sure that you have documented the exact version you're moving from in order to be able to restore your backup.
01:59
Make sure you've taken the backup once the users are logged off at the very beginning of the upgrade,
02:04
and then reinstall Vault and restore the backup.
02:08
The actual steps -- so choose your upgrade window.
02:11
If you're working with an Autodesk representative, let them know your plan to upgrade Window.
02:16
Have all your users log out of the system and do an IISRESET from the command line of the ADMS console.
02:22
And you want to validate that the replication is synced.
02:26
You can do this by looking on the SQL server and looking at the replication monitor or the synchronization monitor on the subscriber.
02:35
And you should see a message that says "It's been polling for 60 seconds."
02:39
If that's happened and your users are not in the system,
02:42
you know that your subscribers and publishers are in sync.
02:45
At that point, you want to backup the current Vaults, the publisher, in case you need to do a roll back.
02:51
And then you're going to run the server installation on the current server, apply the Hotfixes.
02:57
And then you're actually going to want to run the installation on both the current server and all your subscribers.
03:03
Apply the Hotfixes and then once the upgrade is complete, you will start your ADMS console.
03:10
You should be asked if you want to migrate your Vaults. Select "Yes."
03:13
And if this step doesn't start automatically, you can do a manual B2B migration.
03:18
Instructions for that are in the resources PDF.
03:21
Once you've migrated your database, the publisher should begin creating a snapshot that will be used by the subscribers.
03:28
It's important to note that the publisher will create a new snapshot to send to the subscribers,
03:36
for both major upgrades and minor updates.
03:40
Once everything is complete, and you're ready to install your client,
03:43
but since you are only moving within two versions, you can use the existing clients until you have them updated.
03:51
And then make sure that you backup your Vault in the new working state.
03:55
For the subscribers, the publisher has to be done first.
03:58
Once the publisher is finished at the complete migration level, you are going to go to your subscribers.
04:05
Your subscribers should have already been installed.
04:08
They do need to be online during the upgrade,
04:10
but you can stop the SQL server jobs that perform the replication until you're done.
04:15
So make sure all your users are out of the system on the subscriber, and as mentioned in the previous slide,
04:21
you're going to want to upgrade all of the servers at the same time.
04:24
So you will have run this server installation on the subscribers and applied the Hotfixes.
04:29
Once the publisher is all set, then and only then can you start your ADMS console on the subscriber.
04:37
And at that point, the subscriber will begin consuming the snapshot that was created by the publisher.
04:44
You should wait for the snapshot to be consumed before starting the ADMS console.
04:50
Enable your Vaults and then repeat for each subscriber.
04:56
When doing a multi-site upgrade, it is important to note the publisher and the subscriber must be at the same version and patch level.
05:04
Any time you do an upgrade or even an update, as I mentioned on the publisher, a new snapshot is created and sent to the subscribers.
05:11
After the database migration is complete, on the publisher work group, a new snapshot is generated.
05:16
And once the new snapshot generation is complete, the subscribers will begin to consume it.
05:21
This is why you want to make sure that you have installed the Vault on all the servers.
05:27
Assuming or if you do have a slow connection, it may be possible to use an alternate snapshot method.
05:33
This is documented in the resources PDF on how to do this.
05:37
It is a method by which you send the snapshot manually or on a disk or you copy it separately,
05:43
and then you apply it to the subscriber.
05:48
And do not proceed until the update has been successfully applied on all ADMS servers and work groups.
05:54
Ensure that all work groups are online and accessible,
05:57
make sure that they're synced and stay polling for 60 seconds for each replicated Vault in library.
06:03
And then once the replication status is displaying is "Waiting 60 seconds,"
06:07
it's safe to open your ADMS console on the subscriber and your database replication is scheduled by default every 60 seconds.
06:15
So for AVFS, it's going to continue as configured, as this does not include a SQL server, it's just file store application.
Video transcript
00:00
[MUSIC PLAYING]
00:05
Please note, Autodesk recommends that when you are upgrading or migrating a complex environment in Vault,
00:10
that you work with a Value-Added Reseller or your Autodesk Account Team.
00:15
When upgrading a multi-site environment and an in-place server, as mentioned earlier,
00:22
Autodesk does recommend that you test your upgrade prior to go-live and in a multi-site environment.
00:27
If you can, it's best to have both a publisher and a subscriber.
00:31
If you already have a test server,
00:32
you can do a backup from production and restore it to the test server and then you can perform the process on the test server.
00:39
To create a test server, you're going to build a server as close to the same as your production,
00:45
with the same version and patch level as your existing Vault server.
00:48
You're going to want a backup from production and restore to that new test server.
00:52
And again at that point, you're ready to perform and document the steps that are going to be required on go-live day.
00:58
Preparation for go-live for SQL and check your SQL in your Windows version,
01:03
make sure you document your current version in case you have to roll back.
01:07
So you want to know both the Vault version and the patch level.
01:10
Ensure that the server that you are using does meet the minimum hardware and software requirements.
01:16
In case you need to upgrade either SQL server or Windows, you'll need to the impersonation account and the SA account.
01:24
And if your organization doesn't allow access to an SA account,
01:28
you will then need a SQL account that has been set up as a sysadmin and have the password for that.
01:33
It can be disabled after the install.
01:36
It is only needed during install and updates.
01:40
Make sure you have all the required software and patches,
01:43
that you know the serial number, product key, network license,
01:46
server model, and the name if roll back is required.
01:50
In case you need to reinstall the older version for any reason,
01:53
make sure that you have documented the exact version you're moving from in order to be able to restore your backup.
01:59
Make sure you've taken the backup once the users are logged off at the very beginning of the upgrade,
02:04
and then reinstall Vault and restore the backup.
02:08
The actual steps -- so choose your upgrade window.
02:11
If you're working with an Autodesk representative, let them know your plan to upgrade Window.
02:16
Have all your users log out of the system and do an IISRESET from the command line of the ADMS console.
02:22
And you want to validate that the replication is synced.
02:26
You can do this by looking on the SQL server and looking at the replication monitor or the synchronization monitor on the subscriber.
02:35
And you should see a message that says "It's been polling for 60 seconds."
02:39
If that's happened and your users are not in the system,
02:42
you know that your subscribers and publishers are in sync.
02:45
At that point, you want to backup the current Vaults, the publisher, in case you need to do a roll back.
02:51
And then you're going to run the server installation on the current server, apply the Hotfixes.
02:57
And then you're actually going to want to run the installation on both the current server and all your subscribers.
03:03
Apply the Hotfixes and then once the upgrade is complete, you will start your ADMS console.
03:10
You should be asked if you want to migrate your Vaults. Select "Yes."
03:13
And if this step doesn't start automatically, you can do a manual B2B migration.
03:18
Instructions for that are in the resources PDF.
03:21
Once you've migrated your database, the publisher should begin creating a snapshot that will be used by the subscribers.
03:28
It's important to note that the publisher will create a new snapshot to send to the subscribers,
03:36
for both major upgrades and minor updates.
03:40
Once everything is complete, and you're ready to install your client,
03:43
but since you are only moving within two versions, you can use the existing clients until you have them updated.
03:51
And then make sure that you backup your Vault in the new working state.
03:55
For the subscribers, the publisher has to be done first.
03:58
Once the publisher is finished at the complete migration level, you are going to go to your subscribers.
04:05
Your subscribers should have already been installed.
04:08
They do need to be online during the upgrade,
04:10
but you can stop the SQL server jobs that perform the replication until you're done.
04:15
So make sure all your users are out of the system on the subscriber, and as mentioned in the previous slide,
04:21
you're going to want to upgrade all of the servers at the same time.
04:24
So you will have run this server installation on the subscribers and applied the Hotfixes.
04:29
Once the publisher is all set, then and only then can you start your ADMS console on the subscriber.
04:37
And at that point, the subscriber will begin consuming the snapshot that was created by the publisher.
04:44
You should wait for the snapshot to be consumed before starting the ADMS console.
04:50
Enable your Vaults and then repeat for each subscriber.
04:56
When doing a multi-site upgrade, it is important to note the publisher and the subscriber must be at the same version and patch level.
05:04
Any time you do an upgrade or even an update, as I mentioned on the publisher, a new snapshot is created and sent to the subscribers.
05:11
After the database migration is complete, on the publisher work group, a new snapshot is generated.
05:16
And once the new snapshot generation is complete, the subscribers will begin to consume it.
05:21
This is why you want to make sure that you have installed the Vault on all the servers.
05:27
Assuming or if you do have a slow connection, it may be possible to use an alternate snapshot method.
05:33
This is documented in the resources PDF on how to do this.
05:37
It is a method by which you send the snapshot manually or on a disk or you copy it separately,
05:43
and then you apply it to the subscriber.
05:48
And do not proceed until the update has been successfully applied on all ADMS servers and work groups.
05:54
Ensure that all work groups are online and accessible,
05:57
make sure that they're synced and stay polling for 60 seconds for each replicated Vault in library.
06:03
And then once the replication status is displaying is "Waiting 60 seconds,"
06:07
it's safe to open your ADMS console on the subscriber and your database replication is scheduled by default every 60 seconds.
06:15
So for AVFS, it's going to continue as configured, as this does not include a SQL server, it's just file store application.
How to buy
Privacy | Do not sell or share my personal information | Cookie preferences | Report noncompliance | Terms of use | Legal | © 2025 Autodesk Inc. All rights reserved
Sign in to start learning
Sign in for unlimited free access to all learning content.Save your progress
Take assessments
Receive personalized recommendations
May we collect and use your data?
Learn more about the Third Party Services we use and our Privacy Statement. May we collect and use your data to tailor your experience?
Explore the benefits of a customized experience by managing your privacy settings for this site or visit our Privacy Statement to learn more about your options.