Channging the Control Station IP address on NS-120...

I'll give you the quick way to do this, because emc has tons of info on their powerlink site and most of it is outdated. By outdated I mean it doesn't really need to be done that way with newer version of DART. So as of code 5.6.4x-x the following should work. I was on version 5.6.41-2.
Change the IP address on the Control Station 1st, then change the SPA and SPB.

1. Use your favorite web browser to login to the Control Station (current ip address)
   Login as root.
   
2. Look under the tab for Control Station Properties, and change the IP Address information, Gateway, subnet, DNS, NTP, etc. click apply.
3. Reboot the control station. This can be done from the same Control Station Properties Tab. at the bottom there is a reboot button.

Now what about SPA and SPB?? If you need to change them as well this needs to be done through the command line. Use your favorite SSH application to login to the new ip you setup for the control station.

1. Login as nasadmin.
2. su root
3. run the following command:
4. /nasmcd/sbin/clariion_mgmt -modify -spa_ip xxx.xxx.xxx.xxx -spb_ip xxx.xxx.xxx.xxx
5. The results should look something like this:
   

Checking if running as root...yes
Checking if model is supported...yes
Checking for integrated system...yes
Checking if interface eth3 is configured...yes
Checking if interface eth3:1 is configured...no
Checking if interface eth3:2 is configured...no
Checking if SP (10.64.247.141) is up...yes
Checking if SP (10.64.247.142) is up...yes
Checking if a gateway is setup for eth3...yes
Step 1/7: Setting up Proxy ARP for SPA on Control Station
Adding host specific route for SPA
Adding rules to allow outbound traffic from SPA
Adding ARP entry for SPA
Updating /etc/hosts entry for SPA
Step 2/7: Changing SPA IP address.
Changing SPA IP from 10.64.247.141 to 10.64.247.147 (subnetmask 255.255.255.0, gateway 10.64.247.1)
Step 3/7: Waiting for SPA to reboot.
Waiting for SPA to go down...done
Step 4/7: Waiting for SPA to boot up.
Waiting for SPA to come back up...done
Step 5/7: Waiting for CLARiiON software to start on SPA.
Waiting for CLARiiON software to start on SPA..................done
Step 6/7: Removing old Proxy ARP setup for SPA on Control Station
Removing host specific route for SPA
Removing rules that allow outbound traffic from SPA
Removing ARP entry for SPA
Step 7/7: Updating NAS database with SPA IP address
Updating SYMAPI database with new CLARiiON IP addresses...done

VMDK Recovery Tool with 3.5 update 3

I was taking a look at some of the release notes for esx 3.5 update 3 and noticed a VMDK recovery tool. This is experimental and has tons of warnings, but in some cases it may work for rudimentary backup, and looks to foreshadow some possible backup features to come. There is a script intended to help customers to recover VMFS and VMDK data stores from accidental deletion of a data store or physical disk corruption. Basically looks to be a very basic backup and recovery functionality. Check out this KB link it goes through an example:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1007243