Salta al contenuto principale

Backups Fail When Validating

Thread needs solution

I have created a new backup task and it is set to validate the backup.  The backup is encrypted, and the password was set when the task was created.

The validation task failed, stating:

The password for the protected backup is incorrect.

Date and time
May 23, 2018, 12:20:40 PM
Code
1641
Module
309
Message
TOL: Failed to execute the command. Validating
Additional info:
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"CommandID":"489B4D82-0676-4F49-BC9F-C6F504A10721","$module":"service_process_lxa64_9010"}
Message: TOL: Failed to execute the command. Validating
------------------------
Error code: 22
Module: 309
LineInfo: 0x8D165E86FB81959B
Fields: {"CommandID":"489B4D82-0676-4F49-BC9F-C6F504A10721","$module":"staging_command_lxa64_9010"}
Message: TOL: Failed to execute the command. Validating
------------------------
Error code: 208
Module: 161
LineInfo: 0x0B320396ADFE3C6A
Fields: {"IsReturnCode":"1","$module":"disk_bundle_lxa64_9010"}
Message: Failed to validate the archive.
------------------------
Error code: 500
Module: 64
LineInfo: 0xFA6AC65D19A97894
Fields: {"$module":"disk_bundle_lxa64_9010"}
Message: The archive is password-protected.
 
 
Is there some other step I need to do to get validation working when the backup is encrypted?  It seems to work on subsequent runs of the backup, but not the first run.
 
When I try without encryption, the first run produces a similar error when it tries to validate.  It states that the backup archive could not be located, even though the backup job has just created it.  Subsequent runs of the job work fine.
 
The end result is that it looks like the first run of a full backup job (we're saving each backup to separate files) will always report that it failed.  Am I doing something wrong?
0 Users found this helpful

It looks like this bug is due to the order in which you set things up.

If you turn encryption on before you setup your locations, then they'll fail to validate the first time you run the backup task.

To workaround this, set up your locations first, then set up encryption.

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Messaggi: 0
Commenti: 82

Brian, hello,

seems like you faced a known issue. Thank you for letting us know! Our developers are working on it, the internal ID for reference is ABR-135087.

And I hope that if there is anything else I can do for you, you will not hesitate to let me know.