00:08
Welcome to Autodesk Vault Migration Planning.
00:11
My name is Traci Peurasaari, and I'm a designated support
00:14
I currently support the Vault Planner
00:16
because I have over 25 years as a Microsoft Certified
00:19
Professional in SQL server database administration.
00:23
And what we're going to cover today
00:24
is going to be how to do a vault migration,
00:27
and hopefully, by the end, you will
00:29
understand and be ready to plan your next migration.
00:32
So the objective today is to cover
00:35
planning an in-place upgrade or a new server migration.
00:39
What we're going to include is how
00:41
to handle both multi and single site environments.
00:45
And additionally, I'm going to go through the basic how-tos
00:48
for actually upgrading your vault.
00:50
So what we're looking to do is set the expectations
00:53
during the process so you know exactly what to expect.
00:56
That you can be prepared for all the steps
00:58
that are involved in vault migration,
01:01
make sure you know where to get the requirements,
01:05
know how to perform a successful migration, that you understand
01:10
how to best plan if you are doing replication, or using
01:14
a multi-site environment.
01:15
And also, at the end, there are several links
01:18
on how you can get help and the resources
01:20
that you need to go forward.
01:21
Please take a look at the safe harbor statement.
01:24
This is just basically to let you
01:25
know that I may discuss forward-facing ideas
01:28
and that they do not constitute a promise.
01:32
So vault Migration-- what is a migration.
01:36
The word migration has many, many definitions.
01:39
For the purpose of this presentation,
01:42
we are talking about upgrading your vault from one release
01:45
to another, such as moving from 2019 to 2020 or 2021.
01:50
This can also include upgrading vault edition
01:52
if you're using vault work-group and you
01:54
want to move to professional.
01:56
And then lastly, it can include moving your vault
01:58
to a different server, whether that's on the same version
02:01
or on a new version.
02:04
So when you plan your migration, there are key areas
02:07
that you need to plan for.
02:09
You need to look at your hardware
02:10
requirements, your software requirements, your network
02:13
environment, and what you might need to manage and support.
02:16
This could be passwords, access to servers.
02:20
The hardware requirements could be CPU, memory,
02:24
software requirements, and what version of SQL,
02:27
and what version of Windows the software itself network
02:32
permissions and SSL.
02:34
So at a high-level overview, the very first step
02:38
of doing a migration is to create a test environment
02:42
so that you can validate.
02:44
In order to create a test environment,
02:46
you want to use a machine that's got a similar CPU memory.
02:50
You're going to install and test the system
02:54
with the same version of vault. You're
02:56
going to backup the production server
02:58
and put the data onto the tester so that you're
03:00
using the same data, and you're going
03:02
to want to verify that the file storing everything is complete.
03:07
Pictorially, what this looks like,
03:08
then you should take a backup in order
03:11
to take a backup on your production environment.
03:13
You're going to create a test environment by restoring
03:16
that backup to the new server.
03:18
Then you're going to validate.
03:19
What a validation could mean is checking in, checking out,
03:23
do you have access to your files?
03:25
Does it perform in the way that you
03:27
are expecting it to perform?
03:30
And then, you can also keep this environment
03:32
available for future minor and major upgrades
03:35
once you've got it set up.
03:37
The next step is looking at your SQL server vault
03:41
has very specific SQL server requirements
03:43
based on the version.
03:45
So before you do an upgrade, you need
03:46
to make sure that the version of SQL server
03:49
you are planning to use is supported
03:51
by the version of vault that you are planning to install.
03:55
The following chart here will tell you.
03:57
If it's got a green, it means it's supported
03:60
in production for that version.
04:02
If it's got a yellow, it means that it's
04:04
supported during migration.
04:06
And what that can mean is if you've
04:08
got multiple versions to upgrade through,
04:10
you can go ahead and install further additional SQL server
04:15
so that you don't have to stop in the middle,
04:17
install a new edition or a new version of SQL server
04:20
and then do it again.
04:22
Once you've got your SQL server ready,
04:25
the next step is to install the current vault server.
04:29
So you're going to install the version that you're
04:31
going to upgrade to.
04:33
You're going to apply any hotfixes.
04:37
And then you're going to migrate your vaults and libraries.
04:39
We'll go into that and a little bit more
04:41
in the further sections.
04:42
But basically, once you do an instalment and upgrade,
04:45
vault's going to ask you if you want to migrate your databases.
04:48
This is in order to account for any SQL server sequences,
04:53
so that the databases and working
04:54
levels for the current version.
04:57
When you're migrating vaults, unlike other products,
05:01
there is a limitation because it is database-based.
05:03
That it can handle more than two versions upgrade at a time.
05:07
So if you take a look at the flowchart here,
05:10
it follows through the steps.
05:12
But basically, if you're currently running 2018,
05:16
you can go to 2019 and 2020.
05:20
So if you're running 2018 and you want to install vault 2021,
05:24
you would actually have to go through two upgrades.
05:28
One from '18 to '20 and one from '20 to '21.
05:32
Or '18 to '19 and '19 to 21.
05:34
However, you prefer.
05:35
If you are planning on going to a new server,
05:38
the easiest way to do this is to go over
05:39
the new server for the very first one
05:42
and then to do it in place for the remaining
05:44
ones on that server.
05:46
Additionally, beyond being able to only upgrade
05:49
two versions at a time, the vault client only
05:52
supports two versions back.
05:55
This is again in order to allow you to upgrade your vault
05:58
server, and maybe you haven't upgraded your CAD tools yet
06:01
or your vault client.
06:03
If you are within two versions, so if you are at 2019,
06:07
and you are going to 2021, new users
06:10
can still use the 2019 clients while you are taking the time
06:15
to go through the upgrade process for both the CAD
06:17
and vault tools your system.
06:20
To look at this pictorially-- so if you're running vault server
06:32
This is also true-- this is just the vault client.
06:34
This is also true for the CAD tools.
06:37
Each of the CAD tools has a vault add on,
06:39
and those also have to match.
06:41
So if you take a look back, what you'll see
06:43
is, here's the inventor, or the AutoCAD add-in vault 2019,
06:48
with the vault 2019 client, connect to a vault
06:56
It's really important to know that your CAD
06:59
client and your client have to be the same.
07:02
As long as you're within of both,
07:04
but those two do have to match.
07:08
And you have to install that from the client.
07:10
So basically, when you're setting up CAD,
07:12
if your CAD tool is already installed,
07:14
if you've installed inventor in 2021 or AutoCAD 2021,
07:18
and then install vault, it will automatically
07:22
If vault is installed first, and then install your CAD add-in
07:27
you will have to go back into vault
07:29
and have the Add-on for the product.
07:30
So If you're doing it all at once,
07:32
it's best to do CAD tools first.
07:35
So now you've gone through the client,
07:37
and you've through the server.
07:38
You've done the SQL server.
07:39
You've done the validation.
07:40
And everything is functioning.
07:42
A Really critical point here.
07:44
Once that happens, make sure you make a backup.
07:46
When you're all done, it's ready to go.
07:49
You don't want to have to start again.
07:51
Make sure you have a backup.
07:52
You're ready to go forward.
07:53
People are going to start processing.
07:55
If you do find any issues, once processing starts,
07:57
you have a valid place to go back
07:59
to as opposed to having to go back
08:00
all the way to the begining.
08:02
So there are two options involved.
08:04
There's a single-site environment,
08:06
which means you have one vault server
08:07
or is a replicated environment which
08:09
is a multi-site environment.
08:11
If you're doing a single site environment,
08:13
you can be doing an in-place upgrade,
08:15
or you can be going to a new server.
08:17
If you're doing an in-place upgrade, what
08:18
you need to make sure is that your computer that you're
08:22
going to be upgrading, has a mix of minimum system requirements.
08:26
You're going to need to make sure that you have all the IDs
08:30
This would be the vault administrator ID.
08:33
This would be SQL server, SA or system admin, user ID
08:38
This would be the impersonation account in the vault user ID
08:43
and password for that.
08:44
You're going to need to make sure that you have all vault
08:46
software, and all the updates.
08:49
And then the serial number, product key and all that fun
08:51
stuff whenever you're installing vault or any product itself.
08:56
When you look at testing.
08:57
How are you planning on creating--
08:58
or do you have a test server?
08:60
As I said in the beginning, Autodesk always
09:02
recommends that you test for backup or upgrade
09:06
prior to doing it live.
09:08
And that you have a backup server to do this on.
09:12
This allows you not only to test the upgrade,
09:14
see how long it's going to take.
09:16
And moving forward, it also allows
09:17
you to validate the data, and see that there's not any issues
09:20
with any of your work phones.
09:22
And then make sure you have a rollback plan.
09:24
If you're doing an in-place upgrade,
09:26
you're not going to have another server to go back to.
09:28
So what you're going to need to do
09:29
is you're going to need to make sure
09:31
that you have the exact version that you started with.
09:33
This includes [INAUDIBLE],, updates upgrades.
09:36
You're going to want to take a backup,
09:38
and then you're going to need your rollback plan mapped out.
09:41
So there's a couple of options, if you're doing a snapshot.
09:44
You need make sure you get a snapshot of both the vault
09:47
server and the SQL server, if they're not
09:49
on the same machine.
09:51
And you need to plan for how long you can be down.
09:54
So if there is a problem and then you're
09:55
doing an in-place upgrade, how much time
09:58
do you have before you have to get those service up
10:00
and running again, and how much time is it going to take.
10:03
Because basically at that point, you're
10:05
going to have to reinstall on the existing
10:07
server, unless you've done a snapshot, in which case,
10:10
you will be restoring a snapshot.
10:12
We should have an idea of about how long that will take.
10:16
And so looking at the individual steps of an in-place upgrade
10:19
as far as how to do it.
10:20
So you're going to make sure that the vault is not
10:22
being used when ready to go.
10:24
You're going to run a backup, then
10:26
you're going to install the software.
10:28
Once you install the software, you're
10:30
going to actually start the ADMS console.
10:33
And it's going to come up the very first time only
10:35
that you started it, and it's going
10:37
to ask you if you want to migrate your databases.
10:43
This will migrate them to the current version.
10:45
If by chance you start your ADMS console and close it
10:50
Or someone says no, then you will
10:53
have to migrate the databases, one
10:55
at a time inside the client.
10:57
Once you've got your server already,
10:59
your next step would be to set up your clients.
11:01
And again, as I said, once you're done,
11:03
make sure you make a backup of vault
11:06
in the vault working state.
11:09
Easier than an in-place migration
11:11
as far as the rollback goes, is if you're
11:13
migrating to new server.
11:14
If You're migrating to the server,
11:16
and something doesn't work, you could just go right back
11:19
to the server you started with.
11:20
And you still got a working vault.
11:23
So in order to go to the server migration, same as before,
11:26
you're going to want to verify that the existing ADMS and SQL
11:30
server meets the minimum requirements for Windows
11:34
You're going to need all those IDs, just like before,
11:37
and the serial number.
11:38
Apart from a step standpoint, you're
11:40
going to need to build the new servers, which
11:43
means verifying that the SQL server meets requirements.
11:46
And there's a link both here and at the end that you
11:50
can get those requirements.
11:52
You're going to want to check on the SQL.
11:55
Use the vault release that you're upgrading to,
11:57
to start with, so that you have two identical servers.
12:01
So if you are installing from
12:07
thing you're going to do on a new server vault
12:14
If you're just wanting to test the version,
12:15
you can go ahead and start with 2021.
12:18
Then you're going to set up your SQL server, you're ADMS.
12:21
So there's two options for that.
12:23
You can have the ADMS and the SQL on the same server,
12:27
or you can have them on separate servers.
12:31
If you're going to have your SQL server on a separate server,
12:35
you're going to have to create a shared folder,
12:38
and you will need to decide whether you're going to put
12:40
that on the ADMS or on SQL.
12:42
And if you're installing version 2021 or higher,
12:47
you can choose an instance name.
12:49
For those of you that have been using vault
12:51
for any length of time, currently SQL server
12:54
is forced to use Autodesk vault as the name of the instance.
12:58
Starting with version 2021, you can select a different instance
13:02
name for your server.
13:05
So if you've already installed the software,
13:07
and tested installation migration,
13:09
and then you know that the server is set up correctly.
13:11
And then you check the backup completed
13:14
and you take a new backup of the old server.
13:17
So that when you restore the backup again and test,
13:19
you can do this as many times as you need to on the server,
13:22
it will give you an idea of how long it's
13:24
going to actually take.
13:26
However, if you are unable to get the server functioning,
13:29
or there's any problems, the current server is available.
13:32
And you just point your users back to it.
13:34
So the steps on the how to for a new server migration,
13:37
you build the new servers, backup your existing vault.
13:40
You're going to restore that backup in the new server.
13:43
You're going to take a new backup
13:44
and restore, so that you can test to make sure the backup
13:48
And to start ADMS console, you're
13:50
going to enable your vault, and migrate your databases,
13:53
set up your client and backup your vault.
13:56
A little bit more complicated is a multi-site environment,
13:60
or a replicated environment.
14:02
There are multiple types of replication.
14:04
There is a vault server or publisher
14:07
with multiple subscribers that also include their own SQL
14:10
server, or there's file store replication,
14:14
which is just by a neighbor or a file store that just contains
14:18
file store and other locations.
14:20
When you're doing multi-site migration,
14:23
the planning is slightly different.
14:25
The publisher always has to be completed first
14:27
as soon as you start the upgrade on the publisher,
14:29
it will disable the subscribers, and the publisher
14:32
will be available once the operation finished.
14:35
So while the subscribers are being built and upgraded,
14:37
people can do that to the publishers,
14:39
and new users will still be able to work.
14:41
You can now do the upgrade on subscriber
14:43
until you know the publisher is completed and ready to go.
14:47
Subscribers will be unavailable until they're not
14:50
only upgraded, but once you do an upgrade,
14:54
the SQL server will create a snapshot,
14:56
and that snapshot has to be completely applied
14:59
before the subscriber is available.
15:02
Currently, and in the system by default,
15:05
snapshot retention to 14 days.
15:08
So if there's something that is going to go wrong
15:11
or something happens during this process,
15:13
you may want to increase those days so that you have some time
15:17
so it doesn't give you an error snapshot attention
15:20
And then subscribers have to be online during the upgrade you
15:23
can't take them offline but you do start
15:26
to see a replication jobs.
15:28
Preparation for a multi-server multi-site upgrade
15:31
is again very similar.
15:33
You're going to want to make sure
15:34
that you're using the right versions that you've
15:36
got the ID and passwords and that you've got the license
15:42
Additionally, from there you want
15:43
to make sure that the publisher and subscribers are saying
15:47
you can do this by looking and see server at the replication
15:50
monitor and make sure that there are no pending changes.
15:53
If you have a high latency connection between two
15:56
of your locations, there are options
15:59
for copy in the snapshot.
16:02
And there's a link at the end of this presentation on how to do
16:05
an alternate snapshot method.
16:07
And then you need to make sure that you know where the shared
16:09
folders are in the accounts and you have access to those.
16:13
Testing is very similar.
16:14
You're going to want to set up a test server to do validation.
16:18
The question that you need to ask
16:19
is, do you have the time to set up both
16:21
a publisher and a subscriber?
16:23
And do you want to test replication as well as
16:26
testing the upgrade.
16:28
And that will be a decision that you'll
16:29
have to make when you're going through the upgrade.
16:32
If you do, it will give you an idea
16:34
of the general timing that is going
16:36
to take to get to a subscriber.
16:38
And only one subscriber will be brought up at a time.
16:40
But it is not necessary.
16:41
What they want is to make sure that you have a publisher.
16:44
While you're doing this, you're going
16:46
to want to document all the steps
16:47
and take screenshots if you are going
16:49
to do it with a subscriber and publisher.
16:52
And then make sure again, the resulting document
16:55
comes before you go forward.
16:57
Once you're done, your rollback that plan again--
16:59
this is in same place--
17:01
is to use your snapshot or your backup
17:04
and restore, reinstall and go back to where you were.
17:08
And as subscribers are offline or unavailable
17:11
to the publisher during the upgrade, the upgrade does that.
17:14
And you will not have upgraded your subscribers yet.
17:17
So once you go back, you should be
17:20
able to connect to the subscribers
17:22
and go forward until you figure out
17:24
what the plan is to continue.
17:27
When you are upgrading the publisher,
17:28
the steps that you will follow then
17:30
are to validate the replication status.
17:33
Make sure that vault isn't being used.
17:35
Backup your vault. Install vault software.
17:41
Migrate your databases.
17:43
Make sure you catch a snapshot or a backup,
17:47
or however you are going to do that.
17:49
And then again, backup, use a vault backup
17:51
to have your copy of it in new working state.
17:56
When you go to upgrade the subscribers,
17:58
now the publishers working.
18:00
The publishers are ready to go.
18:04
Your users can work on the publisher,
18:06
then you're going to want to make sure
18:08
that there's no users logged in to the subscribers.
18:11
You should have already checked that
18:12
and they should still not be.
18:14
You're going to run the actual software
18:16
installation on subscriber.
18:18
And so, you're going to start the ADMS console
18:22
And the subscriber is going to give you a message,
18:25
the database is not available, while it consumes the snapshot
18:29
that is a picture of the database
18:32
as it exists on the publisher.
18:35
Once the snapshot is fully consumed,
18:37
you can enable your vaults, and you'll
18:39
repeat the step for each subscriber, one at a time.
18:43
So you've got stored documents in vault.
18:46
And this includes content center libraries, or libraries.
18:52
Where once you've done an upgrade,
18:54
if you are using older versions or you
18:57
have older versions of software, you're
18:59
going to need library files that match those versions.
19:03
So you would make a new partition in the new version,
19:05
and upgrade any custom content center libraries, custom
19:10
partitions, and you would migrate them
19:13
to the new version, just like you did your vaults.
19:16
The standard libraries are available for install
19:21
And you would need to install or migrate the standard libraries
19:25
If you're not going to be editing any documents
19:28
in earlier versions, then you could just
19:31
create the new partition, and you don't
19:33
need to keep the old ones.
19:35
When you're ready to start working,
19:37
there's a decision that you can make on how you're
19:40
going to do your CAD files.
19:43
Do you want to upgrade them as you go,
19:45
or do you want to upgrade them all to the new version?
19:48
There is no right answer.
19:50
It's what works for you.
19:51
You can-- the link here goes to the steps
19:54
on using task scheduler.
19:56
So you can update the Inventor files using the inventor SQL
20:01
And it will basically, in the background do a check out
20:05
and, then check it back in the new version.
20:09
And it's a time you can set batches.
20:11
One of the reasons to upgrade them,
20:13
is you do then get access to the new features
20:16
and the CAD involved.
20:19
And then you also get access to the new contact center files.
20:23
However, there is no backward compatibility.
20:26
So if there is any group that's using an older
20:29
version of Inventor or AutoCAD, once they've
20:32
been upgraded to 2021, then you will need 2021 to open them.
20:37
So if you may need to open them in 2019,
20:39
you would want to wait until they were
20:43
upgraded in the later version.
20:45
At the bottom, there is a link to an AutoCAD compatibility
20:47
chart, which ones you can see, which
20:49
what, and which files are available,
20:52
and which version to open.
20:55
So you've completed your upgrade.
20:56
You've made your decision on how you're going to do your files,
20:59
and it is Upgrade Go Live Day.
21:01
Three key points-- planning, follow your plan and everything
21:06
that we've laid out here.
21:08
If there's issues, contact support.
21:10
And when you're done, make sure you do a backup.
21:14
It's really helpful if you can let your designated support
21:16
specialist know your plan date for the migration.
21:20
That way, they can make sure that the appropriate people
21:22
are available and can hear, should you have a problem.
21:25
If you have an issue that you cannot get resolved,
21:28
you would want to create a severity one ticket.
21:31
And these must be done over the phone.
21:34
It's available 24/7 to work with support to resolve.
21:38
And you would be contacted within an hour
21:41
to connect you with a support representative.
21:43
And then again, backup, backup, backup.
21:47
You want to make sure that you are
21:49
able to go back to the upgraded state
21:51
if anything happens once this is done.
21:54
Autodesk offers a lot of helpful resources.
21:56
The very first one will be the Customer Success Learning Hub.
22:00
This will give you access to articles, product updates, tips
22:07
There are recordings.
22:09
There's events, and there's also forums where
22:13
you can share your expertise.
22:14
The link is on screen, and it has a lot
22:18
of very, very good information.
22:20
And then lastly, I've compiled a list of some links
22:24
for your benefit while you're doing the upgrade.
22:26
A B2B migration is when I was referring to if you
22:30
need to upgrade your vaults.
22:32
And it doesn't ask you, or you'd say no,
22:35
and you then have to migrate through vaults
22:39
The next link is actually instructions--
22:41
if you wish to install your SQL server out of time,
22:43
now you install and set up a SQL server.
22:46
There are the vault requirements.
22:49
So what Windows and SQL versions you need to be at?
22:53
There's actual instructions-- step by step instructions--
22:56
on installing vault,
23:02
The vault server has to have internet information
23:06
So there's instructions on how to set up internet information
23:09
services, as I mentioned earlier.
23:11
And if you're doing a replicated environment,
23:13
the alternate Snapshot method, should you
23:15
have a slow connection.
23:17
And then again, upgrading your vaults
23:19
server, so additional instructions on how to do that.
23:23
Thank you for watching this video today.
23:27
And I hope it's helped you get ready for any vault
23:29
migrations you will do in the future.
23:31
If you have a more complicated set-up than what
23:34
I've discussed here.
23:35
If you are getting new servers across an entire multi-site,
23:38
or if you have any additional issues,
23:41
make sure that you reach out to me,
23:43
or your value-added reseller or your Autodesk designated
23:48
And I hope I've helped you, and have a good day.
AutoCAD
AutoCAD LT
Fusion
AutoCAD Revit LT Suite
Architecture, Engineering & Construction Collection
Revit
Civil 3D
BIM Collaborate Pro
Product Design & Manufacturing Collection
Maya
Inventor
Navisworks
3DS Max
Flow Production Tracking
Revit LT
Forma
Recap Pro
Alias Concept
Maya Creative
Flame
Arnold
Mudbox
Flow Capture
Media & Entertainment Collection
