Cloud Region Migration Q&A

This article provides answers to the most frequently asked questions about cloud region and provider migrations. It aims to equip you with essential information and guidance to ensure a seamless and efficient migration experience.

Question: What happens in the background during a cloud migration?
Answer: The background process of region migration involves several key steps to ensure data integrity and consistency. 
Firstly, the storage buckets are migrated from one cloud provider to another. 
Once the buckets are synced the database migration can start, which will be performed by running pg_dump to export the data from the source database.
Then pg_restore is triggered to import the data into the destination database. 

This method ensures that all data is accurately copied and restored in the new region.

Question: Will I face downtime for my services?
Answer: Yes, customers will face downtime during the agreed and provided time frame required for a given migration. 
Our roadmap includes an improvement to make the process with zero downtime, which will be communicated once available to our customers.

Question: What are the SLAs in the event of an incident?
Answer: The SLA is set as part of our agreement with our customers, please revert to your JFrog contract.

Question: How long does the migration usually take?
Answer: The migration will take up to 4 hours. The JFrog Support team will provide a time estimate for the migration, as it varies depending on the data in the database.   

Question: What is required from me? (the customer)
Answer: To facilitate the migration, you will need to:
Inform our support team of the region and cloud provider to which you wish to be migrated.
Specify a date and time when such migrations should not be scheduled.
The migration will be scheduled at a time that is mutually convenient for both parties. We will work with you to find a time frame that minimizes disruption to your operations.
This coordination ensures that the migration process is smooth and aligns with your operational needs.

Question: How will I know the migration status and if it is finished?
Answer: Our engineers will inform the support team once the migration is complete. 
As soon as the migration is finished, you will be notified by the support team, and you will be able to verify and check that everything is running smoothly from your end.

Question: What if something goes wrong during the migration process?
Answer: If something goes wrong during the migration process:
We can always roll back to the old region and the original databases during the planned migration window.
We ensure that nothing is deleted during the migration.
We only copy the data from the source to the destination. 
The original data will remain intact and relevant in the source region until the customer will confirm the migration was successful and have started to use the new data source.
Once reverting back to the original database, all JFrog services should work as before.

Question: Can the migration process be reversed if we want to?
Answer: Even after the customer data is migrated (And this is confirmed by your teams),we can reverse the process. However, please note that any NEW data that was deployed on the new database will NOT be available unless we set a new migration process to bring on the missing data.  
Past a certain point, it will be more efficient to handle this like a new migration request.

Question: What will happen to my PrivateLink endpoint?
Answer: Because the process will migrate a JFrog server from one region to another, the endpoint will no longer be active as it will point to the old region.
This will require you to reconfigure the PrivateLink endpoint from MyJFrog UI to point it to the new region, once the migration is successful.
To reconfigure the PrivateLink Endpoint after a successful migration, refer to Manage PrivateLink Connections. ​​​​​​​

Question: Can I suggest improvements to the current migration process?
Answer: Of course! Please share your feedback with your contact in JFrog and he will refer the improvements to the technical team to review them.