helpstoreBackup - Support: sr #108318, keeping max backups / maximum use...

 
 

sr #108318: keeping max backups / maximum use of target space

Submitter:  None
Submitted:  Sat 08 Jun 2013 03:56:26 PM UTC
 
Category:  None Priority:  5 - Normal
Severity:  3 - Normal Status:  Done
Privacy:  Public Assigned to:  None
Originator Email:  -email is unavailable- Open/Closed:  Open
Operating System:  GNU/Linux
* Mandatory Fields

Add a New Comment (Rich Markup)
   

Comment Type & Canned Response:
       

 

Mon 10 Jun 2013 09:50:03 PM UTC, comment #2: 

Heinz-Josef,

I will have an eye on disk usage and tune the  keep parameters.

Thank you for your generousness

lopiuh
lopiuh [at] gmail.com

Anonymous
Mon 10 Jun 2013 07:53:35 PM UTC, comment #1: 

I think you need some kind of an expert system to support this. I think it could work as follows:

1. you need some kind of prioritisation to get a basis which backups should be deleted with which preference.

2. you need to analyse all backups (means the hard links) to know which deletion of which combination of backups would free how much memory.

3. you have to make a "dry run" (including compression) of storeBackup.pl to see, how much space the new backup will need (this may be totally different from backup to backup - which means the freed memory may be totally different also when deleting old backups)

4. depending on 1., you can use 3. to make a decision with the values gotten from 2. (This is the "expert system".)

It will be totally confusing, if multiple backups are running at the same time ;-) .

This beyond my scope. If you have any idea (maybe a better one) -> you're welcome!

Regards, Heinz-Josef

Heinz-Josef Claes <hjclaes>
Project Administrator
Sat 08 Jun 2013 03:56:26 PM UTC, original submission:  

Does anyone have a tip, how to keep as many backups as possible (depending on target disk size and amount of backuped data)?

I suppose there is no "automatic" strategy like "delete as many old backups until the next backup will have enough space" because
storebackup do not know in advance how much space will bee needed for the next backup.

So pragmatically one has "to play" with the keep parameter in order to maximize disk use, is this correct?

Are there any best practice settings  / experiences? (the settings are a little bit overwhelming ;-) to use most of the disk space?

I'd like to keep as many dailys as possible. If there is "no space left, say less then 100GB free" (backup target is only useed for storebackup) I want to keep monthly / yearly ... I think this is not possible because the delete procedure (or storeBackupDel.pl) would have to check target free space. Maybe this could be another extension to the many keep rules? ;-)

Greetings

lopiuh
lopiuh [at] gmail.com

Anonymous

 

(Note: upload size limit is set to 16384 kB, after insertion of the required escape characters.)

Attach Files:
   
   
Comment:
   

No files currently attached

 

Depends on the following items: None found

Items that depend on this one: None found

 

Carbon-Copy List
  • -email is unavailable- added by hjclaes (Posted a comment)
  •  

    There are 0 votes so far. Votes easily highlight which items people would like to see resolved in priority, independently of the priority of the item set by tracker managers.

    Only logged-in users can vote.

     

     

     

     

    Follows 1 latest change.

    Date Changed by Updated Field Previous Value => Replaced by
    2013-06-29 hjclaes StatusNone Done

    Back to the top


    Powered by Savane 3.9