![]() ![]() What I'm wanting to do, is avoid having to manually alter said path in the backup's job settings, each time I use it in a different system. ![]() I already tried to exclude said folder by starting with an empty list, adding an exclusion filter that matches "*.default" folder names, and another filter that includes all the rest of files/folders, but it didn't worked.Īug 21, 2019It's alright, I'm already using this really simple backup job, which involves no sophistication at all, but I'm wondering if the above issue could be avoided the next time I have to restore it.īasically, I'm backing up a Firefox's profile folder, so each time I install it on a new system, such "source" profile's folder with get a "partially new" random name, but the remnant path will always remain the same. That way, the next time I have to restore such job's settings, I wouldn't need to manually fix its source path again, which will change for sure. Now, what if I want to modify the job, in a way it omits the aforementioned randomly named folder, but at the same time, copy all its content? That is, copying all its content into a main folder, like this: But I'm still curious about why the settings file had the incomplete source path when it was saved?Īug 09, 2019I see, but what I can't still understand is why despite the settings file had the incomplete path, when I had to restore the backup job contents to the new profile folder, it actually wasn't saved into a randomly named folder but to the main one that I created for the backup it seems for some reason the backup job kept saving the content correctly anyway.Īfter updating the job's path, now if I save the settings file, it does include the random folder name in its path. When I created the backup job back then, the original intention was all the "fault" source content was saved into just one backup folder, like this:Īnd the job somehow kept working fine like that.īut now, after restoring the job through the settings file, I have to modify the source's folder path, in a way the destination path keeps like this:Īnd despite at first it copied the content to a new folder, I modified it in a way it copies just the folder's content, excluding the folder itself. What I'm wondering is why despite having the incomplete path, the job as saved by the settings' file still worked fine? ![]() But when I wanted to run the restored backup job the error message was about the destination path being incorrect, since it lacked the needed profile's folder name. When I manually restored the profile's content from one of the backup locations, it was saved into a "Firefox-BK" folder, which had all the respective files, but without them being saved into a "fault" kind of folder, but all into the "Firefox-BK" folder itself. "C:\Users\Administrator\AppData\Roaming\Mozilla\Firefox\Profiles" ![]() "C:\Users\Administrator\AppData\Roaming\Mozilla\Firefox\Profiles\fault\"īut to my surprise, the job saved into the settings file had a different destination path, like this: But the weird issue showed up when I went to fix the job's destination path: The thing is, when I restored the settings file and wanted to run the job, there was an error message about an invalid "source" path being used and that was correct, since the when I installed the Firefox in the new system, it generated a new profile folder, with a new random name. Basically, there was a specific job within such file, which does a backup from a Firefox profile folder this folder has a randomly generated name, which designates a particular user. Aug 07, 2019Hi, recently I had to use the "bvckup2-settings.zip" file to restore jobs to a new Bvckup2 installation, and although the process itself went fine, there was some weird issue I'm still wondering how could it been possible. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |