When you install the Autodesk Vault 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 file store 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.
Important: Never modify the files or folder structure in the file store. Only access these files through the client interface.
Learn About Vault Data
In Microsoft SQL Server, the data and transaction log files of a vault can be detached, and then reattached to another server, or to a different location on the same server. Detaching a vault removes it from SQL Server and from the vault master database, but leaves it intact within the data and transaction log files that compose the vault. These data and transaction log files can be used to attach the vault to any instance of SQL Server, including the server from which the vault was detached. This makes the vault available in exactly the same state it was in when it was detached.
Detaching and attaching vaults is useful if you want to move a vault to a different physical disk. For example, the disk containing the vault file ran out of disk space, and you want to expand the existing file rather than add a new file to the vault on the other disk.
When you attach a vault, you must specify the name and physical location of the primary data file as well as the SQL log file. The primary file contains the information needed to find the other files comprising the vault unless one or more of those files have changed location since the vault was detached. Any files that have changed location must be specified in addition to the primary file. Otherwise, the SQL Server tries to attach the files based on incorrect file location information stored in the primary file, and the vault is not successfully attached.
Warning: The vault server consists of two vaults by default: KnowledgeVaultMaster and Vault plus an additional vault for each new vault created. If you are moving to a new server you must move both vaults to capture all the required information for the vault server. If you are only moving locations on the same server, you do not need to change the vault master location.
The most effective way to move a vault from one computer to another is to backup the vault on the original computer and then restore the vault on the new computer. This ensures that all data is maintained.