Migrating More Than Two Versions Single Site Environment

00:00

[MUSIC PLAYING]

00:04

When I refer to migration, I am talking about going to a new server.

00:08

It is really important to note that Autodesk recommends when upgrading or migrating a complex environment,

00:13

that you do work with a value-added reseller or your Autodesk account team.

00:18

So testing - as mentioned in the beginning,

00:20

Autodesk recommends that you test your upgrade prior to go-live,

00:24

both to test the upgrade itself as well as testing the new features.

00:29

If you already have a test server, you can do a backup from production,

00:33

restore it to the test server, and then upgrade the test server 2 versions at a time to the final version.

00:39

If you need to create a new server or you want to have a separate one, you would create a separate test server.

00:47

And if you wish to have it after the upgrade, you can use the server you are migrating to for test purposes.

00:54

So you would follow the same steps that I'm going to outline below.

00:58

Once your servers are built,

00:59

you are ready to perform and document the same steps that will be required on go-live day.

01:04

So go-live day, you need to check your SQL server and your Windows, and see if the versions are compatible.

01:10

If they are not, then you will need to make sure that you do have a compatible version installed on the new server.

01:18

You need to know both the requirements from the version that you're going to,

01:23

and the final version and the version that you're coming from.

01:28

So again, ensure that the server meets the minimum hardware and software requirements, and check both steps along the middle and the end.

01:36

You'll need the impersonation account and the SA account.

01:39

And if your organization doesn't use the SA account, you will need an account that has been set up as a sysadmin.

01:46

Make sure you have all the software, know the serial number, the product key, the license mode.

01:52

So when you build the new SQL server, you want to make sure that you're using the correct version of SQL and Windows.

01:58

And you can use that chart or the resources PDF to get a link to the chat to find out which ones you need.

02:05

If you are going to have your SQL server separate from your ADMS console on your new servers,

02:13

you will need to have some folders and sharing information.

02:17

You will want to check your production server and see how it is currently configured.

02:22

The resources PDF also includes links to get more information on installing SQL Server for Autodesk Vault,

02:28

and pre-configuring IIS.

02:31

If a rollback is needed in this case, and you need to restore the older version for any reason,

02:37

you want to make sure that you know the exact version you're moving from in order to be able to restore your backup.

02:43

Take a backup once the users are logged off at the very beginning of the upgrade,

02:47

and then restore to the first session upgrade.

02:53

Assuming the new server is compatible with the version of Vault you were installing,

02:58

so if you've got your existing server is running Windows 16,

03:01

and your new server is running SQL 19,

03:05

and the version that the first step in your two-at-a-time will run on the SQL,

03:13

and Windows version on the new server, you would go directly to the new server.

03:18

You would choose your upgrade window.

03:20

If working with an Autodesk representative,

03:22

let them know the planned upgrade so they can be prepared should any questions come in.

03:27

And again, if the new hardware and software will run on the first release that you're going to,

03:32

then you have all users log out of the system.

03:35

You're going to do an IISRESET from the command line on the ADMS console.

03:39

You're going to back up your current Vault.

03:42

You're going to run the server installation up to 2 releases newer, and then apply Hotfixes.

03:48

Once you've applied the Hotfixes, you're going to migrate your database.

03:52

And this should happen automatically.

03:54

If it doesn't, you may have to do a manual B2B migration.

03:58

And information on how to do that can be found in the resources PDF.

04:02

Now, since you're more than 2 versions behind,

04:05

you're going to repeat those steps until you get to the release you're going to.

04:08

So you're going to go back, and you are going to install the next release of Vault up to 2 releases newer, apply the Hotfixes,

04:16

start the console, and migrate the database.

04:19

You will loop through those stops until you get to the version that your final version is going to be.

04:24

And then once you know it's working,

04:25

you're going to want to backup your Vault, and you're ready to install your clients.

04:30

Because you are more than 2 versions back,

04:32

you will have to upgrade the clients before the users can access Vault.

04:37

If your server is not immediately compatible,

04:40

so the first release that you have to upgrade to will not run on the Windows or SQL of your final new server,

04:49

then you would upgrade the first one in place until it is.

04:55

So you would choose your upgrade window.

04:57

And again if working with an Autodesk representative, let them know.

05:02

And assuming the new hardware will not run in the first release of Vault,

05:07

you would have all of your users log out of the system,

05:09

the current Autodesk Vault, do an IISRESET to make sure that no one's running.

05:15

You're going to backup the current Vault for rollback purposes in this case.

05:19

You're going to run the server installation up to 2 releases newer and see the installation link, if you like, in the resources PDF.

05:27

Apply your Hotfixes.

05:28

And again, as mentioned in the previous slide, migrate your database.

05:33

If this does not start automatically, you may need to do a manual B2B migration.

05:38

Now, for this one, you're going to want to repeat these steps,

05:40

until you hit a point where the software of Vault version will be compatible on the new server.

05:47

So if that's 2 times, 1 time,

05:49

so you would go back to the step of installing the next release up to 2 forward, applying the Hotfixes, starting the console,

05:57

and migrating your database.

05:59

Once the next version 2 forward will be compatible, you would go to your new server.

06:06

You will backup the one that you just finished with.

06:09

You'll go to the new server.

06:10

You're going to restore the backup on that one.

06:13

So first you're going to build the server, and you're going to install Vault up to 2 releases forward from the previous server.

06:20

You're going to apply the Hotfixes.

06:22

You're going to start your ADMS console.

06:25

And you're going to restore the backup.

06:27

Once you restore the backup, you should get the message about your database needs to migrate.

06:33

If it doesn't, you will need to do it manually.

06:35

And then, if you're still not done, install the next release of Vault up to 2 forward,

06:40

apply the Hotfixes, start your ADMS console, migrate your databases.

06:44

And again, you'll look to do that until you are finally at the last release.

06:48

Hopefully, you do not have to run either of these steps more than 1 or 2 times.

06:53

So once you're all set, you're going to want to backup your Vault, and then you're ready to install the clients.

06:59

So in a Combination Upgrade or New Server or if you are able to go directly to the new server,

07:07

you should backup each step along the way so that you can go back one step and not have to go back to the beginning.

07:12

Make sure you pay attention on the 2 different methods to what is needed for rollback.

07:18

For example, if you were able to go directly to a new server,

07:21

it's easy to roll back because you can just go and use the original server.

07:25

It's still sitting there in its current state.

07:27

Whereas, if you have to start on the existing server and move forward, you're going to need a backup,

07:32

and you're going to have to reinstall the older version of Vault.

07:35

Always make sure your users are out of Vault from the point,

07:37

where you're going to backup the production server to the point that you're going to go live.

07:42

And again, you will have to upgrade the client applications in order to use the updated Vault because you will be more than 2 back.