Quite possibly, though I don't recall your name off the top of my
head...then again, I left Houston 23 years ago and I've slept in the
interim...

On Fri, Jul 18, 2025 at 8:01 PM Steve Beaver <
[email protected]> wrote:

> Are you the Same Jay Maynard I knew in Houston
>
>
>
> Sent from my iPhone
>
> No one said I could type with one thumb
>
> > On Jul 18, 2025, at 19:30, Jay Maynard <
> [email protected]> wrote:
> >
> > As I understand things, you'd need to replicate the AMI Cloud management
> > server - or simply run it  on AWS to begin with. (Or your favorite cloud
> > provider.) If you don't have to restore DASD, all you'd need to do is
> make
> > sure you can connect to your cloud data store and the management server
> > from your DR site, and you're off and running.
> > If you're not running backups of your DASD to AWS, then the size
> > requirements for the pipe drop.
> >
> > I'll be sure to post our experiences here. I'm really hoping the product
> > works as advertised. If it does, we'll save a pile of money.
> >
> >
> >> On Fri, Jul 18, 2025 at 7:17 PM Michael Babcock <
> >> [email protected]> wrote:
> >>
> >> Not sure my last post went through so here it is again.
> >>
> >> We have a dedicated DR site that has a DS8950 DASD box where we mirror
> our
> >> production DASD to so we won’t need to FTP anything.  We are wondering
> how
> >> a dataset on tape gets restored during a DR batch cycle.   We have an
> AWS
> >> presence as well but I’m not sure what size of pipe we have.   Thanks
> for
> >> your input and I look forward to hearing more about your PoC.
> >>
> >>
> >> On Fri, Jul 18, 2025 at 5:03 PM Jay Maynard <
> >> [email protected]> wrote:
> >>
> >>> The DR part is the part I'm most interested in, as well. The idea, they
> >>> tell me, is that you FTP your one-pack (or whatever) image to the DR
> >>> system, then IPL it, and it has the agent on it to do the restores.
> I'll
> >>> know more about how that works when I give it a try; the details seem a
> >> bit
> >>> scant.
> >>>
> >>> We're looking to save a big pile of money on the DLm and DD, since ours
> >> are
> >>> about to go out of service. I think it'll work for all that, but I'm
> not
> >>> going to hang my hat on it until we give it a try.
> >>>
> >>> We do have an institutionally large presence with AWS, and we'll be
> >>> using S3 for the backup storage; we have a nice fat pipe there, so
> >>> bandwidth shouldn't be an issue. You will need to pay attention to
> that,
> >>> though.
> >>>
> >>> I'm not expecting to be able to actually try it for another couple of
> >> weeks
> >>> at minimum, hopefully before SHARE in Cleveland. I'll post when I have
> >> some
> >>> results.
> >>>
> >>> On Fri, Jul 18, 2025 at 3:08 PM Michael Babcock <
> >>> [email protected]> wrote:
> >>>
> >>>> We’d be interested in anything you have to say about it.  We were
> >> pitched
> >>>> the product a day or two ago.     We already have DFSMSdss so
> shouldn’t
> >>>> have to worry about that part.   And we also wonder how that works
> with
> >>> DR.
> >>>>
> >>>>
> >>>> On Fri, Jul 18, 2025 at 12:55 PM Jay Maynard <
> >>>> [email protected]> wrote:
> >>>>
> >>>>> We are doing a proof of concept for that right now, as a potential
> >>>>> replacement for FDRABR, DLm, and DD. We haven't actually tried it
> >> yet -
> >>>>> still getting prerequisites done, one of which is a trial license for
> >>>>> DFSMSdss (which IBM is being slow about) - but we expect it to
> >>> completely
> >>>>> replace the DLm and DD, as well as FDRABR. It'll also replace
> >> DFDSSrmm
> >>>> (or
> >>>>> CA-1). AMI Cloud Data will also replace the DLm/DD for other tape
> >> uses,
> >>>>> like, for us, Adabas backups.
> >>>>>
> >>>>> I hope to actually run some tests sometime in the next few weeks.
> >>>>>
> >>>>> On Fri, Jul 18, 2025 at 9:40 AM Michael Babcock <
> >>>>> [email protected]> wrote:
> >>>>>
> >>>>>> Is anyone looking at BMC's AMI Cloud (or actively using it) to
> >>> replace
> >>>>>> Dell/EMC's DLM/DataDomains?   BMC bought Model9, now called BMC's
> >> AMI
> >>>>>> Cloud, and have been enhancing it.  Any experience or thoughts
> >> would
> >>> be
> >>>>>> greatly appreciated.
> >>>>>>
> >>>>>>
> >>> ----------------------------------------------------------------------
> >>>>>> For IBM-MAIN subscribe / signoff / archive access instructions,
> >>>>>> send email to [email protected] with the message: INFO
> >>> IBM-MAIN
> >>>>>>
> >>>>>
> >>>>>
> >>>>> --
> >>>>> Jay Maynard
> >>>>>
> >>>>>
> >> ----------------------------------------------------------------------
> >>>>> For IBM-MAIN subscribe / signoff / archive access instructions,
> >>>>> send email to [email protected] with the message: INFO
> >> IBM-MAIN
> >>>>>
> >>>>
> >>>> ----------------------------------------------------------------------
> >>>> For IBM-MAIN subscribe / signoff / archive access instructions,
> >>>> send email to [email protected] with the message: INFO
> IBM-MAIN
> >>>>
> >>>
> >>>
> >>> --
> >>> Jay Maynard
> >>>
> >>> ----------------------------------------------------------------------
> >>> For IBM-MAIN subscribe / signoff / archive access instructions,
> >>> send email to [email protected] with the message: INFO IBM-MAIN
> >>>
> >>
> >> ----------------------------------------------------------------------
> >> For IBM-MAIN subscribe / signoff / archive access instructions,
> >> send email to [email protected] with the message: INFO IBM-MAIN
> >>
> >
> >
> > --
> > Jay Maynard
> >
> > ----------------------------------------------------------------------
> > For IBM-MAIN subscribe / signoff / archive access instructions,
> > send email to [email protected] with the message: INFO IBM-MAIN
>
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions,
> send email to [email protected] with the message: INFO IBM-MAIN
>


-- 
Jay Maynard

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to