restore process Vault 2019

[dwayne_smith]

Does anyone know where I might find more detailed information, or a walkthrough of the restore process of a 2019 vault?  I've read Traci Peurasaari's blog on this, and attended her 2018 AU class.

I'd like to learn how these two restore scenarios work.

1 - Using the backup files (filestore and remote SQL) from my ADMS PROD server, and restoring them on a completely separate ADMS TEST server (with it's own remote SQL).  This will verify my backups are good, and provide me with a test environment to experiment on.  As I understand it, this can also be used to recover individual files so they can be added back into the PROD vault.  I haven't tried this process yet.  When I do, my PROD vault will continue to stay up and running.  My biggest concern is that somehow after the restore this clone will come online and think it's the PROD vault, and start talking to the PROD remote SQL server.

2 - Using backup files (filestore and remote SQL) to roll everything back to a previous point in time.  I think if I'm successful in the first process above, I can back up my test ADMS, and then restore it (same server) to try the rollback exercise.

This will probably all make sense after I've done it once, right?  Thanks for any help or advice.

[chris_bluhm]

Dwayne

this class and the powerpoint should have all the info you need

https://www.autodesk.com/autodesk-university/class/Restoring-Your-Vault-Real-World-Tools-Restoring-Y...

or try this kbase

https://knowledge.autodesk.com/support/vault-products/learn-explore/caas/sfdcarticles/sfdcarticles/W...

[traci.peurasaari]

Hi Dwayne

In answer to your concern about the vault thinking it is the Prod Server - once you have installed SQL, installed ADMS and pointed to that remote SQL server the connection is made.  When you restore, it will restore to the SQL you have created and will use that server name.  What you may see is an unattached reference to the Prod server in the ADMS console but this can be deleted once everything is up and configured.

[dwayne_smith]

Thanks for the replies.  The majority of the video addresses the complications of restoring a subscriber in a replicated environment.  My environment isn't that complex.  I have a PROD ADMS using a remote sql server, and a TEST ADSM using a (test) remote sql server.

When I open the ADMS console on my test server and choose restore, the first thing it does is prompt me for the SQL login credentials.  I'm not sure why, since those details are already required during the installation of Vault server, but it's no big deal to re-enter those creds.

The next screen is the restore wizard, which prompts me for Full or Incremental (I know I want full), and the location of the source files from the prod server.  Okay, no sweat, I can copy those or make them available.

It's really the next two prompts on that screen that confuse me.

Reminder:  The files I'm using to restore were backed up from my production server, which remains up and running.  I'm trying to use the backup to create a near-clone, except that it uses it's own remote sql server and filestore.

1. Database restore location (default or select).  It doesn't specify which database, but I assume this means all of them - the KVM, content centers, and every vault that existed and was backed up.  What will this ADMS consider to be the default?  Will it use the remote SQL server that I specified during creation and installation of the test server, the one I just provided credentials for (above), or will it read the backup files and try to use the production sql server?  On the other hand, if I choose "select", what path syntax can I use to point it to the remote sql server I want?  Or, maybe I'm supposed to point it to the database share folder?  I know that folder is used as a conduit back & forth during backups & restores.
2. File Store Location (original or select).  If I choose Original, is the restore going to read the backup files and see the network share where my production files are, and start restoring there?

Thanks for any help.  I know this post is waaaay too long.

Not to muddy the waters here, but I also wonder what I would select differently from the restore wizard screens if I really was trying to do a true PROD to PROD restore from backup files.

[chris_bluhm]

Dewayne

to try and address your issues:

The sql prompt is to make sure you have correct permissions before performing the restore and so we dont store your sa pw

regarding your other two main issues

• Database restore location (default or select).  It doesn't specify which database, but I assume this means all of them - the KVM, content centers, and every vault that existed and was backed up.  What will this ADMS consider to be the default?  Will it use the remote SQL server that I specified during creation and installation of the test server, the one I just provided credentials for (above), or will it read the backup files and try to use the production sql server?  On the other hand, if I choose "select", what path syntax can I use to point it to the remote sql server I want?  Or, maybe I'm supposed to point it to the database share folder?  I know that folder is used as a conduit back & forth during backups & restores.
• You answered it correctly. It uses the server you specified during installation. Vault does not look at the "backup" folders it looks at what is configured during install. AS traci said it will show your old server but that can be deleted or it will automatically clear itself up during normal maintenance.
• File Store Location (original or select).  If I choose Original, is the restore going to read the backup files and see the network share where my production files are, and start restoring there?
• your network share is not recorded as part of the backup by "original" we mean the same file path as the previous server, ie d:\vault\vaultnamefilestore\. the references her are for the local server.

[dwayne_smith]

Thanks Chris, this is helpful and I am understanding it better.

Can you explain a bit more about what the restore process will use as the default filestore path?

[chris_bluhm]

not sure what you are looking for, could you provide more context?

The restore uses whatever logical path that was on the source server for each vault.

If you are using a unc path for your filestore then you would encounter problems. However assuming your source server is using logical drive paths then the restore server will try to restore them to the same drive letter on the new server.

[dwayne_smith]

For this one I'm using UNC paths to a network storage location.

Since I'm only verifying my backups (PROD > TEST), and production is still running, it seems pretty important that this time I avoid choosing the original (UNC) location, or I would end up with a mess - two vaults trying to write to the same file store.  Is that correct?

a different example:  If these were the vaults from my server (two local and one UNC), and I selected the original file store choice from the restore wizard, would it try to write them each back to their original locations?

vault1 - c:\vaultdata

vault2 - \\servershare\vaultdata

vault3 - d:\localshare\vaultdata

If instead I chose an alternate location, say \\server_restore\, would it put them all there instead?

\\server_restore\vault1

\\server_restore\vault2

\\server_restore\vault3

Thanks again for your help.  I appreciate it, and I am understanding better which options I will choose to restore production, or to verify backups.

[chris_bluhm · Accepted solution]

Dewayne

You are correct on both counts. This is also why I would recommend against using a unc path for the filestore and instead use logical mapped drives or a iSCSI lun(but thats my own preference)

Either way, yes if you have a unc path do not restore to original location as it would overwrite your pro data. I would advise(for an overabundance of caution) limiting your test machine's access to the prod file store and server through the firewall or hosts file