Our "production source" is considered part of our production environment.

Kenneth
Kenneth E. Graap
http://www.linkedin.com/in/kennethgraap


-----Original Message-----
From: midrange-l-bounces+kenneth.graap=nwnatural.com@xxxxxxxxxxxx [mailto:midrange-l-bounces+kenneth.graap=nwnatural.com@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, November 08, 2011 4:32 AM
To: Midrange Systems Technical Discussion
Subject: RE: Backups in an iCluster environment...

While we have our development in a separate lpar there might be some things you want to consider even for your 1 lpar situation. If you are not replicating development to your HA machine then what do you do when you are running on your HA machine, and your primary machine is running a restricted state full system save and some user says this job has blown up and a developer needs to look at source?



Rob Berendt
--
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: "Graap, Kenneth" <Kenneth.Graap@xxxxxxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>,
Date: 11/07/2011 06:07 PM
Subject: RE: Backups in an iCluster environment...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



Thanx guys ... Good ideas.

Since we also have our developer environments in the same LPAR as
production, maybe I'd just replicate the production environment to my
offsite system. This would simplify my replication environment and in a
real disaster I could restore the development libraries from tape after my
production users are all up and running.

I'd could then run production BU's from the HotSite system and my
Development BU's anytime I want, from the production system, without
affecting production users access. Once a quarter I'd fail over to the
HotSite for production users and run a FULL backup of the production
system so I have a place to start if I needed to recreate the Production
System after a major disaster.

Kenneth
Kenneth E. Graap
http://www.linkedin.com/in/kennethgraap


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [
mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Monday, November 07, 2011 6:32 AM
To: Midrange Systems Technical Discussion
Subject: Re: Backups in an iCluster environment...

We do a complete save on our system on an every other month basis. Next
year that drops to once a quarter. It's not a bad idea to test switching
over to your backup system anyway and while you do a test is a good idea
to do a full save and IPL for PTF's and whatnot.


Rob Berendt
--
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: "Graap, Kenneth" <Kenneth.Graap@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion (midrange-l@xxxxxxxxxxxx)"
<midrange-l@xxxxxxxxxxxx>,
Date: 11/04/2011 06:37 PM
Subject: Backups in an iCluster environment...
Sent by: midrange-l-bounces@xxxxxxxxxxxx



We are thinking of implementing IBM iCluster in order to maintain a HOT
copy of our system at a DR location. I have a Power6 system so I can use
the new IBM System Mirror product and iASP's ...

I would like to do backups to tape at our HOT Site so the production
system can remain available to our users 7/24.

If I do that, would I have to do ANY kind of BU on the production system
... (Like a SAVSYS???) ... OR ... would backing up the HOT site be
sufficient?

[Description: Description: nwnatural]
Kenneth E. Graap | Systems Administrator
keg@xxxxxxxxxxxxx<mailto:keg@xxxxxxxxxxxxx> 503-226-4211 x5537
http://www.linkedin.com/in/kennethgraap


As an Amazon Associate we earn from qualifying purchases.

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-2024 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].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.