Current Filer Head:
- Upgrade OS to match new filer head
- Shutdown filer head
New Filer Head
- Run options disk.auto_assign off
- Shutdown filer head
- Connect only one of the shelf chains from the current filer head
- Boot to maintenance mode
- Run disk assign all
- Shutdown the filer head
- Connect the other shelf chain
- Boot to normal mode
- Verify shelves – aggr status
- Run aggr online
- Verify shelves are online
- Run options disk.auto_assign on
Create volume vol create NEW_VOLUME_FOR_NFS -s volume AGGREGATE 10g vol status NEW_VOLUME_FOR_NFS Read current exports rdfile /etc/exports Export exportfs -p /vol/NEW_VOLUME_FOR_NFS Export options - read-only for all, root and read-write for only ALLOWED_HOST exportfs -io ro,root=ALLOWED_HOST:ALLOWED_HOST.sub.domain.com,rw=ALLOWED_HOST:ALLOWED_HOST.sub.domain.com /vol/NEW_VOLUME_FOR_NFS Confirm client can access ethe xport (Use IP Address) exportfs -c ALLOWED_HOST_IP_ADDR /vol/NEW_VOLUME_FOR_NFS Unexport #exportfs -u /vol/NEW_VOLUME_FOR_NFS Flush access-cache #exportfs -f
SnapMirror Volume Level Source: vol create BLAH options snapmirror.enable rdfile /etc/snapmirror.allow wrfile -a /etc/snapmirror.allow "Destination" Destination: vol create sm_BLAH -s volume aggr0 50g vol restrict sm_BLAH snapmirror init -S Source:/vol/BLAH Confirm on Destination: snapmirror status Schedule on Destination: rdfile /etc/snapmirror.conf Resync on Destination: snapmirror resync Break on Destination: snapmirror quiesce snapmirror break Update on Destination: snapmirror update Abort on Destination: snapmirror abort
Source: http://communities.netapp.com/docs/DOC-1060
FAQ NetApp Deduplication 08_25_08.pdf
—
3. HOW DO I ADD THE DEDUPLICATION CAPABILITY TO A FAS SYSTEM?
Installing the nearstore and a_sis licenses on a supported system will enable the deduplication capability. Although these licenses must be requested by the customer, there is no charge for either license. Note: R200 systems do not required the nearstore license.
—
9. IS THERE A MINIMUM DATA ONTAP RELEASE REQUIRED FOR NETAPP DEDUPLICATION?
Yes. NetApp deduplication for FAS requires the installation of Data ONTAP 7.2.4 or greater. NetApp deduplication for V-Series requires Data ONTAP 7.3 or greater.
—
21. WHAT PROTOCOLS DOES NETAPP DEDUPLICATION SUPPORT?
NetApp deduplication is independent of protocols and thus supports all NetApp SAN and NAS protocols: iSCSI, FCP, NFS, and CIFS
—
22. ARE THERE ANY SPECIAL CONSIDERATIONS IN USING DEDUPLICATION WITH LUNS?
NetApp deduplication operates regardless of protocol. However, LUNs are a somewhat special case because of reservations and space guarantees. The default mode of deduplication and LUNs is to apply any space savings to the snapshot reserve area. However, If LUN space guarantees are disabled, and the snapshot reserve set to zero, LUNs can be deduplicated and “thin provisioned.â€Â
—
24. CAN I ESTIMATE MY SPACE SAVINGS BEFORE INSTALLING DEDUPLICATION?
Yes. A space savings estimation tool (SSET) is available to NetApp and Partner SE’s. This tool is a standalone application that operates on a Windows or Linux client and will “crawl†through any NFS volume (up to 2TB) and will estimate the amount of space savings you will get with deduplication.
—
25. CAN PREVIOUSLY WRITTEN VOLUME DATA BE DEDUPLICATED?
Yes. NetApp deduplication can scan and deduplicate existing data on a volume. This can be run at any time on a volume that contains previously written data, and is recommended to be run whenever deduplication is first enabled on a volume.
—
29. CAN I MANUALLY START AND STOP THE DEDUPLICATION PROCESS?
Yes. You can initiate the deduplication process at any time with a CLI command, and also stop it at any time with a CLI command.
—
30. CAN THE DEDUPLICATION PROCESS BE AUTOMATED?
Yes. The default operation of deduplication is to automatically begin deduplication of a volume if a 20% new data change rate is detected since that last time deduplication was run. If the user prefers regularly scheduled or manual deduplication, this automatic feature can be turned off.
—
31. HOW OFTEN SHOULD DEDUPLICATION BE RUN ON A VOLUME?
The frequency of deduplication scheduling depends on the frequency that redundant writes are taking place on the volume. Typically, deduplication might be run approximately once per week on the volume. If more frequent redundant writes are taking place, for instance nightly SQL database dumps, then running deduplication more frequently may be recommended.
—
33. HOW DO I VERIFY THE SPACE SAVINGS WITH DEDUPLICATION IN A GIVEN VOLUME?
Use the “df –s†command to verify the cumulative space savings per volume. The results are listed in number of blocks and % saved. An example of the output from this command:
> df -s /vol/VolPST Filesystem used saved %saved /vol/VolPST/ 24072140 9316052 28%
—
49. CAN I DEMO DEDUPLICATION FROM THE DATA ONTAP SIMULATOR?
Yes. The Data ONTAP 7.3 simulator supports deduplication.
# Gather original volume size and LUN serials vol size /vol/SOURCE_VOL lun show -v /vol/SOURCE_VOL/SOURCE_1_LUN lun show -v /vol/SOURCE_VOL/SOURCE_2_LUN ( Note Volume Size & Serial# for each LUN ) # Create volume vol create TARGET_VOL -s volume NEW_AGGREGRATE SIZE_FROM_SOURCE vol options TARGET_VOL nosnap on vol options TARGET_VOL nosnapdir on vol restruct TARGET_VOL snapmirror initialize -S FILER:SOURCE_VOL TARGET_VOL snapmirror status # Unmount LUNs from the host # Update Snapmirror (host) umount LUN_1_PATH (host) umount LUN_2_PATH snapmirror update -S FILER:SOURCE_VOL TARGET_VOL snapmirror status # Break Snapmirror # Update volume options snapmirror break TARGET_VOL snapmirror status -l (record snapshot volume) snap delete TARGET_VOL BASE SNAPSHOT FROM STATUS -L) vol options TARGET_VOL fs_size_fixed off snap sched TARGET_VOL 0 0 0 snap reserve TARGET_VOL 0 vol size TARGET_VOL ANY_NEW_SIZE # Unmap source LUNs lun unmap /vol/SOURCE_VOL/SOURCE_1_LUN LUN_HOST lun unmap /vol/SOURCE_VOL/SOURCE_2_LUN LUN_HOST # Offline source & target LUNs lun offline /vol/SOURCE_VOL/SOURCE_1_LUN lun offline /vol/SOURCE_VOL/SOURCE_2_LUN lun offline /vol/TARGET_VOL/TARGET_1_LUN lun offline /vol/TARGET_VOL/TARGET_1_LUN # Apply serial number on target LUNs lun serial /vol/TARGET_VOL/TARGET_1_LUN SERIAL# lun serial /vol/TARGET_VOL/TARGET_2_LUN SERIAL# # Online target LUNs lun online /vol/TARGET_VOL/TARGET_1_LUN lun online /vol/TARGET_VOL/TARGET_2_LUN # Map target LUNs lun map /vol/TARGET_VOL/TARGET_1_LUN LUN_HOST lun map /vol/TARGET_VOL/TARGET_2_LUN LUN_HOST # Mount LUNs from the host # Applying the serial number to the LUN keeps the device path (host) mount LUN_1_PATH (host) mount LUN_2_PATH
Data migration from filer to filer using SnapMirror.
## On source-filer wrfile -a /etc/snapmirror.allow "destination-filer" ## On destination-filer wrfile -a /etc/snapmirror.allow "source-filer" vol create DESTINATION_VOLUME aggr0 100g vol restrict DESTINATION_VOLUME snapmirror initialize -S source-filer:SOURCE_VOLUME DESTINATION_VOLUME snapmirror status -l snap delete DESTINATION_VOLUME <BASE_SNAPSHOT_FROM_SNAPMIRROR_STATUS>
There is a very cool unofficial NetApp Mailing list, its called toasters. Subscribe by sending an email to lists@mathworks.com. Be sure to include “subscribe toasters” in the body of the email.
To go into the advanced mode: - priv set advanced (diag mode) To read files on the console: - rdfile To read files from your machine: - Mount :/vol0 To write files on the console: - wrfile (CTRL-C) Some useful disk commands (use -v for more info): - sysconfig -r (show disks) - aggr status - vol stat vol options - nosnap - nosnapdirectory - no_i2p vol create -s dist_vol origin:source_vol guarantee=none (thin provisioned) Security: - qtree security /vol/volume/qtree - options wafl Snapmirror: - snapmirror status - snapmirror destinations - rdfile /etc/snapmirror.allow - vol create volumes -s none aggr0 100g (source) - vol create volume_dr -s none aggr1 110g (destination) - vol restrict volumes_dr - snapmirror initialize -s 5train:volumes volume_dr - snapmirror status - rdfile /etc/snapmirror.conf Exports: - exportfs -p - exportfs -a (if you do this with a file)
