Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 2043175

Summary:	[CBT][Veeam] automatically increase Scratch Disk
Product:	[oVirt] ovirt-engine	Reporter:	md
Component:	BLL.Storage	Assignee:	Nobody <nobody>
Status:	CLOSED DUPLICATE	QA Contact:	Avihai <aefrat>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.4.10	CC:	ahadas, bugs, nsoffer
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	All
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2022-01-24 15:15:03 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Storage	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description md 2022-01-20 18:51:36 UTC

Description of problem:

When you start a Backup of VM with a preallocated QCOW2 Disk, the Scratch Disk will be created with the Size MaxBackupBlockScratchDiskInitialSizePercents Value in Percent.
Now if the Scratch Disk will run out of Space, the VM will be paused. 
When the Backup is finished, the VM must be manually resumed.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:

1. Create a VM with preallocated QCOW2 Disk and enabled Incremental Backup
2.Start a Backup of the VM
3. Write more than MaxBackupBlockScratchDiskInitialSizePercents on the VM while the Backup is running.

Actual results:

VM is paused and must me manually resumed after the Backup is finished


Expected results:

The Scratch Disk should be increased (linke a Snapshot does) when it reaches the end of cpacity, the VM should never be paused


Additional info:

Relevant Bugs: 1913315, 2018986, 2018971

Comment 1 Arik 2022-01-24 15:15:03 UTC

This would be handled as part of bz 1913387 - scratch disks will be thin-provisioned and extended automatically they are being written

*** This bug has been marked as a duplicate of bug 1913387 ***

Comment 2 Nir Soffer 2022-01-24 16:03:06 UTC

For the current release, you can increase MaxBackupBlockScratchDiskInitialSizePercents
if this is an issue in your environment.

Comment 3 Arik 2022-01-24 16:17:58 UTC

(In reply to Nir Soffer from comment #2)
> For the current release, you can increase
> MaxBackupBlockScratchDiskInitialSizePercents
> if this is an issue in your environment.

+1
Yeah, forgot to write this part - thanks!
See more details on this in bz 2018986