![]() ![]() Since the big VBK changes each day, robocopy is going to re-copy all data each night instead of just the incremental data, which will take too long. The problem with this, for my scenario, is that the next phase of my plan was to setup some robocopy jobs to mirror my backup folders to an offsite location each night. I did some more reading here and in the FAQs and now understand that each night it is having to pull out the changed bytes and write them to the VBR files, and is injecting the new changes back into the VBK. I didn't fully understand the reversed incremental process and just noticed that the VBK is changing size each night. The plan seems to be working fine, for what it is. I've been using the reversed incremental and have my 3 sets of jobs setup to accomplish this. I couldn't figure out how to stop that until I just selected the D: drive (USB) without any folders and, then, it all came together.As I posted before, I am trying to setup multiple jobs so that I can have varied retention cycles (son-father-grandfather type). The first few times, I had already created a new folder on my USB drive and found that FBackup created another new folder under my new folder based on the info provided in the backup profile setup. I will continue to experiment with FBackup and one other free program I downloaded during my extreme frustration with FBackup to see which one I might prefer to use going forward.īTW, I think checking the sub-folder box simply means that FBackup creates a folder on the USB drive for the backup. At least, I got the "SUCCESS" message instead of the warning one. I don't know why the log file shows all those deletions but FBackup seems to have worked for me this time. The fast mirror saved only the new files (as advertised) and the delete function showed that a HUGE amount of other files were deleted from the LOG FILE but NOT the USB thumb drive. Then, I changed some files and ran it again. Today, as well, I cleared one of my USB thumb drives one more time, selected all four of the boxes in mirror and ran another new 2.5 hour backup. In all fairness, I do NOT think it was FBackup's fault. Today, I resolved my Testing WARNING issue by DELETING the offending file from my computer. I don't know, also, if the NEW v.7 is MORE sensitive during the testing phase or not but, AGAIN, I was WARNED about the same file "CRC stored in catalog is 1B0D685A, destination is D06D2AD7." This, what used to be a simple process, is getting extremely frustrating. SO, I am completely dumbfounded at the moment. Today (10/14/17), I tried to run FBackup for that same result, after having done a completely new backup last night, and FBackup started another completely new backup again instead of loading only the new, changed files. Historically, I've always use the delete function box with the mirror selection and it has worked fine, deleting only the old, unused files I had previously loaded and loading only the new or changed files while leaving the old unchanged files alone. ![]() I guess that is why I ended up saving ONLY the new files and deleting the ones already in the catalog. I have no idea what to do about that except try to run a brand new backup with the selections like "fast" mirror and sub-folder boxes NOT checked to see if that changes thing back to "normal." That is happening as I type this response to your question.Ĭlarification: I had also check the box for Delete Removed and whatever files when I ran "fast" mirror. exe files warning me after the testing process was done that "CRC stored in catalog is 966BED32, destination is BE6D7D6B" and 1B0D685A is D06D2AD7. Neither did I check the box on sub-folders because I have no clue what that does to a backup which had been working fine until version 7.Īlso, since v.7, I've gotten warnings on files which backed up perfectly before with v.6. I've redone my backups about 5 times, now, trying to figure out what I was doing wrong before I realized I should never have checked the "fast" box. Well, checking the box for "fast" mirror seemed better to me until I totally messed up my backups by only backing up the changed files and totally deleting all of the rest of my files because they were not new or changed. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |