Plesk
Back up websites, databases and settings from Plesk to Zata.
Plesk can store server and website backups in a Zata bucket. You use the Amazon S3 Backup extension with a custom (S3-compatible) service provider.
Before you start
- A bucket for the backups, for example
plesk-backups. See Create a bucket. - An access key from the same region as the bucket. See Access keys.
- Admin access to Plesk (usually
https://your-server:8443).
Connection settings
| Setting | Value |
|---|---|
| Service provider | Custom (Minio, OpenStack, etc.) |
| API Endpoint URL | https://idr01.zata.ai for Indore, https://bom01.zata.ai for Mumbai |
| Login (Key) | Your access key from Access Keys in the Zata console. The key must be from the same region as the bucket. |
| Password (Secret) | Your secret key |
| Bucket | Your bucket name |
| Path | / or a folder in the bucket |
Set up Plesk
Open Extensions, search for Amazon S3 Backup, and install it.
Open Tools & Settings → Backup Manager.
Click Remote Storage Settings and choose Amazon S3 Backup.
Tick Use the storage and fill in the fields from the table above. Click OK. If Plesk can connect, the storage is saved.
Test it
In Backup Manager, click Back Up. Under Store in, choose Custom (Minio, OpenStack, etc.) (or both server storage and custom storage) and click OK. When the backup finishes, check that the backup files are in your bucket in the Zata console. Then restore one item from that backup in Backup Manager.
Troubleshooting
| Problem | Fix |
|---|---|
| Saving the settings fails | Check that Service provider is Custom (Minio, OpenStack, etc.) and API Endpoint URL matches the bucket's region. |
| Access denied or invalid credentials | Copy the keys again from Access Keys and check that the key can use the bucket. |
| Amazon S3 Backup is missing under Remote Storage Settings | Install the extension first. |
For other errors, see Signature errors and Endpoint and region.