A few days ago, I had to restore an SBS2003SP1 server from backup.
The situation was complicated by the fact that the server was
undocumented, control of RAID driver diskettes didn't exist, etc, etc.
After several tries, I got a backup to restore and to recognize the
RAID5 array (which had not been backed up). The boot drive is on a
RAID1 mirror and is drive C:. Just about all the default locations
for folders were chosen at setup.
The server has been running reasonably well except for nits and things
we're dealing with sequentially except that:
NTBACKUP complains about an error accessing a folder on the RAID5
array (assigned drive letter F:). The name of that folder is
"F:\SYSVOL\SYSVOL\localdomain.local".
I don't know how this folder ever got created in the first place but
it looks like a partial copy of the C:\WINDOWS\SYSVOL folder; partial
in that the "localdomain.local" subfolders are inaccessible. The
gross folder tree looks plausible as:
F:\SYSVOL\
\domain\
\staging\
\staging area\
\localdomain.local\
\sysvol\
\localdomain.local\
In both cases, the "localdomain.local" folders are inaccessible.
I've checked the registry and every FQN reference to SYSVOL is given
as C:\WINDOWS\SYSVOL -- exactly as a default SBS installation should
be (AFAIK).
I'm really nervous about this situation because apart from the
catastrophic TELNET session the user claims blew his server away in
the first place, I've no idea how this beast got this way.
What I'm doing is to exclude this apparently spurious F:\SYSVOL folder
from the SBS Backup procedure that runs every night starting tonight.
I really want to get a "clean" backup for a change and I'm hopeful
that this will do the trick.
Then, if it's truly safe to do so, I'm going to try to remove that
F:\SYSVOL folder and its subfolders. Problem is, I'm not at all
certain it's really safe to do so.
I'd be grateful for any guidance anyone has to offer here.
Thanks,
--
BilBo