Snapshots are not deleted according to the snapshot policy

2013년 04월 25일 11:56

Snapshots are not deleted according to the snapshot policy

We configured CloudStack to take snapshots daily and delete all old snapshots to keep only the 2 most recent snapshots. But the old snapshots are not deleted.

From the log on Secondary Storage VM, we can see the CleanupSnapshotBackupCommand was sent to Secondary Storage VM and the Secondary Storage VM agent received this request.

2013-04-25 00:01:37,978 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Request:Seq 25-300817340: { Cmd , MgmtId: 153252621541, via: 25, Ver: v1, Flags: 100011, [{"CleanupSnapshotBackupCommand":{"secondaryStoragePoolURL":"nfs://172.18.30.12/export/secondary","dcId":1,"accountId":2,"volumeId":2422,"validBackupUUIDs":["/snapshots/1/2/2422/gitfraud01_DATA-2396_20130311171422","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130322114746","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130414110421","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130415110421","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130416110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130417110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130418110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130419110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130420110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130421110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130422110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130423110053","/snapshots/1/2/2422/gitfraud01_DATA-2396_20130424110406"],"wait":0}}] }

From the log of Secondary Storage VM, as shown below, it seems the command was successfully executed.

2013-04-25 00:01:37,978 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Processing command: com.cloud.agent.api.CleanupSnapshotBackupCommand
2013-04-25 00:01:37,979 DEBUG [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-4:) Executing: mount
2013-04-25 00:01:37,980 DEBUG [storage.resource.NfsSecondaryStorageResource] (agentRequest-Handler-4:) Execution is successful.
2013-04-25 00:01:37,980 DEBUG [cloud.agent.Agent] (agentRequest-Handler-4:) Seq 25-300817340: { Ans: , MgmtId: 153252621541, via: 25, Ver: v1, Flags: 10, [{"Answer":{"result":true,"wait":0}}] }

However, the snapshots that are not listed in the validBackupUUIDs were not deleted.

In addition, the validBackupUUIDs were wrong as well. We configured to only keep the most recent 2 snapshots, but the validBackupUUIDs sent by CloudStack Manager also contain several old snapshots. But when we view the snapshots for that VM from CloudStack Web UI, it only shows the 2 most recent snapshots.

Anyone has seen this issue before? Any idea on what the causes are? How to fix it?

Lianping Chen MEMBERS 25 April 2013 - 11:56 AM

댓글 3개

댓글을 남기려면 로그인하세요.

Previous 댓글 3개

날짜 투표수

Pankaj Paliwal

2016년 03월 23일 07:14

Snapshots are not deleted according to the snapshot policy

Not sure if you are still seeing an issue. But the deletion of the snapshots from secondary storage depends on the type of hypervisor in your environment.

In case of KVM and VMware every snapshot is a full snapshot and once you delete the snapshot, the snapshot will be removed from secondary storage based on the global config variable storage.cleanup.interval.

In case of Xenserver First Snapshot on a volume is always full snapshot. And the next full snapshot is taken based on the value of snapshot.delta.max (default 16). Default value of 16 indicates that after the 1st Snapshot (FULL SNAP) the next 15 are Delta's ( Incremental Snaps) created on Secondary Storage. The 17th Snapshot on the volume will be again a Full Snapshot. If we delete an incremental snapshot, then the respective snapshot is marked as deleted in DB, but the VDI chain on the Secondary storage is never disturbed (as other snapshots are dependent on it)

Prashanth Reddy Mandadi CITRIX EMPLOYEES 30 April 2013 - 06:14 AM

Pankaj Paliwal

2016년 03월 23일 07:14

Where the variable storage.cleanup.interval is specified, in terms of the name and location of the configuration file?

Lianping Chen MEMBERS 30 April 2013 - 14:03 PM

Pankaj Paliwal

2016년 03월 23일 07:15

No configuration file, as such. If you go to "Global Settings" in the CCP UI, and search for 'delta' you will be able to modify this setting. You will need to restart your cloud-management service on all management servers to have this take effect.

--Mike

Mike Little MEMBERS 30 April 2013 - 16:33 PM