Further investigation, it almost looks like there wouldn't be a way to restore a file directly without reinstall backuppc on a box and mounting our offsite box as the topdir. I just don't see how to access a file directly for example /etc/named/zones/db.demo. Am i correct or am i missing something. I was able to find the attrib id of the files in the zone directory i was using to test.
From: "David Hoskinson" <david.hoskin...@astroshapes.com> To: "backuppc-users" <backuppc-users@lists.sourceforge.net> Sent: Thursday, October 29, 2020 1:15:14 PM Subject: Re: [BackupPC-users] Important question concerning offsite backups CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders. Follow up. Disaster occurs and backup server out of commission. We have this copy sitting at remote location but will take several weeks to get new backup server. Can i still recover a file? I am trying to navigate to one of the host directories. Go to /etc/named/zones and i see the attrib file. I believe you said there was a attribPrint command? Would doing that tell us which directory in cpool our file was? Thank you, should answer all From: "backuppc-users" <backuppc-users@lists.sourceforge.net> To: "backuppc-users" <backuppc-users@lists.sourceforge.net> Cc: "Craig Barratt" <cbarr...@users.sourceforge.net> Sent: Thursday, October 29, 2020 12:45:05 PM Subject: Re: [BackupPC-users] Important question concerning offsite backups CAUTION: This email originated from outside your organization. Exercise caution when opening attachments or clicking links, especially from unknown senders. David, For doing offsite backups weekly we have 2 synology drive arrays that we rotate between 2 buildings. If i did some kinda of rsync of /backup/astrobackup to offsite1:/backup/astrobackup would that make our data be recoverable in case of disaster? Yes - you should rsync that entire directory tree, including cpool. Also check if the BackupPC config is stored in /etc/BackupPC, rather than below /backup/astrobackup (it's configurable in [ https://linkprotect.cudasvc.com/url?a=http%3a%2f%2fconfig.pl&c=E,1,LyCJKyGsEF-PYOTiebjeD3FjG5IoM_AWSxJUDw3YLzlmVIy5PDnfiDn97UmGSYoTwcoBsWy9WdGi1AigX8g98fND1Hh884KDAOUXMj3lJzkhUQ,,&typo=1 | config.pl ] ). If so, you should copy that too. BQ_BEGIN Before we would just do a rsync -aruX of each backed up host to the offsite drive, but with the attrib and pool coming into the mix i'm not sure thats enough without copying the entire directory BQ_END That would have worked correctly with BackupPC v3, since it used hardlinks to populate each backup's contents. But in v4, as you note, there aren't hardlinks and attrib files are used to reference cpool files; all the file contents are in cpool and only the metadata is stored below each backup. Craig On Thu, Oct 29, 2020 at 8:22 AM David Hoskinson < [ mailto:david.hoskin...@astroshapes.com | david.hoskin...@astroshapes.com ] > wrote: BQ_BEGIN Hello, I asked this the other day and didn't get any responses so maybe i wasn't clear in my question. We have a new 4.4 installing and all backups are now being successfully ran. Our setup is that the backups are pointed at the /backup/astrobackup directory which is 96 TBs in size What i have noticed and was told was that now the attrib files are the only thing being sent to the /backup/astrobackup directories for each backed up host? It seems that the bulk of the data is being sent to /backup/astrobackup/cpool. For doing offsite backups weekly we have 2 synology drive arrays that we rotate between 2 buildings. If i did some kinda of rsync of /backup/astrobackup to offsite1:/backup/astrobackup would that make our data be recoverable in case of disaster? Before we would just do a rsync -aruX of each backed up host to the offsite drive, but with the attrib and pool coming into the mix i'm not sure thats enough without copying the entire directory If i am still not being clear let me know as i am getting pressured to close this project before audit. Thank you David Hoskinson Systems Administrator Ext 226 . _______________________________________________ BackupPC-users mailing list [ mailto:BackupPC-users@lists.sourceforge.net | BackupPC-users@lists.sourceforge.net ] List: [ https://lists.sourceforge.net/lists/listinfo/backuppc-users | https://lists.sourceforge.net/lists/listinfo/backuppc-users ] Wiki: [ https://github.com/backuppc/backuppc/wiki | https://github.com/backuppc/backuppc/wiki ] Project: [ https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbackuppc.github.io%2fbackuppc%2f&c=E,1,z-_rkX6gtnB-oVHHIhbDTiSD5HcB4FLGpMijrr3xusaSHw2jC9Joxtx2uP3og6Wn0ESK7Doe0rnUkb4-3G7xVpfxiSSMJRaDFHf6lTtHrGVb4nrF5mvSUA7x&typo=1 | https://backuppc.github.io/backuppc/ ] BQ_END _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbackuppc.github.io%2fbackuppc%2f&c=E,1,TxSiIowrzDk_9a3wu7xvNIe56rkP02IcdHtXIwedLYJm3fuJCxKv87U9xFU3RcptILlCOGCwRAkeUBWncG-qIOPsIbdP-qYjKkGDKytX&typo=1 _______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://linkprotect.cudasvc.com/url?a=https%3a%2f%2fbackuppc.github.io%2fbackuppc%2f&c=E,1,fsMVExWKMF3SHLqV8nK1W-YpgetyoRsfxSxiwsCOUeT0AhAVOKmhczwfo_ZsKpFpKnmVSaYBIdc_MBRjDRsmDKbZ78et4uolTMpZgudQ6Rrl&typo=1
_______________________________________________ BackupPC-users mailing list BackupPC-users@lists.sourceforge.net List: https://lists.sourceforge.net/lists/listinfo/backuppc-users Wiki: https://github.com/backuppc/backuppc/wiki Project: https://backuppc.github.io/backuppc/
