I need to chime in on this one because this is something we have been
asking for for years.

As we become more and more dependant on the use of Intermapper it is
increasingly important that the system be available on a 99.999% basis.

I have suggested a few different ways in which Dartware could create a
server/client, master/slave or other means of creating primary and
secondary systems to maintain proper operations.

This could even be beneficial for Dartware since it is something they
could sell on top of the standard application.

-----Original Message-----
From: [email protected]
[mailto:[EMAIL PROTECTED] On Behalf Of William Yardley
Sent: Wednesday, October 24, 2007 8:51 PM
To: InterMapper Discussion
Subject: Re: [IM-Talk] Keeping maps synchronized on different
InterMapperservers?

On Thu, Oct 18, 2007 at 01:26:47PM -0400, Christopher L. Sweeney wrote:
> At 10:00 AM -0400 10/18/07, Steven Good wrote:

>> Keeping maps synchronized on different InterMapper servers?  We have
>> two InterMapper servers that should have the same maps, settings and
>> polling.
[...]
>> Is this as simple as copying over directories and files? 
[...]
>> Do I need to shut down either server when doing the copy (if the way
to
>> do this is to copy folders and files)?

> You would definitely need to shut down the test server. I think it
> would be safer if you were to shut down both, to avoid doing the copy
> while IM is in the midst of auto-saving a map or writing something to
> the prefs. (If you want to copy logs and chart data, too, you
> definitely have to shut down both.)

I've been thinking about this too. I don't know if there are plans to
add such a feature, or how many other people it would be useful to, but
it would be very nice if there were a feature to allow multiple
Intermapper machines to share maps, in a master / slave or multimaster
situation (it would be even better if only one machine actually did the
polling, since I imagine having 2-3 or more machines polling the same
devices could cause issues in a large enough environment).

We had a problem on our main Intermapper server recently, and it
definitely reminded us how much we rely on it. Having some built in
functionality for at least a cold spare type setup would be handy for
us, though maybe it's not a feature required by enough users to be worth
adding.

On a semi-related note, is it relatively safe to backup Intermapper maps
/ data using standard backup tools, assuming the maps are generally not
being modified when the backups are running?

w

____________________________________________________________________
List archives: 
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]
____________________________________________________________________
List archives:
http://www.mail-archive.com/intermapper-talk%40list.dartware.com/
To unsubscribe: send email to: [EMAIL PROTECTED]

Reply via email to