This post is more than 5 years old
1 Rookie
•
12 Posts
0
4292
September 26th, 2016 04:00
Networker 8.1 guidelines to configure Netapp (c mode) backup using NDMP
added a new NDMP client for netapp with all default setting
42617:nsrndmp_save: NDMP Service Log: Session identifier: 40142
42909:nsrndmp_save: Performing DAR Backup..
83563:nsrndmp_save: Performing full backup, BASE_DATE = 0
42794:nsrndmp_save: Performing backup to Non-NDMP type of device
42658:nsrdsa_save: DSA savetime = 1474878982
85183:nsrndmp_save: DSA is listening for an NDMP data connection on: XX.XX.XX.XX, port = 8763
42597:nsrndmp_save: data connect: failed to establish connection
No Events found!
skvenkateshan
1 Rookie
•
12 Posts
0
October 2nd, 2016 02:00
Thank you Hrvoje,
Finally worked after few KBs that are useful, links for the KBs are below. ensure to add "/svm name/vol junction point" and required application command following the KB instruction. rest is all default
----------------------------------------------------------------------------
Networker settings
----------------------------------------------------------------------------
https://support.emc.com/kb/420975
https://support.emc.com/kb/424647
https://support.emc.com/kb/323108
Application commands added are below
USE_TBB_IF_AVAILABLE=Y
EXTRACT_ACL=T
DIRECT=Y
BUTYPE=dump
HIST=Y
UPDATE=Y
/"SVM name"/"netapp volume junction name"
----------------------------------------------------------------------------
Netapp setting for C mode
----------------------------------------------------------------------------
From the clustershell, confirm that node-scope-mode is disabled:
::> system services ndmp node-scope-mode status
NDMP node-scope-mode is disabled.
If it is displayed as enabled, modify the status to off:
::> system services ndmp node-scope-mode off
NDMP node-scope-mode is disabled.
Verify that the NDMP protocol is allowed on the Vserver:
::> vserver show -vserver -fields allowed-protocols
For example:
::> vserver show -vserver vs_cifs -fields allowed-protocols
vserver allowed-protocols
------- -----------------------
vs_cifs nfs,cifs,fcp,iscsi,ndmp
If NDMP Protocol is not seen in the list, add it along with the required protocols:
::> vserver modify -vserver -allowed-protocols nfs,cifs,fcp,iscsi,ndmp
For example:
::> vserver modify -vserver vs_cifs -allowed-protocols nfs,cifs,fcp,iscsi,ndmp
Note: Ensure not to remove any existing protocols from this list.
Enable Vserver-scope NDMP on the Vserver in question:
::> vserver ndmpd on -vserver
For example:
::> vserver ndmpd on -vserver vs_cifs
Run the following command to confirm:
::> vserver ndmpd show
VServer Enabled Authentication type
------------- --------- -------------------
cifs false challenge
cm2220a-cn false challenge
dd false challenge
svm_cifs false challenge
svm_nfs false challenge
vs_cifs true challenge
vsarun false challenge
7 entries were displayed.
Set up the authentication for the Vserver.
For more information, see 1014597: How to configure NDMP authentication in the ‘Vserver-scope’ mode.
Ensure that correct LIFs are being used.
For more information, see 1014598: How to identify which resources are available through NDMP based on LIF type.
vserver show -vserver vs1 -protocols
vserver add-protocols -vserver vs1 -protocols cifs,ndmp,iscsi,fcp
cluster::> vserver services ndmp generate-password –vserver [vserver_name] –user [user_name]
cluster::> vserver services ndmp generate-password -vserver prod_vs1 -user vsadmin
Vserver: prod_vs1
User: vsadmin
Password: XXXXXXXXXXXXXXX
ble1
2 Intern
•
14.3K Posts
0
September 26th, 2016 06:00
It failed to connect filer over the name you provided. With C mode, you have several names in game... I forgot which storage guys me, but it works just fine for me, but before we made it work we also had to play around to see which name we would use to access it (not sure, but I believe we either used node owner or that was what was not supposed to be used - one of the two :-) ).
skvenkateshan
1 Rookie
•
12 Posts
0
September 27th, 2016 04:00
any advise whether there should be any device setting or configuration that has to be carried out at networker server or the destination devise setting (emc data domain)
Once backup job stats, we do see an active NDMP session within netapp console using port 10000, however not sure why should it point the following event with below IP / port.
85183:nsrndmp_save: DSA is listening for an NDMP data connection on: 169.XX.XX.XX, port = 8763
ble1
2 Intern
•
14.3K Posts
1
September 28th, 2016 13:00
Nothing on NSR or DD side.
vinesh_pandit
5 Posts
0
November 17th, 2016 11:00
Guys,
Client should be created with netapp cluster name? Because with virtual server name its not possible. Also how about restore data of one volume to another?
Vinesh
skvenkateshan
1 Rookie
•
12 Posts
0
December 14th, 2016 23:00
Using the vitrual server name works, however it works with home port only, volume part of other node are backed up only when we create node fail-over.
is Networker 8.1 a cluster aware backup software?