But seriously, I just finished a contract at a large bank maanging the disaster recovery for a w2k advanced server environment(over 100 servers around the world, terabytes of data). To make it more complicated it was exchange (now there is a backup anoyance).
I never had any problems even using the internal NT backup (before they chose a solution).
All you need is a good DR procedure. In short:
1. Make backups (Full, diff and incremental to taste) 2. Have OS install disks ready. 3. At disaster time, install the OS and any drivers necessary to access the backup hardware. 4. Restore over the top of the OS, wipe everything. 5. Reboot and get coffee, done.
It is more complicated for Active Dir DC's and GC's etc but it's not rocket science.
Some apps require special backup programs (like e2k) or that you simply shut down services while you backup but to tell the truth, this happens in the Unix world (and mac world) as well.
I have never seen w2k fail on a file that is critical and distinct to each instance. A new install just makes a new file (for example pagefile.sys)
I seem to remember our turnaround was 12 hours for an e2k server with 10 databases and 350gb of mail storage. (Assuming the SAN did not have to be rebuilt, then it was more like 20 hours).
This is bad, because it's probably able to be automated but on the other hand, how many people throw their cc receipts away in the first bin they come to?
Since MS has posted KB on their MSDN and/or Technet CD's for quite a while, I fail to see how this can happen.
Will they stop doing that as well? Doubt it.
Slashdot Mirror
This exploit affects the Weblogic product. Oracle only acquired that a few months ago.
It's got squat to do with the DB product.
Sorry, this is not morphing... It's just a flapping wing. Anyone else sadly dissapointed by the images?
I live in the Netherlands and I can do all of those except the last. The netherlands is so small that I'd never consider flying internally anyway.
Here
That will teach him. Must be hard to do any rendering with that server overheating.
Probably a whole lot more than the server...
Dude, you can skip C:\pagefile.sys
But seriously, I just finished a contract at a large bank maanging the disaster recovery for a w2k advanced server environment(over 100 servers around the world, terabytes of data). To make it more complicated it was exchange (now there is a backup anoyance).
I never had any problems even using the internal NT backup (before they chose a solution).
All you need is a good DR procedure.
In short:
1. Make backups (Full, diff and incremental to taste)
2. Have OS install disks ready.
3. At disaster time, install the OS and any drivers necessary to access the backup hardware.
4. Restore over the top of the OS, wipe everything.
5. Reboot and get coffee, done.
It is more complicated for Active Dir DC's and GC's etc but it's not rocket science.
Some apps require special backup programs (like e2k) or that you simply shut down services while you backup but to tell the truth, this happens in the Unix world (and mac world) as well.
I have never seen w2k fail on a file that is critical and distinct to each instance. A new install just makes a new file (for example pagefile.sys)
I seem to remember our turnaround was 12 hours for an e2k server with 10 databases and 350gb of mail storage. (Assuming the SAN did not have to be rebuilt, then it was more like 20 hours).
I live in amsterdam and I reckon this guy should have got a mention...
Of course it's not a scientific job, but it still rates a mention.
/me wonders if the SMPng stuff is for me...
I am installing a new mailserver, I wonder if there are many advantages to SMPng (Speed etc..)
Put me down for 50 bucks.
This is bad, because it's probably able to be automated but on the other hand, how many people throw their cc receipts away in the first bin they come to?
Since MS has posted KB on their MSDN and/or Technet CD's for quite a while, I fail to see how this can happen. Will they stop doing that as well? Doubt it.