A solid backup strategy is essential for any Vault Server environment, whether you’re running Vault Professional, Vault Basic, or supporting remote Vault Client access. In this guide, KETIV’s Application Engineer walks you through how to configure Autodesk Vault backups using Windows Server tools and Vault’s own command‑line interface. You’ll learn how to automate full Vault database and file store backups, cascade backup folders, and safeguard your CAD files and design data against data loss.
Why Backups Matter in Autodesk Vault
- Data Integrity & Recovery: A backup of your Vault database plus the file store folder ensures you can restore both metadata and actual CAD files after hardware failure or human error.
- Consistent Version Control: Scheduled backups capture your lifecycle transitions and revision history, so no edits are lost.
- Minimal Downtime: Automated scripts run off‑hours, giving Vault Users continuous service during business hours.
- Backup Tip: Keep at least two backup sets, your primary and a secondary “backup of the backup”, to safeguard against disk corruption.
1. Check Your Storage Space
Before you begin, confirm that your backup location has enough free space to store at least one full backup—preferably more. This is of course dependent on the size of your Vault installation.
-
In this example, we’re using the K: drive with a dedicated
Backupsfolder. -
Create subfolders to manage multiple backups (e.g.,
\Afor the newest backup,\Bfor the previous one).
Tip: Never store your only backups on the same server that runs Vault. Use a cloud service, third-party backup software like Veeam, or an external hard drive to keep an offsite copy safe from hardware failure or ransomware.
2. Create the Backup Script
To avoid running the backup by accident during editing, start by creating your script as a .txt file instead of a .bat file.
Your script will have three main parts:
A. Close the Data Management Server Console
Vault backups can’t run if the ADMS Console is open.
Use a taskkill command to close Connectivity.ADMSConsole.exe before starting the backup. Include switches to force close and terminate related processes:
:: ++++++++++++++++++++++++++++++++++++++++++ :: Kills ADMS if Open :: ++++++++++++++++++++++++++++++++++++++++++ taskkill /IM Connectivity.ADMSConsole.exe /F /T
Key Switches:
/IM → Declares it is the Image we want to kill|
/F → Forces
/IM → Kills any services spawned from the task
B. Cascade the Backups
This process removes the oldest backup [RMDIR], renames the most recent to the older backup folder [Rename], and creates a new folder for the next run [MKDIR]. Example:
:: ++++++++++++++++++++++++++++++++++++++++++ :: Cascade Backup Folders :: ++++++++++++++++++++++++++++++++++++++++++ RMDIR /Q /S "K:\Backups\B" Rename "K:\Backups\A" "B" MKDIR "K:\Backups\A"
Key Switches:
/Q → Grabs all folders underneath [recursive]
/S → Does so silently, with no prompting
C. Run the Vault Backup Command
Navigate to the folder where Vault Server is installed (e.g., C:\Program Files\Autodesk\ADMS Professional 2025) and run the console with backup parameters:
:: ++++++++++++++++++++++++++++++++++++++++++ :: Run Backup :: ++++++++++++++++++++++++++++++++++++++++++ "C:\Program Files\Autodesk\Vault Server 2025\ADMS Console\Connectivity.ADMSConsole.exe" -Obackup -B"K:\Backups\A" -VU"Vaultbackup" -VP"" -S -L"K:\Backups\Logs\VaultBULogs.txt"
Key Switches:
-Obackup → Declared the operation is a Backup [recursive]
-B → The location where the backup will be placed
-VU → The Vault User
-VP → The Vault Password
-DBU → The SQL Database User
-DBP → The SQL Database Password
-S → Runs silently
-L → Sets log file location
3. Convert to a Batch File
Once your script is finalized:
- Change the file extension from .txt to .bat
- Store the .bat file in a secure folder (e.g., K:\Backups\Scripts) for Task Scheduler to access later.
4. Automate with Task Scheduler
Running backups manually works, but automation ensures consistent protection.
-
Open Windows Task Scheduler
-
Create a New Task → Name it clearly (e.g., “Vault Weekly Backup”) and optionally add a description.
-
Security Settings:
-
Ensure the account has access to the Vault file store
-
Has administrator privileges
-
Has the “Log on as a batch job” permission on the server
-
Run whether the user is logged in or not
-
Run with highest privileges
-
-
Triggers:
-
Set the schedule (e.g., every Friday at 8 PM when the system is idle)
-
-
Actions:
-
Select Start a Program and browse to your
.batbackup script
-
-
Save and enter the account password
5. Verify Backups Regularly
Even with automation in place, periodically check:
-
That the task runs without errors
-
Backup logs for successful completion
-
Available drive space, especially as your Vault data grows