5

Six months ago I created an EC2 Instance with a Plesk license from the AWS Marketplace. Now I would like to add an ephemeral disk in order to put the temporal backup data generated by the Plesk.

The problem is that I cannot find a way to add an ephemeral disk to an existing instance (even stopping it).

I already have tried to create a new instance with the ephemeral disk and attach the root volume from the old instance. With this alternative I had a lot of problems coming from the plesk (Mainly because they have different internal IPs).

I know that I have the option create a new instance with a new disk and restore a Plesk backup from the old server.

The question is if I can add this ephemeral disk in a faster/easier way that just create a new server and copy the data from the old one.

  • Plesk should be able to handle different internal IPs, there's a number of ways that can occur on EC2. Maybe try shifting the host to a new size at the same time as attaching the root volume. Plesk should expect an IP change then. – Matt Sep 12 '13 at 10:43
  • I'm no so sure that changing the instance type will change the private IP (It is associated to a network interface). But that gives me a tip: I can try to attach the network interface to the new instance!!. I will try it tonigh! Thank you for the tip. – jbaylina Sep 12 '13 at 14:29
  • Changing the instance type (m1, m3,c1, c3, m2, t1 etc) will generally move your instance to physically different hardware which is in a different location in Amazon's network/DC. Internal Amazon IP's are assigned by DHCP and will change. From what I've been led to believe their network subnetting is per rack or smaller, at least for the small instances. There are types you can swap between where you can be sure of a hardware move, e.g cg1 – Matt Sep 13 '13 at 9:04
8

Just to provide some clarification on the initial point here: you cannot add an EPHEMERAL drive to an instance AFTER initial creation. Ephemeral drives are a part of the base instance configuration which is only written on instance creation, and is non-modifiable.

Another point to bear in mind, though you may already know this, is that ephemeral drives are not available on t1.micro instances.

1

I do this a bit at work. Your process needs to be something like

  1. Stop the server (do whatever failovers or rerouting you need to)
  2. Create an AMI from the stopped instance, right click and choose "Create Image" make sure you add one "Instance Store X" for each ephemeral disk expected. More is totally okay (an i3.16xlarge offers 8 ephemeral disks, so plan ahead for future growth) enter image description here
  3. Wait for AMI to complete
  4. (optional) If you want to encrypt the disk, use "Copy AMI" to the same region now, and turn on encryption. You'll end up with a second AMI, with encrypted disks.
  5. Create a new instance from that AMI. It will come up with a new IP but all the other data exactly the same, so you may wish to move the private IP over from the original server.

After a couple days you can cleanup by deleting the AMI and the original stopped host.

0

The problem is that plesk does not start when an IP changes. You have to run this commands:

# /usr/local/psa/bin/reconfigurator --autoconfigure
# /usr/local/psa/admin/sbin/httpdmng --reconfigure-all
# /etc/init.d/nginx restart

See this page: http://kb.parallels.com/en/114245

So the procedure is correct. Create a new instance with an AMI generated from the old server, and add the ephemeral disk.

After attaching the old root device, jus run the plesk reconfiguration commands and restart.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.