Odd behaviour after Windows reinstall
After a long fight I'd finally got my backups working as I wanted them, then Windows (8.1) update failed and left me with an unbootable system. Once Windows was running again everything had to be reinstalled.
System: Windows 8.1, Backup4all 5.2.
First requirement:
Source: C:\Users\Anne\Documents\LydgateDesign\Projects
Destination: X:\LydgateDesign\Projects (mapped drive from NAS)
Type: Differential or Smart (recommendation welcome)
Problem:
"Backup aborted. Reason:
Cannot create folder "X:\LydgateDesign\Projects". The system cannot find the path specified"
If I specify X:\LydgateDesign\Projects\ (trailing slash) it fails with
"Backup aborted. Reason:
Cannot create folder "X:\LydgateDesign\Projects\Projects". The system cannot find the path specified"
Any ideas?
Anne
System: Windows 8.1, Backup4all 5.2.
First requirement:
Source: C:\Users\Anne\Documents\LydgateDesign\Projects
Destination: X:\LydgateDesign\Projects (mapped drive from NAS)
Type: Differential or Smart (recommendation welcome)
Problem:
"Backup aborted. Reason:
Cannot create folder "X:\LydgateDesign\Projects". The system cannot find the path specified"
If I specify X:\LydgateDesign\Projects\ (trailing slash) it fails with
"Backup aborted. Reason:
Cannot create folder "X:\LydgateDesign\Projects\Projects". The system cannot find the path specified"
Any ideas?
Anne
-
- Posts: 1944
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Odd behaviour after Windows reinstall
Hi,
Can you manually create this folder: X:\LydgateDesign\Projects\Projects ?
Can you manually create this folder: X:\LydgateDesign\Projects\Projects ?
Re: Odd behaviour after Windows reinstall
Yes indeed - though of course that's not what I want to do.
-
- Posts: 1944
- Joined: Wed Dec 16, 2009 12:46 pm
Re: Odd behaviour after Windows reinstall
Hi,
Do you have the same problem if you start Backup4all using the "Run as administrator" option?
Do you have the same problem if you start Backup4all using the "Run as administrator" option?
Re: Odd behaviour after Windows reinstall
Earlier this week in my search for solutions I set the target to X:\LydgateDesign\ hoping it would find the subdirectory Projects and write into that. Since then I've been getting success notices, saying that the backup completed having found 0 files and 0 folders to back up. There are definitely files and folders that have been added since that directory was last written to.
Sample report:
[12/12/2014 17:55:09] Checking backup destination (Local hard drive)
[12/12/2014 17:55:09] Opening file "C:\Users\Anne\AppData\Roaming\Softland\Backup4all 5\Catalogs\Projects(1).bkc"
[12/12/2014 17:55:09] Checking if the drives of the sources exist
[12/12/2014 17:55:09] Checking backup destination (Local hard drive)
[12/12/2014 17:55:09] Creating the list of files to backup
[12/12/2014 17:55:09] Opening file ":memory:"
[12/12/2014 17:55:09] Cannot use USN journal for this backup. Reason: USN journal disabled in settings
[12/12/2014 17:55:09] Folders found to backup: 0
[12/12/2014 17:55:09] Files found to backup: 0 (0 bytes)
Next scheduled backup: 12/12/2014 18:17:28
Backup completed in 2 second(s) at 12/12/2014 17:55:09 with 0 error(s), 0 warning(s)
[12/12/2014 17:55:09] Sending mail to "[email protected]"
I've run the program as administrator, though it normally runs as user, with exactly the same result.
I'm suspicious of that catalogue name quoted. In C:\Users\Anne\AppData\Roaming\Softland\Backup4all 5\Catalogs there is a Projects.bkc dated a month ago, and there was a Projects(1).bkc. Thinking this may be a corrupt catalogue I renamed it. The latest run (quoted above) has recreated Projects(1).bkc. Incidentally, I had asked for that one to be a full backup, again, in an attempt to side-step any legacy problems.
My gut feeling is that I need to somehow clear out all its memory of what has gone before, so that a clean full backup stands a better chance of being correct.
Sample report:
[12/12/2014 17:55:09] Checking backup destination (Local hard drive)
[12/12/2014 17:55:09] Opening file "C:\Users\Anne\AppData\Roaming\Softland\Backup4all 5\Catalogs\Projects(1).bkc"
[12/12/2014 17:55:09] Checking if the drives of the sources exist
[12/12/2014 17:55:09] Checking backup destination (Local hard drive)
[12/12/2014 17:55:09] Creating the list of files to backup
[12/12/2014 17:55:09] Opening file ":memory:"
[12/12/2014 17:55:09] Cannot use USN journal for this backup. Reason: USN journal disabled in settings
[12/12/2014 17:55:09] Folders found to backup: 0
[12/12/2014 17:55:09] Files found to backup: 0 (0 bytes)
Next scheduled backup: 12/12/2014 18:17:28
Backup completed in 2 second(s) at 12/12/2014 17:55:09 with 0 error(s), 0 warning(s)
[12/12/2014 17:55:09] Sending mail to "[email protected]"
I've run the program as administrator, though it normally runs as user, with exactly the same result.
I'm suspicious of that catalogue name quoted. In C:\Users\Anne\AppData\Roaming\Softland\Backup4all 5\Catalogs there is a Projects.bkc dated a month ago, and there was a Projects(1).bkc. Thinking this may be a corrupt catalogue I renamed it. The latest run (quoted above) has recreated Projects(1).bkc. Incidentally, I had asked for that one to be a full backup, again, in an attempt to side-step any legacy problems.
My gut feeling is that I need to somehow clear out all its memory of what has gone before, so that a clean full backup stands a better chance of being correct.
Re: Odd behaviour after Windows reinstall
In fact much of what has been said was pure "red herring". As recommended elsewhere I changed my local password to match the pw on the NAS. Since then it has been possible to backup files to the NAS and from the NAS to a local USB drive. Clearly the problem lies in Windows Scheduler not passing my credentials for the NAS, even though I set them carefully.
Thanks for trying to help.
Thanks for trying to help.