2014 vs 2016 -- I gained some, I lost some...
I just bought v2016 because my v2014 wouldn't backup to my new RAID1 array correctly. (Asus Rampage IV Extreme mobo using the X79 chipset with an Intel chipset SATA RAID controller and the latest version of the IRST software on Windows 7 Pro 64-bit)
v2016 seems to backup to the RAID1 array correctly, but why did Acronis dumb down the interface and options on me?
I used to be able to decide what information went into the name of each backup, but it seems as though Acronis has gone the route of M$ and decided they know best.
v2016 will only allow me to name a backup like this "Boot_Backup_" and then the program will insert the version of the backup at the end of the name I gave it.
What happened to allowing the user to insert the date of the backup in its name, etc. as I could with v2014 and previous versions?
I have v2014-created backups named like this: Boot_Backup_2016-22-02_full_b1_s1_v1
But now I can seemingly only have: Boot_Backup_full_b1_s1_v1
Am I missing something here or has Acronis decided I don't really need this flexibility?
Also, one of my MAJOR complaints since the 2010 version (when I started using Acronis priooducts) is that I only have the option to tell the computer to SHUT DOWN after a backup is complete, why not have SLEEP as an option? My system is regularly in SLEEP mode when the backup starts. The computer wakes itself via the option in the software, but won't go back to SLEEP after the backup completes.
I have purchased versions: 2010, 2012, 2014 and now 2016 and yet this simple functionality has never been implemented.
William,
There is a workaround for the naming issue. Please refer to the link below...A lot of work, but it can be done.
https://forum.acronis.com/forum/91956
And per Steve's recommendation, still send your feedback to Acronis.
FtrPilot
Hello William,
Thank you for your posting! We've already registered feedbacks regarding backup naming options. I've added your feedback so our product management can see the scope.
Thank you,
Thank you for the responses and the workaround. I easily renamed the backups, but the average, or below average, user will never go and do this. Then again, maybe the average or below average user wouldn't care about this once-present feature. If the person is new to the product then they wouldn't know that this product used to be more powerful and user-friendly.
Since Ekaterina Surkova is reading this thread... where's 2016's ability to go out and search for previous backups like the older versions could do? Seriously, I have to MANUALLY add all my old backups to the list? If this option was offered upon first run then I must have missed or ignored it -- I certainly can't find that option now (assuming it exists, which I won't).
Finally, the "TOOLS" selection does absolutely nothing.
Believe me, if 2014 actually supported my RAID1 array for backups I would have never bought the unfinished 2016 version. I am very disappointed in the dumbed-down direction this product is going in. There are "power users" and other above average users out here using your products. Less is NOT more, if you know what I mean? Maybe Acronis needs to develope a "light" version and a "pro" version with two different price points?
Thank you for listening and hopefully responding.
William - I actually have the exact opposite issue as you. Whenver I reinstall ATIH 2016 from scratch, it loads all of my old backups into the console and I have to manually delete each one to get rid of them because I don't want to see them there (I only keep them around for offline bootable media recovery if needed). I can't find the forum link at this time, but it was stated by one of the Acronis techs that the first run is supposed to scan drives for existing backups and add them. I would also appreciate the ability to change the behavior - sounds like it would be beneifical to give users the option to make the choice as to whether or not to add old backups automatically.
As for the "tools section" the deafult rescue media builder relies on Linux. The driver support on the Linux side has been much slower, but I believe Acronis is working on getting newer drivers added in future releases. Even so, Windows PE is often needed for RAID controller drivers which usually aren't available in the Linux builds... sometimes this is also the case for newer hard drives like the PCIE NVME disks, EMMC flash disks, and even a few NICS.
Unfortunately, and I don't know why, when creating Windows PE, through the default media builder, there is no option to add custom drivers at build. This is avaialble in the Universal REstore WinPE media builder, but going that route only gives you Universal Restore disk (which will allow you to inject the necessary drivers into any pushed image so it should theoretically work, but is another step in the process). The alternative is to later use Windows ADK to inject the drivers into your bootable USB WIM, or gry using the DISMGui tool to do this which should also work and simplifies the process. I am hoping that Acronis will simplify the WinPE process in future builds and I have submitted feedback about this and suggested it to Acronis technicians directly as well.
Mustang has a sticky about creating WinPE and adding drivers (see my signature for direct link). You want to make sure that you inject 64-bit drivers as ATIH 2015/2016 WinPE is strictly 64-bit.