Using an NDMP Accelerator with your Avamar

June 9, 2009

In an Avamar System, the NDMP Accelerator is used for backup of EMC Celerra IP storage systems and Network Appliance filers.

The NDMP accelerator is a dedicated single node that provides a complete backup and recovery solution. The NDMP accelerator acts as a pass-through conduit from the NAS device to the Avamar server and can support multiple NAS storage devices.

Here are the steps I followed to install a NDMP Accelerator for a client with an EMC Celerra.


Enabled NDMP services on the EMC Celerra and rebooted the data mover

Setup ndmp user on the Celerra

  • Open a Putty Session to the Celerra/NetApp
  • On Celerra type:


/nas/sbin/server_user server_2 –add –md5 –password ndmp

Set User ID= 1000

Set Group ID= 1000

Home Directory: (leave blank)

Set ndmp password (must be 6 to 8 characters long)

Open Putty session to NDMP Accelerator

Change location to /usr/tmp

Open WinScp session with NDMP Accelerator

Copy Linux 4 64bit clients for NDMP and Linux to the /usr/tmp folder on the NDMP Accelerator node

Switch back to Putty session with NDMP Accelerator

Make sure path is /usr/tmp

Install rpm files for Linux client and NDMP client, type:

rpm –ivh <linuxclientname.rpm>

rpm –ivh <NDMPLinuxclientname.rpm

Run NDMP installation, type:


The Avamar NDMP Accelerator will be configured using this script. 

First you will need to stop all running agents on the accelerator, a prompt will then ask for the Avamar server’s (utility node) DNS name or IP address. 

You will then be prompted for the Avamar server’s administrator password.

NOTE: this is not the OS root password, the Avamar’s default password is 8RttoTriz

Next, you can enable multiple simultaneous backups, keep in mind this functionality requires at least 8GB of RAM.  This shouldn’t be a problem since most accelerators come with 32GB of RAM.

You will now be presented with a menu with the following choices:

Add a new system

(choices are: EMC Celerra, NetAPP Filer or Novell Netware),

Edit an existing system,

Remove a system from the list


When adding a new EMC Celerra system, you will need  the NDMP filer IP address or hostname (Note: this is not the IP address of the control station, but the IP address of an interface on the data mover).

You will then be prompted for the ndmp user password that you assigned in the beginning steps.  Re-enter the password to verify you typed the password correct. 

You will then need to specify the correct password encoding scheme, the only options are “md5” or “text”, we used “md5”above.

You will then need to enter a routable DNS name to be used for the filer.

Wait for avsetupndmp to complete.  Add any additional Filers then choose 4 to Exit.

The last step is to register and activate the accelerator with the Avamar Server, this is performed by running a script using the following command from the accelerator node’s putty session:


Provide the Administrator Server’s host name (Avamar Utility Node)  and assign the domain you would like to assign the accelerator node client too.  The default is “clients”, if you choose to change the default to a domain that was created under the root domain, omit the / and just specify the “root name”, including “/” will cause the register process to fail.

Press “Enter” and you should see results similar to this:

avagent.d Info: Server stopped. [ OK ]
avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log
avagent.d Info: Client activated successfully. [ OK ]
avagent Info <5241>: Logging to /usr/local/avamar/var/avagent.log
avagent Info <5417>: daemonized as process id 3385
avagent.d Info: Server started. [ OK ]
Registration Complete.


You are now ready to backup your EMC Celerra!


One comment

  1. Great article but I am having trouble getting ndmp backups of my Celerra to work using the accelerator node.

    I have a support ticket submitted to EMC for this but was wondering if you have seen this problem:

    The ndmp accelerator is registered and when I try to set up a data set it is able to see my file systems on the Celerra but the backup fails with the following errors:

    2009-06-29 17:36:00 avtar Info : Parsing ’emctar’ stream format from stdin
    2009-06-29 17:41:00 avtar Info : Unable to write inode table.
    2009-06-29 17:41:00 avtar Info : Backup complete, wrapping-up session with Server
    2009-06-29 17:41:00 avtar Error : Comment entry “comment” file “/usr/local/avamar/var/loki/tmp-1246296959/dumpdate25320” not found.
    2009-06-29 17:41:00 avtar FATAL : Backup aborted. No backup created.
    2009-06-29 17:41:00 avtar Info : Finished at 2009-06-29 17:41:00 GMT, Elapsed time: 0000h:05m:00s
    2009-06-29 17:41:00 avtar Info : Error summary: 2 errors: 5155, 0
    2009-06-29 17:41:00 avtar Info : Writing wrapup to alg file for agent to read
    2009-06-29 17:41:00 avtar Info : Command failed (2 errors, exit code 10023: Externally cancelled by TERM


    Mon Jun 29 17:36:04 2009 ndmpcopy: CONNECTED: CONNECT: Connection established.
    Mon Jun 29 17:40:59 2009 ndmpcopy: LOG (msg.reason 35111): SnapSure file system creation fails
    Mon Jun 29 17:41:00 2009 ndmpcopy: Connection halted: HALT: The operation was aborted!
    Mon Jun 29 17:41:00 2009 ndmpcopy: Releasing file history stream ‘/usr/local/avamar/var/loki/tmp-1246296959/ndmpcopy_filehist.fifo’.
    Mon Jun 29 17:41:00 2009 ndmpcopy: File history stream ready.
    Mon Jun 29 17:41:00 2009 ndmpcopy: FAILED to complete transfer.
    Mon Jun 29 17:41:00 2009 ERROR: bad ndmpcopy exit code 157
    Mon Jun 29 17:41:00 2009 INFO: ——-> ndmpcopy finished ‘/loki-cifs/’ on with 157 &1 |
    Mon Jun 29 17:41:00 2009 INFO: Waiting for backup/restore process (pid=25362)
    Mon Jun 29 17:41:00 2009 INFO: avtar process is (pid=25364)
    Mon Jun 29 17:41:00 2009 INFO: Giving avtar 0 seconds to finish (after detecting no log activity)
    Mon Jun 29 17:41:00 2009 INFO: – Waited 0 seconds, sending TERM signal to 25362, , 25364
    Mon Jun 29 17:41:00 2009 INFO: Waiting for avtar to finish (pid=25362)
    Mon Jun 29 17:41:15 2009 INFO: Avtar process (pid=25362) finished
    Mon Jun 29 17:41:15 2009 INFO: Exiting with 1 error(s).
    Mon Jun 29 17:41:15 2009 INFO: AVNDMP exit code: 174
    Mon Jun 29 17:41:15 2009 ——————————————————————————–

    Like I said I do have a support ticket open for this so I just figured I would ask around while waiting on them.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

%d bloggers like this: