On Jan 17, 2007, at 6:37 PM, James Harper wrote:
>> The other option that came to mind would be to recover the C
>> partition, boot the machine into Windows, finish creating the
>> remaining partition(s) and restore the balance of the machine while
>> in Windows. After all, we now have a nice wintel version of bacula we
>> can use.
>
> If the machine is a domain controller then I believe Microsoft best
> practises would suggest putting some of the log files on a physically
> different set of disks. You would have to boot into active directory
> restore mode to fix this anyway so maybe it doesn't matter.
>
>> We know the OS will complain bitterly as I suspect you're off
>> loading things like SQL and Exchange onto the other partitions - but
>> after a reboot, it should find all the things it's looking for and
>> work after running Exchange and SQL specific utilities to bring those
>> databases back into a consistent state.
>>
>
> It should do. Even Backup Exec will not restore the exchange and SQL
> databases (except I think the actual backup exec database itself) as
> part of the disaster recovery restore. You have to restore the disk
> volumes and system state and then boot up and restore the databases.
Ah yes, and one more reason to end the madness with Backup Exec and
move completely over to Bacula.
>
> James
>
>
-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Bacula-users mailing list
Bacula-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/bacula-users
