Backup aborted! - Error Code 64?


Author
Message
lovelyjubbly
lovelyjubbly
Talented Member
Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)
Group: Forum Members
Posts: 78, Visits: 288
I'm getting this error on a user's machine, I googled but found nothing, any ideas?

Backup aborted! - '33C887D3C031CF26-04-04.mrimg' Verification failed at 13% (Error reading 113023 bytes from file. Error code = 64)

The vss log:

(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 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 file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- Get file list descriptors
- Get database descriptors
- Get log descriptors
- 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 'Shadow Copy Optimization Writer' since it has no selected components for restore.
- Excluding writer 'MSSearch Service 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
* Writer 'MSMQ Writer (MSMQ)':
 - Add component \config
 - Add component \storage
* Writer 'IIS Config Writer':
 - Add component \IISCONFIG
Creating shadow set {4f46d62b-3605-41f8-b49e-447aa3a2cabf} ...
- Adding volume \\?\Volume{80668dc6-6f57-11e4-a4c7-806e6f6e6963}\ [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 succesfully created.
Saving the backup components document ...

List of created shadow copies:


Querying all shadow copies with the SnapshotSetID {4f46d62b-3605-41f8-b49e-447aa3a2cabf} ...

* SNAPSHOT ID = {96c42509-87e0-4977-b331-14eeddb0f556} ...
 - Shadow copy Set: {4f46d62b-3605-41f8-b49e-447aa3a2cabf}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{80668dc6-6f57-11e4-a4c7-806e6f6e6963}\ [C:\]
 - Creation Time: 13/03/2018 10:00:51 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy4
 - Originating machine: Rebeka-2015
 - Service machine: Rebeka-2015
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential


Windows Events
*****************************
Date  13/03/2018 10:18:22 AM
Type  Error
Event  0
Source  irstrtsv



*****************************
Date  13/03/2018 10:13:22 AM
Type  Error
Event  0
Source  irstrtsv



*****************************
Date  13/03/2018 10:08:22 AM
Type  Error
Event  0
Source  irstrtsv



*****************************
Date  13/03/2018 10:03:22 AM
Type  Error
Event  0
Source  irstrtsv




jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)Macrium Evangelist (5.9K reputation)
Group: Forum Members
Posts: 4K, Visits: 29K
The job log would be more helpful than the VSS log and Event Viewer entries for this, but is that 04-04 file a file that was created during the backup job and subsequently failed verification (do you have verification enabled for your backups?) or is 04-04 a file that already existed at the destination? If the former, your system apparently isn’t writing backup files properly, or isn’t reading them back properly. If backups are going to a USB drive, try replacing the cable or the drive itself. If it’s the latter, then the existing 04-04 file may be damaged, which might prevent appending new Incrementals from it, in which case you may need to delete that 04-04 file to have a new Incremental built off the previous backup, or else start a new Full.
Edited 13 March 2018 12:55 AM by jphughan
lovelyjubbly
lovelyjubbly
Talented Member
Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)
Group: Forum Members
Posts: 78, Visits: 288
jphughan - 13 March 2018 12:51 AM
The job log would be more helpful than the VSS log and Event Viewer entries for this, but is that 04-04 file a file that was created during the backup job and subsequently failed verification (do you have verification enabled for your backups?) or is 04-04 a file that already existed at the destination? If the former, your system apparently isn’t writing backup files properly, or isn’t reading them back properly. If backups are going to a USB drive, try replacing the cable or the drive itself. If it’s the latter, then the existing 04-04 file may be damaged, which might prevent appending new Incrementals from it, in which case you may need to delete that 04-04 file to have a new Incremental built off the previous backup, or else start a new Full.

Thank you for that advice Smile
I've started a Full Backup and we'll see how we go.
Nick
Nick
Macrium Representative
Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)Macrium Representative (3K reputation)
Group: Administrators
Posts: 1.7K, Visits: 9.2K
lovelyjubbly - 13 March 2018 2:00 AM
jphughan - 13 March 2018 12:51 AM
The job log would be more helpful than the VSS log and Event Viewer entries for this, but is that 04-04 file a file that was created during the backup job and subsequently failed verification (do you have verification enabled for your backups?) or is 04-04 a file that already existed at the destination? If the former, your system apparently isn’t writing backup files properly, or isn’t reading them back properly. If backups are going to a USB drive, try replacing the cable or the drive itself. If it’s the latter, then the existing 04-04 file may be damaged, which might prevent appending new Incrementals from it, in which case you may need to delete that 04-04 file to have a new Incremental built off the previous backup, or else start a new Full.

Thank you for that advice Smile
I've started a Full Backup and we'll see how we go.

Error 64 is  ERROR_NETNAME_DELETED

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

It appears the the network connection dropped during verification.

Kind Regards

Nick - Macrium Support

RayG
RayG
Advanced Member
Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)Advanced Member (554 reputation)
Group: Forum Members
Posts: 277, Visits: 1.3K
Nick - 13 March 2018 9:48 AM

Error 64 is  ERROR_NETNAME_DELETED

https://msdn.microsoft.com/en-us/library/windows/desktop/ms681382(v=vs.85).aspx

It appears the the network connection dropped during verification.

As a quick way to get the error message you can use this in a powershell prompt:

([ComponentModel.Win32Exception][Int]64).Message

For the error the OP had '64' it returns:

"The specified network name is no longer available"

You need the [int] because it's a decimal and it looks like a [string]. If you have a HEX number you can just use:

([ComponentModel.Win32Exception]0x40).Message

Which is the same error as above but the value supplied as HEX '0x40' where '0x'  to Windows means Base 16 (HEX)
Which is '01000000' in Binary Base 2

You can also use the convert function:

[convert]::ToInt32("40",16)

which returns 64 as the value

Win the above example "40" is the HEX value and 16 is the base

So to convert a Binary value it would look like this:

[convert]::ToInt32("1000000",2)

Binary being to Base '2' so you can do this:

([ComponentModel.Win32Exception][convert]::ToInt32("1000000",2)).Message

and we get the same message: 'The specified network name is no longer available' as the result.

I hope that may be useful to others in the future,



Regards
RayG
Windows10 Pro X64 V1809 B17763.194 MR v7.2.3906

lovelyjubbly
lovelyjubbly
Talented Member
Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)Talented Member (152 reputation)
Group: Forum Members
Posts: 78, Visits: 288
Thanks everyone, you've been very helpful Smile

I ran a full backup yesterday and it went fine.

Best wishes, Martin

GO

Merge Selected

Merge into selected topic...



Merge into merge target...



Merge into a specific topic ID...




Similar Topics

Reading This Topic

Login

Explore
Messages
Mentions
Search