Sudden increase in warnings.

Post here if you have problems installing or using FBackup
fullerdf
Posts: 48
Joined: Mon May 07, 2012 4:43 pm

Postby fullerdf » Sun Aug 26, 2012 7:40 pm

I have been using fBackup successfully for months on my Win 7 laptop to create a mirror in a shared public folder on my Win 7 desktop machine via a wireless home network. Everything seemed to be working fine so thanks to the fBackup team.


However, yesterday the backup completed with warnings at the usual time (2PM). In the past that happened sometimes when I am using my machine and some of the files to be backed up are in use. But running the job again manually after closing down work activities would complete the backup successfully.


Yesterday when I ran the job manually to correct warnings, the job did not complete successfully. Rather it had 20 warnings (20 files were to be backed up) even though the tasks that had been open were closed and files not in use.


I then tried rebooting and ran the backup again. Same result.


I then tried manually copying the files to the backup folders. Did not have permission according to Windows.


Here is one of the warnings from the job log -- [ Warning: Skipping file C:\Users\Public\Documents\Drilling Data\Near Socrates\Unleased.pdf

Destination error (code 5). Access is denied. (\\NOTINGHAM\Documents\New Crossbow Daily\FBackup\C\Users\Public\Documents\Drilling Data\Near Socrates\Unleased.pdf). \\NOTINGHAM\Documents\New Crossbow Daily\FBackup\C\Users\Public\Documents\Drilling Data\Near Socrates\Unleased.pdf.]


It seems that access to the backup is denied even though both the backup file and file to be backed up reside in Public shared folders. It also seems that the permissions for the folders may have changed somehow. I can not even copy the files or a zip of the files manually from the public folders on my laptop to the desktop.


Any ideas?



fullerdf
Posts: 48
Joined: Mon May 07, 2012 4:43 pm

Postby fullerdf » Tue Aug 28, 2012 5:08 am

Now it is up to 30 warnings.



fullerdf
Posts: 48
Joined: Mon May 07, 2012 4:43 pm

Postby fullerdf » Tue Aug 28, 2012 5:09 am

No new files will be backed up.



Softland
Posts: 1650
Joined: Thu May 23, 2013 7:57 am

Postby Softland » Tue Aug 28, 2012 5:24 pm

Hi,


Have you checked the permissions for the source folder?



fullerdf
Posts: 48
Joined: Mon May 07, 2012 4:43 pm

Postby fullerdf » Wed Aug 29, 2012 2:25 am

How did permissions change and what were they (should they be)? If I can figure out how to check them/change them, why would that cause an issue with the destination as shown in the log? The log says "Destination error (code 5). Access is denied."


Please direct me to a link that tells how to check permissions and how to set them for "public" "shared" folders.



Softland
Posts: 1650
Joined: Thu May 23, 2013 7:57 am

Postby Softland » Wed Aug 29, 2012 2:45 pm

Hi,


To check the permission: try to manually copy a source file to destination using Windows Explorer.

If you cannot do that, you have a permission issue that needs to be fixed. If you don't know how to fix it, please ask a computer specialist to assist you.



fullerdf
Posts: 48
Joined: Mon May 07, 2012 4:43 pm

Postby fullerdf » Mon Sep 03, 2012 1:25 am

As indicated earlier, manual copy to the Public Documents folder were not possible due to a permissions issue.


However, I was able to get the permissions on the Public Documents folder of my desktop machine reset to allow backups to run (as well as manual copy and paste of files.


Now the FBackup is working again. For others who may see this issue and need help fixing it here is what I did.


On the destination drive I selected the Public folder and right clicked.


I selected the Properties option then the Sharing tab and clicked on the Share button.


Note the backup had been working fine until about a week ago so I have no idea why the permissions changed. My only guess is that something happened while letting Windows Update install the updates and patches that were available at about that time. Hope this helps.




Return to “Troubleshooting”