Hey guys,
we are using CS 4.5 with XenServer 6.5 SP1 and observed a behavior with volume-snapshots that
will fill up your primary storage over time:
Workflow:
1. create an instance
2. create a volume-snapshot of the ROOT-disk of that instance
3. delete instance and expunge it
4. check primary storage of XenServer. The latest snapshot of each volume-snapshot will stay
on primary storage and is not being deleted even after waiting for storage.cleanup.interval
Can somebody reproduce this?
As far as I understand the workflow of volume-snapshots CS will XenServer ask to do a snapshot
of the vm and then copy this snapshot to secondary storage. But why CS is not deleting the
snapshot on primary storage after a success copy to secondary storage? Is this a "broken"
workflow or is there a reason for that?
Is this the same behavior in newer releases of CS?
Mit freundlichen Grüßen / With kind regards,
Swen
- proIO GmbH -
Geschäftsführer: Swen Brüseke
Sitz der Gesellschaft: Frankfurt am Main
USt-IdNr. DE 267 075 918
Registergericht: Frankfurt am Main - HRB 86239
Diese E-Mail enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Mail.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Mail sind nicht gestattet.
This e-mail may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this e-mail in error) please notify
the sender immediately and destroy this e-mail.
Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly
forbidden.
|