topic Re: Vault Pro 2015 backup failures in Vault Forum

Vault Pro 2015 backup failures

Anonymous — Tue, 03 Feb 2015 23:59:35 GMT

I have a client that just installed a replicated Vault and has the backup scheduled 4 hours prior to the replication so there should be plenty of time between operations.

Problem is his scheduled backups fail and leave no log file. He's able to do the backups manually, but the scheduled ones fail.

Below, if it posts legibly is a screen shot of the console log.

Any help would be great as I'm stumped.

Re: Vault Pro 2015 backup failures

Neil_Cross — Wed, 04 Feb 2015 00:18:57 GMT

What is the contents of the script he's using? The switches etc and is this backing up locally or to an external location?

Also, assuming this is running on a windows scheduled task, I'd check what account is being used to authenticate the task, if he does a manual backup is he backing up to the same target location as the script should be? But usually that sort of stuff would kill the script from starting in the first place.

There's definitely something suspicious there with regards to rights, the Vault looks tiny, less than a minute to validate the filestore and 5 minutes to get through the databases. I reckon it's authentication issues somewhere as it's then taking 6 hours to timeout and kill the backup.

Re: Vault Pro 2015 backup failures

Anonymous — Fri, 06 Feb 2015 14:38:42 GMT

Well, we figured out what the issue was.

This might be something you'll want to keep in mind if and when you run a backup and get an error that the backup failed.

The client was running the backup while having the Console window open.

If he ran the backup (scheduled) with the Console closed, it worked fine. Just to verify this we scheduled a backup again but this time left the Console window open, and failure.

So, word to the wise, make sure you do not have the Console window open while running a scheduled backup.

Re: Vault Pro 2015 backup failures

Anonymous — Fri, 06 Feb 2015 14:40:31 GMT

Neil, it is a very small, brand new Vault, only 2000 files if I recall. But anyways, I posted the fix, he had the Console window open, that seems to kill the process.

Re: Vault Pro 2015 backup failures

Neil_Cross — Fri, 06 Feb 2015 17:00:26 GMT

I guess if it's fixed that's good, but I'd be genuinely surprised if that was the actual problem? Reason I say that is because the backup script obviously loads the connectivity.admsconsole.exe process to begin the backup, if this process is already running (i.e. console already open), the backup just doesn't start at all, it would never get to backing up the databases. What it shows in the screen print is the backup almost completing then terminating, which is inconsistent with what you'd see if you had the console open.

But Vault has never been know for it's die hard consistency so it very well could have been that!

Edit - This is working on the assumption that the script and console are on the same server, and that Autodesk haven't changed the behaviour of that process when called twice, but who knows. In all my previous experiences of having a console open, the script just doesn't start and logs nothing, because it can't start. But then again your script could be different! I'm just waffling now, thumbs up for it being fixed anyway.

Re: Vault Pro 2015 backup failures

Anonymous — Fri, 06 Feb 2015 17:05:05 GMT

Thanks Neil.

Honestly, I'm just waiting to hear back from the client that it failed again or some odd error.

No news is good news I guess.

When it first started I found it very odd that there were no error logs being generated, just that it failed.

But again, if it's working now, I'm happy.

Re: Vault Pro 2015 backup failures

paul.gunn — Mon, 09 Feb 2015 17:31:46 GMT

Hi,

I can confirm that there can only be one instance of ADMS console running at a time. When the second instance is started, if it sees there is already on running then it will exit. So the existing instance will never be killed or shutdown . This is pretty old behavior so would be consistent across the various releases of Vault. So it is definitely a good policy not to leave ADMS console open if there are any scheduled tasks.

Paul

Re: Vault Pro 2015 backup failures

Neil_Cross — Tue, 10 Feb 2015 07:46:27 GMT

Paul, that behaviour had already been explained and confirmed above but thanks for the input.

-Neil.

Re: Vault Pro 2015 backup failures

yugendran_bY7EJS — Thu, 21 Aug 2025 18:52:06 GMT

I am using Vault Professional 2019. I want to take a backup of a specific vault instance using the command-line prompt.

This is my script:

@echo off
REM =========================================================
REM Autodesk Vault Professional 2019 - Backup Script
REM Backs up ONLY the vault named "Testing"
REM =========================================================

set BACKUP_DIR=C:\Backup
set LOG_FILE=%BACKUP_DIR%\BackupLog.txt

echo Starting Vault backup...
echo Backup location: %BACKUP_DIR%
echo Log file: %LOG_FILE%
echo.

"C:\Program Files\Autodesk\ADMS Professional 2019\ADMS Console\Connectivity.ADMSConsole.exe" -N"Testing" -Obackup -B"%BACKUP_DIR%" -VUadministrator -VPpassword-L"%LOG_FILE%"

echo.
echo Backup completed. Check %LOG_FILE% for details.
pause

This script works in Autodesk Vault Professional 2024 and takes a backup of a specific vault instance only. However, in Autodesk Vault Professional 2019, it is not working as expected—it takes a backup of all vault instances instead

Re: Vault Pro 2015 backup failures

arkad_s — Fri, 22 Aug 2025 07:08:57 GMT

-N switch (the one you specify which specific Vault database needs to be backed up) is not going to work in earlier version. Option to backup specific Vault databases only was introduced in Vault 2024 so not going to work with version like Vault 2019 - Vault 2024 Help | Administration Enhancements | Autodesk. To use that switch you need to update - for earlier versions only option is to back up every Vault database which is currently attached to your server.

Just side note - your question seems to be something different than initially discussed here - I would suggest creating new topics for different issues in future.