Backup Folder Creation - WD 2017
I upraded WD 2015 to 2017 = YEA! Howver, when ran a backup of my entire I could not figure out how create a sub-folder name (which would contain the entire contents of the backup).
e.g.:
Dec-2016
Jan-2017
Feb-2017
etc.
The TIBs are appropriately named.
Once a backup task name has been set, that is what Acronis uses for the backup .tib files. Unfortunatley, you can NOT create subfolders in Windows Explorer via Acronis (well, you can, but only when creating the backup) if you want to create a new folder at the time of setting up the backup.
You don't want to manually move files around in File explorer either as that will break the database that Acronis makes when the backups are made and catalogs the backup locations. The .tib files themselves, can be moved in Windows and accessed from the offline media without issue (assuming all files are in one location for a specific backup chain). However, the Windows version of ACronis (as installed in your OS), uses the back-end database to keep track of all fo the settings and backup locations so manually moving them outside of Acronis can cause issues.
I would recommend that you sumbit feedback through the app, requesting a feature to move backup files to a new location or redirect them more easily.
Oh dear, I was afraid this would be difficult to explain. I'll give it another shot. I had already upgraded 2015 WD OEM to full version. When 2017 came out I did same thing and was pleased to note it kept the WD OEM flavor.
I can't get back to 2016 (lest I screw up my last full save) so I have remember this a bit by rote.
I have a disk farm. e.g. - one disk contains swan, disk 2 contains pigs, disk contains cows, etc.
Each time I do a full save representing current month's partitions - e.g. Dec-2016. All tib names after that included the name Dec-2016 (e.g. F:\Dec-2016_full_b1_s1_v1.tib). (I've done this for 15 years, or so). I'm talking about normal version of TrueImage, NOT OEM version. Subsequent diff backups had Dec-2016 diff in the tib name. (See bottom of page which allows FULL path of destination - OEM version does not allow incuding full path - which is why I'm here). BTW - I have to use OEM because I have a WD Passport that needs to contain backup.
The VERY first backup will be just fine until the next backup (full or diff, etc.) as it will write over the last backup as both at the root of the disk.
Thomas, thanks for the further information, though I have to confess to still not fully understanding what you are asking here.
Taking things backwards (in a sense) - you stated: "BTW - I have to use OEM because I have a WD Passport that needs to contain backup." - that is not the case, rather it is the opposite if anything. OEM versions of ATI can be restricted to work with the manufacturers products, i.e. WD with WD drives, but the full version of ATI will work with any manufacturer of drives, and definitely work with WD Passport drives.
Next, you say that you are only saving to the root of your F:\ Passport drive and the backups are being overwritten - that should not be happening and would suggest an issue with your ATI installation, most likely caused by having upgraded originally from the OEM WD version, and then again from 2016 to 2017.
Now to the focus of the question, you are backing up multiple different disk drives all to the same root folder and using the same root task name, i.e. Dec-2016 for these backups. If you are doing this for different backup tasks, i.e. One task backs up your swans to F:\Dec-2016_full_b1_s1_v1.tib, then another task backs up your pigs to the same file name, it will overwrite the file already present, and again when you backup the cows etc.
The way around this is to adopt a different approach for how you perform your backups.
First create a folder at F:\Dec-2016 then create separate tasks for each disk drive to write to this folder, but this time give them unique names, i.e. Swans_full_b1_s1_v1.tib; Pigs_full_b1_s1_v1.tib, Cows_full_b1_s1_v1.tib etc - you will have easily identifiable backup files in a folder showing which month these were created.
For the next month, create a new folder at F:\Jan-2017 then clone your existing task settings for your Swans, Pigs and Cows backup tasks and point these to be stored in the new F:\Jan-2017 folder - repeat this for each subsequent month.
Note: If you have been making a full backup that includes all your different disk drives in a single backup image file, then I would recommend not doing so, as this has several disadvantages - the image file size is very much larger, backup time is longer, recovery is more complex, and the risk of a file being impacted by any disk or bad sector errors is increased.
"For the next month, create a new folder at F:\Jan-2017 then clone your existing task settings for your Swans, Pigs and Cows backup tasks and point these to be stored in the new F:\Jan-2017 folder - repeat this for each subsequent month.
Note: If you have been making a full backup that includes all your different disk drives in a single backup image file, then I would recommend not doing so, as this has several disadvantages - the image file size is very much larger, backup time is longer, recovery is more complex, and the risk of a file being impacted by any disk or bad sector errors is increased."
BINGO! I know you had difficulties understanding me (as did I) but, you managed to give me the solution(s) I was looking for = THANKS!
Thomas, that's great if this is the answer you were seeking. My apologies for finding it not easy to understand but the important point is getting there in the end.