I just installed Areca today. I was able to make a full backup of my D
drive without issue, but there is a problem with backups of the C
drive. Both C drive backup operations failed, because the backup
application did not have access to a file. Why would the failure to
access a single file cause the entire backup operation to fail? I do
not know why the protection on the files was set so strictly, but I did
not change it.
Am I doing something wrong; is there a setting that can direct to Areca
to log the error, but continue with the backup?
When the first failure occurred, I changed the protection on the
offending file and restarted the backup. Then 3.5 hours later the same
error, but with a different file, caused the backup to fail again.
However, checking the file that caused the second failure showed that I
had full access to the file which is a file in the
C:\ProgramData\Microsoft\Crypto\Keys folder.
If there are lots of files with restricted permissions and it takes me
3+ hours to find each file, getting a complete backup could take weeks.
Any suggestions?
Rick
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
bumped into this by searching another info. it says that it can not backup files that are in use by system. this is not system imaging program but data backup program. so you should be ok with backing up My Documents/Documents and such that hold user created data.
For system backup you need to boot into some kind of live session (i.e. into another working operating system) and then do an image of the OS (whole disk or partition). Suggest you look at Clonezilla for that or if you want a friendlier interface try Redo Backup. Both are free and will boot Linux to ram and then enable the backup of the OS.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi,
I just installed Areca today. I was able to make a full backup of my D
drive without issue, but there is a problem with backups of the C
drive. Both C drive backup operations failed, because the backup
application did not have access to a file. Why would the failure to
access a single file cause the entire backup operation to fail? I do
not know why the protection on the files was set so strictly, but I did
not change it.
Am I doing something wrong; is there a setting that can direct to Areca
to log the error, but continue with the backup?
When the first failure occurred, I changed the protection on the
offending file and restarted the backup. Then 3.5 hours later the same
error, but with a different file, caused the backup to fail again.
However, checking the file that caused the second failure showed that I
had full access to the file which is a file in the
C:\ProgramData\Microsoft\Crypto\Keys folder.
If there are lots of files with restricted permissions and it takes me
3+ hours to find each file, getting a complete backup could take weeks.
Any suggestions?
Rick
bumped into this by searching another info. it says that it can not backup files that are in use by system. this is not system imaging program but data backup program. so you should be ok with backing up My Documents/Documents and such that hold user created data.
For system backup you need to boot into some kind of live session (i.e. into another working operating system) and then do an image of the OS (whole disk or partition). Suggest you look at Clonezilla for that or if you want a friendlier interface try Redo Backup. Both are free and will boot Linux to ram and then enable the backup of the OS.