CODEWITHSUNDEEP
amazon-web-servicesamazon-ec2
Niag Ntawv
Niag Ntawv

Reputation: 337

mount EBS volume from one host to totally different host

Here is my problem:

The app is hosted in AWS on an EBS-backed volume. I would like to attempt to create a volume from an earlier snapshot which contains the needed attachment files. The question is have is, ServerA is the prod server and ServerB is the staging server, both with completely different/unique FQDNs, if I were to mount the volume from ServerA into ServerB, would that cause any problems with ServerA?

I have tested the mounting method and i know it works. I can mount the volume and then from within the instance, I can mount the volume to a virtual device and then mount that virtual device to a mount point. From there, I can access the files and copy as needed. I just don't want to mess up anything on ServerA since it contains our prod application. Has anyone done this before? Will mounting an earlier snapshot of ServerA onto ServerB cause problems for the live version of ServerA??

Sorry for the confusing explanation.

Upvotes: 0

Views: 82

Answers (1)

John Rotenstein
John Rotenstein

Reputation: 269282

An Amazon EBS volume can only be attached to one Amazon EC2 instance at a time.

If you have created a new EBS volume from an EBS snapshot, then it is a totally separate volume and may be attached to any instance (prod/non-prod, any VPC, etc) within that Availability Zone. (You nominate the AZ when creating the Volume from the Snapshot.)

No danger will result from mounting your 'restored' volume on any instance. It will not impact your production system. Just think of it like plugging a portable USB drive into a computer -- it will not impact any other drive.

Upvotes: 1

Related Questions