intermittent failures - Backup to NAS


Author
Message
Tech Addicts
Tech Addicts
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 11
Hi Team,
We have been having intermittent issues with a Macrium backup to a Synology NAS i was hoping someone could help me understand what the issue is?

Backup aborted! - Write operation failed - An unexpected network error occurred.

I have had a look at the VSS log and it appears the only issue is macrium not being able to write to a LOG file. Can someone please give me an understanding of what is happening with this backup as it appears to be failing at random.

Please see attached a recent log file.


x(Gathering writer metadata...)
(Waiting for the asynchronous operation to finish...)
Initialize writer metadata ...
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get exclude files
- Enumerate components
- Get exclude files
- Enumerate components
- Get file list descriptors
- Get database descriptors
- Get log descriptors
Discover directly excluded components ...
- Excluding writer '' since it has no selected components for restore.
- Excluding writer '' since it has no selected components for restore.
- Excluding writer 'MSSearch Service Writer' since it has no selected components for restore.
- Excluding writer 'Shadow Copy Optimization Writer' since it has no selected components for restore.
Discover components that reside outside the shadow set ...
Discover all excluded components ...
Discover excluded writers ...
Discover explicitly included components ...
Verifying explicitly specified writers/components ...
Select explicitly included components ...
* Writer 'Task Scheduler Writer':
 - Add component \TasksStore
* Writer 'VSS Metadata Store Writer':
 - Add component \WriterMetadataStore
* Writer 'Performance Counters Writer':
 - Add component \PerformanceCounters
* Writer 'Registry Writer':
 - Add component \Registry
* Writer 'COM+ REGDB Writer':
 - Add component \COM+ REGDB
* Writer 'WMI Writer':
 - Add component \WMI
Creating shadow set {b24af1d1-b759-440d-b0e1-25722998a10f} ...
- Adding volume \\?\Volume{0c2b2178-7337-4cb7-ab0c-94d15e532f39}\ [I:\] to the shadow set...
- Adding volume \\?\Volume{051c79c8-0ff6-49f4-af86-d6bfd65274cb}\ [C:\] to the shadow set...
Preparing for backup ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Creating the shadow (DoSnapshotSet) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)
Shadow copy set successfully created.
Saving the backup components document ...

List of created shadow copies:


Querying all shadow copies with the SnapshotSetID {b24af1d1-b759-440d-b0e1-25722998a10f} ...

* SNAPSHOT ID = {85f4c98a-149d-4303-84e8-6eb9fc22536d} ...
 - Shadow copy Set: {b24af1d1-b759-440d-b0e1-25722998a10f}
 - Original count of shadow copies = 2
 - Original Volume name: \\?\Volume{0c2b2178-7337-4cb7-ab0c-94d15e532f39}\ [I:\]
 - Creation Time: 25/07/2020 9:40:13 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy23
 - Originating machine: 1-Server
 - Service machine: 1-Server
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential

* SNAPSHOT ID = {e14f6bed-b9ab-4bcf-ab95-badf95524830} ...
 - Shadow copy Set: {b24af1d1-b759-440d-b0e1-25722998a10f}
 - Original count of shadow copies = 2
 - Original Volume name: \\?\Volume{051c79c8-0ff6-49f4-af86-d6bfd65274cb}\ [C:\]
 - Creation Time: 25/07/2020 9:40:13 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy24
 - Originating machine: 1-Server
 - Service machine: 1-Server
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential


Windows Events
*****************************
Date:  26/07/2020 3:41:59 AM
Type:  Error
Event:  455
Source:  ESENT

svchost (8328,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

*****************************
Date:  25/07/2020 6:55:55 PM
Type:  Error
Event:  455
Source:  ESENT

svchost (1724,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

*****************************
Date:  25/07/2020 6:01:09 PM
Type:  Error
Event:  455
Source:  ESENT

svchost (10972,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.

*****************************
Date:  25/07/2020 5:55:56 PM
Type:  Error
Event:  455
Source:  ESENT

svchost (6832,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile C:\WINDOWS\system32\config\systemprofile\AppData\Local\TileDataLayer\Database\EDB.log.


Edited 29 July 2020 10:56 PM by Tech Addicts
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)Macrium Evangelist (10K reputation)
Group: Forum Members
Posts: 7.3K, Visits: 52K
The VSS log isn't going to have information about this.  If you don't see any errors specifically relating to the VSS snapshot, which is captured before any data starts getting backed up, then you don't have to worry about the VSS log.  In terms of the error you're seeing in the main job log, every time I've seen somebody ask about that error when backing up to a network location, the answer from Macrium Support is that it's an error passed up from the Windows API that Reflect relies on for writing a file to the network, and it's caused by even a network connectivity interruption, even if it's only momentary.  Unfortunately Reflect at the moment doesn't seem to have any sort of graceful handling of network interruptions; the job just dies -- which is unfortunate because Reflect backups for most users will generate a lot more network traffic than other tasks they perform, which can make induce network interruptions even if the environment is stable under less intensive loads.

In terms of what to do about it, if you haven't already, try updating network card drivers and NAS firmware.  If you're on Ethernet, maybe swap cables.  If you're on WiFi, that's adds a whole other dimension of possible causes of brief connection interruptions.

Tech Addicts
Tech Addicts
New Member
New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)New Member (3 reputation)
Group: Forum Members
Posts: 2, Visits: 11
jphughan - 29 July 2020 11:22 PM
The VSS log isn't going to have information about this.  If you don't see any errors specifically relating to the VSS snapshot, which is captured before any data starts getting backed up, then you don't have to worry about the VSS log.  In terms of the error you're seeing in the main job log, every time I've seen somebody ask about that error when backing up to a network location, the answer from Macrium Support is that it's an error passed up from the Windows API that Reflect relies on for writing a file to the network, and it's caused by even a network connectivity interruption, even if it's only momentary.  Unfortunately Reflect at the moment doesn't seem to have any sort of graceful handling of network interruptions; the job just dies -- which is unfortunate because Reflect backups for most users will generate a lot more network traffic than other tasks they perform, which can make induce network interruptions even if the environment is stable under less intensive loads.

In terms of what to do about it, if you haven't already, try updating network card drivers and NAS firmware.  If you're on Ethernet, maybe swap cables.  If you're on WiFi, that's adds a whole other dimension of possible causes of brief connection interruptions.

Thank you for your reply and clearing this one up. I will try the steps provided and see how we go.

Kind Regards
Scot
GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Reading This Topic

Login

Explore
Messages
Mentions
Search