![]() 700 is a lot in it's own right and not something I'd personally be comforatble relying on. ![]() #Roboform problems full#Instead of incrementals for life, perhaps a backup scheme that does the same hourly file/folder backup, but with a full every day followed with 23 incrementals? You could then use an automated cleanup task and keep say 30 versions of that email backup (roughly a months worth), or as many as you need for your retention scheme? At the most, I would say at least do a full in your incremental scheme once a week to try and limit risk a little bit by not letting the incrementals get to some astrononmical #. Acronis supports (allows is a better terminology I think) it, but from a data reliability scheme, it seems very risky. In a month, if you have to rely on that backup, you're now close to 700 and this goes on forever - that's a lot of incrementals to depend on when you get down the road a month or two and you want to risk all of these incrementals being perfect when the time comes for recovery? Even though you have a full backup every 3rd day, this incremental scheme will rely on the original full and everything from the beginning to the end which is going to be a boatload of icnrementals. You're doing 24 a day, in a week that's already 168. A quick search indicates it hasn't been updated since 2015 RoboForm Companion 3.5.166 so I'm a little surprised Roboform support is responding to issues about it. My only concern with never ending incrementals is that incrementals always rely on the backups before them. If it is with that, rather than the main Roboform program you are experiencing problems, it might be worth simply uninstalling it and verifying that Roboform itself is ok. ![]() ![]() If one is in progress, the next one in line will queue up behind it run when the other has completed. The full and incrementals won't conflict. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |