Will I lose my ephemeral storage on EC2 instance upgradeRebooting an EC2 InstanceIP changed when EC2 instance stopped and startedQuestions about adding space to an Amazon EC2 InstanceAmazon EC2 instance - STOPUpgraded Amazon EC2 Instance Type, how do I access increased storage?EC2 Ubuntu 12.04 m1.large ami isn't showing extra drives for full 850GB Instance StorageUpgrade EC2 Instance to a larger SPOT InstanceAmazon EC2 ephemeral drive permissions for SQL Server tempdbOn EC2 Windows Server 2016, automatically mount instance storage when restarting the instanceDoes the size or type of EC2 instance effect the autoscaling/provisioning/termination time?
Question in discrete mathematics about group permutations
When the Torah was almost lost and one (or several) Rabbis saved it?
Who decides how to classify a novel?
Could a 19.25mm revolver actually exist?
Of strange atmospheres - the survivable but unbreathable
Did 20% of US soldiers in Vietnam use heroin, 95% of whom quit afterwards?
Is it true that cut time means "play twice as fast as written"?
Why do Russians almost not use verbs of possession akin to "have"?
Did this character show any indication of wanting to rule before S8E6?
Is it legal to meet with potential future employers in the UK, whilst visiting from the USA
How should I introduce map drawing to my players?
Where's this lookout in Nova Scotia?
Why did Theresa May offer a vote on a second Brexit referendum?
In general, would I need to season a meat when making a sauce?
Is "cool" appropriate or offensive to use in IMs?
Why were helmets and other body armour not commonplace in the 1800s?
How can I tell if I'm being too picky as a referee?
Count rotary dial pulses in a phone number (including letters)
What does $!# mean in Shell scripting?
My employer faked my resume to acquire projects
Alternatives to achieve certain output format
Find the three digit Prime number P from the given unusual relationships
What is the difference between singing and speaking?
Are black holes spherical during merger?
Will I lose my ephemeral storage on EC2 instance upgrade
Rebooting an EC2 InstanceIP changed when EC2 instance stopped and startedQuestions about adding space to an Amazon EC2 InstanceAmazon EC2 instance - STOPUpgraded Amazon EC2 Instance Type, how do I access increased storage?EC2 Ubuntu 12.04 m1.large ami isn't showing extra drives for full 850GB Instance StorageUpgrade EC2 Instance to a larger SPOT InstanceAmazon EC2 ephemeral drive permissions for SQL Server tempdbOn EC2 Windows Server 2016, automatically mount instance storage when restarting the instanceDoes the size or type of EC2 instance effect the autoscaling/provisioning/termination time?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty height:90px;width:728px;box-sizing:border-box;
I'm considering upgrading from an R3-large to an R3-xlarge instance in EC2. I'm aware that I will lose the contents of the ephemeral drive when I stop my instance. But after I alter the instance type and start it, will the ephemeral drive still be there? Will it be upgraded as well with the larger instance?
amazon-ec2
add a comment |
I'm considering upgrading from an R3-large to an R3-xlarge instance in EC2. I'm aware that I will lose the contents of the ephemeral drive when I stop my instance. But after I alter the instance type and start it, will the ephemeral drive still be there? Will it be upgraded as well with the larger instance?
amazon-ec2
add a comment |
I'm considering upgrading from an R3-large to an R3-xlarge instance in EC2. I'm aware that I will lose the contents of the ephemeral drive when I stop my instance. But after I alter the instance type and start it, will the ephemeral drive still be there? Will it be upgraded as well with the larger instance?
amazon-ec2
I'm considering upgrading from an R3-large to an R3-xlarge instance in EC2. I'm aware that I will lose the contents of the ephemeral drive when I stop my instance. But after I alter the instance type and start it, will the ephemeral drive still be there? Will it be upgraded as well with the larger instance?
amazon-ec2
amazon-ec2
edited Jan 29 '16 at 1:04
Chris
asked Jan 29 '16 at 0:18
ChrisChris
63
63
add a comment |
add a comment |
5 Answers
5
active
oldest
votes
No, the data on your ephemeral drive will not be there.
Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.
add a comment |
When you change the EC2 instance type (for example, from r3.large to r3.xlarge), the instance must be stopped and restarted. This is not the same thing as a reboot.
When an EC2 instance is stopped, any data on the ephemeral storage will be lost.
So in your case, your ephemeral data will be discarded.
When you switch EC2 types and restart your instance, you'll have the new increased volume available to you.
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
add a comment |
When changing instance classes, the instance, after restart, should have the same number of instance store volumes as the were attached before the change, assuming it is of a class that offers the same number of volumes, or more. If it offers more, you can't get access to the additional ones. The size of the volumes should match the new instance class's size allotment for ephemeral disks.
add a comment |
I'm not sure if this answers your question, but I feel it has the information you seek:
"When you resize an instance, you can't add instance store volumes; the resized instance has the same instance store volumes that you specified when you launched it. If you want to add instance store volumes, you must migrate your application to a new instance with the instance type and instance store volumes that you want. For more information about instance store volumes, see Amazon EC2 Instance Store."
This is from the following AWS doc (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)
According to this, it seems that your instance store volumes should remain the same as on your original instance but you can't add any more. I would probably go ahead and test it by making a new temp instance, mounting an ephemeral drive on it and then resizing it to see if the resized instance still has an ephemeral drive on it.
Hope this helps.
add a comment |
You will lose that data if you stop and start the instance or change instance sizes. A reboot will not lose the data.
This storage is located on disks that are physically attached to the host computer. If there's a problem with the underlying physical machine and you have to reboot your server (and hence move to another physical machine) you will lose your data. Changing your instance size requires a reboot, so according to the documentation I link and copy below you will lose your data.
You can use it as a cache, but have a strategy to rebuild it if the system reboots.
From this amazon page.
However, data in the instance store is lost under the following circumstances:
- The underlying disk drive fails
- The instance stops
- The instance terminates
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
add a comment |
Your Answer
StackExchange.ready(function()
var channelOptions =
tags: "".split(" "),
id: "2"
;
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function()
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled)
StackExchange.using("snippets", function()
createEditor();
);
else
createEditor();
);
function createEditor()
StackExchange.prepareEditor(
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader:
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
,
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
);
);
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f752546%2fwill-i-lose-my-ephemeral-storage-on-ec2-instance-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
5 Answers
5
active
oldest
votes
5 Answers
5
active
oldest
votes
active
oldest
votes
active
oldest
votes
No, the data on your ephemeral drive will not be there.
Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.
add a comment |
No, the data on your ephemeral drive will not be there.
Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.
add a comment |
No, the data on your ephemeral drive will not be there.
Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.
No, the data on your ephemeral drive will not be there.
Honestly, though, if you have to ask anything about the resiliency of data on the ephemeral drive, you're doing it wrong. To use EC2 correctly, you must assume that you will lose your ephemeral storage.
answered Jan 29 '16 at 0:23
EEAAEEAA
103k16149221
103k16149221
add a comment |
add a comment |
When you change the EC2 instance type (for example, from r3.large to r3.xlarge), the instance must be stopped and restarted. This is not the same thing as a reboot.
When an EC2 instance is stopped, any data on the ephemeral storage will be lost.
So in your case, your ephemeral data will be discarded.
When you switch EC2 types and restart your instance, you'll have the new increased volume available to you.
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
add a comment |
When you change the EC2 instance type (for example, from r3.large to r3.xlarge), the instance must be stopped and restarted. This is not the same thing as a reboot.
When an EC2 instance is stopped, any data on the ephemeral storage will be lost.
So in your case, your ephemeral data will be discarded.
When you switch EC2 types and restart your instance, you'll have the new increased volume available to you.
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
add a comment |
When you change the EC2 instance type (for example, from r3.large to r3.xlarge), the instance must be stopped and restarted. This is not the same thing as a reboot.
When an EC2 instance is stopped, any data on the ephemeral storage will be lost.
So in your case, your ephemeral data will be discarded.
When you switch EC2 types and restart your instance, you'll have the new increased volume available to you.
When you change the EC2 instance type (for example, from r3.large to r3.xlarge), the instance must be stopped and restarted. This is not the same thing as a reboot.
When an EC2 instance is stopped, any data on the ephemeral storage will be lost.
So in your case, your ephemeral data will be discarded.
When you switch EC2 types and restart your instance, you'll have the new increased volume available to you.
answered Jan 29 '16 at 0:22
Matt HouserMatt Houser
7,9241518
7,9241518
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
add a comment |
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
Thanx Matt - Yes, I realize the data will be lost on the stop. When I first created the instance, the ephemeral had to be mounted at creation time and couldn't be later on, so just want to make sure I don't lose the drive itself.
– Chris
Jan 29 '16 at 0:28
add a comment |
When changing instance classes, the instance, after restart, should have the same number of instance store volumes as the were attached before the change, assuming it is of a class that offers the same number of volumes, or more. If it offers more, you can't get access to the additional ones. The size of the volumes should match the new instance class's size allotment for ephemeral disks.
add a comment |
When changing instance classes, the instance, after restart, should have the same number of instance store volumes as the were attached before the change, assuming it is of a class that offers the same number of volumes, or more. If it offers more, you can't get access to the additional ones. The size of the volumes should match the new instance class's size allotment for ephemeral disks.
add a comment |
When changing instance classes, the instance, after restart, should have the same number of instance store volumes as the were attached before the change, assuming it is of a class that offers the same number of volumes, or more. If it offers more, you can't get access to the additional ones. The size of the volumes should match the new instance class's size allotment for ephemeral disks.
When changing instance classes, the instance, after restart, should have the same number of instance store volumes as the were attached before the change, assuming it is of a class that offers the same number of volumes, or more. If it offers more, you can't get access to the additional ones. The size of the volumes should match the new instance class's size allotment for ephemeral disks.
answered Jan 29 '16 at 4:42
Michael - sqlbotMichael - sqlbot
16.6k3563
16.6k3563
add a comment |
add a comment |
I'm not sure if this answers your question, but I feel it has the information you seek:
"When you resize an instance, you can't add instance store volumes; the resized instance has the same instance store volumes that you specified when you launched it. If you want to add instance store volumes, you must migrate your application to a new instance with the instance type and instance store volumes that you want. For more information about instance store volumes, see Amazon EC2 Instance Store."
This is from the following AWS doc (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)
According to this, it seems that your instance store volumes should remain the same as on your original instance but you can't add any more. I would probably go ahead and test it by making a new temp instance, mounting an ephemeral drive on it and then resizing it to see if the resized instance still has an ephemeral drive on it.
Hope this helps.
add a comment |
I'm not sure if this answers your question, but I feel it has the information you seek:
"When you resize an instance, you can't add instance store volumes; the resized instance has the same instance store volumes that you specified when you launched it. If you want to add instance store volumes, you must migrate your application to a new instance with the instance type and instance store volumes that you want. For more information about instance store volumes, see Amazon EC2 Instance Store."
This is from the following AWS doc (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)
According to this, it seems that your instance store volumes should remain the same as on your original instance but you can't add any more. I would probably go ahead and test it by making a new temp instance, mounting an ephemeral drive on it and then resizing it to see if the resized instance still has an ephemeral drive on it.
Hope this helps.
add a comment |
I'm not sure if this answers your question, but I feel it has the information you seek:
"When you resize an instance, you can't add instance store volumes; the resized instance has the same instance store volumes that you specified when you launched it. If you want to add instance store volumes, you must migrate your application to a new instance with the instance type and instance store volumes that you want. For more information about instance store volumes, see Amazon EC2 Instance Store."
This is from the following AWS doc (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)
According to this, it seems that your instance store volumes should remain the same as on your original instance but you can't add any more. I would probably go ahead and test it by making a new temp instance, mounting an ephemeral drive on it and then resizing it to see if the resized instance still has an ephemeral drive on it.
Hope this helps.
I'm not sure if this answers your question, but I feel it has the information you seek:
"When you resize an instance, you can't add instance store volumes; the resized instance has the same instance store volumes that you specified when you launched it. If you want to add instance store volumes, you must migrate your application to a new instance with the instance type and instance store volumes that you want. For more information about instance store volumes, see Amazon EC2 Instance Store."
This is from the following AWS doc (http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/ec2-instance-resize.html)
According to this, it seems that your instance store volumes should remain the same as on your original instance but you can't add any more. I would probably go ahead and test it by making a new temp instance, mounting an ephemeral drive on it and then resizing it to see if the resized instance still has an ephemeral drive on it.
Hope this helps.
answered Jan 29 '16 at 7:24
tanhaatanhaa
1315
1315
add a comment |
add a comment |
You will lose that data if you stop and start the instance or change instance sizes. A reboot will not lose the data.
This storage is located on disks that are physically attached to the host computer. If there's a problem with the underlying physical machine and you have to reboot your server (and hence move to another physical machine) you will lose your data. Changing your instance size requires a reboot, so according to the documentation I link and copy below you will lose your data.
You can use it as a cache, but have a strategy to rebuild it if the system reboots.
From this amazon page.
However, data in the instance store is lost under the following circumstances:
- The underlying disk drive fails
- The instance stops
- The instance terminates
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
add a comment |
You will lose that data if you stop and start the instance or change instance sizes. A reboot will not lose the data.
This storage is located on disks that are physically attached to the host computer. If there's a problem with the underlying physical machine and you have to reboot your server (and hence move to another physical machine) you will lose your data. Changing your instance size requires a reboot, so according to the documentation I link and copy below you will lose your data.
You can use it as a cache, but have a strategy to rebuild it if the system reboots.
From this amazon page.
However, data in the instance store is lost under the following circumstances:
- The underlying disk drive fails
- The instance stops
- The instance terminates
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
add a comment |
You will lose that data if you stop and start the instance or change instance sizes. A reboot will not lose the data.
This storage is located on disks that are physically attached to the host computer. If there's a problem with the underlying physical machine and you have to reboot your server (and hence move to another physical machine) you will lose your data. Changing your instance size requires a reboot, so according to the documentation I link and copy below you will lose your data.
You can use it as a cache, but have a strategy to rebuild it if the system reboots.
From this amazon page.
However, data in the instance store is lost under the following circumstances:
- The underlying disk drive fails
- The instance stops
- The instance terminates
You will lose that data if you stop and start the instance or change instance sizes. A reboot will not lose the data.
This storage is located on disks that are physically attached to the host computer. If there's a problem with the underlying physical machine and you have to reboot your server (and hence move to another physical machine) you will lose your data. Changing your instance size requires a reboot, so according to the documentation I link and copy below you will lose your data.
You can use it as a cache, but have a strategy to rebuild it if the system reboots.
From this amazon page.
However, data in the instance store is lost under the following circumstances:
- The underlying disk drive fails
- The instance stops
- The instance terminates
edited May 12 at 0:45
answered Jan 29 '16 at 1:14
TimTim
18.6k41951
18.6k41951
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
add a comment |
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
Thanx Tim - I understand I'll lose the data. My concern is I will lose the ephemeral drive itself, as if I had launched it without specifying the mapping. Or will the block mapping carry over to the new instance?
– Chris
Jan 29 '16 at 1:28
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
I'm sorry but I don't know. I thought they had to be specified during the launch of the VM.
– Tim
Jan 29 '16 at 1:33
1
1
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
@Taterhead I knew that... not sure why I wrote that incorrectly. Updated.
– Tim
May 12 at 0:45
add a comment |
Thanks for contributing an answer to Server Fault!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function ()
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fserverfault.com%2fquestions%2f752546%2fwill-i-lose-my-ephemeral-storage-on-ec2-instance-upgrade%23new-answer', 'question_page');
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function ()
StackExchange.helpers.onClickDraftSave('#login-link');
);
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown