DPM 2012 R2 CU4 protecting SQL 2014 AlwaysOn AG with Failover Cluster vs. DR location RRS feed

  • Question

  • Hello!

    We have a problem protecting any Database of SQL 2014 AlwaysOn Availability Group with SQL Failover Cluster Instance when moved to DR location. Everything is protected using DPM 2012 R2 CU4 from Primary location.

    - all servers are Windows Server 2012 R2
    - all servers are Virtual (except Hyper-V hosts obviously:)
    - that means virtualization is based on Windows Server 2012 R2 Hyper-V
    - all clusters (SQL, Exchange,...) are Guest Clusters on Hyper-V

    - SQL 2014
    - DPM 2012 R2 CU4

    - Primary and DR location 

    - Primary location: SQL 2014 Guest Cluster with SQL Failover Cluster Instance using Shared VHDX disks
    - DR location: SQL 2014 Standalone using VHDX disks
    - AlwaysOn Availability Group expands between the primary and DR location.

    - Primary location: DPM 2012 R2 CU4
    - DPM 2012 R2 CU4 Agents installed on every possible SQL 2014 Server.

    - DPM is backing up all the SQL Databases normally as long as they exist on any SQL Cluster Node on Primary location.
    - As soon as any Database is moved to DR location, that Database is not backed up anymore with the following error.

    Starting synchronization on SqlServerName\DatabaseName failed:
    Error 104: An unexpected error occurred while the job was running.
    Error details: The system cannot find the path specified (0x80070003)
    Recommended action: Retry the operation.

    - Tried to modify SQL Protection Group in DPM Server while Database was active on DR location
    > error enumerating volumes or drives D:\, E:\, F:\ (I don't have exact error atm)
    > this looks like DPM is not aware that DPM is active on DR location to me
    - Checked Technet, blogs and forums; no useful information

    Is this expected or by-design behavior? Is this a bug? I am aware there were quite some issues backing up AG's from DPM 2012 SP1 ans SQL 2012 on.
    Does anybody have a lab of that kind to try it out?

    Thank you!

    Best Regards,

    Damjan Grimšič


    Friday, January 23, 2015 3:42 PM

All replies

  • OK. The issue has been resolved. Issue was related to possible Disks Owners in Failover Cluster Manager Console for SQL Cluster.

    In Primary's site SQL Cluster Failover Manager Console / Storage / Disks.
    SQL Server(s) from Secondary location need(s) to be unchecked as Possible owner(s) in Advanced Policies for all relevant Volumes.


    Monday, March 9, 2015 2:24 PM