Introduction to Network Attached Storage
Datacenters NYM2, LAX1 and AMS1 are equipped with file server clusters that make up network attached storage systems (NAS). Although these systems support various protocols (FTP, NFS, HTTP), we have selected one for usage within AppNexus: NFS.
We only support NFS over TCP and implement IP based authorization which limits the likelihood of NFS security issues.
Your Network Attached Storage Volume
When we registered your account we created volumes on each of our NAS systems for you in the NYM2, LAX1 and AMS1 datacenters. The welcome email you received included information about your username, password, and share name.
The share name will be in the format of cust###a, where ### is your customer number. For example, if your customer number is 567, your share will be: cust567a.
AppNexus Support mounts the public storage share (which contains our base CentOS image) on the management instance, but all instructions for mounting private customers shares are below. (You can also mount the public share on other instances if desired. See Mount the Public Share for more information.)
Note that storage in the datacenters is functionally separate. If you would like to use storage in each of the datacenters, you will need to mount a volume separately in each datacenter. For example, if a file is only on your LAX1 storage share, it will not be available in NYM2 or AMS1, and vice versa. You will need to copy files from one location to the other in order to access them from each of the datacenters.
Note also that your volume has been locked down to your VLAN in each datacenter, and you will not be able to access it from either another customer's instances or outside of the AppNexus environment. If you would like to create a custom volume that is shared with another customer please open a ticket with our support team.
Mounting Your Volume under Linux
Mounting your volume via NFS
In order to use NFS, you need to open a support ticket to let us know on which IP addresses or vlan, on which you want to mount your share.
The share name provided in your welcome letter is likely cust###a. This means that your nfs share name would be:
Please note that this is case sensitive.
If you want to create a persistent mount that will last across reboots, you must put the following in
and to mount it run:
If you do not want a persistent mount, you can mount by running the
</path/to/mount/point>is the directory on your instance where you want to mount the storage volume, such as
<sharename>is the name of your share provided in your welcome letter (cust###a)
- If the instance where you are mounting the storage is in LAX1, the LAX1 storage volume will be mounted. If it is in NYM2, the NYM2 storage volume will be mounted and if is in AMS1, the AMS1 storage volume will be mounted.
- The last two arguments in
/etc/fstabdefine the behavior of the
dumpbackup utility and the sequence of checking file systems during the boot up process, respectively. If you are not absolutely sure that you need these options enabled, please use 0.
Mounting your Volume on Windows
NFS is the only supported protocol and these same mounts can be mounted on a windows host via NFS. CIFS/SMB is not supported.
Unmounting your Share
To temporarily unmount shares, execute the following instructions on your instance as root:
To prevent the share from mounting at boot, edit the
/etc/fstab file and remove the entry for the share