how to update from x2.mlarge to x2.2mlarge for HANA SPS6

[AlexGiguere]

Hi, I just recently updated my AWS HANA instance from revision 56 to 60 with no problem, I also updated my client and studio software to revision 60,

all updates went successfully, however I have heard we need to update our instance size to x2.2mlarge ...

I am still on the default one (x2.mlarge), should I update and how do we do ??

thanks folks!

alex

[former_member182500 · Accepted solution]

Why not create an AMI from your current instance, and then when next creating a spot instance (most cost effective) select the larger instance size?

[AlexGiguere · Accepted solution]

ok it make sense, but after creating my spot instance request, I need to reinstall the delivery unit (the one that comes with SPS06), any idea of how to do it ?

thanks

alex

[former_member182500 · Accepted solution]

You will be creating an AMI based on  current state of given instance.  Hence the AMI will mirror your instance, so whatever delivery unit you have imported into your instance before an AMI is made of that instance will be reflected in the AMI.

Remember when creating the spot instance to change from the default T1 micro instance and change the security group from default to the hana securi group initially created for your regular instance.

[AlexGiguere · Accepted solution]

thanks, I am not very familiar with AMI and Spots Request,

now I have 2 instances running under Instances, the original and my AMI,

I stop the original but for the AMI, there is no stop, only terminate and reboot option ?

do we need to create a spot instance request each time we want to  run it ?

I updated my AWS to revision 60, as I said the update went fine but I had warning about the delivery unit import, maybe because of my small instance (missing size)

I know the AMI is the same image as my original but I choose x2.2mlarge this time,

my concerns was that maybe I need to reinstall these delivery unit to successfully complete my installation

thanks again for you help

Alex

[former_member182500 · Accepted solution]

Hi Alex,

Yes, as you see, with AMI-based instances you dont have Stop, only terminate. 

You need to create an AMI from that running instance in orderr to persist or save your instance state.  In effect make a backup of your work before you kill off the AMI based instance.

As you create more AMIs your snapshots will grow and need to be managed - when you degister AMIs (delete them) you can delete the snap shots associated with the deregistered AMIs to reduce volume usage.  Using spot instances takes a little more management, but is really straight-forward and worth it from a cost reduction point of view.

If you had warnings when importing delivery units an option would be to re-import into the correctly sized AMI be sure?

[AlexGiguere · Accepted solution]

I finally found the answer of my original question, actually it was a very dumb question ,

my instance was running, so when you right click on your instance, I did not see the option "change instance type", the instance needs to be stopped, make sense ...

I will change it for a larger one, but I don't know how to reinstall the delivery units

maybe this should be another blog post, not related to my original question

should I restart the process of updating the hole instance even if it is already on rev60,

thanks

Alex

[former_member182500 · Accepted solution]

"Should I restart the process of updating...."

Good question - without being aware of any existing known or unknown issues with upgrading to a smaller then recommended instance size, I myself would redo the upgrade process.   Take it as a learning experience in spot instance management 🙂

[AlexGiguere · Accepted solution]

thanks, no problem I will restart the update process

alex