Jump to content


Photo

Cluster Shared Volume support on Server 2008 R2


This topic has been archived. This means that you cannot reply to this topic.
11 replies to this topic

#1 8woodj

8woodj
  • Members
  • 1 posts

Posted 21 April 2010 - 05:53 AM

Is there any likelihood for the support of CSV's on W2K8R2 running Hyper-V sometime in the near future? I have got myself a bit caught up in the great virtualisation rush and after attending a couple of Hyper-V seminars and seeing CSV's used on a SAN to enable live migration I set about configuring here at work 2 x W2K8R2 servers, an iSCSI SAN and creating a CSV. I then installed some test VM's and successfully performed live migration of the VM's which would be great to roll out as it would provide a much higer level of fault tolerance thatn our current set-up. My problem now is backing the VM's up as Yosemite 8.8.0.2 doesn't recognise the CSV. I know I can use guest agents but can that not cause performance problems if multiple guests are backing up simultaneously off the same SAN?I have looked at alternative backup solutions from other vendors and the pricing is just crazy once all the necessary agents are purchased.Many thanksJon

#2 daex1408

daex1408
  • Members
  • 10 posts

Posted 21 April 2010 - 03:42 PM

Hey Jon, i'm into the same issue, running 2 Hyper-V Hosts in Cluster configuration but i also have to use Agents inside the VM.I'm getting Error 5084 (something about inconsistent amount of snapshot objects)Regards,Lars

#3 czakoi

czakoi
  • Members
  • 1 posts

Posted 01 March 2011 - 07:21 AM

Hi!I have the same Error 5084: Snapshot object selection inconsistent issue on clustered HYPER-V based VMs. Will the YSBU support backup of clustered VMs?Regards,Istvan

#4 Ben Kloos

Ben Kloos
  • Barracuda Team Members
  • 10 posts

Posted 03 March 2011 - 06:15 PM

8woodj:Have you installed the software on both 2008R2 machines and confirmed that neither of them can see the shared volume in the software? I would have expected that the primary node in your cluster would have been able to see it. Also, are you trying to backup the virtual machines with our hyper-v connector or are you trying to backup the files which make up the virtual machines. We generally suggest to use the first option since the connector allows you to backup the machines while they are live.As to your other question there would be a performance hit if you installed the agent to each VM and backed them up like that but the advantage would be if you wanted to restore only a specific component of that virtual machine. For example if there was some problem with the registry or IIS or some specific loss on the file system you could restore that specific component without trashing the entire virtual machine if you were using the agent on the guest.

#5 Ben Kloos

Ben Kloos
  • Barracuda Team Members
  • 10 posts

Posted 03 March 2011 - 06:17 PM

For both of you getting the error 5084 I'm going to need a bit more information. Can you look at your event logs from the time those errors were showing up in the backup log and share with us what errors you are seeing there?

#6 jedantamobgd

jedantamobgd
  • Members
  • 1 posts

Posted 06 March 2011 - 09:35 AM

:)

#7 czakoi

czakoi
  • Members
  • 1 posts

Posted 16 March 2011 - 09:43 AM

Hi!There is nothing in event logs about snapshot. But in the yttrace.txt file I can find the following traces:03/16/2011 4:06:51 AM [YClientCtx] CheckWriterStatus from YClientCtx::DoSnapshotSet03/16/2011 4:06:51 AM [YClientCtx] Bad writer status [Microsoft Hyper-V VSS Writer]: VSS_WS_FAILED_AT_PREPARE_SNAPSHOT03/16/2011 4:06:51 AM [YClientCtx] Backup Components Document: <BACKUP_COMPONENTS xmlns="x-schema:#VssComponentMetadata" version="1.2" bootableSystemStateBackup="yes" selectComponents="yes" backupType="full" partialFileSupport="no" snapshotSetId="290bb1a6-9979-46f6-bc45-4b47bf5c8e74"><WRITER_COMPONENTS instanceId="46ae081e-f0ed-4354-a3b6-4128c06cb1a1" writerId="afbab4a2-367d-4d15-a586-71dbb18f8485" backupSchema="0"><COMPONENT componentName="Registry" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS instanceId="9f666e27-f2d3-460a-bd8a-212783139506" writerId="542da469-d3e1-473c-9f4f-7847f01fc64f" backupSchema="0"><COMPONENT componentName="COM+ REGDB" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS instanceId="ea280871-cb56-40fc-96e6-855cdbed3cd0" writerId="be000cbe-11fe-4426-9c58-531aa6355fc4" backupSchema="0"><COMPONENT logicalPath="Volumes" componentName="Volume{b610c70f-327f-11df-aeb6-18a90567de7a}" componentType="filegroup"/><COMPONENT logicalPath="Volumes" componentName="Volume{b610c716-327f-11df-aeb6-18a90567de7a}" componentType="filegroup"/><COMPONENT logicalPath="Disks" componentName="harddisk3" componentType="filegroup"/><COMPONENT logicalPath="Disks" componentName="harddisk2" componentType="filegroup"/><COMPONENT logicalPath="Disks" componentName="harddisk1" componentType="filegroup"/><COMPONENT logicalPath="Disks" componentName="harddisk0" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS instanceId="088e7a7d-09a8-4cc6-a609-ad90e75ddc93" writerId="75dfb225-e2e4-4d39-9ac9-ffaff65ddf06" backupSchema="0"><COMPONENT componentName="WriterMetadataStore" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS instanceId="f0086dda-9efc-47c5-8eb6-a944c3d09381" writerId="0bada1de-01a9-4625-8278-69e735f39dd2" backupSchema="0"><COMPONENT componentName="PerformanceCounters" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS instanceId="a06449cd-6598-4896-aae5-6305a0788a5c" writerId="d76f5a28-3092-4589-ba48-2958fb88ce29" backupSchema="0"><COMPONENT logicalPath="SYSVOL" componentName="fb8e2896-dd28-42ed-b4eb2fb51c60dd92" componentType="filegroup"/></WRITER_COMPONENTS><WRITER_COMPONENTS xmlns="x-schema:#VssComponentMetadata" instanceId="21801302-249f-43c0-b350-0447fb1e4906" writerId="66841cd4-6ded-4f4b-8f17-fd23f8ddc3de" backupSchema="256"><COMPONENT componentName="280A6FF9-28F4-4B6C-AD00-8306F06A6632" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="512*E:VMS*Virtual Machines*280A6FF9-28F4-4B6C-AD00-8306F06A6632*Backup Using Saved State;eb140a16-e064-461c-888c-ae1c11a2bf0d|0|0|100|100|OFFICE|0||;b138f620-c8a6-4416-83b5-59f994a836b9|100|0|100|100|PARADOX|0||;"/></COMPONENT><COMPONENT componentName="70F00BE8-A384-4727-B460-A9DB970484FA" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="512*E:VMS*Virtual Machines*70F00BE8-A384-4727-B460-A9DB970484FA*Backup Using Child Partition Snapshot;bb8459d9-a586-4008-8556-1b1d47f73405|0|0|100|100|OFFICE|0||;"/></COMPONENT><COMPONENT componentName="994BCA97-4DAF-4AEA-B939-E1E4282290C3" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="512*E:VMSHYPERION*Virtual Machines*994BCA97-4DAF-4AEA-B939-E1E4282290C3*Backup Using Child Partition Snapshot;9e0afdd2-82dd-4e86-a3ca-169019a4b1ea|0|0|100|100|OFFICE|0||;"/></COMPONENT><COMPONENT componentName="Initial Store" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="C:ProgramDataMicrosoftWindowsHyper-VInitialStore.xml|Hyper-V services"/></COMPONENT><COMPONENT componentName="2ED88900-34F7-4734-95FB-6DBFE6B3EA9C" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="C:ClusterStoragevolume1vms|Virtual Machines|2ED88900-34F7-4734-95FB-6DBFE6B3EA9C|Backup Using Child Partition Snapshot;7ebb319f-668b-4d67-91fa-599eb902c4d9|0|0|100|100|OFFICE|0||;"/></COMPONENT><COMPONENT componentName="7E6A8C9D-C52D-46CE-92DC-6ADDA367D8D5" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="C:ClusterStoragevolume1vms|Virtual Machines|7E6A8C9D-C52D-46CE-92DC-6ADDA367D8D5|Backup Using Child Partition Snapshot;62e09679-e014-4a72-b730-037e977516ca|0|0|100|100|OFFICE|0||;"/></COMPONENT><COMPONENT componentName="D42A814D-9596-4BB6-B3AA-0C477622F1A3" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="C:ClusterStoragevolume1vms|Virtual Machines|D42A814D-9596-4BB6-B3AA-0C477622F1A3|Backup Using Child Partition Snapshot;5830516b-a13b-4f22-9e8f-a83a14519235|0|0|100|100|OFFICE|0||;"/></COMPONENT><COMPONENT componentName="E251355D-FAAD-4FE2-8D20-0570675DDB9D" componentType="filegroup"><BACKUP_METADATA xmlns="" metadata="C:ClusterStoragevolume1vms|Virtual Machines|E251355D-FAAD-4FE2-8D20-0570675DDB9D|Backup Using Child Partition Snapshot;cc6e0b09-bcbb-473a-abe0-27f5f9e84db2|99|0|100|100|ARGUS|0||;"/></COMPONENT></WRITER_COMPONENTS></BACKUP_COMPONENTS>03/16/2011 4:06:51 AM Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. '03/16/2011 4:06:51 AM [YClientCtx] Failed to perform snapshot Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. '03/16/2011 4:06:51 AM [YClientCtx] Failed to do snap set03/16/2011 4:06:51 AM [YClientCtx] Failed to create backup snapset Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. ' Thanks,Istvan

#8 czakoi

czakoi
  • Members
  • 1 posts

Posted 16 March 2011 - 11:49 AM

Hi!There is nothing in the event logs of servers. But I have found the following trace logs in yttrace.txt on a cluster host:03/16/2011 4:06:51 AM [YClientCtx] CheckWriterStatus from YClientCtx::DoSnapshotSet03/16/2011 4:06:51 AM [YClientCtx] Bad writer status [Microsoft Hyper-V VSS Writer]: VSS_WS_FAILED_AT_PREPARE_SNAPSHOT03/16/2011 4:06:51 AM [YClientCtx] Backup Components Document:..........03/16/2011 4:06:51 AM Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. '03/16/2011 4:06:51 AM [YClientCtx] Failed to perform snapshot Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. '03/16/2011 4:06:51 AM [YClientCtx] Failed to do snap set03/16/2011 4:06:51 AM [YClientCtx] Failed to create backup snapset Exception - Original: 2147754992 - 0x800423f0 Mapped:5084 Location:YClientCtx::CheckWriterStatus:8.98.9.01odsddvamyclientctx.cpp:1525 Description:'The shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. 'Thanks,Regards,Istvan

#9 Ben Kloos

Ben Kloos
  • Barracuda Team Members
  • 10 posts

Posted 16 March 2011 - 04:27 PM

A few more questions:- Are you trying to backup the hyper-v guest and host in the same backup job? Doing so can cause problems. - Is Exchange 2010 installed and if so have you applied this hotfix? http://support.microsoft.com/kb/2181692- Are you positive the event logs do not have anything pertinent? This error should be there being that it is coming from the volume shadow copy service "he shadow-copy set only contains only a subset of the volumes needed to correctly backup the selected components of the writer. "

#10 czakoi

czakoi
  • Members
  • 1 posts

Posted 17 March 2011 - 06:33 AM

- Yes, hosts and virtual guests are backed up in the same job- Exchange is not installed on hosts- No errors about backup in event logBut I can find the following error if I list VSS writers: Writer name: 'Microsoft Hyper-V VSS Writer' Writer Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de} Writer Instance Id: {21801302-249f-43c0-b350-0447fb1e4906} State: [8] Failed Last error: Inconsistent shadow copy

#11 Ben Kloos

Ben Kloos
  • Barracuda Team Members
  • 10 posts

Posted 17 March 2011 - 12:17 PM

I would strongly suggest separating the host and guest in to separate jobs, at least as a test. Asking the host to snapshot it's volume while the guest does the same would give VSS fits in our experience. May or may not be the problem here but certainly is where I want to start.

#12 czakoi

czakoi
  • Members
  • 1 posts

Posted 17 March 2011 - 02:09 PM

I have made a test. If I would like to backup the system state or a file on the host everything goes fine (100% success). If I backup a guest VM via HYPER-V agent on host which is not clustered: 100% OKBut! If I would like to backup a guest VM on the host which is clustered and its files are stored on CSV or a backup job contains a VM which is clustered and stored on CSV: unsuccessfullThe entire job failed not just the clustered VMs.