When you install the Autodesk data management server, a single vault named Vault is created. The database files for the vault are created in the MSSQL$AUTODESKVAULT\Data folder under the Microsoft SQL Server installation folder.
Several of the databases located in the Data folder are used by Microsoft SQL Server while others are specific to the vault. Each database file (MDF) has an associated log file (LDF) that contains important transaction data and must be moved, backed up, and restored along with the database file.
KnowledgeVaultMaster.mdf is the master vault database and it maintains the list of users, user permissions, and a list of vaults and their corresponding filestore location.
Vault.mdf is the database for the vault named Vault. Each vault also has a SQL Server log file associated with it called VaultName.ldf.
The second component of every vault is the associated file store where the files are stored. The file store is structured as a hierarchy of folders that are located under a main folder that has the same name as the vault. The filestore location for the default vault named Vault is C:\Documents and Settings\All Users\Application Data\Autodesk\VaultServer. Each data file is stored in its own folder in a normal, uncompressed format. The folders for the file store are created when you add the first file to the vault.
There are two migration types: automatic and manual.
Automatic Migration
If you have upgraded to a new version of the Autodesk Data Management server and an existing database is discovered, you are prompted to migrate the database for use with the new version of the server the first time you log into the server console. If you choose not to migrate a vault or library database the first time you start the server console, the database is listed in the server console as not migrated.
Manual Migration
When restoring a vault using the server console, the vault is automatically migrated to the latest version. You can also use the server console command line to restore a vault. If a vault has been restored using the command line but not migrated, it is indicated in the server console using a yellow warning sign.
Tip: To improve indexing performance, all unnecessary property definitions should be set to "Not In Use" following migration.