Unsolved
This post is more than 5 years old
3 Posts
0
3339
October 19th, 2017 01:00
backup failing with below error,tried renaming cache file,it didn't worked
17-10-19 03:27:50 avtar Info <8688>: Status 2017-10-19 03:27:50, 97,743 files, 29,999 folders, 33.53 GB (97,743 files, 0 bytes, 0.00% new) 213MB 20% CPU (1 open files) C:\Windows\winsxs\ManifestCache\548c1bd2e27235ea_blobs.bin 2017-10-19 03:32:16 avtar Error <0000>: I/O error failed when writing to a file in a container for backup, length 1259 bytes at offset 36135124864, remaining bytes 1259 2017-10-19 03:32:21 avtar FATAL <5352>: MAIN: Unhandled standard exception failed when writing to a file in a container for backup, length 1259 bytes at offset 36135124864, remaining bytes 1259 2017-10-19 03:32:22 avtar Info <9772>: Starting graceful (staged) termination, error reported in nbackmain (wrap-up stage) 2017-10-19 03:32:22 avtar Info <7883>: Finished at 2017-10-19 03:32:22 Eastern Daylight Time, Elapsed time: 0001h:05m:34s 2017-10-19 03:32:22 avtar Info <17971>: Errors, cancellation or termination caused the backup to not be posted on the DDR 2017-10-19 03:32:22 avtar Info <12530>: Backup was not committed to the DDR. 2017-10-19 03:32:22 avtar Info <19165>: Staging can run is false, possibly due to cancel, inform ddboost 2017-10-19 03:32:22 avtar Info <40176>: - Multi-stream restore summary (current 0, max active 0, max cloned 0, total cloned 0, ddr handle 1): 2017-10-19 03:32:22 avtar Info <19166>: Staging can run is false, successfully informed ddboost 2017-10-19 03:32:26 avtar Info <6149>: Error summary: 2 errors: 5352, 0 2017-10-19 03:32:26 avtar Info <8468>: Sending wrapup message to parent 2017-10-19 03:32:26 avtar Info <5314>: Command failed (2 errors, exit code 10007: miscellaneous error)
END avtar log 2017-10-19 03:32:29 Eastern Daylight Time (0 warnings, 2 errors, 1 fatal error)
No Events found!
Avamar Exorcist
462 Posts
0
October 21st, 2017 03:00
The error in the log is reminiscent of KB 465816 where the cache file was corrupted and it was recommended to rename the existing cache file to allow a new one to be built.
If the log extract given above was taken from the backup which ran after the cache file was renamed I'd suggest opening an SR with Support and providing a log bundle from the client as described in KB 470483
Anu99
3 Posts
0
October 23rd, 2017 00:00
thanks for the response.The above logs are after making changes.I will try this.