Skip to main content

Fork your Aiven for MySQL® service

Fork your Aiven for MySQL® service to create an independent copy for testing, debugging, or development without affecting the original service.

Fork an Aiven service to create a complete copy of it from its latest backup. Forked services are independent and don't share resources with or increase the load on the original service. Common use cases for forking include:

  • Creating a snapshot to analyze an issue.
  • Creating a development copy of your production environment.
  • Testing upgrades before applying them to production services.
  • Creating an instance in a different cloud provider, region, or with a different plan.
  • Renaming a service.

During the forking process, the fork might initially have only one node while backups are being taken. The other nodes appear after the backup process is complete.

When you fork a service, its configuration, databases, and service users are copied to the new service.

Limitations​

  • You can only fork services that have at least one backup.
  • Service integrations are not copied to the fork.
  • Cross-project forking is supported only within the same organization.

Fork a service​

  1. In your service, click Backups in the sidebar.
  2. Click Fork & restore.
  3. Choose the backup to fork from.
  4. Enter a name, and select the cloud and plan.
  5. Click Create fork.

Fork from a specific point in time​

  1. In your service, click Backups in the sidebar.
  2. Click Fork & restore.
  3. Choose the point in time to fork from.
  4. Enter a name, and choose the cloud and plan.
  5. Click Create fork.

Related pages