Jump to content
jrm_dantz

Missing subfolders in linux backup

Recommended Posts

My configuration:

 

server: Mac G4 MDD running 10.5.4 and Retrospect 6.1.230

client: Fedora 9, running Retroclient 7.6.100

 

What's up: Overall, the server and client are working fine; backups are happening. However, the backups are incomplete: some Linux directories are geting backed up, while others don't. For instance, in the /var directory, Retrospect is backing up account, db, lib, local, lock, named, run, spool, www, and yp; it's not backing up cache, cvs, empty, ftp, games, log, nis, opt, preserve, and racoon. I've run a full backup and an incremental, and these directories are picked up on neither.

 

Permissions on the directories seem fine; root owns them all the way down, and they're all read-enabled. Plus, if I set up one of these directories as a subvolume and include it in the list of Sources for the backup script, the directory and its files are detected and backed up. It seems that, once Retrospect knows the files are there, it's happy to back them up; it's just not finding those directories as part of its sweep of the file system. I of course have no idea what other directories might be missing from the backup.

 

Any ideas? This seems pretty serious to me...

Share this post


Link to post
Share on other sites

Do you see these directories when you browse the root of the volume from Configure>volumes?

 

Linux is not my strong area so hopefully one of the other forum members will have a better suggestions.

Share this post


Link to post
Share on other sites

For what it's worth, I was able to replicate this behavior on a second running a virtually clean installation of Fedora 9. Looking at the /var directory, the same subdirectories were (and were not) backed up.

Share this post


Link to post
Share on other sites

A few more data points in this:

 

* I added /var as a subvolume, and it seemed to pick up the directories and files that had been omitted from the previous backups.

 

* Several directories were missing from /home/ -- these seemed to be ones that were empty. For instance, if there was nothing along or at the bottom of /home/joeuser/a/b/c, neither a, b, nor c would be backed up.

 

Help? I'm rather concerned about how much I can trust these backups.

Share this post


Link to post
Share on other sites
* Several directories were missing from /home/ -- these seemed to be ones that were empty. For instance, if there was nothing along or at the bottom of /home/joeuser/a/b/c, neither a, b, nor c would be backed up.

Yes, empty folders are backed up, in a sense, through the catalog, but no files are backed up because the folder are, um, empty. Getting them to be restored as empty folders is a bit, um, odd, and I've had this issue with the interface for a long time, but the procedure is documented and does work:

 

From the Retrospect Read Me:

Empty folders (finding, selecting, and restoring): Retrospect's Find facility and selectors do not find or select empty folders, nor does Retrospect restore empty folders when no files are selected for restoring. To make sure your empty folders are restored when you restore an entire volume, select "Restore an entire disk" from the initial dialog and make sure that "Restore Entire Disk" appears in the pop-up menu of destination actions.

 

The only true workaround of which I am aware is to always restore to a Retrospect "subvolume" (define a subtree of the filesystem for that, just for restoration purposes), then restore "entire disk" to that subvolume. Grumble.

 

Russ

Share this post


Link to post
Share on other sites

Thanks for the pointer re empty directories -- I think I had seen that before, but had forgotten about it. That clears up a lot, but there are still weirdnesses taking place in /var. I just did a clean backup of my clean Fedora 9 box, and it's failing to back up /var/log and /var/cache, both of which have stuff in them.

 

Plus, new weirdnesses: I looked for other directories called "log", and found /usr/share/cvs/contrib/log. That has something in it, and it's not backed up. Also, none of the /sys directory is getting backed up, and there's definitely stuff down in there.

 

The suspicious person in me is wondering whether there might be some code somewhere in the Linux client that is deciding for me that, for whatever reason, I don't want to bother backing up. Crazy, huh?

 

I could look around more, but I've done about all the free QA work I can justify. Does anyone have any other thoughts?

Share this post


Link to post
Share on other sites

Do you have any selectors specified?

 

If so, could you provide a screenshot of that selector's conditions (not merely the name of the selector, because the conditions could have been changed).

 

I've done more than all the free help I can justify. If you don't want to spend more time on this to solve the problem, that's fine with me.

 

Russ

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×