Re: --sequential-read not sequential???
Denis Corbin <[email protected]>
| Newsgroups | gmane.comp.sysutils.backup.dar.support |
|---|---|
| Message-ID | <[email protected]> |
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA256 On 19/02/2020 23:17, Graham Cobb wrote: >> Well, this is my turn to be confuse as I don't see how either >> 'rm' 'echo' or 'gpg' can lead the copy of each slice from the >> NAS... anyway that's not the issue here... > > :-) gpg reads the requested encrypted slice using NFS and decrypts > it into the tmp directory... OK, I see now :^) [...] > > Do I even need dar_xform or could I just concatenate the slices? No you can't. Concatenating all slice will not form a valid archive because there will be slice header in the middle of the slice that dar will just won't be able to handle. It will shift the location of file's data after them and you won't be able to recover anything. Sequential-read mode will allow you to recover most data from such type of wrong manipulation but not those located at the former slice boundaries (as there is a slice header in the middle of their data now). > >> If your NAS support ftp or sftp access, > > No, the unencrypted slices are never present on the NAS (which is > not in a secure location, and I like to be able to throw away old > backup disks without worrying about their contents). OK I understand that the encryption is not done by dar but outside by gpg, so this is not an option here. Note however that if you had used -K gnupg:... option with dar to cipher the backup, you should have been able to read it directly from the NAS while the slices would have been ciphered on the NAS. You could in particular restore any particular file very quicky without requiring the dowload of a whole slice. My 2 cents! > Cheers, Denis -----BEGIN PGP SIGNATURE----- iQIzBAEBCAAdFiEEOzEprx3d76WjfYGPCDGwvQPYsYIFAl5O3iMACgkQCDGwvQPY sYJ3mxAArm902NvgLfeVcM/jmUiwXObruOwZsxJr+uDCBDxwOuCOZ8PrejAn8wCT ZDEliv4SbehsonHl97OglRvSM4u8hoLWzfY1CuadFljwVKd5Tbhv+AOJ4Cps/3n7 WMTp6zgulNQyk3U3AXylBgO4AL9ufrOY7on9ejg5L6nb4Vi5iqS6m9QTP5Uo+QbU CJwWL/lLD0RH0MrD6r7ynyBZh9Z3kRF1oyFpd/LHFxGt2AQ9sYBbcPAic41Fceio WQTd4O8gp71cJDeHfbOCj67cStSbHZy8rdJUg8FZNJ+sR7tf4vIiMNZ4XKhpavTd FSl1DITWs6mMNGkyd5YQG4CFu0U2+PziojqGXq6PHFqMC4arIF4Fh237wa2eWtnt cSAXSiCywdAzP9olMdLTnB+pIBhT+OyQJQeH3xZVE0Bv3mqygZbZ7bvRaynf0O1x wg4jSHxAW1RZEdy6PzbTpKCJ25HaVjUn4iwYEa7k7zkl2Nj1Xokpcoyjax4PDTIX R63bjjmXekZywF8hWtnXc/r11eKsbvQvXy7UsD44DFGZpMZqp3VKT5a0Mm2TzKDn hZoEXLRG+PHwyP2ztKYAWnhbUOg5vzyooQEdB9xpNSUFMZ/l+TjF2pzGdz2zIU22 QxPUdGSizVNf5Avkb1qOhwD5Jz85IqzvUCb1SNSyV53ab8PgF7w= =PEMs -----END PGP SIGNATURE-----