> I recently used g4l (ghost for Linux) to make a backup of the one > Windows 2008 server we have. I already do nightly backups of the MSSQL
I encourage you to be highly skeptical and actually get some new hardware (or disks) and do a restore onto it to truly test it out. I have seen Symantec Ghost (and Norton, when they were Norton) fail to restore windows servers ... I don't know how many times. In general terms, (and I acknowledge there may be different behavior for a non-symantec ghost) there is always one problem: Somebody with intelligence about ntfs, partition tables, etc, thought they had more knowledge than they actually had, and assumed some tiny little detail didn't matter to the windows server. Only to find out (after it was too late) that it mattered. Specific examples: The disk signature (basically a serial number written in the mbr) is ok to change on laptops and desktops, but not on windows server. (MFT entry is to ntfs as inode is to ext3). Non-file, unnamed mft entries contain data. What are they? Proprietary. And essential to such services as sql server. I don't know what else. All the other issues I can think of would affect any backup tool, even dd. _______________________________________________ Tech mailing list [email protected] http://lopsa.org/cgi-bin/mailman/listinfo/tech This list provided by the League of Professional System Administrators http://lopsa.org/
