Direkt zum Inhalt

Acronis Backup 11.7 - failed to open archive for writing/ Backups failing

Thread needs solution

Hello, 

 

I have Acronis Backup 11.7. I'm backing up stations from Management station. The backup Vault is located on NAS. Initial connection to NAS was done using Domain\Administrator account with correct password. First backups were created. Any subsequential backup fails:

 

--------------------
Log Entry Details
--------------------
Type:                Error
Date and time:       1/7/2019 10:30:03 AM
Backup plan:         Backup 1/7/2019 10:25:19 AM
Task:                Simple backup (Full)
Managed entity type: Machine
Managed entity:      DROP181.xxx
Machine:             DROP181.xxx
Code:                20,250,685(0x135003D)
Module:              309
Owner:               
Message:             
  Command 'Backing up' has failed.
Additional info: 
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c9510
Fields:  $module : service_process_vs_44182
Message: Command 'Backing up' has failed.
--------------------
Error code: 22
Module: 309
LineInfo: 8d165e86fb8195f7
Fields:  TraceLevel : 1, $module : gtob_backup_command_addon_vs_44182
Message: TOL: Failed to execute the command. The 'Backing up' command backs up the specified data to the specified location.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields:  $module : disk_bundle_vs_44182
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: 145a191bfe9050c3
Fields:  $module : disk_bundle_vs_44182
Message: Failed to prepare an operation.
--------------------
Error code: 1002
Module: 1
LineInfo: 51ea1282ec004b2
Fields:  $module : disk_bundle_vs_44182
Message: Internal error: Failed to create the image builder.
--------------------
Acronis Knowledge Base: http://kb.acronis.com/errorcode/

Event code: 0x0135003D+0x01350016+0x01490003+0x00010424+0x000103EA

--------------------
 

Moreover I'm sometimes able, sometimes not (multiple credential entry popup appears, and after entering the credentials, pops up again and again) to log to the Vault using exactly the same credential as for creating the vault. domain\Administrator. (see the attached image)

Another try resulted in different error, please see attached log.

 

The NAS is pingable from the management station. Permission on the NAS share are Everyone + full control.

I'm kind of lost what to do to have the backups working.

 

Please can you help me with that?

 

Thanks

 

Vladimir 

 

Anhang Größe
Example.PNG 292.47 KB
Log.zip 1.38 KB
0 Users found this helpful
frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Vladimir,

welcome to Acronis forums!

We strongly recommend that you download and install the latest build #50256 (you use build #44182).

Please recreate the task and check if this helped.

Please also refer to https://forum.acronis.com/forum/acronis-backup-117-former-acronis-backup-recovery-115/internal-error-failed-create-image

Hi Maria,

by installing, can you confirm, that updating Acronis is also fine? There is quite some configuration behind so I would rather avoid clean install.

Will the issue be resolved using actual storage vault or I'll need to delete current vault and create new one?

 

Thanks for your support.

 

With Kind Regards

 

Vladimir

frestogaslorastaswastavewroviwroclolacorashibushurutraciwrubrishabenichikucrijorejenufrilomuwrigaslowrikejawrachosleratiswurelaseriprouobrunoviswosuthitribrepakotritopislivadrauibretisetewrapenuwrapi
Beiträge: 0
Kommentare: 2016

Hello Vladimir,

no, you will not need to delete and recreate a vault, only this backup task.

Please pay attention:

The new build # 50230 is released on 2019-01-29. Of course, we recommend that our customers use this build with the maximum number of different issue fixed by this moment. I can not confirm that the issue you are referring to has been fixed, because I can't check it even in Release notes: the bugfixes lists for such old builds are deleted and replaced with the fresher builds release's info. However, even though the issue still remains, our developers work with the current builds only in order to investigate/fix it.