I’m not really bashing their workstations, i’m actually quite fond of Vista on my laptop.
However, when it comes to servers, I view being in an environment where Microsoft is the PRIMARY operating system by a factor of 20:1 as a form of torture akin to having my finger-naiils pulled out or being tied to a chair and forced to listen to “Barney” all day.
What I hate most about Microsoft – (and if I keep this up, I’m going to have to rename this site to Microsoft-Hates-Me.Com) – is that it can’t handle the simplest tasks.
For a split-mirror backup, whether it be TimeFinder/Mirror, TF/Clone, or TF/SNAP, the process is the same:
1.Â Freeze the database / filesystem
2.Â Snap the volumes.
3.Â Thaw the database / filesystem
4.Â Mount the volumes on your media server host.
5.Â Back the filesystems up.
6.Â Unmount the volumes from the media server
7.Â Terminate the Snap session
Seems pretty basic.Â Microsoft seems to have trouble with #4 and #6.Â Seems this “Super OS” they’ve got can’t handle the idea that SCSI devices might go on and off the bus at different times.Â
EMC gives a tool, TFIM (TimeFinder Integration Modules) at at least allows you to perform the commands that Microsoft doesn’t even make available, mount, unmount, flush, etc.Â Â But god forbid you reboot a host while the SNAPS are inactive or the BCV’s are established (and thereby not ready to the host).Â You’re screwed.
Can *SOMEONE* please write a decent SCSI driver for Windows?Â Please?