Recovering from a "disaster" is beyond the scope of Perl.
Simply put: Perl is just not going to help.
The "care and feeding" of a server farm is beyond what I can explain here. I would hire some pros to do this and its not that expensive as this is a very competitive market.
A Windows server is gonna crash at least once per month ( Hey, at least due to the monthly "re-boot" from Redmond, WA) and probably a lot more often than that!
Keeping a Windows server farm "alive" and "on-line" is a job for Pros. I think you would be lucky if a Windows server only dies 20x per year. This has nothing to do with Active State or Perl.
Update: My Win XP machine just crashed and yes I consider a "mandatory re-boot" as a crash. I've had *nix boxes run for a year without re-boot. A Windows server will die more than 20x per year. These Windows boxes are finicky. Don't try to muck with a bunch of them by yourself. This has nothing at all to do with Perl.
JavaFan has got it right.
In reply to Re: Disaster Recovery follow up.
by Marshall
in thread Disaster Recovery follow up.
by iskinner
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |