NetApp - Cluster takeover and giveback procedure.

1.  To take over partner node, we have to make sure there will be 1-2 minutes connectivity lost (CIFS/NFS)
2. 2.      Release ASUP before giveback options autosupport.doit per-takeovernode1
   3.       node2> cf takeover –f (node1 is takeover by node2)
   4.       node2> cf: takeover initiated by operator
   5.       node2 (takeover)> – Which means takeover completed.
   6.       node2 (takeover)> partner  (To see partner status )
   7.       node2 /node1>
   8.       To do giveback follow from step 9
   9.       When the system isn’t in partner context  and if prompt shows as “ node1/node2>”, follow from step 4, if prompt shows as “node2(takeover)>” follow from step 5
   10.   node1/node2>  partner
   11.   node2(takeover)> cf status
   node2 has taken over node1.
   node1 is ready for giveback.
   12.   Release ASUP before giveback options autosupport.doit per-giveback1node
   13.   node2(takeover)> cf giveback
   14.   If cf giveback is unsuccessful, try forcegiveback..
   15.   node2(takeover)>  cf giveback –f
   16.   once the giveback completes, login to node1 and do health check
   17.   node1> sysconfig –r
   18.   node1>  sysconfig –v
   19.   node1>  storage show disk –p
   20.   node1>  vfiler status –r
   21.   node1>  vfiler run vfilername exportfs
   22.   node1>  vfiler run vfilername cifs shares
   23.   node1>  vol status –s
   24.   node1>  vif status
   25.   node1>  ifconfig –a
   26.   node1> options autosupport.doit post givenback1node

NetApp - Disk Sanitization

To Sanitize all disks except vol0 disks (root volume)

Sanitization is enabled by default for all DOT 8.2+ code, if not enabled, run below command to enable.

options licensed_feature.disk_sanitization.enable on 

If DOT 7.xx to 8.1

·            license add XXXXXX  (You can get license from NetApp)

§  Remove controllers from DFM server to avoid any critical/error/warning alerts from DFM.

§  Offline/destroy all volumes and aggregates leaving vol0 and aggr0.

·                        vol offline volumename

·                        vol destroy volumename

·                        aggr offline aggregatename

·                        aggr destroy aggregatename

·                        CF disable (Disable partner node)

·                        Reboot the filer (Obtain approval prior to rebooting the filer)

·                        Send Final ASUP is issued -- options autosupport.doit decommissioning”

§  Once ASUP is Complete, turn off alerts. 

§  Determine all spare drives using the following command(s):

·         vol status -r

·         vol status -s

§  Begin the sanitization process using the following command(s):

·         disk sanitize start  <all numbered drives>  or disk sanitize start -c 7 <all numbered drives>

·         Monitor status using the following command(s):

§  disk sanitize status

§  vol status –m

§  Unsanitized disks will go thru a SECOND PASS process, rerun the “disk sanitize start” command against drives that fail the sanitization

§  Save sanitization logs

§  rdfile /etc/log/sanitized_disks or rdfile /etc/sanitized_disks and save logs 

To Sanitize vol0 disks (root volume)

Ø  Release 3 sanitize disks (disk sanitize release <disk_list>

Ø  Once you release the sanitized disk, it will be in unowned state (disk show –n)

Ø  Assign the disks back to same node (disk assign <disk_list>

Ø  Once you assign disk, it will be in broken disks (vol status –f)

Ø  Unfail the broken/bad disk (disk unfail –s <disk>

Ø  Now you will see all disks under spare (vl status –s)

Ø  create new aggregate with released disks (aggr create newaggr0 –d <disk_list>), it will take time to create aggregate as disks has to be zeroed, check status with (aggr status new aggr0 –v)

Ø  check current vol0 size (vol size vol0)

Ø  create new volume in newly created aggregate (vol create newvol0 newaggr0 <size>)

Ø  restrict newvol0 before starting copy (vol restrict newvol0)

Ø  Copy vol0 to newvol0 (vol copy start –s vol0 newvol0)

Ø  Once copy is 100%, make newvol0 online (vol online newvol0)

Ø  Make newvol0 as root (vol options newvol0 root)

Ø  Rename vol0/newvol0 & aggr0/newaggr0

Ø  To rename – vol rename vol0 oldvol0, vol rename newvol0 vol0, aggr rename aggr0 oldaggr0, aggr rename newaggr0 aggr0

Ø  Reboot node (reboot)

Ø  Once reboot completes, it will take newly created volume (vol0) as root volume

Ø  Check the status (vol status, aggr status)

Ø  Delete oldvol0 and oldaggr0 (vol offline oldvol0, vol destroy oldvol0, aggr offline oldaggr0, aggr destroy oldaggr0)

Ø  Once we delete old volume/aggregate it will release all disks which are in oldaggr0

Ø  Check the spares (vol status –s)

Ø  Start sanitize (disk sanitize start  <disk_list>)

Ø  Check status (disk sanitize status)

Ø  Once sanitization is 100%, collect logs.

Changing root volume and aggregates - NetApp

Here is the procedure for changing root volume (VOL0) and aggr0 for NetApp Filers

- To do this we need 3 spared disks (Note all disk ID's)
- Priv set advanced
- aggr create newaggr0 -d x.x.x  x.x.x  x.x.x  (Here x.x.x means disk ID's)
- vol create newvol0 newaggr0 337g
- vol restrict newvol0
- vol copy start -S vol0 newvol0 (It will take probably 5 mins to copy)
- vol online newvol0 (Only after copy completes)
- vol options newvol0 root
- reboot (root volume will change from vol0 to newvol0 on reboot)

We will follow this procedure to scrub disks which are owned by vol0.

TCP/IP & Subnet

Good stuff on IP/Subnetting.

Boot from SAN (Brocade HBA's)

Boot from SAN.

EMC TimeFinder Clone (Symclone)

1. Creating a new session.

#symclone -f <devices file> create -copy/-precopy -sid <symm id> -nop

If you use -copy copying blocks from source to target LUNS gets copied in the background  as soon as activate them.   If you use –precopy, copy will start immediately and won’t wait for activate to be run. Note : This will be full copy from source to target

2. Activating a previously created session.

#symclone -f <devices file> activate -sid <symm id> -consistent  -nop

As soon as session is activated block level copy starts if session is created with -copy option.

3. Query the session to find out how is copy going on. You would see status as “copy in progress” or “Copied”.

#symclone -f <devices file> query -sid <symm id> –nop

4. If copying is complete and you want to create a new session. before to that you’ve to Terminate the existing session.

  #symclone -f <devices file> terminate -sid <symm id> –nop

All the above steps does are full copy from source LUN to target LUN. If you don’t want to do full copy & copy the only changed tracks. symclone has that options too.

Differential Copy :

1.Create a first session with -diff option

#symclone –f <devices file> create  -copy/-precopy –diff –sid <symm id> –nop

Note : This session will be full copy too. only thing is subsequent copies can be created with recreate option & they’ll be just differential and fast.

2.   Activate the session.

#symclone -f <devices file> activate -sid <symm id> -consistent  -nop

3. for subsequent point in time clone creations. you don’t(shouldn’t) need to terminate the session. instead Recreate the same session using below and activate them using activate.

#symclone -f <devices file> recreate -sid <symm id> –nop

4. Activate it for start copying blocks. This should be fast.

#symclone -f <devices file> activate -sid <symm id> -consistent  -nop

Restoring or Reverse Cloning :

Incase if something happens to source LUNS. if you want to restore from target. you could do using following commands. you don’t have to flip the devices. you could use same device file.

#symclone -f <devices file> restore -sid <symm id> –nop

you don’t need to activate as restore will establish in opposite directions and automatically activates them to. when you query you should see the status as “Restore in Progress”. once restore is complete you would see “Restored”.

If you want to normal clone from source to target again after restore is complete. you need to Split the existing reverse clone session by using below command.

#symclone -f <devices file> split -sid <symm id> –nop

Now. you could go-ahead with recreate and activate for normal clones.

Format of the device file :

# SRC-LUN    TGT-LUN

   1300              1500

Info took from - gdesaboyina.wordpress.com and EMC docs