I'm in the process of setting up a new stash environment and on the finally stages of testing. The next step for me is to copy the existing STASH (database,data) and put it on the new. The question I have is if I use the migration steps/process is that a one time process. I ask because once I do a copy and put it on the new it will be roughly a week or so before I can actually implement the new servers. I would then have to resync/refresh the content on the new servers. Can I use the migration process multiply times ?, the two stash environments have different database types present stash is using MySQL and the new is using oracle.
The best way of doing this is to create/use a test server to practice the migration (make sure you have the same Stash version as on the production server) and only migrate the production server when you have the machine ready for it.
(The answer to your original question: yes, you can migrate a server multiple times, if you really need to.)
Bitbucket Pipelines helps me manage and automate a number of serverless deployments to AWS Lambda and this is how I do it. I'm building Node.js Lambda functions using node-lambda ...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
We're bringing product updates and pro tips on teamwork to ten cities around the world.Save your spot