anchor.diff:  $ oc logs -f <restic-nr2v5>
   ----
   
  -ifeval::["{mtc-version}" < "1.3"]
   [id="restic-permission-denied-error-for-nfs-storage_{context}"]
  -== `restic: permission denied` error for NFS storage
  +== Restic permission error when migrating from NFS storage with root_squash enabled
   
  -If you are migrating data from NFS storage and `root_squash` is enabled, `Restic` maps to `nfsnobody` and does not have permission to perform the migration. The following error is displayed in the `Restic` pod log.
  +If you are migrating data from NFS storage and `root_squash` is enabled, `Restic` maps to `nfsnobody` and does not have permission to perform the migration. The `Restic` pod log displays the following error:
   
  -.Example output
  +.Restic permission error
   [source,terminal]
   ----
  -backup=openshift-migration/<backup_id> controller=pod-volume-backup error="fork/exec /usr/bin/restic: permission denied" error.file="/go/src/github.com/vmware-tanzu/velero/pkg/controller/pod_volume_backup_controller.go:280" error.function="github.com/vmware-tanzu/velero/pkg/controller.(*podVolumeBackupController).processBackup" logSource="pkg/controller/pod_volume_backup_controller.go:280" name=<backup_id> namespace=openshift-migration
  +backup=openshift-migration/<backup_id> controller=pod-volume-backup error="fork/exec
  +/usr/bin/restic: permission denied" error.file="/go/src/github.com/vmware-tanzu/
  +velero/pkg/controller/pod_volume_backup_controller.go:280" error.function=
  +"github.com/vmware-tanzu/velero/pkg/controller.(*podVolumeBackupController).processBackup"
  +logSource="pkg/controller/pod_volume_backup_controller.go:280" name=<backup_id>
  +namespace=openshift-migration
   ----
   
  -You can resolve this issue by creating a supplemental group for Restic and adding the group ID to the `MigrationController` CR manifest.
  +You can resolve this issue by creating a supplemental group for `Restic` and adding the group ID to the `MigrationController` CR manifest.
   
   .Procedure
   
  -. Create a supplemental group for Restic on the NFS storage.
  +. Create a supplemental group for `Restic` on the NFS storage.
   . Set the `setgid` bit on the NFS directories so that group ownership is inherited.
   . Add the `restic_supplemental_groups` parameter to the `MigrationController` CR manifest on the source and target clusters:
   +
  
positive.code: A data verification error does not cause the migration process to fail.
  ====
  
  You can check the `Restore` CR to identify the source of the data verification error.
  
  .Procedure
  
  
negative.code: 
  . Click *Save*.
  
  [id="resticverifyerrors-in-the-migmigration-custom-resource_{context}""]
  == Restic verification errors in the MigMigration custom resource
  
  If data verification fails when migrating a persistent volume with the file system data copy method, the `MigMigration` CR displays the following error:
  
  .MigMigration CR status
  [source,yaml]
  ----
  status:
  