Convert-VBRLegacyCopyBackup
Short Description
Converts legacy backup file of legacy periodic backup copy job to the per-machine backup with separate metadata files using mapping.
Applies to
Product Edition: Standard, Enterprise, Enterprise Plus, Veeam Universal License
Syntax
Convert-VBRLegacyCopyBackup -Backup <CBackup> [-Days <Int32>] [-EnableTimeBasedRetention] [-RunAsync] -TargetJob <VBRBackupCopyJob> [<CommonParameters>] |
Detailed Description
This cmdlet converts legacy backup file of legacy periodic backup copy job to the per-machine backup with separate metadata files format using synthetic full creation based on the old backup file.
The cmdlet detaches legacy backup file from legacy periodic backup copy job and links the new backup file to the new backup copy job. After you run the cmdlet, you will have two backups: detached legacy backup file (in orphaned node) and per-machine backup with separate metadata files linked to the new backup copy job.
Parameters
Parameter | Description | Type | Required | Position | Accept Pipeline Input |
---|---|---|---|---|---|
Backup | Specifies backup file. The cmdlet will return the backup file you want to link to the new backup copy job. | Accepts the CBackup object. To get this object, run the Get-VBRBackup cmdlet. | True | Named | True (ByValue) |
TargetJob | Specifies a backup copy job to which you want to map a backup file. | Accepts the VBRBackupCopyJob object. To create this object, run the Get-VBRBackupCopyJob cmdlet. | True | Named | False |
Days | Specifies an amount of days after which detached legacy backup file is deleted from the storage. Note: Days count starts from the backup storage creation date. | Int32 | False | Named | False |
EnableTimeBasedRetention | Defines that retention policy is applied to the source legacy backup file and its incremental backup files. The amount of retention days is specified in the Days parameter. When determining whether the number of days is exceeded, the cmdlet compares storage creation date, the current date and retention days. Note: If the number of retention days is exceeded for the source legacy backup file but not exceeded for any of the incremental backup files, the source legacy backup file will not be deleted. | SwitchParameter | False | Named | False |
RunAsync | Defines that the command returns immediately without waiting for the task to complete. | SwitchParameter | False | Named | False |
<CommonParameters>
This cmdlet supports Microsoft PowerShell common parameters. For more information on common parameters, see Microsoft Docs.
Output Object
None.
Examples
Upgrading Backup Chain Format
This example shows how to simplify the backup chain format upgrade process.
Important |
By following this example, you will detach legacy backup file from legacy periodic backup copy job and link the new backup file to the newly created backup copy job. You may need to edit this example script with details that are relevant to your backup infrastructure (GFS retention settings, notification settings and so on). |
Step 1. Getting Job Name and Target Repository
At this step, get the job name and the target repository.
Perform the following steps:
|
Step 2. Specifying Job and Repository Settings
At this step, specify the job and the repository settings.
Perform the following steps:
|
Step 3. Getting Legacy Backup Copy Job Source Objects and Disabling Job
At this step, get legacy backup copy job source objects and disable the job you want to upgrade.
Perform the following steps:
|
Step 4. Getting Legacy Source Backup Files and Starting Upgrade Process
At this step, get legacy source backups files you want to upgrade to the per-machine backups with separate metadata files. Validate which of them are eligible for the upgrade using the foreach statement and start the upgrade process. Any existing per-machine backups with separate metadata files will be skipped.
Perform the following steps:
|
Step 5. Adding New Backup Copy Job and Converting Legacy Backup Files
At this step, add new backup copy job and convert legacy backup files to the per-machine backups with separate metadata files.
Perform the following steps:
|
Full Script Example
|
Related Commands