Hello,  My computer has actually been in sleep mode for the last couple of days.  The last time it was on my backups ran just fine. 

However, upon awakening it, my backups failed with the above error.  I'm not sure why.  All my drives are up and running. 

Also, when I open file explorer (I'm using Windows 10) and click on a folder to which my backups are being saved, I get the following error:
N:\Macrium F Drive Backups is not accessible.  A device which does not exist was specified.

Not sure what is going on since as I said, the last time my computer was on everything ran fine and now it doesn't.

Thanks for any help you can give me.

bruce

+x

 

abrucewebb - 11 May 2020 9:39 AM

Hello,  My computer has actually been in sleep mode for the last couple of days.  The last time it was on my backups ran just fine. 

However, upon awakening it, my backups failed with the above error.  I'm not sure why.  All my drives are up and running. 

Also, when I open file explorer (I'm using Windows 10) and click on a folder to which my backups are being saved, I get the following error:
N:\Macrium F Drive Backups is not accessible.  A device which does not exist was specified.

Not sure what is going on since as I said, the last time my computer was on everything ran fine and now it doesn't.

Thanks for any help you can give me.

bruce

Hi Bruce,

You might want to check if the drive letter of the backup media is still valid with what the program expects. I have a number of externel HD's
and every time I connect a different one, I have to change the drive letter. You can do this simply under Windows via Drive Control or Computer
Control. You can also leave it that way and change the schedule that Macrium is using for the backup. Your choice...

By the way: Macrium is also able to use the UUID of the backup media. There is a setting somewhere in the program. By using this, you have
nothing to do anymore with drive letters.

Hendrick / Amsterdam

That setting is under Edit Defaults > Advanced > Destination Drive Discovery. After making that change you have to edit any existing definition file so Reflect updates its destination path to use a Volume ID.

For my simpler setups, I just manually assign my backup drive a letter far down in the alphabet so Windows remembers that and it never gets auto-assigned to anything else. For deployments that involve a disk rotation, I use USB Drive Letter Manager to make sure that any backup drive in the rotation is always assigned the same drive letter.

I don't know if it applies in your case, but on my new PC I got in January, when the device exists power saving modes, the PC "forgets" the internal mechanical HDD exists until Windows is restarted.

+x

 

Hendrick99 - 11 May 2020 10:17 AM

+x

 

abrucewebb - 11 May 2020 9:39 AM

Hello,  My computer has actually been in sleep mode for the last couple of days.  The last time it was on my backups ran just fine. 

However, upon awakening it, my backups failed with the above error.  I'm not sure why.  All my drives are up and running. 

Also, when I open file explorer (I'm using Windows 10) and click on a folder to which my backups are being saved, I get the following error:
N:\Macrium F Drive Backups is not accessible.  A device which does not exist was specified.

Not sure what is going on since as I said, the last time my computer was on everything ran fine and now it doesn't.

Thanks for any help you can give me.

bruce

Hi Bruce,

You might want to check if the drive letter of the backup media is still valid with what the program expects. I have a number of externel HD's
and every time I connect a different one, I have to change the drive letter. You can do this simply under Windows via Drive Control or Computer
Control. You can also leave it that way and change the schedule that Macrium is using for the backup. Your choice...

By the way: Macrium is also able to use the UUID of the backup media. There is a setting somewhere in the program. By using this, you have
nothing to do anymore with drive letters.

Hendrick / Amsterdam

Thanks Hendrick,

I assigned N and Z to my external backup drives and they were correct.  As it turns out, dbminter had the right solution.  I rebooted and everything worked fine.  Don't know why that is as I have put my computer in sleep mode when not using it for months now since upgrading to Windows 10 and the backups have always run successfully until now.  I can also now access all of my backup folders instead of just some of them.

+x

 

jphughan - 11 May 2020 1:11 PM

That setting is under Edit Defaults > Advanced > Destination Drive Discovery. After making that change you have to edit any existing definition file so Reflect updates its destination path to use a Volume ID.For my simpler setups, I just manually assign my backup drive a letter far down in the alphabet so Windows remembers that and it never gets auto-assigned to anything else. For deployments that involve a disk rotation, I use USB Drive Letter Manager to make sure that any backup drive in the rotation is always assigned the same drive letter.

Thanks jp.  How do I find the unique ID's?  I've done some googling and can't find a straight answer.  Is it the serial number?  Or some other number?
Thanks

+x

 

dbminter - 11 May 2020 2:15 PM

I don't know if it applies in your case, but on my new PC I got in January, when the device exists power saving modes, the PC "forgets" the internal mechanical HDD exists until Windows is restarted.

Thanks db.  That solved the issue though I don't know why it had to be rebooted this time and not for the multiple times for months prior

Don't know if applies to your situation, either, but this only started up after a period of time on my PC.  And it didn't always do that when waking.  Most of the time it did, but sometimes it didn't.


Yeah, when in doubt, first try rebooting. 

+x

 

abrucewebb - 12 May 2020 12:17 AM

Thanks jp.  How do I find the unique ID's?  I've done some googling and can't find a straight answer.  Is it the serial number?  Or some other number?
Thanks

If you configure Reflect to rely on unique identifiers rather than drive letters, then it uses the Volume ID.  That is randomly generated whenever a volume is created (and I believe regenerated whenever it's formatted, but I'm not sure.)  If you really want to see it, there are various ways, one of which is within Reflect itself in the area shown below, where it's displayed in partially truncated form.  But you don't actually have to worry about seeing it.  If you set Reflect to use unique identifiers, then within Reflect you'll still specify your destination by drive letter.  But when Reflect actually stores that configuration in the definition file, it will write the volume identifier of whatever drive had that letter at the time, rather than the actual drive letter as it does by default.  As a result, if you were to close Reflect, assign that drive a different letter, and reopen Reflect, your definition file would magically now be using that drive's new letter as the destination -- because under the hood Reflect is relying on that volume identifier and simply mapping that to whatever volume has that drive letter at any given time.

If you've already got drive letters assigned such that the desired disks always have those letters and nothing else ever accidentally has those letters assigned, then this solution is probably unnecessary complication for you.  The downside to this approach is that if you ever replace your disk, it's not enough to just set the replacement disk to use the same drive letter you were already using.  You instead have to go into Reflect and update your definition file so that it will start using the unique identifier of the new disk.  The volume identifier method is typically used for backup strategies that involve a rotation of multiple destination disks and where you do NOT want to rely on some other tool to ensure consistent drive letter assignment for those disks, as I've chosen to do for various reasons.  And in that case, you would also be using the "Alternative locations" option in your definition file so that you could store multiple volume IDs as "allowed" destinations for your backups, so that whenever a backup ran, Reflect would simply use whichever of those disks was attached at that particular time.

Well, this issue has once again reared its ugly head.

I once more began getting this error message.  I did think it might be because the external drives went to sleep.  I got this error message when attempting a scheduled backup.  I would go to my computer where the drive was listed.  I could open the drive.  I got the same error message when I tried to open any of my backup folders on the drive.  However, I could create a new folder.  I could open that folder.  So, last night I left my computer on (I normally use sleep mode when I'm done for the day).  This morning I tried to run one of my backups and got this error message again.  However, I could open the drive and open all of my backup folders without getting the error.  I just can't run a backup.

It always seems to work right after I reboot.  However, I don't want to have to boot my computer every time I want to use it just to run backups manually.  I like Macrium, but if I have to reboot my computer every time I want to back something up, I will have to look for something else which I don't want to do.

It would seem based on my results last night that the issue isn't with the USB drives, but with Macrium.  All my USB drives were online and accessible with Windows and all of my folders were accessible. 

I have assigned permanent drive letters near the end of the alphabet so there isn't a conflict. 

Thanks in advance