|06-17-2010, 02:49 AM||#1|
Join Date: Jun 2010
Time machine mess. Bug re RAID ?
I have a highpoint RAID array, but because of firmware limitations at the time of install, I boot from a separate SATA drive. A few months ago, I moved the home directory from the boot disk to the RAID. For convenience, I made a symlink from the boot disk to the new directory (but changed each user's info to point to the new directory directly). I had been running Time machine, but never need to restore files, so I assumed the new director was being backed up. Today, I cleared out my Downloads directory (If there were something critical in there, I would have checked the backup disk first.) Later, I wanted to find a deleted item, and was shocked to see that the entire new home dir had NEVER been backed up.
To illustrate, here is the machine before and after the directory move:
(MacOSX): Mounted on /
/. . .etc
(RAID partition): Mounted on /Volumes/Mass
(boot): Mounted on /
/Users -> /Volumes/Mass/home (symbolic link)
/. . .etc
(RAID): Mounted on /Volumes/RAID
However, the Time machine for every backup since looks like:
MacOSX/Users -> /Volumes/Mass/home (symlink got backed up)
/Volumes/Mass/ (nothing, the /Volumes/Mass/home directory was never backed up!)
I could provide the ls -l output, but the above summarizes the issue. Basically, NO backups of the new directory. I have checked to ensure that there are no explicit exclusions in the time machine config. Any suggestions for what went wrong here? Is this a mis-configuration, or a bug. How to I get time machine to start seeing this directory?
|Display Modes||Rate This Thread|