This post is more than 5 years old
19 Posts
0
6952
Netwoker Client Direct Backup not Working
Hi,
We have the NW 9.1 deployed on a VM. OS is Win 2012 R2. We are expecting backup slowness on our DB client. It contains ~1.4 TB data. We are use the client direct for backup the data to DD. To investigate this issue we have rendered the daemon.raw file in the NW server and go through it. Then we are able to identified client direct backup it not happening. Pls refer the below log output.
70896 9/19/2018 4:00:50 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool 'Digital_Banking_Prod_DB' (DigitalBankingProdDB.001)
91797 9/19/2018 4:00:50 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device 'DWHDD1_Digital_Banking_Prod_DB'; setting up traditional save for save-set ID '3600907418' (prdbsvr1:DB2:/PB_PROD/NODE0000)
71659 9/19/2018 7:44:12 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 done saving to pool 'Digital_Banking_Prod_DB' (DigitalBankingProdDB.001) 1358 GB
70896 9/19/2018 7:44:15 AM 0 0 2 8440 1320 0 win-afvg9er8ckm nsrd NSR info prdbsvr1:DB2:/PB_PROD/NODE0000 saving to pool 'Digital_Banking_Prod_DB' (DigitalBankingProdDB.001)
91797 9/19/2018 7:44:15 AM 4 5 0 4664 9432 0 win-afvg9er8ckm nsrmmd NSR severe Unable to perform direct file save with Data Domain device 'DWHDD1_Digital_Banking_Prod_DB'; setting up traditional save for save-set ID '2124525815' (prdbsvr1:DB2:/PB_PROD/NODE0000)
Then we have check the connectivity between the client and DD vice versa. Connectivity is fine. And we are use the dedicated VLAN for the backup purpose. That means all the backup clients and DD are in the same range.
How can we solve this issue. Pls advised.
masonb
445 Posts
0
September 27th, 2018 06:00
Hi,
Client here was Linux ppc64le and support for DDboost client direct backup was not introduced in NMDA until version 9.2 for this OS. Other linux x64 clients were also running 9.1.0.2 but the libraries required for DDboost were not present in the /usr/lib64 directories. There were also some other minor name resolution issues which need correcting to allow communication to be established. Running save -D 5 /etc/hosts on the Linux clients highlighted what the particular issues were on the hosts e.g. failing back to traditional backup as library not available, DD server not reachable etc.
ppc64le/NMDA clients need NW 9.2 software installed - others with missing libraries we would also upgrade as its the same amount of work as deinstalling/reinstalling old version.
name resolution and networking (ping/traceroute) checks also required to ensure connectivity can be established.
Regards,
KarthikS
36 Posts
0
September 19th, 2018 08:00
Hi Client direct option in NMC is enabled ? Data domain backup option is also checked in NMC for the client resource ? Also if the ping via the dd name is working and no duplicate entries in client hosts files for the same DD with a different ip , what is the outcome of a manual backup ? that should also give some clue ... as far as i know we have such issues only for solaris x86 systems on nw 9.X but windows 2012 should be fine ..what is the actualy networker client and nmda version used ?
Pasindu
19 Posts
0
September 19th, 2018 21:00
Hi Karthik,
Yes, Client direct option in NMC is enable. Pls refer the attach image.
And we have check the host file. It also have the only one entry and there is no duplication. And also we again go through the NW server daemon.raw logs that we have rendered. In there we are able to find out for Windows 2012 R2 machines are working the client direct. Pls refer the below log output.
91787 9/2/2018 3:34:22 PM 1 5 0 9060 9596 0 win-afvg9er8ckm nsrmmd NSR notice Save-set ID '1133229473' (PUATHyperVSQL:\\?\GLOBALROOT\Device\HarddiskVolume2\) is using direct file save with Data Domain device 'DWHDD1_Digital Banking'.
71659 9/2/2018 3:34:23 PM 0 0 2 10952 10852 0 win-afvg9er8ckm nsrd NSR info PUATHyperVSQL:\\?\GLOBALROOT\Device\HarddiskVolume2\ done saving to pool 'Digital Banking' (DigitalBanking.001) 25 MB
91787 9/2/2018 3:34:34 PM 1 5 0 9060 9596 0 win-afvg9er8ckm nsrmmd NSR notice Save-set ID '1116452257' (PUATHyperVSQL:C:\) is using direct file save with Data Domain device 'DWHDD1_Digital Banking'.
71191 9/2/2018 3:36:53 PM 0 0 0 10952 10852 0 win-afvg9er8ckm nsrd NSR info Media Alert event: Waiting for 1 writable volume(s) to backup pool 'NSR_Server_Backup' disk(s) on win-afvg9er8ckm
And also we have go through the DD and find out all the Windows machine that we are backing up in the environment are listed under the DD boost active connections. Pls refer the attachment. That means there is an issue with the linux machine. Netwoker Client Version - 9.1.0.2-1 ppc64le and Netwoker NMDA Version - 9.1.1.0-1 ppc64le.
Pls advised.
Deb_PS
156 Posts
0
September 27th, 2018 05:00
@Pasindu_Malintha When you run the backup of the client, please monitor the data domain system that through which interface the backup is flowing, it could be an issue that the backup is going through Management interface as well.
Secondly: It's not always the backup software, try copying around 500 GB of data from the client to another server/storage to understand if the read performance is adequate.