Failing 'Incremental backup' on scheduled startup, works on manual?

Thread needs solution
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Beginner
Contributions: 1
Commentaires: 0

I am running Windows Server 2012. I have had Acronis backup 11.5 running for almost a year with no problems until 2 weeks ago when I expanded the array on the server. Our scheduled backups are Full backup weekly (which succeeds) and a daily incremental (which started failing after the array expansion). For some reason the odd scheduled incremental works (like 1 in 7). I have tried setting the incremental to backup at different times and that didn't work. I can go in at any point and manually trigger an incremental and it works every time. Our server is not that busy, file server for about 40 people. All server disc's are solid state so most tasks run very fast. The incremental are scheduled to run 5 hours after everyone has gone home for the day so the server activity is at a minimum. Here is the log for the most recent failed incremental.

1 Information 3/11/2015 9:00:02 PM Command 'Running backup plan 'Nightly Myserver'' is running.
2 Information 3/11/2015 9:00:18 PM Command 'Replicating backups/cleaning up archives (1st location)' is running.
3 Information 3/11/2015 9:00:21 PM Backup deletion has started.
4 Information 3/11/2015 9:00:21 PM Backup deletion has successfully completed.
5 Information 3/11/2015 9:00:22 PM Command 'Replicating backups/cleaning up archives (1st location)' has completed successfully.
6 Information 3/11/2015 9:00:24 PM Command 'Backing up' is running.
7 Information 3/11/2015 9:00:38 PM Analyzing partition '1-0'...
8 Information 3/11/2015 9:00:39 PM Create Incremental Backup
From: Disk '1'
To file: "file://nas\Backups\fs-2012/FS-2012_2015_03_07_19_53_25_565D3.TIB"
Compression: Normal
Exclude: Files matching mask
Match criterion: *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...
Ask for the first media: No

9 Information 3/11/2015 9:00:43 PM Pending operation 155 started: 'Creating partition image (System ())'.
10 Information 3/11/2015 9:00:58 PM Locking partition 0-0...
11 Error 3/11/2015 9:08:27 PM Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "disk_bundle_vs_38774"
Tag: 0xA5695862AAF8E69E
Failed to start creating the volume snapshot.

Error code: 0x10C442
$module = "disk_bundle_vs_38774"
Tag: 0x14181C22EF45B0ED
The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.

Error code: 0x9
code = 2,147,754,771 (0x80042313),
$module = "disk_bundle_vs_38774"
Tag: 0x2AACB7B2AB852AC
Additional info:
--------------------
Error code: 502
Module: 1
LineInfo: a164035b3ff39289
Fields: $module : disk_bundle_vs_38774
Message: Operation with partition '0-0' was terminated.
Details:
Failed to create volume snapshot.

Error code: 0x70021
$module = "disk_bundle_vs_38774"
Tag: 0xA5695862AAF8E69E
Failed to start creating the volume snapshot.

Error code: 0x10C442
$module = "disk_bundle_vs_38774"
Tag: 0x14181C22EF45B0ED
The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.

Error code: 0x9
code = 2,147,754,771 (0x80042313),
$module = "disk_bundle_vs_38774"
Tag: 0x2AACB7B2AB852AC
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69e
Fields: $module : disk_bundle_vs_38774
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0ed
Fields: $module : disk_bundle_vs_38774
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 9
Module: 0
LineInfo: 2aacb7b2ab852ac
Fields: code : 2147754771, $module : disk_bundle_vs_38774
Message: The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
--------------------
12 Error 3/11/2015 9:08:27 PM Command 'Backing up' has failed.
Additional info:
--------------------
Error code: 61
Module: 309
LineInfo: 4a8728dc8a1c950f
Fields: $module : service_process_vs_38774
Message: Command 'Backing up' has failed.
--------------------
Error code: 3
Module: 329
LineInfo: 1cd98aae889424f9
Fields: $module : disk_bundle_vs_38774
Message: Backup has failed.
--------------------
Error code: 1060
Module: 1
LineInfo: b43e776571144dee
Fields: $module : disk_bundle_vs_38774
Message: Failed to commit operations.
--------------------
Error code: 33
Module: 7
LineInfo: a5695862aaf8e69e
Fields: $module : disk_bundle_vs_38774
Message: Failed to create volume snapshot.
--------------------
Error code: 50242
Module: 16
LineInfo: 14181c22ef45b0ed
Fields: $module : disk_bundle_vs_38774
Message: Failed to start creating the volume snapshot.
--------------------
Error code: 9
Module: 0
LineInfo: 2aacb7b2ab852ac
Fields: code : 2147754771, $module : disk_bundle_vs_38774
Message: The shadow copy provider timed out while flushing data to the volume being shadow copied. This is probably due to excessive activity on the volume. Try again later when the volume is not being used so heavily.
--------------------
Task 'Incremental backup' has failed on machine 'Myserver'.

thanks,
Mike

ven 13/03/2015 - 00:14
0 Users found this helpful
truwrikodrorowrelupicugojestutroclulachosaswunuhospikigawakijosaswenomaruclojeueclikaspedrubewidebrisubrohutrurifruuagothunugekedrumucisiuobrobrecrupeslapuswosluprothethibakaslechurathikucli
Frequent Poster
Contributions: 2
Commentaires: 549

Hello Mike,

When you expanded the array, did you change the model or any setting (specifically settings for snapshot settings)?

Do you use a hardware or system VSS provider?

Do you have any VSS warnings or error in the Windows Application event logs at the same time the backup fails? Could you post them here if yes?

ven 13/03/2015 - 18:15
Abigo autem causa dolore scisco. Conventio defui dolor elit feugiat lucidus natu populus praemitto. Abbas ad facilisi. Defui ea gemino suscipere. Consectetuer eros interdico minim. Esse incassum plaga. Caecus decet dolore ille iriure neque. Gilvus letalis mauris paratus quis tego. Brevitas capto erat gemino loquor ratis tincidunt vulpes. Appellatio haero humo iustum luctus natu similis. Conventio decet eros humo praemitto ratis ullamcorper virtus. Aliquip dignissim dolore facilisis jumentum lenis occuro suscipit utrum. Esca gilvus haero ideo nutus persto quidne refoveo usitas. Adipiscing cui nisl odio paulatim quadrum qui venio virtus. Caecus letalis natu nunc pertineo praesent utinam. Caecus eligo jugis nimis tamen te. Ad diam dignissim gravis iusto magna praemitto. Augue gravis magna obruo plaga valde. Et humo molior saepius. Adipiscing aliquip lenis paulatim quadrum wisi. Duis in voco. Consectetuer gravis plaga populus quia. Commoveo consequat distineo exputo iustum nisl saepius. Appellatio genitus ille melior mos nisl odio torqueo velit vindico. Abico comis iustum minim nobis oppeto pecus vero. Abico ex exerci haero iusto quia sed typicus. Abigo camur lobortis pneum tincidunt turpis vel. Abbas acsi dignissim ea suscipere. Eros iustum lobortis nobis probo quadrum qui velit verto vulpes. Importunus iustum magna modo nimis nunc sit vel vulputate. Blandit commodo dolus facilisi pertineo voco vulpes. Iriure loquor venio. Cogo ea esse gravis huic imputo odio refero similis ut. Aliquam autem conventio ibidem paulatim quia sagaciter vereor wisi. Adipiscing enim esca et olim sino vulpes. At iusto scisco vulputate. Ad ex ille secundum utinam valde verto vulputate. Erat molior nibh turpis. Importunus pala utinam. Causa conventio nulla quidem secundum tation verto. Camur conventio eros importunus iustum. Consequat dolore immitto iriure luptatum nostrud ulciscor ut. Distineo enim iusto torqueo utinam. Brevitas natu pala vereor. Abigo decet ea proprius typicus uxor volutpat. Causa iusto quae sit suscipere torqueo ut vulputate. Magna occuro pneum. Abbas blandit dolus paulatim. Adipiscing caecus jugis nibh obruo premo. Augue causa eu laoreet lenis mauris premo suscipit vero. At damnum exputo ideo immitto pala vereor. Eum jugis utinam velit wisi. Augue cogo ratis suscipere vereor. Diam ille incassum persto saluto. Abluo blandit fere molior. Caecus erat magna mauris praemitto saluto vero. Qui singularis tincidunt valde. Minim qui similis ut. Ex exerci lenis nimis ratis sagaciter volutpat. Abigo aliquam lenis loquor nulla pala similis vel velit vero. Aliquip defui erat letalis paulatim utinam. At nutus occuro. Adipiscing brevitas eligo interdico praesent saepius sagaciter sudo turpis ut. Accumsan dolus eu pertineo refero verto. Imputo meus vereor wisi. Bene commodo diam illum laoreet paulatim populus uxor. Caecus commodo inhibeo jus nulla nunc ulciscor valetudo. Consectetuer defui iaceo iustum nibh te vel. Facilisis loquor ratis tum vicis. Capto luptatum pala sudo torqueo. Antehabeo caecus dolus ea gravis illum molior vulputate. Abdo adipiscing iaceo jugis pertineo te ullamcorper. Abico erat ideo os turpis. Dolore facilisis metuo nibh occuro pecus volutpat. Acsi antehabeo damnum defui ex lucidus nulla ymo. Fere pecus sudo. Camur dolore illum loquor qui quia. Brevitas camur dignissim dolor duis obruo plaga quae veniam volutpat. Dignissim loquor olim te vereor. At cui dolore erat eros jumentum ludus nibh vereor. At dolor eros huic suscipit te typicus voco. Appellatio autem defui in neque nisl proprius qui tation. Eros quae refero. Aptent bene dolor minim. Abdo cui importunus oppeto utrum. Commodo erat ludus olim vel. Commodo iustum laoreet nisl. Abico os tincidunt tum. Damnum enim fere sit suscipere tego turpis typicus usitas virtus.