Truncated archive/backup reparation
Scott Ritchie <[email protected]> Tue, 11 Mar 2025 12:40:32 +0000
| Newsgroups | gmane.comp.sysutils.backup.dar.support |
|---|---|
| Message-ID | <CAO1VBV06WhCOm1CeeXkTLyHfeg11yQp0Q0uYeAw2azKBENGrrA@mail.gmail.com> |
--===============6049763288794325535== Content-Type: multipart/alternative; boundary="000000000000a73d5f063010658f" --000000000000a73d5f063010658f Content-Type: text/plain; charset="UTF-8" Hi, I'm trying to understand how to use the -y/--add-catalogue command to repair a truncated archive, however, unfortunately have not been successful in my own attempts after reading the various documentation/tutorials/man page. First, I create a test backup where I simulate a power fault/computer reboot part way through by sending the SIGKILL signal to the process: dar -c path/to/backup/backup_slice -s 1G -R folder/to/backup -g subfolder Let's say I am creating a backup of 10GB of data, and I send the SIGKILL signal part way through the creation of slice 4 to simulate a power failure / computer reboot. My understanding is the -y command should be able to recover (and continue?) with this backup. To do so, I run: dar -y path/to/cont_backup/backup_slice -A path/to/backup/backup_slice -s 1G -R folder/to/backup After reading through the incomplete archive, dar then tells me the next backup slice (in this case backup_slice.5.dar) is required for further operation, and asks me to provide this file. However, this file obviously does not exist, since the initial backup was interrupted during slice 4. When I hit ESC to tell dar I will not provide the file, dar outputs a message that it failed reading data CRC for the last file in the incomplete slice, and that the file may be damaged and will be marked as dirty, before crashing with a segmentation fault. I'm clearly missing something here, but I'm not sure what. I'd be grateful if someone on the mailing list could clarify, or provide a working example? The version of dar I'm running is 2.7.16 Kind Regards, Scott Ritchie --000000000000a73d5f063010658f Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable <div dir=3D"ltr">Hi,<br><br>I'm trying to understand how to use the=C2= =A0-y/--add-catalogue command to repair a truncated archive, however, unfor= tunately have not been successful in my own attempts after reading the vari= ous documentation/tutorials/man page.<br><br>First, I create a test backup = where I simulate a power fault/computer reboot part way through=C2=A0by sen= ding the SIGKILL signal to the process:<br><br>dar -c path/to/backup/backup= _slice -s 1G -R folder/to/backup -g subfolder<br><br>Let's say I am cre= ating a backup of 10GB of data, and I send the SIGKILL signal part way thro= ugh the creation of slice 4 to simulate a power failure / computer reboot.<= div><br>My understanding is the -y command should be able to recover (and c= ontinue?) with this backup. To do so, I run:<br><br>dar -y path/to/cont_bac= kup/backup_slice -A path/to/backup/backup_slice -s 1G -R folder/to/backup<b= r><br>After reading through the incomplete archive, dar then tells me the n= ext backup slice (in this case backup_slice.5.dar) is required for further = operation, and asks me to provide this file. However, this file obviously d= oes not exist, since the initial backup was interrupted during slice 4.</di= v><div><br>When I hit ESC to tell dar I will not provide the file, dar outp= uts a message that it failed reading data CRC for the last file in the inco= mplete slice, and that the file may be damaged and will be marked as dirty,= before crashing with a segmentation fault.<br><br></div><div>I'm clear= ly missing something here, but I'm not sure what. I'd be grateful i= f someone on the mailing list could clarify, or provide a working example?= =C2=A0=C2=A0</div><div><br>The version of dar I'm running is 2.7.16</di= v><div><br></div><div>Kind Regards,</div><div><br></div><div>Scott Ritchie= =C2=A0=C2=A0</div></div> --000000000000a73d5f063010658f-- --===============6049763288794325535== Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Content-Disposition: inline --===============6049763288794325535==--