What's the best approach to map a nfsServer to an nfsClient?

November 8, 2016 928 views
Linux Commands CentOS


A test nfsServer, as well as a test nfsClient is created. Snapshots of both are created.

The droplets are deleted, and the droplets are then regenerated, using the snapshots.

As I understand it, the ipAddress of the nfsServer droplet would potentially/probably be changed. So, the question, how can a snapshot be used to generate a droplet, and maintain the ipAddress for the nfsClient?


1 Answer

I’m not expert for nfsServer/Client but I can give you hint for IP addresses.
As even you said - when you create snapshot, delete Droplet and re-create Droplet from snapshot it will for sure have another IP address.

The thing that can help you with saving IP address are Floating IPs. Floating IP is IP that can be assigned to one of your Droplet and re-assigned to another one instantly.
It’s free to use when assigned but if Floating IP is unassigned (not attached to any Droplet) you’ll be charged $0.006 per hour for it (this is because of shortage of IPv4 address. To make billing simple, you’ll not be charged for it until you accrue $1 or more.).
How To Use Floating IPs on DigitalOcean.

by Melissa Anderson
A DigitalOcean Floating IP is a publicly-accessible static IP address that can be mapped to one of your Droplets. A Floating IP can also be instantly remapped, via the DigitalOcean Control Panel or API, to one of your other Droplets in the same datacenter. This instant remapping capability grants you the ability to design and create High Availability (HA) server infrastructures by adding redundancy to the entry point, or gateway, to your servers.
Have another answer? Share your knowledge.