can't make any backups


Author
Message
JoeZ
JoeZ
Junior Member
Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)
Group: Forum Members
Posts: 37, Visits: 72
I'm using V6.1. Yes, I know, it's pretty old but but my PC is too and it and the backups have been working fine for years.

My PC is a Dell XPS desktop system from 2014. The OS is 8.1.

I have several backup shortcuts- to make backups to my 2nd internal drive and to 2 external drives. In the many years I've used Macrium, I think I've only seen 1 or 2 failures - which I somehow repeated and then they backed up successfully.

Today when I run the shortcuts- it always fails. I get a notice in the "tray" to check the log. The following is one of the logs. I get the same regardless of which shortcut I use. I have no idea what's wrong. I compared to the logs of past successful backups and they  look similar.
------------------
(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 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
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 'BITS 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 'COM+ REGDB Writer':
 - Add component \COM+ REGDB
* Writer 'Registry Writer':
 - Add component \Registry
* Writer 'WMI Writer':
 - Add component \WMI
Creating shadow set {b35cfc65-0a21-44b8-9591-fd170e8b0a07} ...
- Adding volume \\?\Volume{a93a84d1-55e1-470d-b0c4-8e0d99411825}\ [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 {b35cfc65-0a21-44b8-9591-fd170e8b0a07} ...

* SNAPSHOT ID = {18bfe189-3a2d-4392-856c-e0d18b9df676} ...
 - Shadow copy Set: {b35cfc65-0a21-44b8-9591-fd170e8b0a07}
 - Original count of shadow copies = 1
 - Original Volume name: \\?\Volume{a93a84d1-55e1-470d-b0c4-8e0d99411825}\ [C:\]
 - Creation Time: 8/23/2022 11:10:27 AM
 - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy17
 - Originating machine: hotrod
 - Service machine: hotrod
 - Not Exposed
 - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
 - Attributes: Auto_Release Differential



capair45
capair45
Macrium Hero
Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)Macrium Hero (2.8K reputation)
Group: Forum Members
Posts: 1.9K, Visits: 18K
The log you want to post is the job log, instead of the VSS log that is shown.


Windows 10 Home (22H2)  Build 19045.4046 (Desktop)
Windows 11 Home (22H2)  Build 22621.1992  (Laptop)
Macrium Reflect 8.1.7847



Edited 23 August 2022 3:57 PM by capair45
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 84K
The above screenshot is from Reflect V8.  On Reflect V6, the job log is the one you see when you click the timestamp instead of choosing the VSS item underneath it.  And that job log is the one we'd need to see.  What you posted above is the VSS log, and that's typically only helpful if the job log cites a failure relating to a VSS snapshot.

And on a side note, even if you don't feel the need to upgrade to V7 or V8, you should really update to the latest release of V6.  Several bugs and even a security vulnerability have been fixed in V6 since the 6.1 days.  And in terms of the "But everything has been working fine" logic, while I do understand that to an extent because I've had cases of updates breaking things that worked before without adding anything that I cared about, you also need to keep in mind that BACKUPS working fine are only half of the story.  You also need RESTORES to work fine if you ever need them, and on that front, Macrium has fixed several bugs since 6.1 that pertain to the Rescue Media environment and restore operations in particular.  I have personally helped people here who needed to restore a dead system and had a much harder time accomplishing that because they were using very outdated Rescue Media and were running up against bugs or limitations that had been fixed long ago in updates they never bothered to install.  They ended up having to jump through additional hoops, typically by getting another working PC to build updated Rescue Media, before they could perform the restore they needed to run.  So again, even if you don't update to V7 or V8, at least get the latest release of V6 -- and then update and retest your Rescue Media so that it's current as well.  If you're running some build of 6.1, that is 5-6 years old at this point, whereas the latest release of V6 is "only" about 3 years old.  While any given update carries some risks of disrupting the status quo, on balance you are generally better off by staying current than not.

Edited 23 August 2022 4:24 PM by jphughan
JoeZ
JoeZ
Junior Member
Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)
Group: Forum Members
Posts: 37, Visits: 72
jphughan - 23 August 2022 4:17 PM
The above screenshot is from Reflect V8.  On Reflect V6, the job log is the one you see when you click the timestamp instead of choosing the VSS item underneath it.  And that job log is the one we'd need to see.  What you posted above is the VSS log, and that's typically only helpful if the job log cites a failure relating to a VSS snapshot.

And on a side note, even if you don't feel the need to upgrade to V7 or V8, you should really update to the latest release of V6.  Several bugs and even a security vulnerability have been fixed in V6 since the 6.1 days.  And in terms of the "But everything has been working fine" logic, while I do understand that to an extent because I've had cases of updates breaking things that worked before without adding anything that I cared about, you also need to keep in mind that BACKUPS working fine are only half of the story.  You also need RESTORES to work fine if you ever need them, and on that front, Macrium has fixed several bugs since 6.1 that pertain to the Rescue Media environment and restore operations in particular.  I have personally helped people here who needed to restore a dead system and had a much harder time accomplishing that because they were using very outdated Rescue Media and were running up against bugs or limitations that had been fixed long ago in updates they never bothered to install.  They ended up having to jump through additional hoops, typically by getting another working PC to build updated Rescue Media, before they could perform the restore they needed to run.  So again, even if you don't update to V7 or V8, at least get the latest release of V6 -- and then update and retest your Rescue Media so that it's current as well.  If you're running some build of 6.1, that is 5-6 years old at this point, whereas the latest release of V6 is "only" about 3 years old.  While any given update carries some risks of disrupting the status quo, on balance you are generally better off by staying current than not.

Thanks for your comments. I agree about upgrading. I've just gotten lazy in my old age but I'll do that soon. So, the problem seems to have gotten resolved. First, I tried doing a full scan with McAfee. After numerous hours I realized it was taking too long so I stopped it. Then, I got a message in my tray saying something like "need to reboot to fix drive errors". So I did that- and voila, my next try for a backup worked. I'll do the upgrade- but also look for a new computer. After 8 years of heavy use- it's time for a new PC.
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 84K
Glad your backups are running again, but I would still take a peek at the job log(s) of the backups that failed.  It's quick to do, and when it comes to something crucial like backups, it's arguably better to understand WHY something failed and has now started working again rather than just noting that those events have both happened.  If you don't understand what caused those changes, you can't really be confident that the behavior you want will persist.

JoeZ
JoeZ
Junior Member
Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)
Group: Forum Members
Posts: 37, Visits: 72
jphughan - 24 August 2022 1:52 PM
Glad your backups are running again, but I would still take a peek at the job log(s) of the backups that failed.  It's quick to do, and when it comes to something crucial like backups, it's arguably better to understand WHY something failed and has now started working again rather than just noting that those events have both happened.  If you don't understand what caused those changes, you can't really be confident that the behavior you want will persist.

jphughan, I appreciate your concern. Below, I've pasted the correct log. I can see that it indicates a disk error. My PC discovered that without me running the chkdsk program- and notified me in the tray that if I reboot, it'll fix itself. Not sure what part of W8.1 managed that. Now, before I paste the log, I have a few questions regarding updating. I'll soon upgrade to the newest version. I really like MR. It has saved me several times with complete restores- while I almost chewed off my fingernails waiting for it to finish- which it did incredibly fast. So, when I download the newest version (I mean V8, not the V6 upgrade)- I know I'll need to update my flashdrive rescue media. I have done 1 or 2 version updates years ago and I was happy that MR had no trouble creating the updated rescue media. I also  have installed some years ago the recovery boot menu option. I think that was after my last V6 update. And I did have a need to use it once for a full restore, successfully. So, if I go from V6 to V8- should I first uninstall MR from my PC? Will that remove the existing recovery boot menu option? Then I just reinstall it from V8?
--------------------
Image ID - 62351CA4256C50E3

--------------------------------------------------------------------------------
Imaging Summary


--------------------------------------------------------------------------------
Backup Definition File: D:\Macrium Reflect after clearning News\boot drive after clearing News.xml
Auto Verify: Y
Maximum File Size: Automatic
Compression: Medium
Password: N
Intelligent Copy: Y
Power Saving: N
Email On Success: N
Email On Failure: N
Total Selected: 128.10 GB


--------------------------------------------------------------------------------
Destination:
Backup Type: Full
File Name: D:\Macrium Reflect after clearning News\62351CA4256C50E3-00-00.mrimg


--------------------------------------------------------------------------------
Operation 1 of 4
Hard Disk: 2
Drive Letter: N/A
File System: FAT32 (LBA)
Label: ESP
Size: 496.0 MB
Free: 470.1 MB
Used: 25.9 MB


--------------------------------------------------------------------------------
Operation 2 of 4
Hard Disk: 2
Drive Letter: N/A
File System: Unformatted
Label:
Size: 128.0 MB
Free: 0 B
Used: 128.0 MB


--------------------------------------------------------------------------------
Operation 3 of 4
Hard Disk: 2
Drive Letter: N/A
File System: NTFS
Label: WINRETOOLS
Size: 750.0 MB
Free: 108.4 MB
Used: 641.6 MB


--------------------------------------------------------------------------------
Operation 4 of 4
Hard Disk: 2
Drive Letter: C
File System: NTFS
Label: OS
Size: 464.38 GB
Free: 337.06 GB
Used: 127.32 GB


--------------------------------------------------------------------------------
Starting Image - Tuesday, August 23, 2022 11:10:25
Initializing
Destination Drive: DATA (DSmile - Free Space 708.27 GB
Free space threshold: Delete oldest backup sets when free space is less than 5.00 GB

Creating Volume Snapshot - Please Wait
Volume Snapshots Created
Analyzing file system on volume
Analyzing file system on volume
Analyzing file system on volume C:
Gathering Windows Events - Please Wait


--------------------------------------------------------------------------------
MFT corrupt - Error code = 6. Please run 'chkdsk C: /r'


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



Edited 26 August 2022 11:13 AM by JoeZ
jphughan
jphughan
Macrium Evangelist
Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)Macrium Evangelist (22K reputation)
Group: Forum Members
Posts: 14K, Visits: 84K
First, I would recommend editing your post to remove your Reflect license key, which is the string of characters at the bottom of the log after the version number.  You can edit your post by clicking the three vertical dots in the upper-right corner of your post and selecting Edit Post.

But in terms of the substance of your post, yes if you enter "CHKDSK C: /R" in Command Prompt, you'll be prompted to reboot for the scan to complete.  Sometimes Windows for some reason skips over scheduled CHKDSK scans during a reboot, but if it performs the scan, be aware that it can take a while.  That /R parameter causes it to scan all sectors within the scope of the C drive for errors, which can take a while, so plan accordingly.  But if that has already completed and backups are running again, then I guess you don't have to do that at this point.

In terms of upgrading to V8, you don't have to uninstall V6 first or even disable the boot menu option.  Just run the V8 installer.  It will carry over all of your V6 settings.  Once you launch V8, open Rescue Media Builder.  That will look quite different from what you're used to because Macrium overhauled it for Reflect 7.2, but I find the new interface to be much easier and more efficient to navigate.  In many cases you can build Rescue Media in one click rather than stepping through a bunch of dialogs.  But essentially, when you launch Rescue Media Builder for the first time after upgrading, you'll see a prompt telling you that your boot menu option is currently using an older version of Reflect than what you've got installed, and asking if you want to update it.  Click Yes and wait a moment, and your boot menu will be using V8.  From there, if you select your flash drive in the target list and click Build, you'll get that updated too.  The same behavior will occur going forward if you ever install smaller updates within the V8 "track".

Other things you'll probably notice right away include the Existing Backups view that replaces the Restore view, which has also been redesigned to (in my opinion) make better use of space and show more content in a more organized fashion, as well as the redesigned Log tab that makes it much easier to see individual job logs, since you no longer need to expand every individual date entry to see what logs might exist for that day, and you also get more options for filtering logs.

But of course if you run into any issues or have any questions, we'll be here. Smile

JoeZ
JoeZ
Junior Member
Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)Junior Member (69 reputation)
Group: Forum Members
Posts: 37, Visits: 72
jphughan - 25 August 2022 2:53 PM
First, I would recommend editing your post to remove your Reflect license key, which is the string of characters at the bottom of the log after the version number.  You can edit your post by clicking the three vertical dots in the upper-right corner of your post and selecting Edit Post.

But in terms of the substance of your post, yes if you enter "CHKDSK C: /R" in Command Prompt, you'll be prompted to reboot for the scan to complete.  Sometimes Windows for some reason skips over scheduled CHKDSK scans during a reboot, but if it performs the scan, be aware that it can take a while.  That /R parameter causes it to scan all sectors within the scope of the C drive for errors, which can take a while, so plan accordingly.  But if that has already completed and backups are running again, then I guess you don't have to do that at this point.

In terms of upgrading to V8, you don't have to uninstall V6 first or even disable the boot menu option.  Just run the V8 installer.  It will carry over all of your V6 settings.  Once you launch V8, open Rescue Media Builder.  That will look quite different from what you're used to because Macrium overhauled it for Reflect 7.2, but I find the new interface to be much easier and more efficient to navigate.  In many cases you can build Rescue Media in one click rather than stepping through a bunch of dialogs.  But essentially, when you launch Rescue Media Builder for the first time after upgrading, you'll see a prompt telling you that your boot menu option is currently using an older version of Reflect than what you've got installed, and asking if you want to update it.  Click Yes and wait a moment, and your boot menu will be using V8.  From there, if you select your flash drive in the target list and click Build, you'll get that updated too.  The same behavior will occur going forward if you ever install smaller updates within the V8 "track".

Other things you'll probably notice right away include the Existing Backups view that replaces the Restore view, which has also been redesigned to (in my opinion) make better use of space and show more content in a more organized fashion, as well as the redesigned Log tab that makes it much easier to see individual job logs, since you no longer need to expand every individual date entry to see what logs might exist for that day, and you also get more options for filtering logs.

But of course if you run into any issues or have any questions, we'll be here. Smile

Thanks! This forum is great. I've asked other questions here over the years and always got excellent replies and quickly too. That's certainly not true for many other computer related forums.
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