Iperius Backup
Run scheduled Iperius Backup jobs to a Zata bucket.
Iperius Backup is Windows backup software. It can send backup jobs to a Zata bucket through its Amazon S3 cloud destination, which works with S3-compatible storage.
Before you start
- A bucket for the backups. See Create a bucket.
- An access key from the same region as the bucket. See Access keys.
- Iperius Backup installed.
Connection settings
| Setting | Value |
|---|---|
| Type | S3 |
| Access Key ID / Secret Access Key | From Access Keys in the Zata console. The key must be from the same region as the bucket. |
| Service Point (URL) | idr01.zata.ai for Indore, bom01.zata.ai for Mumbai |
| Use SSL | Ticked |
| Signature version | 4 |
| Bucket name (S3) | Your bucket name, for example my-bucket |
Set up Iperius Backup
Open Iperius Backup and click Create new backup.
On the Items tab, use File or Folder to add the files and folders you want to back up. Filters and exclusions are optional.
On the Destinations tab, add a Cloud destination, choose Amazon S3, and click New Account. Enter a Name (for example zata), fill in the fields from the table above, and click Save.
Select the new account under Account Cloud and enter your Bucket name (S3). Optionally add a Subpath. Choose the Backup type and Number of copies, and turn on zip compression and a zip password if you want them. Click OK.
On the Scheduling tab, tick Run backup automatically using the following scheduling, choose the days, and add the times.
On the Summary tab, enter a Job name and click OK.
For immutable backups, create the bucket with Object Lock turned on before you set up the job. Object Lock can only be turned on when you create a bucket. See Object Lock.
Test it
Run the job once by hand with a small file. When it reports Backup completed successfully, check that the file is in your bucket in the Zata console. Then restore it with Iperius to confirm it can be recovered.
Troubleshooting
| Problem | Fix |
|---|---|
| The backup fails | Click See log after the backup to read the error. |
| Access denied or invalid credentials | Check the keys and the Service Point in the cloud account, and that the bucket exists in the same region as the key. |
| Signature or time errors | Make sure the computer's clock is correct. See Clock and credentials. |
| Large files fail but small ones work | See Large uploads. |
For other errors, see Signature errors.