two unrelated people who agree to help out if need be would be enough :) a
couple migh conceivably be in a car accident together but not separate
peopel in different places.
Barring of course an account with an IT "insurance" company :) I wonder how
many other people think that's a good idea?
Prunebelly is a little different that your situation, Erika, since it is a
small non-profit, but we have attempted to learn from our experience,
thusly:
The domain is registered to the organization not an individual. All
passwords are known to two people. People know who the web host is. I have
made a point of mentioning, repeatedly, that a copy of the former web page
is sufficient -- in the hands of someone with a little knowledge -- to get
the content back online. Submissions to the patient registry go to multiple
locations.
We still struggle with a lot of issues, but if I were hit by a bus tomorrow
the thing would not start over from scratch... it's something :)
Dana
Erika L Walker-Arnold writes:
> Yeah, it's all back-ed up, etc. that's not an issue at all.
>
> It's someone with enough knowledge of the web industry basically
> "inheriting" the business and keeping it running.
> By the time all is said and done there could be over 400 sites running
> on 3 different servers that just need support and possibly further
> services.
>
> I really like the hosting company solution, as we're pretty tight with
> them. they know CF, they already manage and have access to the servers.
> Probably find a few point people to handle the clients and get
> agreements drawn up.
>
> Does that sound pretty feasible?
>
> Whatever we do, it also needs to have a bit of cascading to it, meaning
> we can let someone "inherit" the business, but what if something happens
> to them just days later? How many levels would you take care of and/or
> arrange? We take all this pretty seriously and I have no intention of
> letting anyone "hang out to dry" because that would be horrible. Well, I
> think so anyway...
>
> So much to do ....
>
> Cheers,
> Erika
>
>
> -----Original Message-----
> From: Dan Phillips (CFXHosting.com) [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 11:56 AM
> To: CF-Community
> Subject: RE: For all you freelancers and business owners
>
>
> Good point. If the hosting company offers managed services on the
> dedicated server contract, backups and the like should be included in
> there.
>
> -----Original Message-----
> From: Larry C. Lyons [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 13, 2003 11:49 AM
> To: CF-Community
> Subject: Re: For all you freelancers and business owners
>
> Erika,
>
> Here's my experience. When my former employer EBStor.com suddenly closed
>
> its doors, they were all set just to burn a CD with the customer's and
> leave them in the lurch. Fortunately our network guy found a hosting
> company that was willing to take over the contracts for their duration.
>
> If I were you I'd talk with your hosting company. Then get an agreement
> drawn up by a good lawyer that if anything happened to you, the hosting
> company would take over the contracts. Just make sure that they get
> recent
> copies of your sites, and database backups on a regular basis.
>
> larry
>
> At 11:37 AM 11/13/2003, you wrote:
> >What do you do in the event you no longer exist?
> >
> >By either death, disability or winning the lottery.
> >
> >What happens to your customers?
> >Do you have something arranged with someone to take over?
> >
> >We need to come up with a solution soon, and I was curious about how
> >any of you may deal with it.
> >
> >Our work for our clients are not one-offs. They are all using a hosted
> >solution of ours on several dedicated servers. So if we disappeared off
>
> >the face of the earth tomorrow, as long as there was someone to run the
>
> >servers, they'd be fine ... But it's finding that someone. I toyed with
>
> >the idea of asking the actual hosting company if they'd be interested
> >... But before I do that, figured I'd get some other ideas, if there
> >were any ...
> >
> >And it's not like I can put the code in escrow, because it's not just
> >the code. They wouldn't have a clue what to do with the code, they need
>
> >the service.
> >
> >Does any of that make sense?
> >
> >Cheers,
> >Erika
> >
> >
> >----------
> >[
>
> _____
>
>
>
[Todays Threads] [This Message] [Subscription] [Fast Unsubscribe] [User Settings]
