In a multi-cell vCloud Director installation, all cells need access to a shared spooling area, also known as NFS transfer server storage. When you need to move or replace the NFS transfer server storage because the current presented NFS share is too small or maybe it got lost because of a crash, you can simply provide a new share to the vCloud Director cells.
The following procedure shows you how to replace the NFS transfer server storage:
Create NFS share
First you need to export a share on the new NFS server. The procedure might be different depending on the type of NFS server you’re using. RedHat version 5.7 has been used in the following procedure.
1. Create a directory to export:
2. Export the NFS directory. Add the following line to /etc/exports:
/nfs/vCD-Transfer <accesslist> (rw,no_root_squash)
Note: Replace <accesslist> with the ip addresses of your VCD cells or allow a specific network like 10.1.1.0/24
3. Restart NFS service:
service nfs restart
Mount NFS share on VCD cells
When the new NFS share is ready
1. Unmount the current NFS share:
2. Modify /etc/fstab and make sure the following line is present and matching your NFS server IP and directory:
<nfsip>:/nfs/vCD-Transfer /opt/vmware/vcloud-director/data/transfer nfs rw,soft,_netdev 0 0
Note: Replace <nfsip> with the ip addresses of your NFS server
3. Mount the NFS share:
4. Verify that the permissions on the transfer directory are set to 750 (drwxr-x—). If not change it:
chmod 750 /opt/vmware/vcloud-director/data/transfer
5. Verify that both the user and group on the transfer folder are set to vcloud. If not change it:
chown -R vcloud:vcloud /opt/vmware/vcloud-director/data/transfer
6. Restart VCD cell:
service vmware-vcd restart
Note 1: Be aware that (in a production environment) tasks could be active on the cell. Restarting the cell this way will break any running tasks. You might want to quiesce the cell first as described in http://kb.vmware.com/kb/2034994
Note 2: You’ll notice a warning in the cell.log log file indicating that the cell is unable to verify that the other cells share the same spooling area. This is normal at this stage as the other cells haven’t been updated with the new NFS share yet. Just make sure that you update all cells. When a VCD cell starts it writes a marker file onto the spooling area to verify that the spooling area is writable and checks all other marker files to verify that it’s sharing the spooling area with all other cells.
- vCloud Director offerings are coming Tweet During VMworld Europe 2010 in Copenhagen I had the opportunity to have a glimpse of the VMware vCloud Director (vCD). While back in 2009 VMware was only still introducing...
- Restoring the default vCenter Server alarms Tweet I’ve been troubleshooting some vCenter alarms lately, which involved a lot of editing, removing and adding of alarms. After the troubleshooting I wanted to reset everything back to default...
- Unable to login to your ESX server Tweet Ivo Beerens posted this article last week on the defunct cimservera processes that render an ESX Host unmanageable. See also this VMWare KB Article. Symptoms include: Unable to log...
- HOW-TO: Recover from failed Storage VMotion Tweet A while ago I received a request from the storage department to move a whole ESX cluster to another storage I/O-Group. This would be a disruptive action. I was...