Bug 1302340

Summary: Database backup doesn't expire files from within the backup
Product: Red Hat CloudForms Management Engine Reporter: Martin Welk <mwelk>
Component: ApplianceAssignee: Gregg Tanzillo <gtanzill>
Status: CLOSED DUPLICATE QA Contact: Dave Johnson <dajohnso>
Severity: low Docs Contact:
Priority: unspecified    
Version: 5.5.0CC: abellott, jhardy, obarenbo
Target Milestone: GA   
Target Release: 5.6.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-01-27 14:39:12 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Martin Welk 2016-01-27 14:22:29 UTC 
Description of problem:
I've seen some customers doing block based backups of their virtual machines. They can extract single files from those backups for restore.
So, for CloudForms they have the idea to create an NFS share on the CFME appliance itself, and run the backup into that NFS share. That works well, but the share fills up and they have to clean it manually or through an external job. It would be nice if the backup schedule could expire older files.

Version-Release number of selected component (if applicable):
n/a

How reproducible:
100%

Steps to Reproduce:
1. Create an NFS share
2. Create backups on a daily basis
3. Watch the used space growing

Actual results:
Some day, the disk is full

Expected results:
CloudForms can be told to keep some (for example, three) backups of the database, and expires the older ones automatically

Additional info:
I think this is a good idea as we ship CFME as a VM appliance, and many customers use block based backups and prefer that to other solutions. Furthermore, using an NFS share "on localhost" reduces external dependencies.
Comment 2 Martin Welk 2016-01-27 14:39:12 UTC 
I am sorry. I got an error when I submitted this the first time. This one's a duplicate.

*** This bug has been marked as a duplicate of bug 1302338 ***