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

When migrating system disks from the source to target system. The existing device paths may not correspond to the identical hardware devices on the target system.

THe device paths can be corrected by booting up into single user mode from the dvd or network boot server.

After booting up int single user mode from the dvd or network boot server, use the devices found as single user to correct the device entries on the Sun Solaris OS. Here are the steps (Example uses the disk c1t0d0):

mount /dev/dsk/c1t0d0s0 /mnt
mv /mnt/etc/path_to_inst /mnt/etc/path_to_inst.orig.113009.bsung
rm -rf /mnt/devices/*
rm -rf /mnt/dev/*
cd /devices; find . -print | cpio -pduVm /mnt/devices
cd /dev; find . -print | cpio -pduVm /mnt/dev
rm /mnt/etc/path_to_inst*
eeprom auto-boot?=true
reboot -- "-s -a -r"

The following Sun document can be used as reference for this scenario - http://sunsolve.sun.com/search/printfriendly.do?assetkey=1-61-204249-1.

The Sun LSI Internal SCSI RAID controllers are managed via the raidctl utility. The Solaris OS loads the mpt driver to manage the devices attached to the LSI Internal RAID controllers.
When moving the physical disks and associated raid volumes on the disk to another system. The volume must to be activated on the target system.
Steps taken via OBP to activate the volume (Example using T5220):

setenv auto-boot? false
reset-all

show-disks
select /pci@0/pci@0/pci@2/scsi@0 (T5220)
show-volumes
0 activate-volume
reset-all

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 

From http://support.apple.com/kb/HT1629

defaults write com.apple.desktopservices DSDontWriteNetworkStores true

---

Download globalSAN

# LIST ALL CLIENTS
/usr/openv/netbackup/bin/admincmd/bpplclients 

# LIST WHAT IS BACKED UP ON THE CLIENT 
/opt/openv/netbackup/bin/admincmd/bppllist -L -byclient ${1} | grep Include: | awk '{print $2}'

# LIST CLIENT TYPE /opt/openv/netbackup/bin/admincmd/bppllist -L -byclient ${1} | \
        | grep "Client/HW/OS/Pri:" | awk '{print $3"\t"$4}' | uniq

# SHOW BACKUP SCHEDULE FOR ALL CLIENTS BY DATE
/opt/openv/netbackup/bin/admincmd/nbpemreq -predict -date MM/DD/YYYY 

# SHOW BACKUP SCHEDULE FOR SPECIFIC CLIENT BY DATE
/opt/openv/netbackup/bin/admincmd/nbpemreq -predict -date MM/DD/YYYY -client_filter client-hostname


Note: NDMP displays HW/OS       "NDMP NDMP"
Note: Solaris displays HW/OS    "Solaris Solaris10"

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.

Dig up the following login information for downloading the latest firmware from Raidon.

Site: ftp.raidon.com.tw
Path: /ide4/support/Raidon_Product/SL36xx-2S-LB2/

Username: cust1

Password: 0001