How It WorksĮnable this feature for an appropriate storage account, if you need to comply with the regulations, maintenance or legal requirements, or anything else that requires an immutable backup dataset. If need to use the Compliance mode for your backup purposes, contact the MSP360 support team. When an object is locked in Compliance mode, its retention mode cannot be changed, and its retention period cannot be shortened.Ĭompliance mode helps ensure that an object version cannot be overwritten or deleted for the duration of the retention period defined in the GFS retention policy settings.īy design, when you create a destination bucket, the Governance mode is applied by default. In Compliance mode, a protected object version cannot be overwritten or deleted by any user, including the root user in your storage provider account. With Governance mode, objects in backup storage are protected against being deleted, but you can still delete the object, if necessary, in the backup storage provider console. In Governance mode, users cannot overwrite or delete an object version or alter its lock settings using Backup Agent. These retention modes apply different levels of protection. Generally, there are two retention modes: Careless or light-headedly made settings can cause high storage bills Once backup data becomes immutable, there is no way to delete it from the storage until the specified GFS keeping period expires except for the storage account termination. Use the Object Lock (Immutability) feature with extreme caution. If the Object Lock is applied along with GFS settings, full backups that are subject to the GFS retention policy become immutable for the GFS keeping period.įor example, if in GFS settings you enable weekly and monthly keeping periods with 2 weeks and 2 months of keeping backups accordingly and then enable immutability, it means that all weekly and monthly backups selected by the GFS keeping period assignment mechanism will be locked on backup storage and cannot be deleted with Backup Agent. The Object Lock feature is linked with the GFS retention policy. It allows an administrator to specify a data retention period or to implement a legal hold that prevents data from being deleted until the hold is removed. Object Lock (Immutability) is a solution that suits best data preserving purposes in accordance with compliance requirements. Object Lock (Immutability) is supported for the following storage providers: Within this period, backup data cannot be modified or deleted. Some Plug-in based backup types do not currently work, such as System State, Exchange, and VMware.Object Lock (Immutability) is a feature that locks backup datasets for a period specified in GFS retention policy settings. The plan is to have all backup types be supported in the future. Other S3-compatible (Generic S3 Storage Services device) related links:įor examples of bucket name guides (stating recommendations and naming restrictions) for two popular Generic S3 Storage Services providers, Wasabi's S3 Bucket name guide article can be viewed here, and Backblaze's S3 Bucket name guide can be viewed here.Ĭurrently in NovaBACKUP Generic S3 Storage Services (S3-compatible) devices only support file, Hyper-V and SQL plug-in backups. Importing backups on S3 Storage Devices in NovaBACKUP You can watch the NovaBACKUP 19.8 video series for various topics, including how-to's for Generic S3 devices, by viewing the YouTube playlist here.įor help with Adding a Generic S3 Storage Services device (S3-compatible device) in NovaBACKUP 19.8, please read this how-to guide below or watch this how-to video:įor help with Backing up to a Generic S3 Storage Services device (S3-compatible device) in NovaBACKUP 19.8, please watch the how-to video:īacking up to S3 Storage Devices in NovaBACKUPįor help with Importing backup sets from a Generic S3 Storage Services device (S3-compatible device) in NovaBACKUP 19.8, to be able to restore files from that S3 backup, which could have been produced from a completely different client computer, that can be accomplished by adding a new Generic S3 Storage Services device (your existing device cannot be edited after it is saved the first time for the Domain and Computer Name properties) in NovaBACKUP 19.8 (in case you lose the device itself in the configuration or the computer that had NovaBACKUP installed on it was lost or damaged and need to rebuild your setup and get your indexed backups that are stored on Generic S3 back) please read the how-to guide: It supports file backups and restores to S3-compatible devices only at this time (read the note at the bottom). The Generic S3 Storage Services device type (S3-compatible device type) was added starting in NovaBACKUP 19.8.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |