cloudstack-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Anshul Gangwar <anshul.gang...@accelerite.com>
Subject Re: [GitHub] cloudstack pull request #1735: CLOUDSTACK-9570: Bug in listSnapshots for sna...
Date Thu, 05 Jan 2017 06:51:08 GMT
In case of unmanaged primary storage, we only care about secondary storage for snapshot. In
case of VMware primary storage is only involved while taking snapshot. As far as I know process
to take snapshot is to take VM snapshot, backup volume to secondary and then remove the VM
snapshot on primary. After the snapshot is successfully created primary storage is of no concern
to that snapshot. Somebody can confirm that. I am not able to figure out what performance
improvements you are talking about?

Also, the datastore checks while listing snapshots are there because of managed primary storage
only. 

Regards,
Anshul 

On 04/01/17, 7:39 PM, "Sergey Levitskiy" <Sergey.Levitskiy@autodesk.com> wrote:

    @anshul1886 Actually in unmanaged primary storage scenario the removal of PS doesn't check
for the existence of the volume snapshot copy. Snapshot should be allowed to exist on secondary
after primary is gone. In VMware environment snapshot copy on primary only improves performance
but in the end it always replicates to secondary where it remains as a source of truth for
a given snapshot 




DISCLAIMER
==========
This e-mail may contain privileged and confidential information which is the property of Accelerite,
a Persistent Systems business. It is intended only for the use of the individual or entity
to which it is addressed. If you are not the intended recipient, you are not authorized to
read, retain, copy, print, distribute or use this message. If you have received this communication
in error, please notify the sender and delete all copies of this message. Accelerite, a Persistent
Systems business does not accept any liability for virus infected mails.
Mime
View raw message