Knowledgebase

Applies to: JetBackup 5 and JetBackup for WordPress
Affected region: eu-east-1 (Poland)
Active backup migration deadline: January 29, 2027
Final region retirement: February 28, 2027

Overview

The JetBackup Storage eu-east-1 (Poland) region is being retired. If you currently store backups in this region, you must redirect your backup operations to another supported JetBackup Storage region to avoid service interruptions.

The retirement will take place in two stages:

We strongly recommend completing your migration before January 29, 2027. Storage usage in your new region remains subject to normal JetBackup Storage billing rates.

Recommended migration method

The simplest way to migrate is to create a new storage bucket in a supported region and update your existing backup jobs to use it.

There is no need to recreate your backup jobs or manually transfer your existing backups to establish a new backup chain.

Your original eu-east-1 destination should remain configured in JetBackup so you can continue accessing historical backups until the region is retired.

Important: Existing backups will not automatically transfer to the new bucket. If you need to retain historical recovery points beyond February 28, 2027, you must preserve them separately before that date.

Step 1: Create a New JetBackup Storage Bucket

We recommend selecting one of the following regions:

You may also select any other available JetBackup Storage region that meets your requirements.

The bucket creation process depends on your JetBackup Storage account type.

Option A: S3 Storage (Console Access)

If you have a full JetBackup Storage account with access to the storage console, you can create your replacement bucket directly.

1. Log in to your JetBackup Storage console.

2. Create a new storage bucket.

3. Select Frankfurt (eu-central-2), Copenhagen (eu-north-1), or another supported region.

4. Configure the bucket according to your storage requirements.

5. Ensure you have the appropriate S3 access credentials and connection information.

Next, add the new bucket to your JetBackup application as an S3-Compatible destination.

JetBackup 5: Navigate to Destinations → Add Destination → S3 Compatible, then enter the connection details for your new bucket.

JetBackup for WordPress: Navigate to the destination management interface, add an S3-Compatible destination, and configure it using your new bucket's credentials.

Save and validate the new destination before continuing.

Important: Full S3 Storage accounts should use the S3-Compatible destination type, not the JetBackup Storage Quick Access Code workflow.

Option B: Integrated Storage (Bucket-Only Accounts)

 If you use an Integrated JetBackup Storage account, you will not have access to the S3 web console. You likely have this account type if you signed up through the Quick Access Code workflow in JetBackup 5 or JetBackup for WordPress, or if you were provided only with Access Key and Secret Key credentials for accessing JetBackup Storage.

Instead, you can provision a replacement bucket through the Get Quick Access Code functionality in JetBackup 5 or JetBackup for WordPress.

1. Log in to your JetBackup application.

2. Navigate to Destinations → Add Destination.

3. Select JetBackup Storage as the destination type.

4. Click Get Quick Access Code.

5. Sign in using your JetBackup Client Area credentials.

6. Choose a new bucket in a supported region, such as Frankfurt (eu-central-2) or Copenhagen (eu-north-1). Do not select your existing eu-east-1 bucket.

7. Copy the generated Quick Access Code and paste it into the destination configuration.

8. Complete the remaining destination settings and save.

The Quick Access Code workflow provisions or selects the bucket and provides the authentication needed to configure your JetBackup Storage destination. You do not need separate S3 access and secret keys.

For detailed instructions, see:

• JetBackup 5 — Get Quick Access Code

• JetBackup for WordPress — Quick Access Code

Important: An existing Integrated Storage bucket cannot be moved to another region by changing its region setting. You must provision a new bucket in the replacement region.

Step 2: Update Your Existing Backup Jobs

Once your new storage destination is configured, update your existing backup jobs to use it.

JetBackup 5

1. Log in to your JetBackup 5 administration interface.

2. Navigate to Backup Jobs.

3. Locate a backup job currently using the eu-east-1 destination.

4. Edit the backup job.

5. Under its destination configuration, remove eu-east-1 from the selected destinations.

6. Select your newly created destination in the replacement region.

7. Save the changes.

8. Repeat for any other backup jobs using eu-east-1.

Your existing backup jobs will continue using their configured schedules and settings, with new backups directed to the replacement destination.

You do not need to create separate backup jobs solely for this migration.

JetBackup for WordPress

1. Log in to your WordPress administration dashboard.

2. Open JetBackup.

3. Navigate to your backup job configuration.

4. Locate the backup job using the eu-east-1 destination.

5. Edit its destination selection.

6. Remove the existing eu-east-1 destination from the job and select the newly created destination.

7. Save your changes.

Important: Do Not Delete Your Old Destination

Removing eu-east-1 from a backup job is not the same as deleting the destination from JetBackup.

You should remove the old destination only from the backup job's destination selection.

Keep the original eu-east-1 destination configured in your JetBackup installation so that historical backups remain accessible for restores and downloads until the final region retirement date of February 28, 2027.

Step 3: Verify Your New Backups

After updating your backup jobs, verify that the new destination is working correctly.

1. Run a manual or on-demand backup using an updated backup job.

2. Allow the backup to complete.

3. Confirm that it completed successfully without errors.

4. Verify that the backup was stored on the replacement destination.

5. Where practical, perform a test restore to confirm that the new backup is usable.

The first backup to a new destination may need to establish a new backup chain, depending on your backup configuration. Allow sufficient time and storage capacity for this initial backup.

Once verified, your existing scheduled backups can continue running normally.

Step 4: Keep Your eu-east-1 Destination for Historical Backups

After migrating your active backup jobs, leave your original eu-east-1 destination configured in JetBackup.

This allows you to continue accessing historical backups stored in the old region while all new backups are generated in your replacement region.

You do not need to delete your historical backups immediately.

What happens to existing backups?

Historical backups remain in the original eu-east-1 bucket. They are not automatically copied or migrated to your replacement destination.

Until January 29, 2027, the original region remains available for normal operations.

From January 29 through the read-only transition, existing data remains available for retrieval and restores, but operations requiring write access to eu-east-1 will no longer work.

On February 28, 2027, all remaining data in eu-east-1 will be permanently removed.

What if I need historical backups beyond February 28?

If your backup retention policy or recovery requirements extend beyond the final retirement date, you must preserve the required backup data elsewhere before the region is deleted.

Simply keeping the original destination configured will not preserve its contents after shutdown.

If your backup retention policy or recovery requirements extend beyond the final retirement date, you must preserve the required backup data elsewhere before the region is permanently shut down on February 28, 2027.

Will I be charged for both regions?

To help facilitate this migration, storage usage in the affected eu-east-1 region is no longer billed as of October 15, 2026.

You can continue accessing your historical backups in eu-east-1 while establishing new backups in another region, without incurring overlapping storage usage charges for the original region.

Storage usage in your replacement region remains subject to normal JetBackup Storage billing rates.

Step 5: Remove the Old Destination After Retirement

Once eu-east-1 has been permanently retired on February 28, 2027, the original storage buckets and their contents will no longer be accessible.

At that point, you can remove the obsolete eu-east-1 destination configuration from your JetBackup installation.

Before removing it, confirm that:

• All active backup jobs are using a supported replacement region.

• New backups are completing successfully.

• Any historical backup data you need beyond the retirement date has already been preserved elsewhere.

There is no need to remove the original destination before the region is shut down.

Migration Checklist

Use this checklist to confirm that your migration is complete.

Your active backup migration is complete once your backup jobs are successfully generating backups in the replacement region.

Need Assistance?

If you experience any difficulties creating your replacement bucket, updating your backup jobs, or accessing historical backups, our Support team is available to assist.

Please open a support ticket through the JetBackup Client Area.

We recommend completing your migration as soon as possible, well ahead of the January 29, 2027 read-only transition, to avoid any interruption to your scheduled backups.