John R. Jackson writes: > >Looking at the sendbackup.*.log files, I can see where the index > >program is invoked. I don't see anything to indicate _why_ the > >index files are so small. > > Could you post one of those files? The symptoms seem to imply indexing > is enabled but the client just never sent anything.
Certainly; I've attached one to the end of this message. (A gzip'd original.) > Are your backup images OK? If you pick some client/disk that is > having an index problem, what happens if you try something like > this: > > mt -f /dev/whatever rewind > amrestore -p /dev/whatever <client> <disk> | gtar tf - I'll try that later today. I found that the amidxtape service wasn't properly enabled in my host's xinetd.d directory. That's been fixed, but still no dice on the index file. The client hasn't changed, but the host was rebuilt a couple of weeks back. It's still the same version of amanda, it's just been recompiled with the new system. Is it a good idea to go back and rebuild amanda? Could there be some important build-time config that needs to be set or fixed? > >I'd like to know how to restore index files from tape, if anyone > >knows how to do that... > > As Joshua said, the general problem of doing this with Amanda is > difficult since the client and server may be running totally > different OS's and the software to read an image may not be > available on the server. So the data has to be shoved back to the > client, indexed there and then sent back. Not just a thing you're > going to do with a couple lines of shell script coding :-). > > However, in the special case of using GNU tar, it's portable so > this is easier. The attached script is **not** well tested, but > might get you going: Both client and host are now using GNU tar 1.13.19. Thanks for the script. Again, I'll try this out and see what happens. Cheers, -Adam
