![]() I have since upgraded to the first and second beta of 2017 as well with little issue (other than the beta bugs that are being worked out in testing). I upgraded from 2016 to newer versions in 2016 with no issues. When users switch to a new backup product, they often feel it is "superior" or better because it is a fresh start. Over time, through appicatoin upgdates/upgrades, Windows upgrades/updates, changes to the OS, changes to third party applications, malware, antivirus, etc, at some point, backup programs that are deeply embedded into the OS functionality become impacted. I can tell you from experience that there is no backup product that is truly set and forget. Do what you gotta do to have reliable backups. If you go with something else - best of luck. You can use the product however you want, but if you keep edits to existing backup scripts to a minimum (or not at all), I believe you'll have a better experience with the program as it runs in Windows. If you do make changes to a backup scheme after backup have run, the backup version chain count gets reset so people often wonder why they have more incrementals or differentials than they should before the next full runs and this leads to a delay in the cleanup as well. If you configure the backup scheme correctly from the beginning and leave it alone, you're much more likely to have a very reliable and consitent backup experience. However, I've found the best performance/consitency when leaving them alone. It's a recommendation, not a requirement.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |