Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

NDMPCOPY lun from 7-mode NetApp to cDOT

24 views

Published on

How to copy archived SQL DBs (LUN) from the 7-mode filer to cDOT ONTAP filer.

Published in: Technology
  • Be the first to comment

  • Be the first to like this

NDMPCOPY lun from 7-mode NetApp to cDOT

  1. 1. How to copy archived SQL DBs (LUN) from the 7-mode snapvault snapshot to cDOT SAN volume using NDMPCOPY. Scenario/Use-Case: SQL DBs are archived via snapvault for longer duration, for example up to 1 Year. Requirement: Client requests retrieval of SQL DBs from six to 12 months. Logistics: All the archived snapvault snapshots are on 7-mode FILER. Production DBs (LUN) is already moved to cDOT Filer. Plan: Use NDMPCOPY to move Snapshots from 7-mode to cDOT and then retrieve the DBs and attach it to the Production SQL which is hosted on cDOT, basically in 2 Phases.
  2. 2. PHASE 1: Use NDMPOPY to transfer the DB LUN to the destination volume. PHASE 2: Presenting NDMPCOPIED LUN to the SQL box: Using iSCSI 1. MAP the LUN to the SQL Initiator group 2. On the SQL box - Re-scan the disks [NTFS] 3. Once the disk is detected, bring it online. 4. You should be able to see the databases, simply copy the DB files and later import into the SQL, using SQL Management studio. Tool for copying the LUN:  NDMPCOPY Ingredients required:  Source Filer: 192.168.0.31 [7-mode]  Source volume: /vol/vol_SAN_SV/ [volume type = SAN]  Snapvault Snapshot to copy: source(4082368508)_vol_SAN_SV-base.0  Destination [Puller: cDOT] :  Destination volume = /SVM_ASHWIN/vol_SAN_ISCSI [volume type = SAN] On which Filer NDMPCOPY command is run: Destination cDOT filer : which is a Puller
  3. 3. Following command will copy all the LUN in the given snapvault snapshot to cDOT destination volume. Please note: In this case it's just one LUN, hence there is no need to explicitly give LUN Name. ONTAP92-02> ndmpcopy -sa root:ash2fudge -da vsadmin:qDDx6xrNyPbyD0Qj -st text -dt text 192.168.0.31:/vol/vol_SAN_SV/.snapshot/source(4082368508)_vol_SAN_SV-base.0/ 192.168.0.244:/SVM_ASHWIN/vol_SAN_ISCSI Ndmpcopy: Starting copy [ 20 ] ... Ndmpcopy: 192.168.0.31: Notify: Connection established Ndmpcopy: 192.168.0.244: Notify: Connection established Ndmpcopy: 192.168.0.31: Connect: Authentication successful Ndmpcopy: 192.168.0.244: Connect: Authentication successful Ndmpcopy: 192.168.0.244: Log: Session identifier: 82687 Ndmpcopy: 192.168.0.244: Log: Session identifier for Restore : 82687 Ndmpcopy: 192.168.0.31: Log: DUMP: Using Full Volume Dump Ndmpcopy: 192.168.0.31: Log: DUMP: Date of this level 0 dump: Wed Mar 14 20:14:03 2018. Ndmpcopy: 192.168.0.31: Log: DUMP: Date of last level 0 dump: the epoch. Ndmpcopy: 192.168.0.31: Log: DUMP: Dumping /vol/vol_SAN_SV/.snapshot/source(4082368508)_vol_SAN_SV-base.0 to NDMP connection Ndmpcopy: 192.168.0.31: Log: DUMP: mapping (Pass I)[regular files] Ndmpcopy: 192.168.0.31: Log: DUMP: mapping (Pass II)[directories] Ndmpcopy: 192.168.0.31: Log: DUMP: estimated 83177 KB. Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass III) [directories] Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass IV) [regular files] Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 00:28:03 2018: Begin level 0 restore Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 00:28:04 2018: Reading directories from the backup Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 00:28:06 2018: Creating files and directories. Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 00:28:14 2018: Writing data to files.
  4. 4. Ndmpcopy: 192.168.0.31: Log: ACL_START is '84828160' Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass V) [ACLs] Ndmpcopy: 192.168.0.31: Log: DUMP: 82847 KB Ndmpcopy: 192.168.0.31: Log: DUMP: DUMP IS DONE Ndmpcopy: 192.168.0.244: Log: RESTORE: RESTORE IS DONE Ndmpcopy: 192.168.0.244: Notify: restore successful Ndmpcopy: 192.168.0.31: Log: DUMP_DATE is '5816025739' Ndmpcopy: 192.168.0.31: Notify: dump successful Ndmpcopy: Transfer successful [ 0 hours, 0 minutes, 56 seconds ] Ndmpcopy: Done ONTAP92-02> Following command will copy Specific LUN (in case the volumes have multiple luns) from the snapvault snapshot to the cDOT destination volume: ONTAP92-02> ndmpcopy -sa root:ash2fudge -da vsadmin:qDDx6xrNyPbyD0Qj -st text -dt text 192.168.0.31:/vol/vol_SAN_SV/qtree_14032018_171020/.snapshot/source(4082368508)_vol_SAN_ SV-base.0/lun_SAN_2 192.168.0.244:/SVM_ASHWIN/vol_SAN_ISCSI Ndmpcopy: Starting copy [ 22 ] ... Ndmpcopy: 192.168.0.31: Notify: Connection established Ndmpcopy: 192.168.0.244: Notify: Connection established Ndmpcopy: 192.168.0.31: Connect: Authentication successful Ndmpcopy: 192.168.0.244: Connect: Authentication successful Ndmpcopy: 192.168.0.244: Log: Session identifier: 86634 Ndmpcopy: 192.168.0.244: Log: Session identifier for Restore : 86634 Ndmpcopy: 192.168.0.31: Log: DUMP: Using Partial Volume Dump of selected subtrees Ndmpcopy: 192.168.0.31: Log: DUMP: Date of this level 0 dump: Thu Mar 15 13:22:20 2018. Ndmpcopy: 192.168.0.31: Log: DUMP: Date of last level 0 dump: the epoch.
  5. 5. Ndmpcopy: 192.168.0.31: Log: DUMP: Dumping /vol/vol_SAN_SV/qtree_14032018_171020/.snapshot/source(4082368508)_vol_SAN_SV- base.0/lun_SAN_2 to NDMP connection Ndmpcopy: 192.168.0.31: Log: DUMP: mapping (Pass I)[regular files] Ndmpcopy: 192.168.0.31: Log: DUMP: Reading file names from NDMP. Ndmpcopy: 192.168.0.31: Log: DUMP: mapping (Pass II)[directories] Ndmpcopy: 192.168.0.31: Log: DUMP: estimated 52523 KB. Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass III) [directories] Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass IV) [regular files] Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 13:31:20 2018: Begin level 0 restore Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 13:31:20 2018: Reading directories from the backup Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 13:31:22 2018: Creating files and directories. Ndmpcopy: 192.168.0.244: Log: RESTORE: Thu Mar 15 13:31:22 2018: Writing data to files. Ndmpcopy: 192.168.0.31: Log: ACL_START is '53567488' Ndmpcopy: 192.168.0.31: Log: DUMP: dumping (Pass V) [ACLs] Ndmpcopy: 192.168.0.31: Log: DUMP: 52319 KB Ndmpcopy: 192.168.0.31: Log: DUMP: DUMP IS DONE Ndmpcopy: 192.168.0.244: Log: RESTORE: RESTORE IS DONE Ndmpcopy: 192.168.0.31: Log: DUMP_DATE is '5816087436' Ndmpcopy: 192.168.0.244: Notify: restore successful Ndmpcopy: 192.168.0.31: Notify: dump successful Ndmpcopy: Transfer successful [ 0 hours, 0 minutes, 48 seconds ] Ndmpcopy: Done ONTAP92-02>
  6. 6. Once the SnapVault snapshot is successfully dumped/transferred, 'LUN' can be seen under the destination cDOT volume, as shown below: ONTAP92::> lun show -vserver SVM_ASHWIN Vserver Path State Mapped Type Size --------- ------------------------------- ------- -------- -------- -------- SVM_ASHWIN /vol/vol_SAN_ISCSI/qtree_14032018_171020/lun_SAN online unmapped windows_2008 502.0MB ONTAP92::> Next step, simply follow the Phase 2 as mentioned in the document above. ashwinwriter@gmail.com May, 2019

×