Can snapmanager for hyper-v take backup/snapshot of a vm running linux

[babar]

Hi all,

IHAC who wants to know if its possible to use snapmanager for hyper-v to take snapshot of a vm running RHEL Linux.

Regards,

Babar

[vkarinta]

Yes, SnapManager for Hyper-V can be used to take the backups of linux VMs.

A saved state backup of the VM will be taken by the Hyper-V writer since the Hyper-V Integration components are not supported for Linux.

Thanks,

Vineeth

[babar]

Hi Vkaritna,

Thankyou for your super fast answer. Is there a document which says that? Cause the snapmanager 1.0 for hyper-v best practice says (tr-3805) under "vm support" only shows suse linux.

A saved state backup of the VM will be taken by the Hyper-V writer since  the Hyper-V Integration components are not supported for Linux.

If possible could you elaborate a little. If the vss cannot speak to the underlying os how will it put it into hot standby mode?

Sorry for bombarding you with more queries.

Regards,

Babar

[vkarinta · Accepted solution]

I remember we also only tested suse linux during our QA cycles.

The saved state backup means, the VM will be momentrily put in a special state, during this process

all the contents of the memory are serialized to disk and the VM backup will be taken at this point.

Once the backup is completed the VM is restored to it's original state.

Regarding supportability on different flavours of linux i suggest you can contact NGS to get the official answer.

Thanks,

Vineeth

[babar]

Thank you for your detailed response.

Regards,

Babar

[vkarinta]

One more point i missed to mention is that, during the saved state the clients of the VM can experience some down time until the time saved state is active.

The VM will then be brought to it's original state later.

Thanks,

Vineeth

[wallstreetinstitute]

Hi,

we've a FAS2040. I'va a problem with SnapManager. I can't backup Linux or XP (and some Server2003) Machines in the Hyper-V Cluster, only Server2008 and Server2003 guest vm's works.

SnapManager (using this powershell command: new-backup -ds WIN-VMs -rt daily -rtdays 8 -updmir -assb -bk WIN-VMs or new-backup -ds Linux -rt daily -rtdays 8 -updmir -assb):

[11.04.2011 09:50:13, (38)] Error: Vss Requestor - Backup Components failed with partial writer error.Writer Microsoft Hyper-V VSS Writer involved in backup or restore operation reported partial failure. Writer returned failure code 0x80042336. Writer state is 5.
Application specific error information:
Application error code: 0x1
Application error message: -
Failed component information:
Failed component: \656BE11E-CD14-4B52-AD30-C60FBCFD9BCC
Writer error code: 0x800423f3
Application error code: 0x80004005
Application error message: Failed to create the backup of virtual machine 'WDS'. (Virtual machine ID 656BE11E-CD14-4B52-AD30-C60FBCFD9BCC)

For more information, look at the Hyper-V-VMMS event log in the Windows Event Viewer under "Applications and Services Logs->Microsoft->Windows".

Windows Event Viewer under "Applications and Services Logs->Microsoft->Windows:

Application error code: 0x80004005
<EventID>10102
Failed to create the backup of virtual machine 'WDS'.
Microsoft-Windows-Hyper-V-VMMS/Admin:
Event ID 10102

Log Name:      Microsoft-Windows-Hyper-V-VMMS-Admin
Source:        Microsoft-Windows-Hyper-V-VMMS
Date:          11.04.2011 09:48:11
Event ID:      10102
Task Category: None
Level:         Error
Keywords:     
User:          SYSTEM
Computer:      HYPER-V-1.wallstreetinstitute.de
Description:
Failed to create the backup of virtual machine 'WDS'. (Virtual machine ID 656BE11E-CD14-4B52-AD30-C60FBCFD9BCC)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-Windows-Hyper-V-VMMS" Guid="{6066F867-7CA1-4418-85FD-36E3F9C0600C}" />
    <EventID>10102
    <Version>0</Version>
    <Level>2</Level>
    <Task>0</Task>
    <Opcode>0</Opcode>
    <Keywords>0x8000000000000000</Keywords>
    <TimeCreated SystemTime="2011-04-11T07:48:11.654789200Z" />
    <EventRecordID>4410
    <Correlation />
    <Execution ProcessID="3724" ThreadID="5976" />
    <Channel>Microsoft-Windows-Hyper-V-VMMS-Admin</Channel>
    <Computer>HYPER-V-1.wallstreetinstitute.de</Computer>
    <Security UserID="S-1-5-18" />
  </System>
  <UserData>
    <VmlEventLog xmlns:auto-ns2="http://schemas.microsoft.com/win/2004/08/events" xmlns="http://www.microsoft.com/Windows/Virtualization/Events">
      <VmName>WDS</VmName>
      <VmId>656BE11E-CD14-4B52-AD30-C60FBCFD9BCC</VmId>
    </VmlEventLog>
  </UserData>
</Event>

Need Help!

Thanks,

Frank

[vkarinta]

SMHV does support Backup of linux vms, 2003 non sp2 versions, and XP VMs, backups will be taken using the saved state backup.

Please make sure that proper integration components are installed on the VM. During saved state VM is temprorily put in saved state and backup is taken

once the backup is complete, vm is brought back to the previous state before the backup.

For Linux VMs use the following Linux Integration Services v2.1 from MS

http://www.microsoft.com/downloads/en/details.aspx?FamilyID=eee39325-898b-4522-9b4c-f4b5b9b64551

For windows VMs, please check the application event logs inside the guest to see any errors during the time of the backup from VSS or other components.

Thanks,

Vineeth

[wallstreetinstitute]

Hi Vineeth,

thanks for the answer.

We use Ubunu, so no integration-tools available, anyway, save state backup would be great. But it doesn't work. With Windows Backup (on Hyper-V) it works, all guest machine without integrationtools go into savestate and get backed up. But now in the Hyper-V Cluster an d NetAapp SnapManager it doesn't work. Everytime we get an error. SnapManager SNHV run this command new-backup -ds Linux -rt daily -rtdays 8 -updmir -assb (assb=allowsavestatebackup).

No errors in the vm. Only VSS startet, VSS stopped.

Cheers

Frank

[wallstreetinstitute]

it seems to be a problem with the virtual machine id's and a problem with with machine names. We deleted the machines in the cluster and then imported them to the cluster. Underlines "_" in the name causes problems. Save state for Linux works now.