Salta al contenuto principale

intermittent error backing up to USB drive??

Thread needs solution

I have a backup job configured to run a nightly full backup to an attached USB drive. USB drives are rotated daily, but the drive letter stays the same (Local Folders, F: drive).

Job is set to keep/append to any existing backups and only clean up if there's insufficient space during the backup. Backup is encrypted.

I use this configuration at multiple locations without issue, but the most recent installation is giving me problems. Intermittently, I believe perhaps when the drive is swapped out for a new drive, Acronis reports an error on the scheduled backup. If I try to run the backup manually it errors out again within seconds.

I believe if I edit the job and re-select the destination that the backup will then work fine, but I need to test further to be sure.

Here are the error details which don't mean much to me:


--------------------
Log Entry Details
--------------------
Type: Error
Date and time: 6/30/2014 11:00:09 PM
Backup plan: External Backup
Task: Full backup
Code: 20,250,685(0x135003D)
Module: 309
Owner: Owner@SRV-01
Message:
Command 'Running backup plan 'External Backup'' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : mms_vs_38774
Message: Command 'Running backup plan 'External Backup'' has failed.
--------------------
Error code: 41
Module: 307
LineInfo: e6792a5ee190dda6
Fields: $module : agent_protection_addon_vs_38774
Message: Failed to execute the command.
--------------------
Error code: 1
Module: 149
LineInfo: 15b308bfdeeeb9f
Fields: $module : disk_bundle_vs_38774
Message: Invalid parameters were specified.
--------------------
Error code: 27
Module: 149
LineInfo: 15b308bfdeeeb8d
Fields: $module : disk_bundle_vs_38774
Message: Password is required.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x0135003D+0x01330029+0x00950001+0x0095001B

Can anyone advise on what the issue might be and what the solution is?

Thanks!

0 Users found this helpful

No help with this? If I format the drive and retry the job it runs without issue. It almost seems like the job is having an issue appending to drives existing backups.

Thanks

Hello Kremlar,

first of all I have to tell you that we don't support destination drives rotation within one backup task because it might cause archive metadata corruption. For your scenario it is recommended to use Simplified naming of backup files. Alternatively you can create separate backup plans for each destination drive.

If the above doesn't help please collect system information and send it to me in a PM.

Thank you.

Hi - Thanks for your response!

first of all I have to tell you that we don't support destination drives rotation within one backup task because it might cause archive metadata corruption.

Interesting, since it was an Acronis tech support rep who suggested this configuration when setting up our first location. Can you tell me what the symptoms would be if we encountered the archive metadata corruption? What type of problems would we have?

For your scenario it is recommended to use Simplified naming of backup files.

Thanks. I checked this option out and based on the description I'm not certain how it would help with my scenario. The biggest downside would be that it seems like it would overwrite any existing backups on each drive before backing up. Is this why it would be recommended in my scenario? We do like being able to go back several weeks if needed on each backup drive, so using this option would greatly reduce our backup retention.

Alternatively you can create separate backup plans for each destination drive.

If I'm understanding correctly for this to help it would require the backup drives to be swapped on a consistent, predictable basis. Although this is obviously ideal, I find that it's not uncommon for the backup operator to forget to swap the drive on a given day so I don't think this would work for us.

On a side note, after reformatting the backup drives that were triggering this error I have not experienced this issue since. Fingers crossed - perhaps the problem is resolved.

Can you tell me what the error in the log meant exactly? I'm finding the errors that Acronis throws out to be rather cryptic and difficult to pinpoint.

These seem to be the key errors and I'm not sure what they indicate:

Error code: 1

Module: 149
LineInfo: 15b308bfdeeeb9f
Fields: $module : disk_bundle_vs_38774
Message: Invalid parameters were specified.
--------------------
Error code: 27
Module: 149
LineInfo: 15b308bfdeeeb8d
Fields: $module : disk_bundle_vs_38774

Message: Password is required.

Thanks!

Hello Kremlar,

Metadata corruption is not a very correct word here.
But problems caused by metadata confusion is better. That is basically what you faced.

The error:
Error code: 27
Module: 149
LineInfo: 15b308bfdeeeb8d
Fields: $module : disk_bundle_vs_38774

Message: Password is required.

Is issued in case your parameters for archive protection in the backup plan do not match parameters for archive protection in your actual backup.

It seems that you inserted a drive where the archive was empty or similar situation.
Then Acronis saw that you have archive protection in your backup plan settings and archive is empty on the drive and does not have that protection.
Therefore you got that error.