More about Arq and object lock is in the Arq 7 help. Arq needs to refresh the object locks as de-duplicated objects age, so if you change the schedule, make sure Arq is still backing up often enough to maintain/extend those object locks. Each new backup record points to the same data as the previous backup record except for new/modified/deleted items. Note: Arq stores data in de-duplicated form. That’s it! Arq will add/extend a “ compliance mode” lock to every object needed by the latest backup record to ensure it’s immutable for at least 90 days. Next, create your backup plan using that storage location in 3 steps:įinally, edit your backup plan’s immutability options: Next, add that bucket as a “storage location” in Arq 7 in 2 steps:
Where Arq 6.0 attempted to import Arq 5 data by recreating the data in a new format, we now just read that data, and reuse it for subsequent backup records. Storage options that support object lock include AWS S3, Minio, Backblaze B2 and soon Wasabi.įirst, create a bucket at your storage provider and enable object lock (most providers require you to enable object lock at bucket creation time). The first time you back up after upgrading from Arq 5, a new-format backup record is created for each Arq 5 backup record, pointing to the directory tree of the Arq 5 backup record. This provides extra protection against accidental deletion and malware/ransomware. If you use Arq to back up to a compatible storage provider, Arq can make your backups immutable for a period of time that you choose. Arq 7 now includes support for S3’s “ object lock” API.
0 kommentar(er)
