RE: Stacked backups Was: Virtualizing Tape VIOS vs IBM 1 -- MIDRANGE-L

Some food for thought.
My previous system (2 LPARS) only had 2 drives, I could never do a DUP because of the amount of time required, (DUP overlapped with a save).
My current system (2 LPARS) has 4 drives.
Save, Restores, DUPs can all run simultaneously.
Also, if a drive fails, you can still operate without an immediate replacement.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Kirk Goins
Sent: Wednesday, October 08, 2014 4:10 PM
To: Midrange Systems Technical Discussion
Subject: Re: Stacked backups Was: Virtualizing Tape VIOS vs IBM 1

I will have 2 drives

On Wed, Oct 8, 2014 at 6:55 AM, Roberto José Etcheverry Romero < yggdrasil.raiker@xxxxxxxxx> wrote:

Kirk,

Same card is not same drive. I said no rmtX device (drive) can be
assigned to multiple vhosts at the same time. If your library has
multiple drives then go ahead. But if it's only multiple paths to the
same drive and AIX/VIOS sees it like that and therefore creates a
single rmtX device you'll hit that problem anyways.

Best Regards,

Roberto

On Wed, Oct 8, 2014 at 6:04 AM, Kirk Goins <kirkgoins@xxxxxxxxx> wrote:

I am not using the library in library mode, but rather in SEQ mode
so

that

is not an issue. Sue Baker from IBM does say I can place the card in
VIOS and virtualize it in such a way that 2 partitions can use using
the same card at the same time as long as they are using different
SAS ports. I

will

know first hand in a few weeks once I standup my Power8 that is on order.

On Sun, Oct 5, 2014 at 10:52 AM, Roberto José Etcheverry Romero <
yggdrasil.raiker@xxxxxxxxx> wrote:

Kirk, you wont be able to. A virtualized SAS drive cannot be
assigned

to

more than one partition at the time. Your script will have to use
an

SSH

command to move the rmtX to the next partition, I've just done
that. So either move the entire card the same way you always did
or lose the

library

feature and virtualize with VIOS AND use a script to move it (not
worth

it

in my opinion).

Best Regards,

Roberto

On Sat, Oct 4, 2014 at 11:45 PM, Kirk Goins <kirkgoins@xxxxxxxxx>

wrote:

Timing takes a little practice... I know how each of my backups
take

with a

little fudge factor tossed. Since all my partitions are IBM and
I

have

Object Connect setup ( you could do this other ways ) I do the

following.

I have a dataarea defined on each partition. When backup A
finishes I

first

vary off the drive and via a CL tell the HMC to Move the SAS
Adapter

to

partition #B. Then I set a value in that dataarea and SAVRSTOBJ
to

the

next partition where a program is checking the dataarea for the
OK to start.. I then set the dataarea back to a value for You
Can't Start

Yet

and

end partition A.
Repeat until al the backups are completed. With the new Power8
I am

going

to switch to virtualized tapes drives on a single SAS card owned
by

VIOS

so

I won't have to worry about have the HMC move the card and I can
run

both

drives a the same time with a single card fro 2 partitions.

On Fri, Sep 26, 2014 at 6:11 AM, <rob@xxxxxxxxx> wrote:

Ok. Like I said, I would be too worried about the timing of
each

lpar's

backup. We already have the tapes needed. And what we send
back

and

forth with Iron Mountain fits into the cases used. So it's
not a

grind

for us.

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: "Steinmetz, Paul" <PSteinmetz@xxxxxxxxxx>
To: "'Midrange Systems Technical Discussion'"
<midrange-l@xxxxxxxxxxxx>
Date: 09/26/2014 09:05 AM
Subject: RE: Stacked backups Was: Virtualizing Tape VIOS vs

IBM

1

Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Rob,

Already asked years back.
A BRMS volume can only be owned and used by one LPAR (system).
I wanted to use the same volume for all my nightly backups,
and

dups.

Could not be done.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxx] On

Behalf

Of

rob@xxxxxxxxx
Sent: Friday, September 26, 2014 7:47 AM
To: Midrange Systems Technical Discussion
Subject: Stacked backups Was: Virtualizing Tape VIOS vs IBM 1

Kirk,

Have you thought about submitting a DCR, or a COMMON
requirement,

to

allow

BRMS to stack multiple lpars onto a single tape?
IDK if we could use that as I would be concerned about timing
the

saves

on

each lpar.

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: Kirk Goins <kirkgoins@xxxxxxxxx>
To: Midrange Systems Technical Discussion <

midrange-l@xxxxxxxxxxxx

Date: 09/25/2014 05:31 PM
Subject: Re: Virtualizing Tape VIOS vs IBM 1
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>

Because we Stack our backups from multiple LPARs on a single tape

each

night we can't use BRMS ans SEQ. Mode works just fine for us.

Thanks I

probably won't hear back from Techline for Several More Business

Days.

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

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