Note: You must be registered in order to post a reply. To register, click here. Registration is FREE!
T O P I C R E V I E W
Drac144
Posted - September 05 2014 : 20:16:41 I had a problem, but I managed to solve it after some frustration. Thought I would post this in hopes of helping others with the same issue.
I have an external USB which I use for backup. Actually I have two of them. So, to prevent having Reflect using two different backup definition files I assigned them a share name (the SAME share name) so whichever one is connected and whichever drive letter gets assigned to it I can always access it via the path: \\MYPC\OFFSITE\BACKUP\Current (note that OFFSITE is the share name).
So I got a new, higher capacity, USB drive and went about adding the share name. But when I tried to backup to the drive via Reflect I got a write error. It worked fine when copying files using my file manager (but it was writing to the drive letter not the network path). I changed the backup definition file to use the drive letter and then the backup worked. I was confused but, OK, I had it working. Then I decided to try writing to the network share name using my file manager and IT got a write error. So I assigned the share names to the network path (not to the drive letter path) and then I could use the share name in Reflect as I had previously. I assumed that the share name was assigned to the DRIVE itself but apparently it is assigned based on the access path.
Macrium, you may want to add this clarification to the knowledgebase article related to "cannot write to destination drive" errors.