Re: incomplete backups
On Wednesday 13 November 2002 10:06, Joshua Baker-LePain wrote: On Tue, 12 Nov 2002 at 8:02pm, Gene Heskett wrote Not enough emphasis is placed on the fact that tar won't access a file with any kind of a lock on it, and in the case of amanda, its certainly a fixable problem. I recovered all the indexes and curfiles and such but absolutely nothing else that could be construed as a configuration file. So chg-scsi.conf, amanda.conf, disklist, tapelist the rest of the configuration stuff in /usr/local/etc/amanda/DailySet1 is gone and I'm going to have to re-invent a goodly number of wheels before amanda is back up and running. *snip* Comments everybody? This is exactly why my nightly backup script, after running the amdumps and rewinding/ejecting the tapes, tars up all the amanda config files and directories. That tar ball then gets put two places (on two separate machines), each of which are backed up. So, if my amanda server completely dies, I'll still have my complete config and set up as of last night. So it looks as if I'm going to have to reinvent that wheel too. I take it that must depend on the system, Jon L. tells me his backups do contain all that. I *think* he's doing solaris. -- Cheers, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
Re: incomplete backups
On Tue, 2002-11-12 at 18:02, Gene Heskett wrote: Greets folks; I now have recovered as much as I can, but a couple of things need to be said. Not enough emphasis is placed on the fact that tar won't access a file with any kind of a lock on it, and in the case of amanda, its certainly a fixable problem. I recovered all the indexes and curfiles and such but absolutely nothing else that could be construed as a configuration file. So chg-scsi.conf, amanda.conf, disklist, tapelist the rest of the configuration stuff in /usr/local/etc/amanda/DailySet1 is gone and I'm going to have to re-invent a goodly number of wheels before amanda is back up and running. I'm a little puzzled. When I look at the files that amanda says it backed up it looks like it backed up the above files you mentioned on my system. My system is a RedHat Linux 6.0 system using GNU tar V1.12. Is your system and/or tar different? -- Carl D. Blake Director of Engineering Boeckeler Instruments, Inc. 4650 S. Butterfield Dr. Tucson, AZ 85714 Phone: 520-745-0001 FAX: 520-745-0004 email: [EMAIL PROTECTED] .com
Re: incomplete backups
On Wed, Nov 13, 2002 at 01:20:32PM -0500, Jon LaBadie wrote: Nothing to do with the system at all. It's just a little something added into the script which runs amanda each day - I presume at least 95% of amanda users run amanda from a cron driven script. A couple of lines in that /those (if you run more than one config) script(s) and bingo - indices safely squirelled away. I think Gene was refering to his backup on Linux missing things like amanda.conf, tapelist, disklist, ... He attributed this to tar honoring locks on these files during backup. I noted to him that my backups on Solaris do not seem to lack these files. I'm not sure that was it at all. There's no reason on earth for amanda to issue any kind of a lock on amanda.conf, tapelist, disklist during backup and anyway I don't think tar even looks at such locks - like Frank, I sometimes get tar errors against index files - no biggie. But certainly on my Linux setup, I checked with my amfind script and amanda.conf is backed up. (In fact I've a bazillion amanda.conf files in various place - must go on a cleanup). I thought Gene was bemoaning the fact that he didn't have copies of those files somewhere handy other than on his tapes (so that he first had to restore them from there before he could find out what was on what tape). But I'm sure Gene will clarify matters for us. Regards, Niall O Broin
Re: incomplete backups
On Wednesday 13 November 2002 11:49, Carl D. Blake wrote: On Tue, 2002-11-12 at 18:02, Gene Heskett wrote: Greets folks; I now have recovered as much as I can, but a couple of things need to be said. Not enough emphasis is placed on the fact that tar won't access a file with any kind of a lock on it, and in the case of amanda, its certainly a fixable problem. I recovered all the indexes and curfiles and such but absolutely nothing else that could be construed as a configuration file. So chg-scsi.conf, amanda.conf, disklist, tapelist the rest of the configuration stuff in /usr/local/etc/amanda/DailySet1 is gone and I'm going to have to re-invent a goodly number of wheels before amanda is back up and running. I'm a little puzzled. When I look at the files that amanda says it backed up it looks like it backed up the above files you mentioned on my system. My system is a RedHat Linux 6.0 system using GNU tar V1.12. Is your system and/or tar different? Other than its RH8.0 with a bleeding edge (2.4.20-pre10-ac2) kernel, not really. Tar is of course 1.13-25. Frankly, I also expected them to be there, but after the last dumpcycle tapes had been restored from, all I had was the indices and such. -- Cheers, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
Re: incomplete backups
On Wednesday 13 November 2002 11:59, Niall O Broin wrote: On Wed, Nov 13, 2002 at 11:14:40AM -0500, Gene Heskett wrote: This is exactly why my nightly backup script, after running the amdumps and rewinding/ejecting the tapes, tars up all the amanda config files and directories. That tar ball then gets put two places (on two separate machines), each of which are backed up. So, if my amanda server completely dies, I'll still have my complete config and set up as of last night. So it looks as if I'm going to have to reinvent that wheel too. I take it that must depend on the system, Jon L. tells me his backups do contain all that. I *think* he's doing solaris. Nothing to do with the system at all. It's just a little something added into the script which runs amanda each day - I presume at least 95% of amanda users run amanda from a cron driven script. A couple of lines in that /those (if you run more than one config) script(s) and bingo - indices safely squirelled away. I'm running it directly from crontab, but by the time I get it all breathing again, I suspect that's one of the first wheels I grease. This sucks. -- Cheers Niall, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
Re: incomplete backups
On Wednesday 13 November 2002 13:14, Frank Smith wrote: --On Wednesday, November 13, 2002 09:49:56 -0700 Carl D. Blake [EMAIL PROTECTED] wrote: On Tue, 2002-11-12 at 18:02, Gene Heskett wrote: Greets folks; I now have recovered as much as I can, but a couple of things need to be said. Not enough emphasis is placed on the fact that tar won't access a file with any kind of a lock on it, and in the case of amanda, its certainly a fixable problem. I recovered all the indexes and curfiles and such but absolutely nothing else that could be construed as a configuration file. So chg-scsi.conf, amanda.conf, disklist, tapelist the rest of the configuration stuff in /usr/local/etc/amanda/DailySet1 is gone and I'm going to have to re-invent a goodly number of wheels before amanda is back up and running. I'm a little puzzled. When I look at the files that amanda says it backed up it looks like it backed up the above files you mentioned on my system. My system is a RedHat Linux 6.0 system using GNU tar V1.12. Is your system and/or tar different? I don't think it is a universal problem, although I'm sure it can be painful for those that discover it. My system (Debian 3.0, tar 1.13.19) backs them up fine. I even get occasional 'file changed as we read it' messages backing up changing index files, so tar isn't even skipping files with active write locks on my system. I wonder if thats one of the diffs between tar-1.13-25 which I'm running, and tar-1.13-19. In which case it might be smart to back-pedal one minor version. One of those things that makes one 'hu'. If there are certain versions, filesystems, etc. that can cause this problem then something needs to be added to the docs so the people impacted can work around it. I agree, but first we need to define if we can, just why it didn't, and if possible, fix that. Recoveries are relatively few and far between, as they should be, so this might take a while to draw a bead on. -- Cheers Frank, Gene AMD K6-III@500mhz 320M Athlon1600XP@1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
Re: incomplete backups
On Wednesday 13 November 2002 13:20, Jon LaBadie wrote: On Wed, Nov 13, 2002 at 04:59:19PM +, Niall O Broin wrote: On Wed, Nov 13, 2002 at 11:14:40AM -0500, Gene Heskett wrote: This is exactly why my nightly backup script, after running the amdumps and rewinding/ejecting the tapes, tars up all the amanda config files and directories. That tar ball then gets put two places (on two separate machines), each of which are backed up. So, if my amanda server completely dies, I'll still have my complete config and set up as of last night. So it looks as if I'm going to have to reinvent that wheel too. I take it that must depend on the system, Jon L. tells me his backups do contain all that. I *think* he's doing solaris. Nothing to do with the system at all. It's just a little something added into the script which runs amanda each day - I presume at least 95% of amanda users run amanda from a cron driven script. A couple of lines in that /those (if you run more than one config) script(s) and bingo - indices safely squirelled away. I think Gene was refering to his backup on Linux missing things like amanda.conf, tapelist, disklist, ... He attributed this to tar honoring locks on these files during backup. I noted to him that my backups on Solaris do not seem to lack these files. Thats it precisely, Jon. Once I get the majority of this thing running again, I'll see if amrecover can find those files in the indices I do have. Its disabled in manda's crontab ATM for obvious reasons. -- Cheers, Gene AMD K6-III500mhz 320M Athlon1600XP1400mhz 512M 99.19% setiathome rank, not too shabby for a WV hillbilly
