-
Notifications
You must be signed in to change notification settings - Fork 261
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incremental backup is not preserved when creating a template from a VM #779
Labels
Comments
ahadas
added a commit
to ahadas/ovirt-engine
that referenced
this issue
Dec 15, 2022
Previously, all template disks were created with backup mode = NONE regardless of the backup mode of the disks of the VM that the template is created from. Now the backup mode would propagte from the VM disks to the template disks when their format is qcow2. If the template disks are created as raw their backup mode would be NONE. Enabing to create template disks with incremental backup enabled from VM disks that are raw is outside of the scope of this change. Signed-off-by: Arik Hadas <ahadas@redhat.com>
ahadas
added a commit
to ahadas/ovirt-engine
that referenced
this issue
Dec 15, 2022
Previously, all template disks were created with backup mode = NONE regardless of the backup mode of the disks of the VM that the template is created from. Now the backup mode would propagate from the VM disks to the template disks when their format is qcow2. If the template disks are created as raw their backup mode would be NONE. Enabing to create template disks with incremental backup enabled from VM disks that are raw is outside of the scope of this change. Signed-off-by: Arik Hadas <ahadas@redhat.com>
ahadas
added a commit
to ahadas/ovirt-engine
that referenced
this issue
Dec 15, 2022
Previously, all template disks were created with backup mode = NONE regardless of the backup mode of the disks of the VM that the template is created from. Now the backup mode would propagate from the VM disks to the template disks when their format is qcow2. If the template disks are created as raw their backup mode would be NONE. Enabing to create template disks with incremental backup enabled from VM disks that are raw is outside of the scope of this change. Signed-off-by: Arik Hadas <ahadas@redhat.com>
ahadas
added a commit
to ahadas/ovirt-engine
that referenced
this issue
Dec 15, 2022
Previously, all template disks were created with backup mode = NONE regardless of the backup mode of the disks of the VM that the template is created from. Now the backup mode would propagate from the VM disks to the template disks when their format is qcow2. If the template disks are created as raw their backup mode would be NONE. Enabing to create template disks with incremental backup enabled from VM disks that are raw is outside of the scope of this change. Signed-off-by: Arik Hadas <ahadas@redhat.com>
ahadas
added a commit
to ahadas/ovirt-engine
that referenced
this issue
Dec 15, 2022
Previously, all template disks were created with backup mode = NONE regardless of the backup mode of the disks of the VM that the template is created from. Now the backup mode would propagate from the VM disks to the template disks when their format is qcow2. If the template disks are created as raw their backup mode would be NONE. Enabing to create template disks with incremental backup enabled from VM disks that are raw is outside of the scope of this change. Signed-off-by: Arik Hadas <ahadas@redhat.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When creating a template from a virtual machine, the 'incremental backup' setting doesn't propagate from the disks of the virtual machine to those of the template
The text was updated successfully, but these errors were encountered: