Forum Discussion

arctics2's avatar
arctics2
Level 5
8 years ago

SQL 2014 Mirror on VMware

Backing up SQL 2014 Mirrored VMs on VMware.  Netbackup 7.7.1.  The backups are always partially successful with a status 1.  The Application State Capture job on the passive node returns the following results:

Warning ascc (pid=29156) MSSQL: Skipping database MSSQLSERVER\DB_NAME. The database is in the RESTORING state and cannot be protected.

Just want to confirm this is normal behaviour since it's the secondary node.  I find it odd that it would return a status 1 for this reason.  I would think that the parent job would be able to determine whether the DBs that are in a "restoring state" were picked up in the child job that runs on the primary node.  

2008) Not Applicable
7.7
mssql
SQL
VMware
  • Michal_Mikulik1's avatar
    Michal_Mikulik1
    8 years ago

    Hello arctics2,

    yes with VMware based policy, you cannot get rid of status 1 in this case.

    You must use intelligent MS-SQL-Server based policy with "Skip unavailable databases" option for mirroring partner, if you wanna run without status 1.

    However I would rather run VMware policy because it provides quicker DR. I think that run it once a week is enough for mirroring partner (and once a day or more frequently for the principal).

    Regards

    Michal

  • arctics2's avatar
    arctics2
    8 years ago

    Thanks Michal.  This is exactly the confirmation I was looking for.

    Regarding the intelligent policy option, as per the guide, database mirroring is not supported for Intelligent policies.

    Regarding changing the frequency, my only concern is that if databases failover to the mirroring partner, and I've reduced frequency for the mirror backups, it will be a problem since they are now the principal, and the original principal is now the mirroring partner.

    I will leave it as is so both instances are backed up simultaneously (as recommended in the guide), however, I think the parent job should be intelligent enough to complete with a status 0 since the db's were backed up in the principal node.

8 Replies

Sort By
  • P_Kesavan's avatar
    P_Kesavan
    Level 4
    8 years ago

    Hi ,

    Moreover as per the error log you have posted , it looks like the DB is in restoring state.

    MS SQL does not allow to backup of db's in restoring state as it is not completely online (it is understood as unavailable DB until becomes online).

    Regards,

    Kesavan

    • arctics2's avatar
      arctics2
      Level 5
      8 years ago

      Kesavan,

      Yes, the DB's would be a "restoring" state on the standby node in the Mirror.  This is by design in an SQL mirror.

      However, as per the Netbackup for SQL admin guide, both nodes in the Mirror need to be added to the policy to ensure they are backed up together, specifically for the reason you specified.  The db's on the standby node would not be backed up and only the live db's on the primary node would be backed up. 

      This is understood, however, if this is the only reason it's returning a status 1 at the parent job, it raises a false concern that something has gone wrong, when in fact, it is running as expected. 

      Thanks

      • Michal_Mikulik1's avatar
        Michal_Mikulik1
        Moderator
        8 years ago

        Hello arctics2,

        yes with VMware based policy, you cannot get rid of status 1 in this case.

        You must use intelligent MS-SQL-Server based policy with "Skip unavailable databases" option for mirroring partner, if you wanna run without status 1.

        However I would rather run VMware policy because it provides quicker DR. I think that run it once a week is enough for mirroring partner (and once a day or more frequently for the principal).

        Regards

        Michal

    • arctics2's avatar
      arctics2
      Level 5
      8 years ago

      Marianne,

      Thanks for the quick response. 

      I am actually referring to mirroring, not to be confused with clustering.  From the Netbackup for MS SQL admin guide:

      Database mirroring is a software solution that increases the availability of a SQL Server database. It uses two database instances (normally on different hosts), which contain copies of the same SQL Server database. These databases are identical in both name and content. The copies are the principal and the mirror. The mirror serves as a hot standby to the principal, where transactions take place. The mirror is very closely synchronized with the principal through transaction log porting.  It is immediately available in case the principal fails.