howto:preseed-veeam-hardened
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revision | |||
howto:preseed-veeam-hardened [2025/07/13 10:20] – lessi | howto:preseed-veeam-hardened [2025/07/13 10:20] (current) – lessi | ||
---|---|---|---|
Line 8: | Line 8: | ||
* Until the final Backup Copy Job is running, no new backup may be created! That means during the migration, the primary backup must be paused! | * Until the final Backup Copy Job is running, no new backup may be created! That means during the migration, the primary backup must be paused! | ||
- | * For point 3 (Transfer): To move the data from the intermediate repository (e.g., a USB drive) to the hardened repository, we used “File Copy” in the Veeam VBR GUI. It is important that the entire subfolder (= backup job name) is copied. The files must not be modified during this process. | + | * For point 3 (Transfer): To move the data from the intermediate repository (e.g., a USB drive) to the hardened repository, we used “File Copy” in the Veeam VBR GUI. It is important that the entire subfolder (= backup job name) is copied. The files must not be modified during this process. |
+ | |||
* Immutability is not active immediately after the transfer. It is only set for the chain once the primary backup job runs again for the first time and subsequently automatically triggers the backup copy job. From that point on, the immutable flag is applied to the chain. | * Immutability is not active immediately after the transfer. It is only set for the chain once the primary backup job runs again for the first time and subsequently automatically triggers the backup copy job. From that point on, the immutable flag is applied to the chain. | ||
howto/preseed-veeam-hardened.txt · Last modified: by lessi