You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cloudstack.apache.org by "Lianping Chen (JIRA)" <ji...@apache.org> on 2013/04/26 20:00:19 UTC

[jira] [Created] (CLOUDSTACK-2217) Snapshots backups are not deleted according to CleanupSnapshotBackupCommand. Those snapshots backups that should be garbage collected but not get deleted can fill up the secondary storage.

Lianping Chen created CLOUDSTACK-2217:
-----------------------------------------

             Summary: Snapshots backups are not deleted according to CleanupSnapshotBackupCommand. Those snapshots backups that should be garbage collected but not get deleted can fill up the secondary storage.
                 Key: CLOUDSTACK-2217
                 URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2217
             Project: CloudStack
          Issue Type: Bug
      Security Level: Public (Anyone can view this level - this is the default.)
    Affects Versions: 4.0.0
         Environment: CloudStack Manager running on CentOS
Secondary Storage Manager running on CentOS
Hosts running on CentOS
KVM
            Reporter: Lianping Chen


We are running CloudStack version 4.0.0.20121024012150. We defined a recurring snapshots backup policy to run daily and only keep the most recent 2 backups.

However, we found that the snapshots backups were not deleted according to this policy. According to the logs, the CleanupSnapshotBackupCommand has been sent by CloudStack manager and the command is received by Secondary Storage VM Agent. The secondary storage does contain backups that are not included in the validBackupUUIDs of CleanupSnapshotBackupCommand. But these backups that are not in the list of validBackupUUIDs still remain in the  file system and get the secondary storage being filled up.


--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira