Hello all,
A small update which closes this question.
Now the listSnapshots API provides the size of the snapshot precisely
(physicalsize attribute), and when I count it to match with total secondary
storage count for an account, then there is no descrepancy. This facility
is in with commit
Thanks Mike for details reply!
I checked on VMware and KVM. On KVM, after first snapshot, the secondary
storage count for account increases by 1 (template + snapshot I suppose).
After second snapshot, it again increases by 1.
On VmWare, the secondary storage count remains the same irrespective
Hi everyone,
Can anyone answer these questions Gaurav has about secondary storage?
Marcus - Perhaps you know for KVM?
Kelven - Perhaps you know for VMware?
Thanks!
Mike
On Wed, Dec 10, 2014 at 4:55 AM, Gaurav Aradhye gaurav.arad...@clogeny.com
wrote:
Thanks Mike for details reply!
I
Including Kelven directly on this using a different e-mail address (first
e-mail address bounced).
On Wed, Dec 10, 2014 at 3:16 PM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
Hi everyone,
Can anyone answer these questions Gaurav has about secondary storage?
Marcus - Perhaps you
Hello,
When I create a snapshot, from say, template registered through an account,
then
1) How can I know the snapshot size on secondary storage? (API
listSnapshots does not specify the snapshot size)
2) How is snapshot size counted in secondary storage used by the account?
Currently I can see
I'm not exactly sure how this number is calculated, but - if you are using
XenServer - remember that after the first snapshot for a volume, each
subsequent snapshot is only the blocks that have changed since the prior
snapshot (this might even be true for ESX these days with CloudStack).
That
Thanks Mike!
However, I am observing this in case of first snapshot also. Let me try on
various hypervisors to see the behavior.
Regards,
Gaurav
On Tue, Dec 9, 2014 at 11:04 AM, Mike Tutkowski
mike.tutkow...@solidfire.com wrote:
I'm not exactly sure how this number is calculated, but - if
