|
Bryan& all.. The M36 area is limited to 4GB anyway, the problem is , the remote 170 is a larger box, and itself supports a remote site using remote outq's and tcp. An entire backup on the 170 takes about 3 reels, I can backup the 150 on only 1. The thought was to ship the 150 quickly to the 170 site in the event of a disaster, restore the M36, and any M36 cnfigs, but the result would only yield a stand alone M36 that supported only the 1 site, and not it's remote branch. Here is where one gets into device descriptions, outq configs...etc, so the exercise would be quite time consuming, and I don't believe would mirror the production machine. Incidentally, M36 doesn't use journalling as somebody suggested remote journalling. Apart from the 170's remote site, (data can be batch processed), and assuming the M36 objects can be restored to the 150, what oter pointers can you think of? I mentioned the fact that the 150 seemed a bit sluggish in comparison to the 170, any ideas.... Thanks Ken bdietz@3x.com wrote: > > If I read this right you are just using the *M36 on both boxes?? Since the > *M36 comprises just a couple of OS/400 objects, a config and the machine, > it should be easy to put the *M36 on the 150. You would have to load the > supporting license program and then restore the *M36 objects. I can > envision problems with communication lines, twinax, and maybe tape. And a > biggie, does the 150 have the disk available to hold the *M36 objects?? > > ------------------------- > Bryan Dietz > 3X Corporation > > ------------------------------------------------- > Have a development box V4R4 150, and a production box 170, at same > level, different ptf levels. > Question: > How feasible is it, in your estimation, to have the 150 back-up > the > 170, as a recovery move. > The 150 seems a bit sluggish, but keep in mind, the only active > parts > are M36. > What might the recovery steps be? > My guts tell me, a contract with an outside backup machine might > be the > better move. > Ken > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-L-request@midrange.com > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. -- Best Regards Ken Shields Home phone: 905 404-2062 Bus phone 905 725-1144 (326)
As an Amazon Associate we earn from qualifying purchases.
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.