NetWorker: SQL Always-On backup failing with RPC error

Sammendrag: SQL Always on backup failed with RPC error. No communication issue between SQL nodes and backup server. From the logs backup is starting on node1 as Master node. And sending child job to node 2 but node2 is giving an RPC error. File system backup is successful on node2. ...

Denne artikkelen gjelder for Denne artikkelen gjelder ikke for Denne artikkelen er ikke knyttet til noe bestemt produkt. Det er ikke produktversjonene som identifiseres i denne artikkelen.
Ta en titt på andre ressurser

Symptomer

SQL Always on backup failed with RPC error. No communication issue between SQL nodes and backup server. From the logs backup is starting on node1 as Master node. And sending child job to node 2 but node2 is giving an RPC error. File system backup is successful on node2.

NMM SQL logs are having the following entries:
 

C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe:\n Original file name: nsrsqlsv.exe\n Version: 3.0.1.2.280\n Comments: Supporting SQL 2005, SQL 2008, SQL 2008 R2 and SQL 2012
bkup.com (pid23020) NSR info Command line:
bkup.com (pid23020) NSR info C:\Program Files\EMC NetWorker\nsr\bin\nsrsqlsv.exe -s legato.anadolu.com -g DDSQL_PAYAO -LL -m SC-PAY2012 -l full -q -W 78 -N MSSQL#AGPAY MSSQL#AGPAY
bkup.com (pid23020) NSR info Unable to fetch Application Information from resdb database
bkup.com (pid23020) NSR critical No active SQL Server found
bkup.com (pid23020) NSR critical Internal error in nsr/db_apps/bsmsql/sqlutil.c line 14182.
bkup.com (pid23020) NSR notice Started nsrcscd Successfully
bkup.com (pid23020) NSR critical Failed to get preferred node for backup of Availability group (AGPAY) with error: Can't connect to RPC server on sp.com.
bkup.com (pid23020) NSR notice 13 Stop time: %s 1 35 25 Sat Apr 25 13:32:08 2015

Årsak

There is an issue with the failover-cluster owner.

Oppløsning

Change the failover-cluster owner.

To modify the failover settings for a clustered service or application:
  1. In the Failover Cluster Manager snap-in, if the cluster that you want to configure is not displayed, in the console tree, right-click Failover Cluster Manager, click Manage a Cluster, and then select or specify the cluster that you want.
  2. If the console tree is collapsed, expand the tree under the cluster that you want to configure.
  3. Expand Services and Applications.
  4. Right-click the service or application that you want to modify the failover settings for, and then click Properties.
  5. To configure failback, on the General tab, change settings for preferred owners, then click the Failover tab and choose options under Failback.
You must configure a preferred owner if you want failback to occur (that is, if you want a particular service or application to fail back to a particular node when possible).
  1. To configure the number of times that the cluster service should attempt to restart or fail over a service or application in a given time period, click the Failover tab and specify values under Failover.

Tilleggsinformasjon

Modify the Failover Settings for a Clustered Service or Application.
For more information about failover settings for a clustered service or application, see Modifying the Settings for a Clustered Service or Application.

Berørte produkter

NetWorker, NetWorker Module for Microsoft

Produkter

NetWorker
Artikkelegenskaper
Artikkelnummer: 000018717
Artikkeltype: Solution
Sist endret: 22 jan. 2026
Versjon:  4
Få svar på spørsmålene dine fra andre Dell-brukere
Støttetjenester
Sjekk om enheten din er dekket av støttetjenestene.