Hi,

Does DPM 2012 R2 still needs DataSourceGroups.xml and MaxAllowedParallelBackups key when using Hyper-V VSS Software Writer to backup Server 2012 R2 Hyper-V Cluster with CSV's? Can't find a clear answer somewhere.

Thanx for helping me out.

DJITS.

Hi,

I have Vm that have ISCSI attached drive with ISCSI initiator. DPM does not see the drives when I do a online backup of the VM. 

What is the way (if there is one) to take the ISCSI drives in the online backup?

Or do I need to take the drive with the agent installed in the VM?

Thank you,

Nicolas Desgroseilliers,

We have a 5 node cluster.  All nodes are running fully patched versions of Windows Server2012 Datacenter (including hotfixes KB2813630 and KB2796995).  Storage is EqualLogic running firmware 6.0.2.  All nodes have EqualLogic HIT 4.5 installed and we are using the hardware provider.  We have two 3TB thin provisioned CSVs setup.  One is not in use.  The other currently contains the first 14 VMs that have been moved from our existing stand-alone Windows Server 2008 R2 SP1 Hyper-V servers.  Only 5 of the 14 VMs are being backed up.  Protection was stopped and started for the move and the required consistency check was performed after the move.  The DPM server is a physical server running SCDPM 2012 SP1 RU2.  All Hyper-V servers have had their agent updated after RU2.  The SCDPM server only has a single protection group setup for all Hyper-V servers (legacy 2008 R2 servers and 2012 cluster).  All backups are succeeding on the legacy servers which are running the same EqualLogic HIT version and are storing their VMs on the same SAN.  Overnight, some backups will fail and others will succeed.  When I fix them up the next day, they will sometimes fail as well even if I tell it to resume backups on one VM at a time.  I can see the hardware snapshots being created on the SAN.  The SAN doesn't report any errors.  SCDPM fails and reports the following:

Type:    Recovery point
Status:    Failed
Description:    The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:A function call was made when the object was in an incorrect state
for that function
 (0x80042301))
    More information
End time:    4/23/2013 3:37:09 PM
Start time:    4/23/2013 3:34:44 PM
Time elapsed:    00:02:25
Data transferred:    0 MB
Cluster node    xxxxx.xxxx.xxx
Recovery Point Type    Express Full
Source details:    \Backup Using Child Partition Snapshot\vm1
Protection group:    Hyper-V VMs - Daily

It leaves the Micrsoft Hyper-V VSS Writer in a failed state with a Timed Out error.  All other VSS writers are fine.  I am also intermittently seeing the following in Application log on some nodes only when backups fail:

Event: 12363

Source: VSS

An expected hidden volume arrival did not complete because this LUN was not detected.

 LUN ID            {350f0b61-0244-4708-abab-a413fb710e7b}
 
 Version            0x0000000000000001
 Device Type        0x0000000000000000
 Device TypeModifier    0x0000000000000000
 Command Queueing    0x0000000000000001
 Bus Type        0x0000000000000009
 Vendor Id        EQLOGIC
 Product Id        100E-00
 Product Revision        6.0
 Serial Number        6090A0881074D4686E17059B9F4365CA
 
 Storage Identifiers
 Version        16
 Identifier Count    2

    Identifier        0
    CodeSet        "VDSStorageIdCodeSetBinary" (1)
    Type        "VDSStorageIdTypeFCPHName" (3)
    Byte Count    16

    60 90 A0 88  10 74 D4 68   6E 17 05 9B  9F 43 65 CA    `....t.hn....Ce.

    Identifier        1
    CodeSet        "VDSStorageIdCodeSetBinary" (1)
    Type        "VDSStorageIdTypeVendorSpecific" (0)
    Byte Count    16

    01 00 00 00  1F BF 0E 6A   00 00 00 3F  00 00 10 54    .......j...?...T
 
 

Operation:
   Exposing Volumes
   Locating shadow-copy LUNs
   PostSnapshot Event
   Executing Asynchronous Operation

Context:
   Execution Context: Provider
   Provider Name: Dell EqualLogic VSS HW Provider
   Provider Version: 4.5.0
   Provider ID: {d4689bdf-7b60-4f6e-9afb-2d13c01b12ea}
   Current State: DoSnapshotSet

Event: 8194

Volume Shadow Copy Service error: Unexpected error querying for the IVssWriterCallback interface.  hr = 0x80070005, Access is denied.
. This is often caused by incorrect security settings in either the writer or requestor process.

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {e8132975-6f93-4464-a53e-1050253ae220}
   Writer Name: System Writer
   Writer Instance ID: {d70791b2-f0fe-416e-bbea-e631878ee313}

Hello everybody,

Within the last few days I was trying to Setup the scale out protection of DPM 2012 R2.
The TechNet article isn't describe it clearly so I have to ask before I get lost.

The DPM 2012 SP1 and R2 can protect a Cluster with more than one DPM as descibed here:

http://technet.microsoft.com/en-us/library/jj656645.aspx

the -add Switch seems to be working.

But Flemming Riies writes:

"So adding the same VM to mutiple DPM servers wont work"

http://flemmingriis.com/dpm-scale-out-protection-for-hyper-v/

So scale out doesn't mean protecting a VM twice or more often. It only means I can use more than one DPM Server but every DPM is protecting different VMs?!

At the end it's better to chain the first DPM Server of a Cluster if I wish to have a second backup if the first DPM Fails?

Hello There,

I have a recovery point created for one of the VM which i am trying to recover but as soon as i click recover i get the error.

Please suggest.

Regards,

maqsood

Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

Hey guys,

I have a brand new Ubuntu LTS machine and can back it up properly.
But I don't understand why the machine is offline within DPM.

What I have is a small test System of Ubuntu Server 04.2014 LTS and i installed theVSS Snapshot daemon–

"This daemon is required to create live Linux virtual machine backups."

• and KVP daemon as well.

  Following the TechNet entry: http://technet.microsoft.com/en-us/library/dn531029.aspx

  Live virtual machine backup

  2012 R2

  √ Note 3, 4, 5

  So I'm not sure where the Problem is. Shouldn't the machine visible as online due to creation a protection Group of DPM?
  Everytime I'm creating a recovery Point and run a backup the machine is still online and I couldn't see an offline behavior which i would expect (save state).
  
  May I understand something wrong? Is there a backup guy here who has more Expertise with Debian and or ubuntu machines and can give me a hint?

  P.S.

  guest Services are enabled and the usual stuff like rebooting and dynamic Memory seems to be working very well.
  I have also an VMM 2012 R2 running but I'm pretty sure there shouldn't be a problem?!

Here is the architecture:

Hyper-V VM (2012 R2)

Hyper-V Host (2012 R2)

-------- SMB Share -----

2012 R2 Scale out file Server (2 Nodes)

The cluster validates fine. The error DPM reports in the console is this:

Failure occurred while adding one or more of the volumes involved in backup operation to snapshot set. Please check the event log on HOST to troubleshoot the issue. (ID 30290 Details: Internal error code: 0x809909E2)

Here is the Host's DPMRACurr log, reporting its unable to successfully retrieve the snapshots:

2E28    2DA4    09/11    23:06:39.755    31    vssbaserequestor.cpp(194)    [0000000000E71420]    63DEF0BE-D932-4038-B442-098D692DEEBD    NORMAL   CVssBaseRequestor::StartGatherWriterMetadata [0000000000E71420]
2E28    2DA4    09/11    23:06:42.783    31    vssbaserequestor.cpp(944)    [0000000000E71420]        NORMAL    QueryStatus returned 0x4230a, Releasing VssAsync [0000000001E8F5A0]
2E28    2DA4    09/11    23:06:42.815    22    hypervutil.cpp(493)            NORMAL    VMId: 2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F, ConfigFileName: \\hypervsofs\hypervstorage\vm1\bf200x67\Virtual Machines\2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F.xml
2E28    2DA4    09/11    23:06:42.830    31    vsssnapshotrequestor.cpp(1727)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::[0000000000E71420], Found matching vss logical path: , component name: 2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F, for writer id: {66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}
2E28    2DA4    09/11    23:06:42.830    31    hypervwriterhelperplugin.cpp(213)            NORMAL    Component Info, bstrLogicalPath:, bstrComponentName:2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F, eComponentType:2
2E28    2DA4    09/11    23:06:42.830    31    hypervwriterhelperplugin.cpp(171)            WARNING    Error:0, Failed to read user choice of backup
2E28    2DA4    09/11    23:06:42.830    31    hypervwriterhelperplugin.cpp(283)            NORMAL    bAllowOfflineBackup[1] bLogicalPathContainsOnlineBackup[1]
2E28    2DA4    09/11    23:06:42.830    31    vsssnapshotrequestor.cpp(252)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddComponentForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:42.846    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:42.893    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:42.893    31    vsssnapshotrequestor.cpp(482)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor: AddVolumeForSnapshot - Marked volume \\HYPERVSOFS\HYPERVSTORAGE\ to be snapshot
2E28    2DA4    09/11    23:06:42.893    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:42.940    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:42.940    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:42.971    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:42.971    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:43.033    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:43.033    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:43.080    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:43.080    31    vsssnapshotrequestor.cpp(1925)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForFile [0000000000E71420]
2E28    2DA4    09/11    23:06:43.127    31    vsssnapshotrequestor.cpp(459)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::AddVolumeForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:43.190    31    agentproxyhelper.cpp(67)            NORMAL    CSV share [\\HYPERVSOFS\HYPERVSTORAGE\], owner node [BF200S54]
2E28    2DA4    09/11    23:06:43.205    31    hypervwriterhelperplugin.cpp(558)    [00000000011502C0]        NORMAL    Component 2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F is a VM
2E28    2DA4    09/11    23:06:43.221    31    vsssnapshotrequestor.cpp(544)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::StartPrepareForBackup [0000000000E71420]
2E28    2DA4    09/11    23:06:43.236    31    vsssnapshotrequestor.cpp(1608)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::ReleaseVolumesForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:43.236    31    vsssnapshotrequestor.cpp(1505)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::PrepareVolumesForSnapshot [0000000000E71420]
2E28    2DA4    09/11    23:06:43.236    31    vsssnapshotrequestor.cpp(593)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor: Using provider {00000000-0000-0000-0000-000000000000} for volume \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:06:43.268    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:06:48.299    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:06:53.346    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:06:58.376    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:03.409    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:08.448    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:13.488    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:18.527    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:23.571    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:28.602    31    vsssnapshotrequestor.cpp(610)    [0000000000E71420]        NORMAL    Hr: = [0x8004230c] AddToSnapshotSet failed for Volume: \\HYPERVSOFS\HYPERVSTORAGE\
2E28    2DA4    09/11    23:07:33.618    31    vsssessioncontext.cpp(143)    [000000000331EA20]        WARNING    <VSS_CONTEXT><COMPONENTS><COMPONENT><WriterId>{66841CD4-6DED-4F4B-8F17-FD23F8DDC3DE}</WriterId><WriterName></WriterName><LogicalPath></LogicalPath><ComponentName>2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F</ComponentName><ComponentType>2</ComponentType></COMPONENT></COMPONENTS><SNAPSHOT_CONTEXT>          SelectComponent = 1,          PartialFileSupport = 0,          BootableState = 0,          BackupType = 1,          SnapshotContext = 0,          SnapshotAttributes = VSS_CTX_BACKUP          </SNAPSHOT_CONTEXT><SnapShotVolumes><Volume>             <Name>\\HYPERVSOFS\HYPERVSTORAGE\</Name>              <SnapshotPath>(null)</SnapshotPath>             <MountPoint>\\HYPERVSOFS\HYPERVSTORAGE\</MountPoint>              <MountPointArray></MountPointArray>             <SnapshotId>{00000000-0000-0000-0000-000000000000}</SnapshotId>              <ProviderId>{00000000-0000-0000-0000-000000000000}</ProviderId>             <IsHardwareProvider>0</IsHardwareProvider>              </Volume></SnapShotVolumes>
2E28    2DA4    09/11    23:07:33.618    31    vsssessioncontext.cpp(143)    [000000000331EA20]        WARNING    </VSS_CONTEXT>
2E28    2DA4    09/11    23:07:33.618    05    fsmtransition.cpp(111)    [0000000003323890]        WARNING    Failed: Hr: = [0x809909e2] HasEventErrorCode: completion: 0xa10c, signature: 0xaabbcc00
2E28    2DA4    09/11    23:07:33.618    31    vsssnapshotrequestor.cpp(2056)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::DoFailureCleanup [0000000000E71420]
2E28    2DA4    09/11    23:07:33.618    31    vsssnapshotrequestor.cpp(1608)    [0000000000E71420]        NORMAL    CVssSnapshotRequestor::ReleaseVolumesForSnapshot [0000000000E71420]
2E28    2C98    09/11    23:07:33.618    31    aasubtask.cpp(906)    [000000000331B840]        WARNING    <?xml version="1.0"?>
2E28    2C98    09/11    23:07:33.618    31    aasubtask.cpp(906)    [000000000331B840]        WARNING    <Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2137454110" Reason="Error" CommandID="RAPreBackup" CommandInstanceID="e8cf75b1-4e1e-4404-8536-b2abb128bcab" GuidWorkItem="ca282574-7bc3-4eec-b0da-6f6297707979" TETaskInstanceID="63def0be-d932-4038-b442-098d692deebd"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="998" DetailedCode="-2137454110" DetailedSource="2"/><RAStatus><RAPreBackup xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><BackupTime>0</BackupTime><DSStatus><ComponentName>2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F</ComponentName><LogicalPath></LogicalPath><BackupStamp></BackupStamp><Metadata></Metadata></DSStatus></RAPreBackup></RAStatus></Status>
2E28    2C98    09/11    23:07:33.618    03    runtime.cpp(1376)    [0000000000E740F0]        FATAL    Subtask failure, sending status response XML=[<?xml version="1.0"?>
2E28    2C98    09/11    23:07:33.618    03    runtime.cpp(1376)    [0000000000E740F0]        FATAL    <Status xmlns="http://schemas.microsoft.com/2003/dls/StatusMessages.xsd" StatusCode="-2137454110" Reason="Error" CommandID="RAPreBackup" CommandInstanceID="e8cf75b1-4e1e-4404-8536-b2abb128bcab" GuidWorkItem="ca282574-7bc3-4eec-b0da-6f6297707979" TETaskInstanceID="63def0be-d932-4038-b442-098d692deebd"><ErrorInfo xmlns="http://schemas.microsoft.com/2003/dls/GenericAgentStatus.xsd" ErrorCode="30290" DetailedCode="-2137454110" DetailedSource="2"><Parameter Name="AgentTargetServer" Value="VMHOST"/></ErrorInfo><RAStatus><RAPreBackup xmlns="http://schemas.microsoft.com/2003/dls/ArchiveAgent/StatusMessages.xsd"><BackupTime>0</BackupTime><DSStatus><ComponentName>2C20DA32-A22B-4BC9-B3C8-44AC6F406B3F</ComponentName><LogicalPath></LogicalPath><BackupStamp></BackupStamp><Metadata></Metadata></DSStatus></RAPreBackup></RAStatus></Status>
2E28    2C98    09/11    23:07:33.618    03    runtime.cpp(1376)    [0000000000E740F0]        FATAL    ]
2E28    2C98    09/11    23:07:33.633    31    vsssnapshotrequestor.cpp(656)    [0000000000E71420]    63DEF0BE-D932-4038-B442-098D692DEEBD    WARNING   Failed: Hr: = [0x809909e2] : AddToSnapshotSet failed for volume : \\HYPERVSOFS\HYPERVSTORAGE\ with hr: 0x8004230C
2E28    2C98    09/11    23:07:33.633    31    createsnapshotsubtask.cpp(1532)    [000000000331B840]    63DEF0BE-D932-4038-B442-098D692DEEBD   WARNING    Failed: Hr: = [0x809909e2] : Encountered Failure: : lVal : pSnapshotRequestor->StartPrepareForBackup(snapshotSetId, m_fUseSystemSoftwareProviderOnly)
2E28    2C98    09/11    23:07:33.633    05    fsmstate.cpp(167)    [0000000003322B80]    63DEF0BE-D932-4038-B442-098D692DEEBD    WARNING   Failed: Hr: = [0x809909e2] : Encountered Failure: : lVal : pTransition->Execute(pEvent)
2E28    2C98    09/11    23:07:33.633    05    genericfsm.cpp(225)    [000000000331BC00]    63DEF0BE-D932-4038-B442-098D692DEEBD    WARNING   Failed: Hr: = [0x809909e2] : Encountered Failure: : lVal : m_pCurrentState->SendEvent(pEvent, pNextState)
:

On the Scale out file server, the DPMRA service is acting like it can't find information about the cluster:

2354    1FF0    09/11    23:00:48.497    05    genericstatus.cpp(1662)    [000000000167C700]    FC676096-29B2-4AB1-9D60-12EAE58031B8    NORMAL   majorVerNum[4], minorVerNum[2], buildNum[1217], hotfixNum[0]
2354    1FF0    09/11    23:00:48.588    31    vssbaserequestor.cpp(51)    [0000000003963058]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    NORMAL   CVssBaseRequestor: constructor [0000000003963058]
2354    1FF0    09/11    23:00:48.588    31    vsssnapshotrequestor.cpp(91)    [0000000003963058]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    NORMAL   CVssSnapshotRequestor::CVssSnapshotRequestor [0000000003963058]
2354    1FF0    09/11    23:00:48.588    03    workitem.cpp(86)    [0000000001680F10]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    ACTIVITY   Idle Timer created with timeout = 390000
2354    1FF0    09/11    23:00:48.603    31    vainquirysubtask.cpp(424)    [0000000003962D20]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    NORMAL   Writer metadata not needed for inquiry.
2354    1FF0    09/11    23:00:48.603    61    inquirysubtask.cpp(1031)    [0000000003962D20]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    NORMAL   ==>CInquirySubTask::ExecuteInquiry
2354    1FF0    09/11    23:00:48.603    61    necluster.cpp(84)    [00000000039626B0]    29D2416C-EAE3-4D4F-9FD0-B05C4D1CA0F4    NORMAL   ==>CNECluster::EnumerateClusterDetails
235

Hi

I'm trying to accomplish step G: in the following picture:

"G. Based on the Shadow Copy device name from the Shadow Copy properties on the Application Server, the Backup Server can access the data on the Shadow Copy shares on the File Servers for backup. The Shadow Copy share will have the same permissions as the original share."

Everything works so far: The Fileserver create a Fileshare where the Shadow Copy is accessible. The VM share permissions on original share is: Everyone:Full and NTFS is: Hosts+DPM:Full.

According to Point G: DPM should get his backup directly from the Fileserver. But thats not the Case: Backup Traffic flows between Hyper-V Host and DPM Server. Any ideas?

Environment: all involved Servers are 2012 R2, DPM 2012 R2

Source: http://blogs.technet.com/b/clausjor/archive/2012/06/14/vss-for-smb-file-shares.aspx

Hi

I have created one big protection group containing all our hyper-v hosts. However, i'm not sure the backups that are being done are incremental, since I have already had to increase the replica volume and its been only 5 days. Currently there are "offline" linux vm's in the protection group.

So my question is actually: will dpm do incremental backups of my protection group members is they are all windows servers that state they are "online"?

Hello There,

i am running DPM2010 and i have created a protection group which contains VMs and System State data as you can see in the screen below the details.

The problem is DPM doesn't create any recovery points and i don't see any errors as well when i create short term recovery point manually it works.

This is all tape based protection, please suggest.

Regards,

Maqsood

Maqsood Mohammed Senior Systems Engineer MCITP-Enterprise Admin & ITILv3 Foundation Certified

Basic Configuration:

System Center Data Protection Manager version 2012 R2

OS - MS Server 2012 R2

Storage - DAS - Dell MD3220

Hyper-V - OS MS Server 2012 R2 - Clustered

Virtual Machine - MS Server 2008 R2

The backup of one VM has ran fine for over a month, then two days ago it just stopped working.  The is approx. 350 GB in size with 100 GB free.  The Storage location that DPM uses has over 5 TB free.

This is the error that I keep getting: is 

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:The specified object was not found.
 (0x80042308))

When I run vssadmin list writers on the host all writers show last error as No error, including Microsoft Hyper-V VSS Writer and Cluster Shared Volume VSS Writer.  

I am able to backup using DPM 3 other VM on the same Node.  

I Live Migrated this VM to the other node and got the same error.

I have rebooted the host same error.

I have deleted and recreated the vm same error.

I have verified that the integration services are up to date because the message comes up as This computer is already running the current version of integration services (version 6.3.9600.16384).

If I use Hyper-V Manager I can create manually a checkpoint I can also delete the check point.

Any help on this matter would be greatly appreciated.



Over the past week we have seen a problem where the System Volume Information folder has been growing at the rate of 20GB - 30Gb a days and there are now 670GB of files in the folder. Thjis is not related to the DPM Filter Bitmap files of which there are a lot but the volume is small compared to the remaining 630 files sized between 700MB and 11GB in size.

our setup is as follows:

2 x Node Active Active Server 2012 cluster with a single 5TB CSV volume mounted for Hyper-V images. We have 75 images running accross the two nodes and these are backed up using DPM 2012 SP1. Within DPM the VM's are split into four protection groups with differnet protection and retention setups.

I have checked the Shadop copy for the volume and this is disabled, checking on DiskShadow CLI using List Shadows All it returns 'No Shadow Copies found in Syatem'

DPM has been performing well with not a single backup failure over the last three weeks but all of a sudden on the 7th August (date of the oldes file in System Volume) we are retaining huge amounts of data.

Checking the event log I can see the following errors:

we get the following 7-8 times per day

Volume Shadow Copy Service warning: Writer received a Freeze event more than two minutes ago. The writer is still waiting for either an Abort or a Thaw event.

Operation:
   Gathering Writer Data

Context:
   Writer Class Id: {66841cd4-6ded-4f4b-8f17-fd23f8ddc3de}

   Writer Name: Microsoft Hyper-V VSS Writer
   Writer Instance ID: {7e0fa2fb-7392-485c-bb90-966d0198bd10}

We get these errors about 7 - 10 times per day:

VDS Basic Provider

Unexpected failure. Error code: 48F@01000003

I am really stumped by this so any help greatly appreaciated.

Thanks,

John

Hello, Our environment in currently in transition with planned migration to 2012 R2. In the mean time, we have a 5 node 2008 R2 hyper-v cluster with CSV.  We are currently using DPM 2012 for our backup.  I have read multiple postings about child partition backup and saved state and all that seems to make relative sense.

What I have noticed is that in our existing environment (2008 R2 Hyper-v, DPM 2012) that all 2012 R2 Virtual servers setup in our hyper-v cluster show 'Backup Using Saved State'.  All virtual 2003 - 2008 R2 servers on the same cluster show as 'Backup using Child Partition Snapshot'.

So, the question: is this normal and the only way virtual 2012 R2 servers can be backed up in our environment? Or, is there some configuration on the virtual 2012 R2 servers that needs to be done so that the Hyper-v VSS writers show that it can be backed up using Child Partition Snapshot. (Yes, I viewed the Hyper-V VSS Writer Caption: for each system on all the nodes and no, I am not talking about what is displayed in DPM 2012 since I understand it may not truly reflect the current backup method)

Hi,

We have the following setup and we are unable to take VMs backup that are clustered between two Hyper-v Hosts(server 2012)

• DPM application version: DPM 2012 R2
• DPM server operating system: Server 2008 R2

We are able to take the backup of individual VMs that are hosted in different hyper-v host server (server 2012) but we are unable to take VMs backup that are clustered between two Hyper-v Hosts(server 2012). we are getting the below error.

The replica of Microsoft Hyper-V \Backup Using Child Partition Snapshot\ABCSQL01 on ABCSQL01.ABCCluster.sss.co.in is inconsistent with the protected data source. All protection activities for data source will fail until the replica is synchronized with consistency check. You can recover data from existing recovery points, but new recovery points cannot be created until the replica is consistent.

For SharePoint farm, recovery points will continue getting created with the databases that are consistent. To backup inconsistent databases, run a consistency check on the farm. (ID 3106)

The VSS application writer or the VSS provider is in a bad state. Either it was already in a bad state or it entered a bad state during the current operation. (ID 30111 Details: VssError:A function call was made when the object was in an incorrect state

for that function

(0x80042301))

Rebooted both the hyper-v nodes and checked the writers all are in stable state. Triggered the backup still the same issue. Please help..

Thanks

Sunny

I have a 3 node 2012 hyper-v cluster. It has 2 network interfaces set to 'use for cluster + client can communicate' and one dedicated for 'use for cluster' with the lowest metric (the preferred CSV network). All network connections are 1Gb, all teamed with at least 2 ports each.

DPM backs up to tape only and is on a dedicated physical server.

When the disks are owned by a single node and all VM's are also on that node, the 'production LAN' is saturated and the backup gets the best possible speed, clearly showing the network is the limiting factor.

When some VM's are on another node, but the disks still owned by 'node 1', they are routed via node 1 during the backup process via the CSV network from the other node. I expect this to be the case. The strange thing in this case is that the bandwidth is measured at roughly 33% utilisation against the CSV network. All other interfaces remain idle.

If I take one of the other cluster networks which has 'use for cluster + client can communicate' and remove it from cluster usage, the CSV bandwidth increases to 50%. 

Clearly, the amount of nics that are designated to participate in cluster communication seems to then have a bearing on how much bandwidth the CSV network uses. If I had 4 I would expect 25% usage in the current scenario.

I thought this may be to do with SMB multi channel support in 2012, as I know that when doing a basic file copy from node 1 to node 2, the bandwidth is split across all 3 network interfaces, roughly in 33% chunks. I disabled SMB client and server multichannel on all Hyper-V nodes and when doing a file copy from a specific network from node 1 to node 2, only that interface was used - as per typical behaviour pre 2012.

However, it made no difference to the CSV bandwidth behaviour when VM and disk owner node differ - still at 33%. 

Hi,

We have a Microsoft System Center 2012 R2 Data Protection Manager Version 4.2.1235.0 as a Guest system on a Hyper-V node. The Hyper-V role is on a Windows Server 2012 R2

I receive this error message:

DPM cannot browse the contents of the virtual machine on the protected computer [computername]. Item level recovery is not supported in the following scenarios.
1. The VHD contains a dynamic disk inside the guest OS.2. The VHD has no volume.
3. HyperV role is not installed on DPM server.
4. Automatic mounting of volumes is disabled on the DPM server.

1) Try enabling automatic mounting of volumes using mountvol on the DPM server to perform item level recovery
2) Otherwise perform a full restore of the virtual machine.

ID: 958
Details: Internal error code: 0x80990F4E

One of our protected Hyper-V guest systems backup suddenly refuses to browse the content of the VHD file. The system has 2 VHDs. One for the operating system and one for the data. The OS VHD has no problem with content browsing only the data VHDX started this error after the installation of september update. I already checked the status that was suggested (1. the vhd contains a dynamic disk... etc. ) and everything is well configured. I have no free space to make a full recovery cause it's 6TB of data. 

The updates that were installed are:
DPM Server
KB2977629
KB2966828
KB2988948
KB2993651
KB890830
KB2977765
KB2894856

Protected Guest system
KB2972213
KB2977629
KB2894852
KB2973114
KB2993651
KB2988948
KB890830
KB2977765
KB2894856

Any advice? Thank you in advance for any help.

Andras

Hi, I have a Scale out Storage Spaces Server with 2 nodes, and a 10 node 2012 R2, Hyper-V cluster using this via SMB3.0

I also have installed a DPM2012 R2 backup server.

the DPM agent is installed on all nodes of all servers and I have followed the pre-requisite from Microsoft for setting up DPM backup of SMB Hyper-V machines.

The DPM backups all work fine. but occasionaly I get these errors on the SOFS cluster.

I really thought this issue had been resolved in this revision, this doesn't seem to cause any issues with my VM's that I can notice. and all DPM backups are working fine, but it still causes me concern.

has anyone else seen this or have any suggestions what I can try to resolve.

Regards

Mark Green

Hi,

I have read the MS documentation regarding excluding pagefile churns from virtual machines to increase performance of backups and reduce storage space required and I would like to implement this within our environment.

http://technet.microsoft.com/en-us/library/jj721498.aspx

However, when I move the pagefiile from the system disk onto a seperate VHD I get the following warning:

"If you disable the paging file or set the initial size to less than 400 megabytes and a system error occurs, Windows might not record details that could help identify the problem. Do you want to continue?"

As I understand things this means that I may not get a crash dump if a BSOD occurs. Is this correct, and if so how can I mitigate? How have others managed this scenario, do you just live with the fact that you won't get a dump file in the event of a problem?

Thanks in advance.

Microsoft Partner

I'm trying to restore a VM to an alternate server (S: Win2012R2 to D: Win2012)and keep getting error ID 30299.  

The recovery jobs for Microsoft Hyper-V \Online\(vm) that started at Wednesday, October 8, 2014 11:46:15 AM, with the destination of XXXX.DOMAIN.COM, have completed. Most or all jobs failed to recover the requested data. (ID 3111)

Any ideas?

Thanks,