Copy the LUN from one volume to another Volume using NDMP - Netapp Notes NCDA

This process can be used when you want to copy the existing LUN to another volume without disrupting the existing volume.

Use cases for ndmpcopy

You can migrate data from the source path to a destination path on the same storage system or to a different destination path on a remote host. You can also migrate data from a source path on a remote host to a destination path on the same host or to a destination path on a remote host.

below command is used to copy the Lun from Source filer to Destination Filer

NetAppFiler>ndmpcopy -sa username:password -da username:password myhost:/vol/vol0/source_path myhost:/vol/vol0/destination_path

Copy the LUN from one volume to another volume within the same Netapp filer
NetappFiler>ndmpcopy /vol/vol0/SrcLun /vol/vol2/DstLun


Enjoy....

Please provide your valuable comments...........

Switchover Snapmirror - Change Source as Destination and Destination as Source - Netapp Notes NCDA

Switch-over your snapmirror procedure, changing your snapmirror source as destination and destination as source, without re-initializing the snapmirror.

PRE SWITCHOVER

Before switching over the snapmirror you have ensure that both filers are doing good.

>sysstat -x 1    
Monitor filer CPU utilization for ten minutes no more processes are hiking the CPU

>snapmirror status
 snapmirror status to check all the snapmirror relationships are in idle state

Take all the required information before switching over the snapmirror
>lun show
>lun show -m
>vol status
>vol status -s
>vol status -f
>igroup show
>sysconfig -a
>fcadmin config

by capturing all the above information, later an if anything goes wrong you can verify the before and after configuration status.

SWITCHOVER ACTIVITY

Take the confirmation from all the application and database teams to be stop, all the database activities and applications.

After stopping all the traffic to the Netapp Filer in source. Replicate the last update using below command. Run the below command in destination.

>snapmirror update -S Source:SrcVolume1 DstVolume1

After completion of last update then break the snapmirror

>snapmirror quiesce Volume1

snapmirror will be quiesced ...

>snapmirror break Volume1

This above command will break the snapmirror relationship between source and destination. After completion of break destination volumes will come to write mode.

Repeat above steps for all the Volumes....

completion of snapmirror break, collect all the snapshot list from source and destination.

>snap list

Verify the Zoning in Destination location, because we have to map all the LUN's to bring back the Databases and application in Destination.

now map all the LUN's to servers in Destination using below commands.

>lun map <LUN PATH> <iGroup Name>

map all the LUN's to appropriate igroups

Then comment all the snapmirror schedules in source using # mark in front of the line.

>wrfile /etc/snapmirror.conf
#filer:volume filer1:volume - 40 * * * *

CTRL+C


 Now write the snapmirror schedule in Destination filer.

>wrfile /etc/snapmirror.conf
filer:volume filer1:volume 40 * * * *

CTRL+C

resync from the source to change source and destination

>snapmirror resync -S Destination:DstVolume1 Source:SrcVolume1

after completion of resync update the snapmirror relationship again and again few times, then clean up the old snapshots from source.

Note: Do not delete the snapshots which are in existing relationship

>snap delete -V SrcVolume1 snapshotname

then release the snapmirror from previous destination filer
>snapmirror release DstVolume Source:SrcVolume

now verify the snapmirror status

>snapmirror status

Please provide your valuable comments............

How to configure Netapp AutoSupport - NetApp Notes for NCDA

  Read More Topics

What is Netapp AutoSupport.?

AutoSupport is nothing but "call home" feature, which will be achieved by BMC / SP hardware inbuilt in the Netapp controllers.

 BMC / SP are the hardware parts to collect the events, logging, power status, temperature status, voltage and other hardware status. These hardware parts are connected with inbuilt battery when power is gone, still BMC / SP will not go off immediately it will send an alert and it will go off.
       
    Netapp autosupport will help technical support team to analyze the problem and they will get back to you immediately to you if any problem found in your Netapp filer.

in order to enable the auto support you have to below prerequisites:

1. You should have internet connectivity to your Netapp filer
2. Your mail server should support to send at  least 10MB file size
3. From your network / firewall 443 port should be allowed towards to Netapp

To complete AutoSupport configuration, fill in the following fields:

Configure the 'from' address 7-Mode
NetappFiler>options autosupport.from storageadmin@gmail.com

C-Mode
autosupport modify -node <node name> -from <mail address>

Note: When you add a new 'from' address, it over-writes the existing 'from' address.

Define To Address 7-Mode
NetappFiler>options autosupport.to aravi@gmail.com, me@yahoo.com

C-Mode
autosupport modify -node <node name> -to <mail address>,<mail address>

Add a mail server to transmit AutoSupport message
7-Mode
NetappFiler>options autosupport.mailhost host1,host2

C-Mode
autosupport modify -node <node name> -mail-hosts <Host name or IP>

Define the list of recipients for the AutoSupport short note e-mail, this short email is very useful because immediately you will receive an email when anything went wrong in the Filer.
7-Mode
options autosupport.noteto me@gmail.com, you@gmail.com

C-Mode
autosupport modify -node <node name> -noteto <mail address>

Above is the example options of AutoSupport.

Please provide your valuable comments bellow..................