I was recently setting up a DD160 for a small Oracle instance and came across an issue when trying to mount the data domain via NFS. I tried several variations of the mount command and realized that I needed to be very specific. Since I was simply using a basic mount command the OS was missing some vital information about how it should connect to the data domain. I also realized that even though this Oracle database is reletivily small, the NFS mount should still be optimized for performance. Below is the message I was receiving:

mount: wrong fs type, bad option, bad superblock on datadomain:/data/col1/OracleBackup, or too many mounted file systems

Incoming search terms:

• data domain nfs performance
• data domain nfs mount options
• data domain nfs
• isilon nfs mount options
• yhs-defalttabtransfer
• datadomain nfs mount options
• what is the maximum number of nfs mount points for data domain
• data domain nfs mount
• emc data domain best practices
• nfs permissions data domain

This is my first blog post, just breaking this thing in! You will see more Backup Recovery and Archiving posts as I get rolling !

Incoming search terms:

• backup exec 2012 data domain
• •avamar error 10007 snapshot creation failed
• data domain /data/col1
• datadomain /data/col1
• slow performance with ddboost backupexec 2010r3
• backup exec 2012 nfs share best practices
• backup exec 2012 or networker 8
• backup exec disk storage nfs
• nfs export /data/col1/backup/ost *
• symantec backup exec 2012 data domain