Unsolved

This post is more than 5 years old

1 Rookie

 • 

45 Posts

4913

June 9th, 2017 07:00

Federated Backup Fails after Migration to NetWorker Server version 8.2.4

Hello Experts We've got an issue with a federated SQL Client. After moving to a new NetWorker Server running Version 8.2.4 the federated backup fails. The same client still suceeds on the old NSR running Version 8.1.2.7 NMM has been upgraded from 3.0 to 8.2.4. NetWorker Client has been upgraded from 8.1.x to 8.2.4 as well Running the following Backup Command will lead to a failed Backup: nsrsqlsv.exe -vvvv -s NSR-Server -g "W_SQL_SG060_PRD-09" -m Logical-Host -l full -N MSSQL$RCHZDBA11#R0001971 MSSQL$RCHZDBA11#R0001971 43708:(pid 9840):Start time: Fri Jun 09 13:36:31 2017 43621:(pid 9840):Computer Name: Physical-Host    User Name: Username 85897:(pid 9840): Res-list is NULL85555:(pid 9840):Unable to fetch Application Information from resdb database 29446:(pid 9840):Local host has following SQL Server online: 37977:(pid 9840):              MSSQL server : Physical-Host\RCHZDBA12 100220:(pid 9840):Saveset [MSSQL$RCHZDBA11#R0001971] validated. 96808:(pid 9840):Successfully converted from group id to AG name. 57777:(pid 9840):Multiple client instances of Physical-Host.ad.raiffeisen.ch, using the first entry 51340:(pid 9840):jobhandler(340): Created Job ID: 789359         Save command: nsrsqlsv.exe -vvvv -s NSR-Server -g W_SQL_SG060_PRD-09 -m Physical-Host -l full -z FEDERATED_SLAVE=true -z FEDINDEX_NAME=MSSQL$RCHZDBA11 -z FEDCLIENT_NAME=CNO00197 -z NSR_JOB_PARENT_JOBID=0 -N MSSQL$RCHZDBA11#R0001971 MSSQL$RCHZDBA12:KASD_R0001971 85942:(pid 9840):Stopping Federated backup - ==========nsr/db_apps/bsmsql/sqlxbsacompforsave.cpp(706): Slave backup with job id (789359) failed on node Physical-Host with error status: 127 ========== At the same time the daemon.log on NSR shows this entry: daemon.log:165682 06/09/2017 01:37:08 PM  nsrjobd RPC critical Unable to create session channel to host vwx00198 to execute command 'nsrsqlsv.exe -vvvv -s vlx00371.essd.ch -g W_SQL_SG060_PRD-09 -m vwx00198 -l full -z FEDERATED_SLAVE=true -z FEDINDEX_NAME=MSSQL$RCHZDBA1 -z FEDCLIENT_NAME=CNO00197 -z NSR_JOB_PARENT_JOBID=0 -N MSSQL$RCHZDBA11#R0001971 MSSQL$RCHZDBA12:KASD_R0001971': Unknown host After performing the Slave Backup Job directly, the backup succeeds: nsrsqlsv.exe -vvvv -s NSR-Server -g W_SQL_SG060_PRD-09 -m Physical-Host -l full -z FEDERATED_SLAVE=true -z FEDINDEX_NAME=MSSQL$RCHZDBA11 -z FEDCLIENT_NAME=CNO00197 -z NSR_JOB_PARENT_JOBID=0 -N MSSQL$RCHZDBA11#R0001971 MSSQL$RCHZDBA12:KASD_R0001971 43708:(pid 6304):Start time: Fri Jun 09 13:38:27 2017 43621:(pid 6304):Computer Name: Physical-Host    User Name: Username 163849:(pid 6304):Setting federated worker process=true 163850:(pid 6304):Setting Index name for federated worker process 163851:(pid 6304):Set the client for federated worker process 163848:(pid 6304):Setting job ID for federated worker process:0 107478:(pid 6304): This is a slave node for federated backup. No need to read the client resource. nsr/db_apps/bsmsql/sqlutil.c(12421): SQL Server FILESTREAM Database called for database 'KASD_R0001971'            NSR_BACKUP_LEVEL: full;             NSR_CFI_USE_HINT: TRUE;                   NSR_CLIENT: CNO00197;           NSR_DIRECT_ACCESS: default;                   NSR_GROUP: W_SQL_SG060_PRD-09;               NSR_READ_SIZE: 4194304;             NSR_SAVESET_NAME: "MSSQL$RCHZDBA11#R0001971";                   NSR_SERVER: NSR-Server; 37994:(pid 6304):Backing up KASD_R0001971... 142036:(pid 6304):Backup configured with maxtransfersize = 4194304 4690:(pid 6304):BACKUP database [KASD_R0001971] TO virtual_device='Legato#32ad60e4-fbdb-4bf9-871f-151b59652290' WITH name=N'LegatoNWMSQL', description=N'MSSQL$RCHZDBA11#R0001971', maxtransfersize = 4194304 06/09/17 13:39:43.314190 libDDBoost version: major: 3, minor: 1, patch: 2, engineering: 0, build: 543546 86704:(pid 6304): Successfully established DDCL session for save-set ID '1211795708' (CNO00197:MSSQL$RCHZDBA11#R0001971). nsr/db_apps/bsmsql/sqlxbsacompforsave.cpp(987): Calling job completion attributes for saveset: 1497008376 (0)         time = 91333 microseconds, 53085:(pid 6304):Backing up of KASD_R0001971 succeeded. Physical-Host: MSSQL$RCHZDBA11#R0001971 level=full, 4183 KB 00:00:11      1 file(s) 86704:(pid 6304): Successfully established DDCL session for save-set ID '1144686849' (CNO00197:MSSQL$RCHZDBA11#R0001971).         time = 103938 microseconds, 43709:(pid 6304):Stop time: Fri Jun 09 13:39:47 2017 Any idea what the problem can be? Thanks Christian

2.4K Posts

June 12th, 2017 13:00

Hard to say if you look at this unstructered message.

My personal guess is the name resolution/alias - sometimes the NW server refers to 'NSR-Server', sometimes to'vlx00371.essd.ch'. This looks at least strange.

0 events found

No Events found!

Top