The parameter -RestorePoint doesn’t remove chosen restore point, as the article says, it removes the whole backup or a particular file share from the backup.

Here is an explanation of this cmdlet logic from our developer, Pavel Akhrameev:

‘’ According to the code, it has the following modes of operation:

The first mode is simple. Only the parameter -NASBackup is set, how many backups were passed there - all that the cmdlet finds will be deleted.

The second mode - if you also set the -NASServer parameter. If you set parameters -NASBackup and -NASServer, then the parameter -RestorePoint is ignored. The cmdlet searches among the backups passed to the -NASBackup parameter the file share's backups specified in the -NASServer parameter and removes them from there.

The third mode - the parameters -NASBackup and -RestorePoint are set (the parameter -NASServer is not set). This mode is like the second one. The cmdlet searches among the backups sent to the -NASBackup parameter for file share backups that have the points specified in the -RestorePoint parameter and removes those file shares from the backups.

but this is cmdlet for NAS backup and modifies NAS backup job.

Some of the parameters of this cmdlet moved to Set-VBRNASBackupVersionRetentionOptions , such as: [-EnableActiveFileVersionRetention] [-ActiveFileVersionRetention <int>] [-EnableDeletedFileVersionRetention] [-DeletedFileVersionRetention <int>]

Cmdlet Set-VBRNASBackupArchivalOptions now has only: Set-VBRNASBackupArchivalOptions -Options <VBRNASBackupArchivalOptions [-ArchivalType <VBRNASBackupArchivalType> {All | InclusionMask | ExclusionMask}] [-InclusionMask <string[]>] [-ExclusionMask <string[]>] [<CommonParameters>]

there is no such variable, should be '$files' not the 'folder'

There is no such parameter in this cmdlet. New-VBRNASBackupArchivalOptions cmdlet has only -Archival type, -Inclusionmask, -ExclusionMask parameters

There is no such parameter in this cmdlet. New-VBRNASBackupArchivalOptions cmdlet has only -Archival type, -Inclusionmask, -ExclusionMask parameters

or Backups - Object Storage (Imported) node

Is it necessary to add that Backup copies also can be represented in Object Storage (Copy) node if the secondary repository is Object Storage?

Maybe we should write only: ''If you do not need the published share any more, you can stop the file share publishing" Because when migration to production is completed, we don't need to stop publishing the share manually. The share is already automatically unpublished after migration.