<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
Hi Maor,<br>
<br>
When I run the snapshot I get : "Snapshot antes de produccion
creation for VM NuevoVFTP was initiated by admin@internal."<br>
and that's all I get.<br>
Can you point me the log I must look for?<br>
Here is a screenshot of the snapshot<br>
Regards<br>
<br>
<img src="cid:part1.08010804.01070305@gmail.com" alt=""><br>
<br>
<div class="moz-cite-prefix">On 04/06/13 05:07, Maor Lipchuk wrote:<br>
</div>
<blockquote cite="mid:51ADA05D.50808@redhat.com" type="cite">
<pre wrap="">Hi Juan,
When creating a snapshot, a new volume is should be created in the storage.
The snapshot should contain the VM configuration and the VM disks (not
including shareable disks and direct lun disks).
Which Ovirt version are you using?
What the audit log indicated? Was the operation succeeded?
Can u please add a print screen of your VM and snapshot?
Regards,
Maor
On 06/03/2013 10:07 PM, Juan Pablo Lorier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Maor,
The thing is that I trigger the snapshot creation and everything seems
to be ok, but I can't see any new volume of any kind. As the VM runs
from an iscsi lun, it can not use LVM snapshots as there's no spare
space to create any new LMV volume, neither I see any new volume in the
data storage domain (another iscsi lun) so I can't tell for sure that
the snapshot was really created.
Where are the volumes saved if the VM has no spare disks or space?
Regards,
On 06/02/2013 03:07 PM, Itamar Heim wrote:
</pre>
<blockquote type="cite">
<pre wrap="">On 06/02/2013 02:27 PM, Maor Lipchuk wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi Juan,
Snapshot saves the VM at a particular state in time using qcow (Creates
a new volume and only write the changes from that particular time).
Export domain also saves the VM data but it using copy process of the
volumes, there for, snapshot is more faster process but dependent on the
VM disks.
In a nutshell the difference between the both are, that snapshot is more
related to the VM scope and can be executed while the VM is running
(From Ovirt 3.1)
Export domain is a different domain, there for, can be moved through
setups and DC's.
The info of disks and ram should be displayed in the right pannel for
the VM snapshots, although, for now, marking the active snapshot will
not present this info.
Was that the case you encountered?
Regards,
Maor
On 05/31/2013 07:55 PM, Juan Pablo Lorier wrote:
</pre>
<blockquote type="cite">
<pre wrap="">Hi,
I'm trying to understand how ovirt manages snapshots to start using them
for vm backups. I have my vms to use a iscsi LUN for the system (each
has its own) and I have no extra space to create an LVM snapshot in the
VM disk.
When I hit "create" in the vm snapshot tab, it creates the snapshot and
reports ok, but I see no info in the right pannel (disk, ram,etc) and
nothing is created in the data storage of the DC, so I don't get where
is ovirt storing the snapshot data.
Do I have to create an export storage domain?.
Regards,
Juan Pablo
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre wrap="">
_______________________________________________
Users mailing list
<a class="moz-txt-link-abbreviated" href="mailto:Users@ovirt.org">Users@ovirt.org</a>
<a class="moz-txt-link-freetext" href="http://lists.ovirt.org/mailman/listinfo/users">http://lists.ovirt.org/mailman/listinfo/users</a>
</pre>
</blockquote>
<pre wrap="">
also worth mentioning this feature in the works:
<a class="moz-txt-link-freetext" href="http://www.ovirt.org/Features/Backup-Restore_API_Integration">http://www.ovirt.org/Features/Backup-Restore_API_Integration</a>
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<pre wrap="">
</pre>
</blockquote>
<br>
</body>
</html>