Loading...
Loading...
This article documents an alternative method for migrating backups from a Scale-Out Backup Repository (SOBR) utilizing non-immutable performance tier extents to one using Hardened Linux Immutable performance tier extents. This method is useful in situations where a SOBR contains backup data that cannot be moved using the Backup Move function, such as those created by: Legacy Backup Copy Jobs Veeam plug-ins for Enterprise applications Veeam Plug-in for SAP HANA Veeam Plug-in for Oracle RMAN Veeam Plug-in for SAP on Oracle Veeam Plug-in for Microsoft SQL Server Veeam Plug-in for IBM Db2 Veeam Plug-in Management Unstructured Data Source Jobs File shares (NAS Backup) Object storage Veeam Backup for Nutanix AHV Veeam Backup for OLVM and RHV Kasten K10
The migration procedure documented in this article requires: All backups being migrated are currently located on a performance tier extent of a Scale-Out Backup Repository. The migration procedure utilizes the Evacuate Backups function to relocate all backup data from the non-immutable extent(s) to the hardened linux repository extent(s).If backups are currently located on a simple repository, create a new Scale-Out Backup Repository and add that simple repository as a performance tier extent. The Linux Server that will, in the end, be used as a Hardened Linux Repository must have been added to VBR using single-use credentials.
The complete procedure involves: Phase 1: Prepare for Migration Phase 2: Evacute Backups to Non-Immutable Linux Storage Phase 3: Swap Mutable Linux Extents to Hardened Extents Phase 4: Clean Up & Resume Operations
Immutability on the migrated backups will be set after the next job run.
Veeam Integration
Learn more about where this data comes from
BugZero Plan
Streamline upgrades with automated vendor bug scrubs
BugZero Prevent
Wish you caught this bug sooner? Get proactive today.