After upgrade to Retrospect V18.2 and MacOS 11.6.2 I get error -691

[mturndal]

I have a Mac mini 2014 as retrospect server with V18.2 and MacOS 11.6.1 and the Client is a MacPro 2013 with Retrospect 18.2 and MacOS 11.6.2.
On the Retrospect Server the drives are connected through globalSAN® iSCSI Initiator and the client have ATTO iSCSI initiator and 
they are connected to a Synology DS1618+ with DSM7

I have the following error and really don't know what this is about ?

Can you help ?

Thank you

Mikael

+  Sauvegarde incrémentale utilisant Enzo - Lightroom à 18/12/2021 12:08:32 (Unité d'exécution 2)
    18/12/2021 12:08:33: Numérisation de fichiers de données de sauvegarde terminée
    Vers le jeu de sauvegarde Jeu de médias - Enzo Lightroom AGAG...
    -  18/12/2021 12:08:32: copie de LR_Index sur Enzo
    Utilisation de l'analyse instantanée LR_Index sur Enzo
    18/12/2021 12:08:46: Trouvés : 66745 fichiers, 40005 dossiers, 492,8 Go
    18/12/2021 12:08:46: Correspondance terminée
    18/12/2021 12:08:47: Sélecteur "Tous les fichiers" was used to select 66 745 files out of 66 745.
    18/12/2021 12:08:48: Copie en cours : 66560 fichiers (454,8 Go) et 185 liens durs
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 161 547: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 161 547: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 161 547: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 161 547: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 156 457: erreur -691 (corrupt persistent data)
    [*] MacProLoc::VProFetch error retrieving volume for refnum 161 547: erreur -691 (corrupt persistent data)
       18/12/2021 14:32:29: Création de l'image...
    18/12/2021 14:32:29: Vérification de 40 005 dossiers pour les ACLs ou attributs étendus
    18/12/2021 14:33:16: Copie de 32 448 dossiers avec ACLs ou attributs étendus terminée
    18/12/2021 14:33:17: Copie d'instantané : 2 fichiers (38,2 Mo)
       18/12/2021 14:33:19: image stockée, 38,2 Mo
       18/12/2021 14:33:19: Exécution réussie
    66 560 fichiers traités (454,8 Go) 
    Performance: 3 324,4 Mo/min
    Durée: 02:24:47(00:04:41 inactivité/chargement/préparation)

[RHL IT]

I too am getting the same error, only on some Macs though.  I am wondering if it is an issue with the Mac Drive or the Retrospect Backup Set.  This error has appeared after a company wide power outage so it could be either one.

Looking at the Backups more closely, the error has gone away on at least one Mac, but not on all the Macs.

NOTE: The errors appear on some Macs, but not all Macs in a single backup set.  It also appears on Macs from multiple backup sets.  We have a single Retrospect Server, so only one backup set would have been getting backed up at the time of the power outage.  Normally, corruption only appears in the actively backed up set if the Server goes down unexpectedly.

MacProLoc::VProFetch error retrieving volume for refnum 11,337: error -691 (corrupt persistent data)

[MikeHutch]

Looks like you have corrupt files, Retrospect is trying and failing to backup. As you can see via the '(corrupt persistent data)' bit in the log text.

To find out what is corrupted, as the log doesn't say specific filenames, I suggest you backup a few folders at a time, as a test backup, until you come across this error, so you can narrow it down. Just look at the log everytime it completes a test backup. Once you've hit on the problem, you'll have to backup 1 folder at a time, you narrow it further, OR, manually check the files in those folders, to see if they open up OK, or not, or just resave them.

RHL, I suspect the corrupt file may have gotten corrupted before or after the backup - either way, a file or two are definitely damaged. See above solution for those effected Macs. It's a pain, but that's all I can suggest.