Re: Backing up from your Mimix HA machine

[Jack Kingsley <iseriesflorida@xxxxxxxxx>]

We do that with VISION currently, the drawback is we drop the connection
between boxes and thus lose the journal entries while the backup takes
place.

On Wed, Mar 2, 2011 at 7:59 PM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

> I discussing Mimix and the other HA Products with Vision, the person I was
> talking to classified Mimix as the Industrial Strength of the HA products
> they carry. While products like iTera may be better suited for smaller
> installations. I have setup both Vision's iTera and IBM's iCluster products
> and they both work well. IBM is pushing their PowerHA.
>
> The product you need/choose will depend on your environment. If you are
> running SANs then you might want to consider SAN based replication
> solutions, if not then may any of the Logical Replication ( Mimix, iTera,
> iCluster etc) solutions.
>
> Define the Uptime and Recovery Time Requirements. 24/7 no more than say 5
> minutes downtime with virtually no loss in data or can the system be down
> for say 4hrs with some data entry required?  Will the HA system be ONLY HA
> with no other work being done other than receiving data or will reporting
> or
> other be done on it. ( this will affect Licensing of the OS and products on
> the system among other things ).
>
> On Wed, Mar 2, 2011 at 4:36 PM, Don Osmond <don.osmond@xxxxxxxxxxxxxx
> > wrote:
>
> > We just got a request from one of our hosted clients asking us to provide
> > another system to provide live backup.   I know of mimix but have zero
> > hands
> > on.   Are there other options?   Can anyone share on their experience
> with
> > Mimix?
> > Thanks
> >
> > Donald (Don) P. Osmond, CTO
> > Carolina Technology Associates, LLC
> > 803-325-6019 (Office)
> > 803-325-6006 (Fax)
> > 803-322-8054 (Cell)
> >
> > -----Original Message-----
> > From: midrange-l-bounces@xxxxxxxxxxxx
> > [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Bob P. Roche
> > Sent: Wednesday, March 02, 2011 5:07 PM
> > To: Midrange Systems Technical Discussion
> >  Subject: Re: Backing up from your Mimix HA machine
> >
> > A previous employer of mine did this type of backup at 2 sites that
> needed
> > to be up 24/7. I know they used Mimix, but I wasn't part of the direct
> > support for those locations, so I don't know the commands used. Annually
> > we would take down the production box for a full system save  during a
> > planned outage. This worked well. Of course being the (at the time)
> as/400
> > we never had to run a "live" test of switching to our HA servers only
> > planned outage tests.
> >
> >
> >
> > From:
> > Kirk Goins <kirkgoins@xxxxxxxxx>
> > To:
> > Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
> > Date:
> > 03/02/2011 03:48 PM
> > Subject:
> > Re: Backing up from your Mimix HA machine
> > Sent by:
> > midrange-l-bounces@xxxxxxxxxxxx
> >
> >
> >
> > Well, I  guess a question is does your HA config get EVERYTHING you want
> > backed up on a nightly basis? Another is do your regularly role to the HA
> > system and run? What would it take to rebuild the Production/Source
> system
> > and can the backups from the HA provide what is needed.
> > In theory, This process can minimize your downtime window for backups as
> > long as you are getting what you need and know how to recovery. You may
> > still need a Local Full Save or Save IBM. Are these machine local ( cross
> > town or inthe same room ) vs 1,000's ot 100's of miles apart? How often
> do
> > you grab last night's or last week's tape and restore?
> >
> >
> > On Wed, Mar 2, 2011 at 1:28 PM, <rob@xxxxxxxxx> wrote:
> >
> > > I ran the following by Lakeview support:
> > > <snip>
> > > Suppose your source machine is GDIHQ and your target machine is GDIHQ2.
> > I
> > > am hearing that we should forego backups on GDIHQ and we should be
> > backing
> > > up from GDIHQ2 as to not disrupt our line of business.
> > > Do you have any documentation on the "best practices" of doing that?
> > Like,
> > > do I shut down Mimix enough to free the locks and allow us to perform
> > our
> > > backups but not so far as to kill the remote journals from still
> getting
> > > their entries?
> > > We want to use BRMS.
> > > </snip>
> > >
> > > And their reply was
> > > <snip>
> > > Yes, lots of installations do their backups on their HA systems. There
> > > really isn't an official "Best Practice" recommendation, but
> personally,
> > I
> > > would set it up just as you describe. Specifically, you can do:
> > > <mimix>/ENDDG DGDFN(*ALL) PRC(*DBAPY) ENDOPT(*IMMED) ENDRJLNK(*NO)
> > >
> > > at the beginning of your backup process, then restart the MIMIX
> > processes
> > > with:
> > >
> > > STRDG DGDFN(*ALL) PRC(*DBAPY)
> > > </snip>
> > >
> > > Sounds pretty straight forward to me.  Does anyone have any comments or
> > > suggestions?
> > >
> > >
> > > 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
> > >
> > > --
> > > 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.
> >
> >
> > --
> > Kirk
> > --
> > 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 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.
>
>
> --
> Kirk
> --
> 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.