Backup Retention not working as expected after reschedule

Schedule tagging on backups/snapshots are not retroactive. For example, if the user created a 30 daily retention backup job, then changed to 10 daily and 10weekly. The next scheduled backup will erase everything except the last 10 daily backups.

Once a backup is generated, it cannot add a “weekly” tag on it to keep the previously generated backups.

Some best practices to safely change between schedule types includes adding a new schedule on top of your existing schedule(s) and giving your backup job ample time (the full retention length of your new schedule) to generate and correctly mark backups with the appropriate schedule type(s). Once complete, you can then safely remove the previous schedule from the backup job and keep only the new retention.

  • 0 A felhasználók hasznosnak találták ezt
Hasznosnak találta ezt a választ?

Kapcsolódó cikkek

Amazon S3 Backup Sizes Not Displayed In JetBackup

If you notice JetBackup 4 Restore and Download page is missing Backup Sizes for Backups located...

Backup Issue - Skipping Account Not Enough Disk Space

JetBackup uses a local workspace to store an account backup before transferring it to its...

Backup Job stuck on CloudLinux servers

There is a known issue with CloudLinux servers when using JetBackup's default rsync...

Failed to Prepare Temporary Snapshot

The error: Failed to prepare temporary snapshot can appear for many different reasons. Please...

Database Backups Errors: No Such File or Directory

We have found that occasionally mysqldump has problems connecting via localhost on some...