Archive Already Exists
Trying to do a full backup of some files on a Windows 2008 R2 server. I've inserted a blank/fresh tape and inventoried it. When I attempt to do the backup I get the following errors
Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields: $module : service_process_vs_43956
Message: Command 'Backing up' has failed.
--------------------
Error code: 207
Module: 161
LineInfo: b320396adfe3be1
Fields: IsReturnCode : 1, $module : disk_bundle_vs_43956
Message: Failed to create an archive in location 'arl:/70B40180-D88C-4DE3-9F67-DAB5704E27C5/A64A3497-74AC-45E1-A158-58D673CB4379'.
--------------------
Error code: 67
Module: 39
LineInfo: 19dd9920ed7240d6
Fields: IsReturnCode : 1, $module : storage_server_vsa64_43956
Message: Cannot create archive 'SERVERNAME_Archive(1)' in vault 'arl:/70B40180-D88C-4DE3-9F67-DAB5704E27C5/A64A3497-74AC-45E1-A158-58D673CB4379'.
--------------------
Error code: 181
Module: 39
LineInfo: 6e0cfc45a7ec4974
Fields: $module : storage_server_vsa64_43956
Message: Error while processing metadata in the database.
--------------------
Error code: 9
Module: 39
LineInfo: 6e0cfc45a7ec495a
Fields: $module : storage_server_vsa64_43956
Message: Archive 'SERVERNAME_Archive(1)' already exists.
--------------------
How can the archive already exist if the tape is new?
Hello Keith,
As you can see from the error message (the line Error while processing metadata in the database), this is most probably not related to the actual empty tape media in question.
When working with tapes, our product relies heavily on the use of meta-data stored in a database in the ProgramData\Acronis folder. This is done because tapes don't allow for random reads so some lookup operations will be very slow.
In particular, our product does not look at the actual tape media to figure out the contents unless you do a rescan operation.
So basically, for each tape, the product stores a tape media identifier and the information about contents of this tape in a seperate database.
An error like the one you are facing is caused by a conflict in this database. The exact cause of this conflict isn't something you can figure out just by the error message, but I would suggest look at the following as the first step:
- Some tape drives have dummy barcode readers that always return the same value for all the inserted tapes.
- In some cases, this can cause confusion for our product: each new tape is misidentified as being as the previous one.
- Since the actual contents of the tape (empty) in this case do not correspond with what our product thinks is there (the contents of the previous tape), this can cause errors like the one you are facing.
So please double check that, when you insert a new tape, the previous one is correctly greyed out with an offline status and a new online tape appears in the product GUI.
The old tape is definitely greyed out. It's an odd one as once I recreated the job, it was ok