Bug 1024785

Summary: [TRACKING][RFE] RHEV Windows Guest VSS support (Volume Shadow Copy Service Quiescing)
Product: Red Hat Enterprise Virtualization Manager Reporter: Sean Cohen <scohen>
Component: Windows Guest ToolsAssignee: Allon Mureinik <amureini>
Status: CLOSED ERRATA QA Contact: Elad <ebenahar>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 3.3.0CC: aberezin, acanan, acathrow, amureini, bazulay, cpelland, eedri, iheim, knesenko, lindsay.mathieson, lveyde, pstehlik, Rhev-m-bugs, scohen, sherold, yeylon, zdover
Target Milestone: ---Keywords: FutureFeature, Tracking, ZStream
Target Release: 3.3.2   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard: storage
Fixed In Version: Doc Type: Enhancement
Doc Text:
Volume Shadow Copy Service Guest Quiesce for application-level consistency is now supported.
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-09 17:52:31 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Bug Depends On: 948017    
Bug Blocks:    

Description Sean Cohen 2013-10-30 12:36:37 UTC
Add support for Volume Shadow Copy Service Guest Quiesce for application-level consistency.

The RHEV Backup and Restore API will provide integration with Microsoft Windows Volume Shadow Copy Service (VSS) using qeum-ga. The VSS provider registration will be made in the guest level as part of the Guest Tools deployment.

Comment 2 Ayal Baron 2013-10-30 12:58:15 UTC
Basically everything should be there (we deploy qemu-ga which provides vss support and live snapshot automatically tries to quiesce whenever possible).

Comment 3 Sean Cohen 2013-11-13 10:26:44 UTC
Can be tested using vshadow tool part of the following SDK: http://www.microsoft.com/en-us/download/details.aspx?id=23490

See usage: http://msdn.microsoft.com/en-us/library/windows/desktop/bb530725%28v=vs.85%29.aspx

Comment 4 Elad 2013-11-27 16:37:29 UTC
I'm using RHEV3.3 (IS25) and I've installed its rhev-guest-tools on a windows VM (RHEV-toolsSetup_3.3_6.iso on windows server 2008).
The rhev-guest-tools ISO contains qemu-guest-agent but VSS for windows is not supported.

Comment 17 Kiril Nesenko 2014-03-23 09:58:03 UTC
This bug can't be added to the 3.3.2 errata due to a missing acks.

- Kiril

Comment 18 Aharon Canan 2014-03-23 10:04:33 UTC
Sean, please check my comment #15

Comment 20 Elad 2014-03-26 15:37:53 UTC
vshadow creation succeeded:

Reproduction steps:
1. installed a windows VM with 2 disks and rhevm-guest-tools with the mentioned qemu-guest-agent version which support vss for windows.
2. installed Volume Shadow Copy Service SDK 7.2 on the guest.
3. created vshadow using VSS SDK


Querying all shadow copies with the SnapshotSetID {1aba6254-ef36-4297-94da-72b4c
d15a886} ...

* SNAPSHOT ID = {2a41a81c-1978-47b7-a551-773fec0beaad} ...
   - Shadow copy Set: {1aba6254-ef36-4297-94da-72b4cd15a886}
   - Original count of shadow copies = 1
   - Original Volume name: \\?\Volume{8e3996cf-b534-11e3-89fe-001a4afb125c}\ [E:
\]
   - Creation Time: 3/26/2014 3:29:12 PM
   - Shadow copy device name: \\?\GLOBALROOT\Device\HarddiskVolumeShadowCopy1
   - Originating machine: WIN-12DQ34BZQBR
   - Service machine: WIN-12DQ34BZQBR
   - Not Exposed
   - Provider id: {b5946137-7b9f-4925-af80-51abd60b20d5}
   - Attributes:  Auto_Release Differential

- Mark all writers as succesfully backed up...
Completing the backup (BackupComplete) ...
(Waiting for the asynchronous operation to finish...)
(Waiting for the asynchronous operation to finish...)

Snapshot creation done.


===============================================================
Checked with:
RHEV-3.3.2-IS35.1
RHEV-toolsSetup_3.3_14.iso
qemu-ga-win-7.0-7

Comment 21 Sean Cohen 2014-03-26 16:02:15 UTC
No longer depend on Bug 1036341

Comment 23 errata-xmlrpc 2014-04-09 17:52:31 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2014-0387.html