| Author |
 Topic  |
|
|
Time_to_go
New Member
United Kingdom
10 Posts |
 Posted - August 30 2010 : 19:25:36
|
My PCs do a full image every Sunday evening and incrementals every day. They will delete a full + incrementals older than 12 days.
However, at holiday time, after 2 weeks away, when the PC has not been on for 14 days ........ the only images are older than 12 days, so as soon as the PC is turned on the entire set of backups disappears.
OK, I could think ahead and change the tasks and schedules ... but I should not have to. (It would have been a bit easier before W7 when there was a tick box enabling runs to be de-activated).
There could be an option around not automatically deleting all the images. Alternatively, there could be a remove option which works on space usage ie not enough space, then delete the oldest set. |
|
|
Nick
Moderator
United Kingdom
6303 Posts |
Posted - August 30 2010 : 23:43:07
|
Hi
Thanks for your post. You can set the DSM purge to retain a fixed number of full backups not just age. This should ensure that you keep the correct history, even if you return from holiday.
Make sure you are running the latest version by taking the 'Help' > 'Check for updates' menu option. Edit your backup definition(s) and click the 'Advanced' button on the final page. Choose the 'Disk Space Management' option and select 'Keep a maximum of n backups'.
Note: You can also set the purge to run before or after the current backup. If set to run 'before' then the number of full backups to retain is the number *before* the current backup is run.
Hope this helps
Nick - Macrium Support
|
 |
|
|
Time_to_go
New Member
United Kingdom
10 Posts |
Posted - August 31 2010 : 07:44:40
|
Ah ! The options have changed since I set up the backup scripts !
I am on the latest version, but I did not realise these options had been added. I will edit accordingly. Thank you ! |
|
|
|
VBDavie
New Member
33 Posts |
Posted - July 01 2011 : 00:38:50
|
Nick, long time to see ;)
I couldn't resist a reply here. When I set the backup limit to "3", then everything goes as planned. BUT, when I change it from "AFTER" to "BEFORE", then it doesn't work as "expected". IE: I expected it to STILL leave me with 3 full sets of backups. But that's not what happened. Instead, it said "disk full backup failed". I was running low of space. But I thought that if it deleted the OLD backups BEFORE starting the current backup, then everything would be fine. But it doesn't. I had to manually delete the old backup (so that left me with 2 sets of full) then the backup job worked. SOoooo, why is it that it works that way? Doesn't that seem a little illogical. So, I had to go into the backup job and tell it to keep "2" instead of "3". Dissappointing, but it works. The way I think, i would do any deleteing before the backup starts (it does that right now) and then do the backup (it does that right now). But what it DOESNT do is the calculation for the space required AFTER the deletions. It seems like it does the calc before the deletion occurs and thus it tells me there is NOT enough space (DUH). When in fact it should just delete the old set and then I would have plenty of space.
Any comments?
Davie
Thanks in advance
Davie
creator of Photo Jockey www.photojockey.com |
|
|
|
C.Bamford
Moderator
United Kingdom
1002 Posts |
|
| |
Topic |
|
|
|
RSS Feed
KB
Deleting old image
Forum Locked
