ghosting server for quick recovery???
I have a boss who isnt the greatest when it comes to IT.
I am going to be setting up their domain and exchange server, its been down for a few years since their last crash.
If it crashes again, he wants it up in like an hour.
I figured what I could do for him is tell him I will do nightly backups and once a week, I will ghost the machine to another set of disks so all i have to do is switch out the disks and if he can handle the time, i will do a restore from the night before.
I was thinking I could just ghost from one set of raid drives to another. make sure both raids are the same size, same disks and everything.
How does that sound?
I am going to be setting up their domain and exchange server, its been down for a few years since their last crash.
If it crashes again, he wants it up in like an hour.
I figured what I could do for him is tell him I will do nightly backups and once a week, I will ghost the machine to another set of disks so all i have to do is switch out the disks and if he can handle the time, i will do a restore from the night before.
I was thinking I could just ghost from one set of raid drives to another. make sure both raids are the same size, same disks and everything.
How does that sound?
0
Comments
Your certainly not running raid-0 are you?
Tex
2. Ghost is crap. Use Acronis
3. SBServer, Are you using this server for multiple tasks? IE Exchange, domain controller, file server?
4. Get a second machine in place as a fail over controller and use replication as your first line of redundancy. You should always have a second controller that is nightly replicated to. Then you rely on your mirrored drives, drive images, etc.
We have two of the same servers. I want one for our domain controller and one for our file server/backup controller.
Our SBServer is nothing more then a file server right now, AD is crashed on it, but once I rebuild their domain, it will be a domain controller, Exchancge, DHCP, and DNS.
Thanx for the info, will put that down on paper.