I think for the most part biztalk uses shares on the IFS, I don't think it accesses the DB. Our imaging system does though.

We have copiers/scanners that FTP scans, if they access via DNS they would be ok too i guess.

Thanks. Any non computer/IT steps in your documentation?

On Dec 9, 2015, at 1:55 PM, rob@xxxxxxxxx wrote:

This will differ by shop. And as you evolve. And your equipment.

For example, some routers allow you to have the same IP address in two
different locations. This would send our network guy into a heart attack
by not having different subnets by location.

We change the DNS. We do NOT change any router configs. None. And we do
switches every quarter with one coming up this weekend. We change the DNS
by CL. The mimix switch calls a CL program which talks to a Windows
client which then submits a DNS change. The timeout of this entry is set
pretty low. IOW we do not set up the expiration of this DNS entry very
high, more like 5 minutes.

Let's say you have PROD1 and PROD2. They both should have a database name
of PROD. This is what your biztalk type applications should be talking
to. With directly accessing PROD1 or PROD2 limited to systems stuff that
needs to know the difference.

WRKRDBDIRE

On GDISYS1
Relational database . . . . . . : GDISYS
Remote location:
Remote location . . . . . . . : *LOCAL
Type . . . . . . . . . . . . : *IP

Relational database . . . . . . : GDISYS
Relational database alias . . : GDISYS1
Remote location:
Remote location . . . . . . . : GDISYS1


On GDISYS2
Relational database . . . . . . : GDISYS
Remote location:
Remote location . . . . . . . : *LOCAL

Relational database . . . . . . : GDISYS
Relational database alias . . : GDISYS2
Remote location:
Remote location . . . . . . . : GDISYS2


I do find that one often has to UNMOUNT and re MOUNT stuff using NFS
though.

We have this documented enough that there are a few people who can do a
switch. And we alternate who works which shift on these downtime
weekends.

I will say that Darren and I are more the 'go to' guys on this here.

There are some crappy applications out there where you type in a name,
like PROD and the <expletive deleted> do a look up of the name and bury
the IP address in their configuration instead.
Another reason I despise host table entries, hard coded IP addresses,
etc...

Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Jack Tucky <jacktucky@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 12/09/2015 12:41 PM
Subject: Disaster recovery documents/help
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Does anyone have a high level document of steps required for a fail over?

Something like...

1. Do fail over on Mimix
2. Change DNS servers
3. Change router configuration
3. Check PC servers online
4. Check PC Apps (like Biztalk) running
5. Phone systems

etc.

Thanks, Jack
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.



--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.


This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2019 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].