Sorry for the confusion! You need to reach out to our support team so that they enable FFI for your Minio storage account

Not for Linux backup yet, sorry

Can you send a link where you found Minio listed as a supported storage destination?

Check this thread https://forum.msp360.com/discussion/1956/how-to-move-backup-files-from-one-storage-account-to-another

Hi Jackie! What is your support case number?

"Repeat every" can be used if you choose one weekday on the Daily schedule to run a weekly backup every two weeks, for example. For monthly backup, this setting can be used to schedule backups to run once per quarter, etc.

It's not supported for S3-compatible storage destinations yet. For Amazon S3, Wasabi, and Backblaze B2, it's only possible to enable object lock (immutability) during new storage new bucket creation only and can't be changed later.

It should

Steve is correct that NBF with synthetic full takes significantly less time to upload and allows resuming backups. Unfortunately, with S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive storage classes, it's technically impossible to perform synthetic fulls.

One of the possible takes can be using one of the S3 hot or cool storage classes for initial data upload and then using S3 Lifecycle Rules to transfer objects to archive storage. Still, I think you will have at least two copies of your data in the cloud with this approach. Also, AWS itself has some limitations on how S3 Lifecycle Glacier storage classes work together; check out here
https://docs.aws.amazon.com/AmazonS3/latest/userguide/lifecycle-transition-general-considerations.html

A few questions to better understand your requirements:
- Are you looking to backup VMs on a host level with item-level restore capability?
- Do you use our standalone or managed backup solution?

Are you trying to restore from the new or legacy backup format? Are you trying to restore via the Restore Plan Wizard in the UI?

Thanks for the details. I will discuss your use case with the RnD team and see what we can do for you.

How frequently do you run your backups? As I mentioned in my previous post, synthetic full backup, one of the core features of NBF, wouldn't work with long-term archival storage in the cloud due to technology limitations. In other words, if we add an option to disable synthetic full for NBF, you will need to upload an entire data set every time the software runs a full backup. With FFI, synthetic fulls happen every next backup plan run after your initial retention period expires.

Can you give an example of your typical backup plan schedule and retention settings?

Hi , FFI should work with S3 Glacier Instant Retrieval. NBF doesn't support S3 Glacier Flexible Retrieval and S3 Glacier Deep Archive storage classes. That is due to no instant access to the storage required for the software to perform in-cloud copy operations to synthesize full backups inside the cloud.

Forever Forward Incremental backup is designed to keep only one backup generation on the storage, e.g., one full and a series of increments. Are you looking for an FFI scheme together with an option to keep several full backups?

Speaking of Immutability, currently, it works only with backup plans configured with GFS schedule enabled. We plan to make it available outside of GFS plans, meaning it will work with Forever Forward Incremental too.

Legacy simple will work if you don't need encryption and compression

The new backup format uses a different approach to how data is backed up. It creates archives or backup generations (Full+Increments) that can later be used as restore points. This approach allows for better backup performance and ensures data consistency and recoverability. With this approach, the number of versions for each backup is defined by the backup schedule and retention policy.

If you want to run daily incremental backups, your configuration might look like the following.

1. On the Schedule Option step of the backup plan wizard, select the Recurring (Incremental) option and click edit. Check days from Monday through Friday, pick the time, frequency and save


2. On the same step, check the "Execute full backup" box, pick Sunday, define frequency and save.


3a. If you want to keep increments for generations (full+increments) on the "Retention Policy" step, select the "keep backup for" option and set it to 3 weeks.


3b. In case you want to keep increments only for the latest generation, set "Keep backup for" to 1 week and check the "Enable GFS" box, then enable the "Period for keeping weekly backups" option and set it to 3 weeks.


I hope that helps

I'm expecting forever forward with the new format to come out soon. I mean it. Stay tuned

That would be an excellent way to go.