![]() ![]() Governance mode – there is no specified retention period and object locking can be removed by any user with s3:PutObjectLegalHold permission. ![]() S3 object lockĪmazon S3 Object Lock is a WORM (Write Once Read Many) technology which prevents stored objects from being deleted or overwritten for a specified amount of time (retention period). Veeam’s S3-compatible object storage vendors will also implement these API capabilities. This enables our customers to follow the Veeam 3-2-1 rule (create three copies of the most important files, use at least two different media and make sure that one copy is always stored off-premise) because as soon as those backup files land on the performance tier of the scale-out, backup repository they are immediately copied to object storage.”Īdditionally, there will also be the ability to make those backups immutable by leveraging the object lock API within AWS S3. Michael Cade, senior global technologist at Veeam, told us via email: “In V10, this feature is enhanced with the ability to immediately copy backup files to object storage. That included AWS S3, Azure Blob Storage, and IBM Cloud Object Storage. Users can push backups to an S3-compatible service to increase overall backup capacity. Faster copies with S3Ī native S3 interface for Veeam Backup & Replication, called Cloud Tier, was part of the Release 9.5 update 4, generally available since January 2019. Veeam has a 1PB NAS specific license to enable customers to protect PB-scale NAS environments. No additional licenses are needed for NAS CIFS backup to tape. Users need a Veeam Universal License for every 250GB backed up to disk with a NAS CIFS backup. With the object format NAS backup, wanted files and folders are found and located via a metadata lookup, which is faster than image crawling. To restore files from an image backup requires a so-called crawl through the image backup to find the desired file and folder. The NAS backup file format differs from the image-based backup format in being object-based with added metadata. This makes the restore process almost instant and faster than file-level restore from an image backup. There’s no need to run a Mount operation when restoring NAS backups, as they are not image-level. File-level restore from an image-level backup will be faster with v10. Performance optimisations have been added to the v10 release to speed file to tape and NDMP to tape jobs. It also improves the UI experience with registering a CIFS share as the data source for file to tape jobs, which was quite clumsy before. V10 adds file-level restores from NAS backups and support for disk targets. Also there was no support for NAS backup to disk-based target systems. NDMP has scalability limitations and entire NFS volumes needed to be backed or restored, not files within them. Veeam added the capability to backup NAS servers to tape in Veeam Availability Suite v9.5 Update 4 via NDMP, the standard market protocol for NAS backup. It also means that DR verification testing becomes easier to do and so ensure DR processes are accurate. The recovery of multiple VMS with a single click, together with faster recovery, makes disaster recovery processes simpler and faster. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |