Error 404--Not Found |
From RFC 2068 Hypertext Transfer Protocol -- HTTP/1.1:10.4.5 404 Not FoundThe server has not found anything matching the Request-URI. No indication is given of whether the condition is temporary or permanent. If the server does not wish to make this information available to the client, the status code 403 (Forbidden) can be used instead. The 410 (Gone) status code SHOULD be used if the server knows, through some internally configurable mechanism, that an old resource is permanently unavailable and has no forwarding address. |
We're a paperless office, so we depend heavily on our e-mail system in all three of our [California] locations - San Rafael, Irvine and Santa Barbara. All of the transactions that take place over e-mail need to have some kind of digital backup. We have a large Microsoft Exchange environment, and there are a lot of messages with important attachments.
| Steve Perry | |
| • Title: IT director, Costello & Sons Insurance, in San Rafael, Calif. | |
| • Years in networking: 22 | |
|
“Thirty minutes later, I have my system back up and running.”
|
|
Mimosa NearPoint Server does three things for us: It backs up Exchange in real time; it provides continuous data protection for our e-mail system; and it provides a failover for the Exchange server. If you've ever worked with Exchange, you know these are all critical features.
Before, if someone made a mistake on Exchange, we used to have to restore it from tape, and that would take a day and a half just to get the e-mail system back on its feet. The company would come to a grinding halt. Microsoft never invented a way to have a warm backup for Exchange. Now, if my Exchange server crashes, I can go to the NearPoint Server and click "restore." Thirty minutes later, I have my system back up and running. At most we might have lost an hour of productivity from the time of the last snapshot to complete restoration. I've done a lot of Exchange recoveries in my time, and you're lucky if you lose less than a day typically.
I can also configure the NearPoint Server to extract attachments from Exchange and deliver them from the NearPoint Server. That way, I don't have to have everyone's kids' pictures and other attachments clogging up the Exchange server. When a user sends an attachment to everyone in the company, it simply inserts a pointer to a file on the NearPoint Server. This makes Exchange more efficient and boosts performance, because the database shrinks considerably in size - in fact, ours has been reduced by two-thirds.
| Start a public discussion with other Network World users on this article (scroll up to send this article to a colleague). Log In | Register for an account (Why you should) |
Note: Register to have your user name appear; otherwise your comment will show up as "Anonymous."
*Anonymous comments will only appear once they are approved by the moderator.
Copyright 2008 Network World Inc.
Start-up shields against Exchange failures
01/31/05
Continuous data protection finds supporters
09/19/05
Study revisits e-mail archiving
01/18/06
|
Does Verizon's Voyager stack up to the iPhone? |
|
TOP STORIES
|
5 IT skills that won't boost your salary
[1,407]
Women 4 times more likely than men to cough up personal info
[589]
Japan's 10 funniest tech-related commercials [Videos]
[407]
Throwing away a promo CD is "unauthorized distribution"?
[1,265]
Adults too quick to dismiss educational video games
[682]
Attack of the iPhone clones [Slideshow]
[578]
10 things IT needs to know about AJAX
[1,258]
This Year's 25 Geekiest 25th Anniversaries [Slideshow]
[409]