BackupTargetOptions.TransformToSyntethicDays for copy jobs?

[pirx]

I wanted to change BackupTargetOptions.TransformToSyntethicDays for a couple of backup jobs. But the used wildcard for job name did also include copy jobs. My check for $Job.BackupTargetOptions.TransformToSyntethicDays now returns the changed day (Thursday) also for copy jobs.

Code: Select all

# (Get-VBRJob -Name "mycopyjob").BackupTargetOptions.TransformToSyntethicDays
Thursday

But if I check the copy jobs settings in GUI, the day has not changed, it still shows Friday. Is this option used at all for copy jobs?

[oleg.feoktistov]

Are you talking about VM/files copy jobs or backup copy jobs? What VBR version do you use?

[pirx]

Latest version 12.1.1, backup copy jobs.

[david.domask]

Hi @pirx,

I think you need to set this with with Set-VBRBackupCopyJob on the -GFSOptions flag:

https://helpcenter.veeam.com/docs/backu ... ml?ver=120

That is the intended way of setting it -- the Get-VBRJob cmdlet will return CJob object which has a lot of properties that aren't used on all backup types anymore, so that's why it accepted the change but the UI didn't see any changes because it's reading the info from a different location.

[pirx]

Ok, I just wanted to ensure that I do not have to adjust anything after running the script against copy jobs.

[david.domask]

Aha, understandable; what you ended up doing here was setting the retention value in some XML somewhere, but the backup copy will read the _real_ values from elsewhere. This is just a made up example but you can imagine some XML looking like:

Code: Select all

<JobOptionsRoot>
     <RetentionSettings>
          <BackupTargetOptions>
                <TransformToSyntethicDays>Thursday</TransformToSyntethicDays>
           </BackupTargetOptions>
      </RetentionSettings>
      <GFSSettings>  <== This is where the UI/Job would read the data from
             <GFSWeeklyDay>Friday</GFSWeeklyDay> <== This is where the UI/Job would read the data from
      </GFSSettings>
</JobOptionsRoot>

So ultimately it's fine, the Backup Copy is not relying on the other data you set initially.