All updates
Jobs

Backups at a glance, monthly schedules, and a destination you create on the spot

Every backup card now shows how its last ten runs went. Schedules can run monthly, can be changed after the job is created, and the destination bucket can be created from inside the backup dialog.

A round of improvements to how backup and migration jobs are set up and read.

The last ten runs, on the card

Each backup job shows a row of ten marks, one per run, green for a clean run and red for one that failed, newest on the right. A job that has been quietly failing for a week is now visible from across the room, without opening it.

Monthly

Schedules gain Monthly, on a day of the month you choose, alongside hourly, daily and weekly. Month-end archives no longer need a weekly job you ignore three weeks out of four.

Change the schedule after the fact

Editing a job now includes its schedule — frequency, time and day — instead of asking you to recreate it.

Create the destination as you go

When a backup needs a bucket that does not exist yet, the backup dialog can create it there and then, on your own cloud account or on BucketPilot Cloud, and use it as the destination.

Smaller things you will notice

  • The migration dialog is a lot shorter; the filters fold away until you need them.
  • When the source is a server drive, the dialog shows the drive's root path so the folder you type is relative to the right place.
  • Re-indexing a bucket from the jobs page now updates on its own instead of sitting on *Queued* until you refresh.
  • A bucket that was indexed once and is not set to re-sync now says so on its page and in analytics, so an old snapshot is never mistaken for live data.