Re: Fwd: Saving a *SAVF to another LPAR

We have a tool based on backups and remote journals.
It's more a continuous backup than a replication, but works

El jue., 13 de dic. de 2018 06:15, Rob Berendt<rob@xxxxxxxxx> escribió:

Bruce,
I thought of researching and posting those same two APIs. Thank you.

This is what really opened my eyes to the difference between the SAVRST*
commands and the use of save files.


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: "Bruce Vining"<bruce.vining@xxxxxxxxx>
To: "Midrange Systems Technical Discussion"<midrange-l@xxxxxxxxxxxx>
Date: 12/12/2018 05:26 PM
Subject: Fwd: Saving a *SAVF to another LPAR
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx>



---------- Forwarded message ---------
From: Bruce Vining<bruce.vining@xxxxxxxxx>
Date: Wed, Dec 12, 2018 at 4:24 PM
Subject: Re: Saving a *SAVF to another LPAR
To: Midrange Systems Technical Discussion<midrange-l@xxxxxxxxxxxx>


I'm not sure about the reference to "uses special APIs". I would assume
they're using the Save to Application (QaneSava)
<

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/apis/QaneSava.htm

and Restore from Application (QaneRsta)
<

https://www.ibm.com/support/knowledgecenter/en/ssw_ibm_i_73/apis/QaneRsta.htm

system
APIs.

Bruce

On Wed, Dec 12, 2018 at 1:33 PM Rob Berendt<rob@xxxxxxxxx> wrote:

To expand on this further...
The SAVRST... genre of commands do NOT save the entire object before
starting the restore on the other system. It uses special APIs to save
NOT to any device (save file or otherwise). Instead it saves to an API.
This API captures a chunk and sends over right away to the other system
and starts the restore.
This way, neither the source, nor the object system, have any space tied
up in save files to transmit data.


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: "Mark Waterbury"<mark.s.waterbury@xxxxxxxxxxxxx>
To: "Midrange Systems Technical Discussion"

<midrange-l@xxxxxxxxxxxx>

Date: 12/12/2018 02:25 PM
Subject: Re: Saving a *SAVF to another LPAR
Sent by: "MIDRANGE-L"<midrange-l-bounces@xxxxxxxxxxxx>



Jerry,
You could install and configure Enterprise Extender, an optional part of
IBM i OS and then you could use SAVRSTLIB, SAVRSTOBJ, or SAVRST etc. to
save and restore libraries, objects, etc. directly without having to

first

save everything into a save file.
Hope that helps,
Mark S. Waterbury

On Wednesday, December 12, 2018, 1:50:48 PM EST, Jerry Draper
<midrangel@xxxxxxxxxxxxx> wrote:

How can this be accomplished?

We want to refresh some libs on another LPAR nightly but we don't have
enough disk space to do this on the current system.

Jerry


--
Jerry Draper, Trilobyte Software Systems, since 1976
IBMi, Network, and Connectivity Specialists, LAN/WAN/VPN
Representing WinTronix, Synapse, HiT, and others .....
(415) 457-3431 opt-1 . www.trilosoft.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com

--
Thanks and Regards,
Bruce
931-505-1915



--
Thanks and Regards,
Bruce
931-505-1915
--
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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.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: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at https://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: https://amazon.midrange.com