Hi I have another 3.0.2 set up locally and that does the snapshot rotation with no issues. I am using the same snapshot and cleanup settings and I started them almost the same time: 04 Jul 2012 04:17:09 04 Jul 2012 05:17:09 04 Jul 2012 06:17:09 04 Jul 2012 07:17:09 04 Jul 2012 08:17:09 04 Jul 2012 09:17:09 04 Jul 2012 10:17:09 04 Jul 2012 11:17:09
The two setups are exactly the same 3.0.2 setup, same global configuration settings except other IPS. The only difference the weird one is a 3.0.1->3.0.2 upgrade while the working one is fresh 3.0.2. Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk Follow us on Twitter: www.twitter.com/veberhost Follow us on Facebook: www.facebook.com/veberhost -----Original Message----- From: Tamas Monos [mailto:[email protected]] Sent: 04 July 2012 11:06 To: [email protected] Subject: Snapshot weirdness Hi, I have scheduled hourly snapshots (keep 8) and daily snapshots (keep 7) on one of my ROOT volume. 03 Jul 2012 17:16:23 03 Jul 2012 18:16:23 03 Jul 2012 19:16:23 (Snapshot Failed) 03 Jul 2012 21:16:23 03 Jul 2012 22:16:23 03 Jul 2012 23:16:23 04 Jul 2012 00:16:23 (Snapshot Failed) 04 Jul 2012 02:16:23 After 02:16 no more hourly snapshots were created. The scheduler wants to run them, but gets: 2012-07-04 10:47:52,054 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Snapshot scheduler.poll is being called at 2012-07-04 09:47:52 GMT 2012-07-04 10:47:52,056 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Got 1 snapshots to be executed at 2012-07-04 09:47:52 GMT 2012-07-04 10:47:52,061 DEBUG [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Scheduling 1 snapshot for volume 209 for schedule id: 12 at 2012-07-04 02:15:00 GMT 2012-07-04 10:47:52,108 WARN [storage.snapshot.SnapshotManagerImpl] (SnapshotPollTask:null) Snapshot resource limit exceeded for account id : 16. Failed to create recurring snapshots 2012-07-04 10:47:52,111 DEBUG [cloud.alert.AlertManagerImpl] (SnapshotPollTask:null) Have already sent: 1 emails for alert type '21' -- skipping send email 2012-07-04 10:47:52,111 INFO [cloud.api.ApiDispatcher] (SnapshotPollTask:null) Maximum number of resources of type 'snapshot' for account name=Sandbox in domain id=6 has been exceeded. 2012-07-04 10:47:52,111 WARN [storage.snapshot.SnapshotSchedulerImpl] (SnapshotPollTask:null) Scheduling snapshot failed due to com.cloud.api.ServerApiException I have: snapshot.max.hourly (Maximum hourly snapshots for a volume) set to 8 which would make sense why the resource limits kick in. However either the snapshot scheduler or storage cleanup or something should remove the oldest snapshot allowing snapshot rotation I'd say. It seems the scheduler does not so the storage cleanup then, but that runs once a day so the snapshots would be blocked until it cleans up? Could someone shed some light on this snapshot weirdness? What limits do I need to set where to allow hourly snapshosts with rotation? Regards Tamas Monos DDI +44(0)2034687012 Chief Technical Office +44(0)2034687000 Veber: The Hosting Specialists Fax +44(0)871 522 7057 http://www.veber.co.uk<http://www.veber.co.uk/> Follow us on Twitter: www.twitter.com/veberhost<http://www.twitter.com/veberhost> Follow us on Facebook: www.facebook.com/veberhost<http://www.facebook.com/veberhost>
