I have a requirement to provide a failover plan for my production server (NT
4.0/AR 4.0.3/SQL 7.0).

Obtaining a failover server with duplicate specs won't be a problem, as I
have already rec'd a commitment for the necessary hardware.

Once I have the failover server on the network, what's the best way to use
it?

1) AL with execution order of 999 firing on submit/modify to set fields on
the failover machine?
2) Perle scripts to update the failover machine periodically (hourly?)
3) Install and configure software, but manually import data when the
production machine goes 'south'?
4) Something I haven't thought of...

To clarify 'best', as in "what's the best way..."; we would consider 'best'
to mean a minimal amount of manual interaction balanced with 'reasonable'
cost.

Thanks in advance,

Rick

Hi Rick,

I think a filter (not AL) with execution order of 999 firing on
submit/modify will be the best option. This will make the solution purely
written in Remedy which saves time installing and testing other software
(like perl).

If you do care about response time, you would consider an escalation that
run every whatever (hour, day...etc), that sets a flag, and then this flag
fires a filter that does the work.

HTH,

Ashraf Elrefaey
Remedy Consultant
Workflow Solutions Ltd
* Phone: +64 4 385 2885
* Cellular: +64 21 377523
* Fax: +64 4 385 2911
* E-Mail: mailto:refaey@workflow.co.nz
1 Webpage: http://www.workflow.co.nz


-----Original Message-----
From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
Sent: Thu, 28 December 2000 12:42
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Setting up a failover system


**

I have a requirement to provide a failover plan for my production server (NT
4.0/AR 4.0.3/SQL 7.0).

Obtaining a failover server with duplicate specs won't be a problem, as I
have already rec'd a commitment for the necessary hardware.

Once I have the failover server on the network, what's the best way to use
it?

1) AL with execution order of 999 firing on submit/modify to set fields on
the failover machine?
2) Perle scripts to update the failover machine periodically (hourly?)
3) Install and configure software, but manually import data when the
production machine goes 'south'?
4) Something I haven't thought of...

To clarify 'best', as in "what's the best way..."; we would consider 'best'
to mean a minimal amount of manual interaction balanced with 'reasonable'
cost.

Thanks in advance,

Rick

Hi, Rick.

First, 4 questions:

1) Are you shooting for ZERO downtime or almost zero?

2) Will the server be supporting anything other than Remedy - now or in the
future?

3) What's the server hardware configuration (hard drives, RAID, etc)?

4) How is the DB configured (filegroups, transaction logs and location,
etc)?

Depending on your answers to the above, I have a couple of suggestions for
you.

NOTE: I'd discourage using Remedy workflow for this. You'll need something
far more dependable. (my 2¢)

Cheers,

Eric
Eric Evans, Remedy Skilled Professional
Senior Remedy Developer/Administrator
Senior Systems Analyst
Computer Sciences Corporation
Stuttgart, Germany
011-49-711-680-6190


-----Original Message-----
From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
Sent: Thursday, December 28, 2000 12:42 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Setting up a failover system


**

I have a requirement to provide a failover plan for my production server (NT
4.0/AR 4.0.3/SQL 7.0).

Obtaining a failover server with duplicate specs won't be a problem, as I
have already rec'd a commitment for the necessary hardware.

Once I have the failover server on the network, what's the best way to use
it?

1) AL with execution order of 999 firing on submit/modify to set fields on
the failover machine?
2) Perle scripts to update the failover machine periodically (hourly?)
3) Install and configure software, but manually import data when the
production machine goes 'south'?
4) Something I haven't thought of...

To clarify 'best', as in "what's the best way..."; we would consider 'best'
to mean a minimal amount of manual interaction balanced with 'reasonable'
cost.

Thanks in advance,

Rick

Eric,

We'd obviously like zero downtime, but don't want to pay 'an arm and a leg'.

The server is dedicated as Remedy failover.

The server will have the same hardware config as the production unit, dual
processors, 1 GB of memory, etc. No one would be opposed to using a RAID,
other than the cost factor. Do you know of an economical solution?

I'm assuming we have a 'standard' (is there such a thing?) SQL
configuration. We haven't had a DBA, but are backing up data using Perle
scripts.

If this isn't detailed enough, let me know; I'll go back and get some more
answers.

Thanks,

Rick

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Evans, Eric W.
Sent: Thursday, December 28, 2000 3:12 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Setting up a failover system


**

Hi, Rick.

First, 4 questions:

1) Are you shooting for ZERO downtime or almost zero?

2) Will the server be supporting anything other than Remedy - now or in the
future?

3) What's the server hardware configuration (hard drives, RAID, etc)?

4) How is the DB configured (filegroups, transaction logs and location,
etc)?

Depending on your answers to the above, I have a couple of suggestions for
you.

NOTE: I'd discourage using Remedy workflow for this. You'll need something
far more dependable. (my 2¢)

Cheers,

Eric
Eric Evans, Remedy Skilled Professional
Senior Remedy Developer/Administrator
Senior Systems Analyst
Computer Sciences Corporation
Stuttgart, Germany
011-49-711-680-6190


-----Original Message-----
From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
Sent: Thursday, December 28, 2000 12:42 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Setting up a failover system


**

I have a requirement to provide a failover plan for my production server (NT
4.0/AR 4.0.3/SQL 7.0).

Obtaining a failover server with duplicate specs won't be a problem, as I
have already rec'd a commitment for the necessary hardware.

Once I have the failover server on the network, what's the best way to use
it?

1) AL with execution order of 999 firing on submit/modify to set fields on
the failover machine?
2) Perle scripts to update the failover machine periodically (hourly?)
3) Install and configure software, but manually import data when the
production machine goes 'south'?
4) Something I haven't thought of...

To clarify 'best', as in "what's the best way..."; we would consider 'best'
to mean a minimal amount of manual interaction balanced with 'reasonable'
cost.

Thanks in advance,

Rick

Rick,

That's plenty of info. I'll keep cost in mind.

Let me sleep on it and drop you a line tomorrow.

Eric

-----Original Message-----
From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
Sent: Thursday, December 28, 2000 3:50 PM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Setting up a failover system


**

Eric,

We'd obviously like zero downtime, but don't want to pay 'an arm and a leg'.

The server is dedicated as Remedy failover.

The server will have the same hardware config as the production unit, dual
processors, 1 GB of memory, etc. No one would be opposed to using a RAID,
other than the cost factor. Do you know of an economical solution?

I'm assuming we have a 'standard' (is there such a thing?) SQL
configuration. We haven't had a DBA, but are backing up data using Perle
scripts.

If this isn't detailed enough, let me know; I'll go back and get some more
answers.

Thanks,

Rick

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:ARSLIST@LISTSERV.VISTAIT.COM]On Behalf Of Evans, Eric W.
Sent: Thursday, December 28, 2000 3:12 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Re: Setting up a failover system


**

Hi, Rick.

First, 4 questions:

1) Are you shooting for ZERO downtime or almost zero?

2) Will the server be supporting anything other than Remedy - now or in the
future?

3) What's the server hardware configuration (hard drives, RAID, etc)?

4) How is the DB configured (filegroups, transaction logs and location,
etc)?

Depending on your answers to the above, I have a couple of suggestions for
you.

NOTE: I'd discourage using Remedy workflow for this. You'll need something
far more dependable. (my 2¢)

Cheers,

Eric
Eric Evans, Remedy Skilled Professional
Senior Remedy Developer/Administrator
Senior Systems Analyst
Computer Sciences Corporation
Stuttgart, Germany
011-49-711-680-6190


-----Original Message-----
From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
Sent: Thursday, December 28, 2000 12:42 AM
To: ARSLIST@LISTSERV.VISTAIT.COM
Subject: Setting up a failover system


**

I have a requirement to provide a failover plan for my production server (NT
4.0/AR 4.0.3/SQL 7.0).

Obtaining a failover server with duplicate specs won't be a problem, as I
have already rec'd a commitment for the necessary hardware.

Once I have the failover server on the network, what's the best way to use
it?

1) AL with execution order of 999 firing on submit/modify to set fields on
the failover machine?
2) Perle scripts to update the failover machine periodically (hourly?)
3) Install and configure software, but manually import data when the
production machine goes 'south'?
4) Something I haven't thought of...

To clarify 'best', as in "what's the best way..."; we would consider 'best'
to mean a minimal amount of manual interaction balanced with 'reasonable'
cost.

Thanks in advance,

Rick

Hi Rick,

Maybe you'd consider DSO, it's 35k (or so), but you can create and update an
independent copy of each entry from your production server in almost real
time.
Considerning the fact that you are using NT where the scripting capabilities
are very limited, I'd say arsperl is the other way. Filters, al's, etc.
might not be in great help because there is no utility you can trigger to
import the data into the other server (backup).
May be the migrator can do some good work for you.
BTW, folks, can you run the migrator in batch mode.

Nicky Madjarov
Intellico Solutions, Inc.

1507 Hermitage Pk. Dr.
Hermitage, TN 37076
Phone: (615) 883 7591
Mobil : (201) 747 8672
Pager: 2017478672@mobile.att.net
e-mail: nickym@intellicosolutions.net
http://www.intellicosolutions.net
----- Original Message -----
From: "Ashraf Elrefaey"
To:
Sent: Wednesday, December 27, 2000 5:55 PM
Subject: Re: Setting up a failover system


> **
>
> Hi Rick,
>
> I think a filter (not AL) with execution order of 999 firing on
> submit/modify will be the best option. This will make the solution purely
> written in Remedy which saves time installing and testing other software
> (like perl).
>
> If you do care about response time, you would consider an escalation that
> run every whatever (hour, day...etc), that sets a flag, and then this flag
> fires a filter that does the work.
>
> HTH,
>
> Ashraf Elrefaey
> Remedy Consultant
> Workflow Solutions Ltd
> * Phone: +64 4 385 2885
> * Cellular: +64 21 377523
> * Fax: +64 4 385 2911
> * E-Mail: mailto:refaey@workflow.co.nz
> 1 Webpage: http://www.workflow.co.nz
>
>
> -----Original Message-----
> From: Rick Phillips [mailto:netfirst@EARTHLINK.NET]
> Sent: Thu, 28 December 2000 12:42
> To: ARSLIST@LISTSERV.VISTAIT.COM
> Subject: Setting up a failover system
>
>
> **
>
> I have a requirement to provide a failover plan for my production server
(NT
> 4.0/AR 4.0.3/SQL 7.0).
>
> Obtaining a failover server with duplicate specs won't be a problem, as I
> have already rec'd a commitment for the necessary hardware.
>
> Once I have the failover server on the network, what's the best way to use
> it?
>
> 1) AL with execution order of 999 firing on submit/modify to set fields
on
> the failover machine?
> 2) Perle scripts to update the failover machine periodically (hourly?)
> 3) Install and configure software, but manually import data when the
> production machine goes 'south'?
> 4) Something I haven't thought of...
>
> To clarify 'best', as in "what's the best way..."; we would consider
'best'
> to mean a minimal amount of manual interaction balanced with 'reasonable'
> cost.
>
> Thanks in advance,
>
> Rick
>
>
>

>

I don't know anythign abut SQL, but I'd check out what kind of repliation it
is capable of first.


Neil Anderson
Senior Systems Developer
Halifax plc (UK)

disturbed@freewebaccess.co.uk
disturbed_uk@yahoo.com

Mobile: 07785 372821

'This message is attributable to the sender and does not necessarily reflect
the view of Halifax Group plc or its subsidiaries'


----- Original Message -----
From: "Rick Phillips"
To:
Sent: Wednesday, December 27, 2000 11:42 PM
Subject: Setting up a failover system


> **
>
> I have a requirement to provide a failover plan for my production server
(NT
> 4.0/AR 4.0.3/SQL 7.0).
>
> Obtaining a failover server with duplicate specs won't be a problem, as I
> have already rec'd a commitment for the necessary hardware.
>
> Once I have the failover server on the network, what's the best way to use
> it?
>
> 1) AL with execution order of 999 firing on submit/modify to set fields
on
> the failover machine?
> 2) Perle scripts to update the failover machine periodically (hourly?)
> 3) Install and configure software, but manually import data when the
> production machine goes 'south'?
> 4) Something I haven't thought of...
>
> To clarify 'best', as in "what's the best way..."; we would consider
'best'
> to mean a minimal amount of manual interaction balanced with 'reasonable'
> cost.
>
> Thanks in advance,
>
> Rick
>
>
>

>