Discussion Locked

Accessing SBS 4.5 partition

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I'm running Back Office SBS 4.5 on a dual boot system (Drive C = NT4Wks SP4 and Drive D = SBS 4.5).
The idea is to do a complete backup of Drive D (my entire SBS installation)in case of a disaster.
But SBS does not allow me to access Drive D from NT4 Wks.
Is there a way to enable this ?
Help will be appreciated.
Thanks a lot.

PM

4 replies

by mckaytech

It's an interesting and unorthodox plan and I generally am respectful of such creative thinking. But to be honest, in my opinion, it's a bad plan.

At the very least, as you've discovered, there are going to be permissions problems that result from the SBS PDC security model that doesn't support trusts.

My advice would be to scrub this plan and plan instead on using NTBackup to back up the SBS to DAT tape. Cost needn't be a deterrent - I just paid less than $200 for a re-conditioned DAT drive and controller.

If you have two physical drives, you might also want to take the additional step of mirroring them rather than using this dual-boot setup.

With mirrored drives and tape backup, the chances of an unrecoverable catastrophe are very, very small.

paul

by touti

Thank you Paul for your comments.
The big idea is to minimize the server "put back into production" time in case of a major disaster (fire, robbery).
Disk mirroring is of no help for those events.
Since I've started this discussion, I have installed Ultrabac software on NT4Wks and launched a full backup of D drive and it started well until it reaches the WIN.SBS/SYSTEM subfolder where one DLL causes the backup to fail on a timeout error.
So I'll continue looking for an answer to unlock access to the drive.
Thanks again.
PM

by mckaytech

I'm still missing something here because it's not clear to me how your plan is better for disaster recovery than doing a normal NTBackup from within SBS. If your server is destroyed or stolen, you're probably going to be recovering to different hardware and that could create significant problems for your plan, both as regards permissions/rights issues and HAL-type problems.

However, you seem pretty intent on doing it this way so I would just urge you to try a test recovery after (if) you get the backup problems fixed but before you have to do it in real life.

As far as the timeout error, it would appear that you have access to the drive but that it is just a small number of files in the SYSTEM directory that are causing the problem. This would be the expected result if the SBS partition is NTFS because the NTWS would not be part of the domain or local security accounts on the SBS partition. If that is the case, the only workaround I know is to make the SBS system partition a FAT partition.

The other possibility is that the DLL that is causing the backup to fail is hosed (particularly if the SBS partition is FAT).
Just thinking out loud here, from NTWS is it possible to manually copy that particular file?

paul

by touti

Thanks again Paul for your advice.
In fact we have in stock a spare server (same machine) which is in a separate building and run as a BDC.
After reading back your first advice, I then tried NT Backup and surprisingly, it works well and it gave mea complete full backup of SBS partition.
But still, I can't access that SBS partition from within Windows Nt Explorer.
I have upgrade Nt workstation 4.0 to Win 2000 Pro and what was my surprise not seeing Drive D (SBS partition) from within Windows Explorer. But the Nt 2000 backup works fine too.
Anyway, that's the end of this discussion.
Thank you again for your time.

This discussion is closed to new replies.