As part of this process we had to failover to our standby datamover. Thought these commands might be useful later so here they are.

server_2 – Primary datamover
server_3 – Standby datamover

Fail over to standby mover

# server_standby server_2 -a mover

Faults server_x and renames it to server_2.faulted.server_3
Renames server_3 to server_2
server_3 is now online as server_2

During the time it took to failover I dropped 3 pings to the datamover.

Fall back to primary mover

# server_standby server_2.faulted.server_3 -r mover

Renames standby server to server_3
Renames server_2.faulted.server_3 to server_2
server_2 is now back online as the primary mover.

Again I dropped 3 pings while the datamovers switched.

Here are a couple other useful Celerra commands.

Listing your datamovers and their status from the command line:

# /nas/bin/nas_server -l
id type acl slot groupID state name
1 1 0 2 0 server_2
2 4 0 3 0 server_3

You can get this info from the GUI but this is quick if you are logged into the Control Station CLI.

View the nas version running on your datamovers:

# server_version ALL
server_2 : Product: EMC Celerra File Server Version: T5.6.46.410
server_3 : Product: EMC Celerra File Server Version: T5.6.46.410

Basic stuff but it might be useful to have on hand later.

The script is just a .bat file that uses the NET USE command to map a network drive to the share on the Celerra.  This worked fine, except I noticed that only files with read access for everyone were being backed up.  All of my user profile or home directories were returning access denied errors.  I did not want to grant everyone access to all files and directories.

To fix this I had to add a username and password to the NET USE command to map the drive as a user that has read access on all directories on the shares.

I created a backup admin user for this and set all files and directories to allow this user read access.

The pre backup script mount_x.bat now looks like this:

net use /delete X:
net use X: \\NAS\Share /USER:Domain\backupadmin password

Once the backup is complete I then run a post backup script to to remove the mapping with another script umount_x.bat:

net use /delete X:

The scripts have to be in C:\Program Files\avs\etc\scripts\ on the avamar client.