Name is required.
Email address is required.
Invalid email address
Answer is required.
Exceeding max length of 5KB

Upgrade process using "Migration Tool"

I read this in the release notes:
"The preferred (and safest) way to upgrade is now to launch a new copy of Matillion ETL running the latest version, use the Migration Tool to move and validate the new version...In-place upgrade may be removed in future versions."

There are aspects of this that I like, and I want to try it out. But I also have a couple of questions/concerns about it...

First, I am wondering about things that are not "migratable resources." The two things I can think of are that my EC2 instance has (a) additional Python packages I've installed, and (b) certificate files that are needed to authenticate with some APIs.

I suppose it is just a few minutes of effort for me to re-add things like these, to a new instance. Is that indeed what you'd recommend?

Second, how does it work with licensing and costs? If I have an annual license for a single instance, then what happens when I launch a new, second instance? Do I incur hourly Matillion charges for the second instance, while I have two instances running at the same time? And then, do I need to do anything to "map" my annual license to the new instance? Or once I finish the migration and validation, and delete the old instance, does the annual license automatically get "mapped" to the new instance?

1 Community Answers

Matillion Agent  

Ian Funnell —

Hi Kevin,

I completely agree with your points about certain things being non-migratable.

From a convenience and functionality perspective I’d agree that you have the right to administer your Matillion instance in any way you see fit.

From an instance management / DR perspective I’d argue that it’s good practice to always have a procedure that would allow you to rebuild your instance from scratch if you ever needed. That would include any bespoke customizations that you’ve made. E.g. where are your important packages and certificates backed up? Hopefully not solely on-instance!

From Matillion’s perspective, it makes you easier to support if you have not extensively customised your instance. We’re seeing more and more customers who have policies which specify that compute instances should be replaced rather than upgraded in situ. So this is partly in response to that trend.

If you have an annual license and you launch a new, second instance, you will for a short time incur an hourly charge for the second instance. Once you’re happy that the migration is complete and the new instance is working, you can stop the original instance and the annual license will automatically get switched over to the new instance (assuming it’s the same type and is in the same region).
You can keep the old instance in a stopped state, at minimal cost, to act as a DR backup or reference.

Best regards,

Post Your Community Answer

To add an answer please login