Ticket #1155 (closed Feature Requests: fixed)

Opened 5 years ago

Last modified 6 months ago

Backup rotation

Reported by: webrainstorm Assigned to: mbrevda
Priority: minor Milestone: 2.10
Component: Backup & Restore Version: SVN-HEAD
Keywords: Cc: csabka
Confirmation: Unreviewed SVN Revision (if applicable):
Backend Engine: All Backend Engine Version:

Description

I think FreePBX needs a backup rotation system, otherwise used space on hdd will grew fast (Expecially if you have a 1 year old CDR table and a lot of voicemails ;) )

I think the best way it can be implemented is by adding a field in a backup set to specify how many old copies of the backup should be keeped.

I'll start this implementation in a few days, if you have any comment or proposal give me feedback on this ticket.

-- Ed

Change History

09/29/06 04:06:28 changed by webrainstorm

  • owner set to webrainstorm.
  • status changed from new to assigned.

01/08/07 13:46:49 changed by

  • milestone deleted.

Milestone 2.3 deleted

01/08/07 14:11:21 changed by vgster

  • milestone set to 2.3.

07/24/08 18:12:50 changed by mbrevda

  • confirmation set to Unreviewed.
  • engine_version changed.
  • svn_rev changed.

webrainstorm: from when do we start counting?

02/28/10 09:58:13 changed by p_lindheimer

  • milestone changed from Cut Line to 2.8.

05/25/10 15:27:47 changed by p_lindheimer

  • milestone changed from 2.8 to Cut Line.

09/15/10 13:34:24 changed by p_lindheimer

  • owner deleted.
  • status changed from assigned to new.
  • milestone changed from Cut Line to 2.9.

09/15/10 13:37:37 changed by p_lindheimer

  • cc set to csabka.
  • version set to SVN-HEAD.

duplicate reported #4523

11/09/10 17:54:57 changed by p_lindheimer

  • owner set to GameGamer43.

11/09/10 22:18:33 changed by mbrevda

#4593 would be helpful here

11/10/10 10:28:46 changed by p_lindheimer

you could use the cron manager which, iirc, runs ever hour so could easily be used if that was the desired approach. However, I think there is a much simpler way to handle this. Each time a backup set runs, determine if there are any older sets that need to be deleted based on a configured rotation. You could either have it configured to keep the last N backups (which would probably be the easiest to implement), or you could configure it to keep backups based on time. Either way, it is probably a much simpler option to simply cull the old backups when doing a new one for a given set. That is my suggestion on how this should be handled.

03/04/11 23:36:47 changed by p_lindheimer

  • milestone changed from 2.9 to 2.10.

06/05/11 09:33:33 changed by mbrevda

  • owner changed from GameGamer43 to mbrevda.

08/17/11 08:11:05 changed by mbrevda

  • status changed from new to closed.
  • resolution set to fixed.

(In [12414]) re #5166, closes #5308, #3563, #4949, #5184, #1155, #4323, #5121, #5136, #5236, #5290