How do you save backups 1 week at a time?
What I'd like to do, is put my backups in a folder like: Feb 27 - March 5. That's my plan. What's happening is I have two full b/u's and the rest are diff's. Although I saved a custom b/u, the program, didn't recognize that - that custom name I gave to the b/u, was the one I wanted it to use.
So, does anyone know how to get this done?
Thanks in advance,
CotS
What I was thinking of was to catagorize my backups by the week, like Feb 27 to March 5th. where in that folder you would find the backups performed for that week. Then I'd create another folder as the weeks went by: March 6th to March 12, and on so on.
So, I'm wondering how to "limit" the backups to seven days per folder; with the first backup being a Full backup...and the rest differentials.
Perhaps that's a bit clearer; at least I hope so.
That was only my first idea as to backup management. How do others stay organized? (Maybe I'm "barking up the wrong tree," as they say) in other words, maybe there are better approaches...
CotS
The difficulty with taking the approach that you are proposing is that each time you change the backup folder for a new week, you will then also need to either create a new task for this change, or clone / change the existing task. Doing this will then also prevent the ability of ATIH to offer you a full listing of all backup restore points based on date / time, as each backup chain per folder will be deemed a separate unrelated backup.
There should be no need to go to the lengths that you are proposing in order to manage your backups and stay organised.
My own preferred method is to have a separate target backup folder for each backup task and use the automatic cleanup rules to limit the size of the backups stored, and use the folder name / backup task name to easily identify the purpose that each holds.
On my NAS I keep one backup folder per each computer system that I am backing up, and name the tasks for each individual disk drive or data category that I am storing for that computer.
This is my own implementation of the K.I.S.S. principle (Keep It Simple Steve...)
(Keep It Simple Steve...)
Lucky you, your name starts with an "S"; so it works. Me on the other hand, the saying reverts back to it's original form. Oh well. :)
If I employ Automatic Cleanup, with a 4TB Ext. Drive, how far out can I go? (No. of Days) before it deletes the first one? Roughly 90 GB on SSD so far.
I gather you are not splitting your backups, if you are using Automatic Cleanup.
With 4TB of space, how much of a range of dates will I be able to retain?
How big are your backup version chains? Without knowing that detail, I cannot start to guess how much data you can store on your 4TB of backup space.
Automatic cleanup works on completed version chains plus one full backup.
So for example.
If you have a backup version chain comprising 1 x full backup plus 5 incremental backups giving a size of 90GB.
And you select to store no more than 5 recent version chains.
Then you would need capacity to store 5 x 90GB plus say 80GB for a further full backup before the automatic cleanup rules would fire and delete the oldest version chain to free 90GB of space.
Sorry for the late response. For the SSD, they were running 55,00 some odd KB. For the data drive, they were running 6,500 6,600KB each, once a day.