× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



First off understand what you are doing: (BTW there are typos in your examples... Are you just copying what you really use, if so there might be an issue..)

Option 21 is a full backup including the OS, a bare metal back up if you will.

Option 23 saves all user data (meaning your stuff) but none of IBM's. They are meant for different things although the 21 save could be used in place of a 23 save if needed since it has everything the 23 save has and more.

As to the restore question, that have a great deal to do with how you do the restore. I guarantee that Larry Bolhuis, Pete Massiello, and I will all wind up with the same result, but we might do it a bit differently, depending on the methods used.

In the end we need to know more about what you are trying to do, OS levels at each side, and things like, will the IP addresses change, has the target box been built and just waiting for the customer data, many questions like that? (Also, that's why you hire guys who do this for a living to help you with the once in three-year migration. Saves time, money and effort)




--
Jim Oberholtzer
Agile Technology Architects

-----Original Message-----
From: MIDRANGE-L <midrange-l-bounces@xxxxxxxxxxxxxxxxxx> On Behalf Of gio.cot via MIDRANGE-L
Sent: Wednesday, June 26, 2019 8:31 AM
To: 'Steinmetz, Paul' <PSteinmetz@xxxxxxxxxx>; 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: gio.cot <gio.cot@xxxxxxxxxxx>
Subject: R: Migration data to new IBM i

Hi
Thanks all for the reply
A thing that i don't understand ..

Option 21 (menu save) do this:
SAVSYS
SAVLIB LIB(*NONSYS) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT)
('/QDLS' *OMIT)) UPDHST(*YES)

Option 23 do this:
SAVSECDTA
SAVCFG
SAVLIB LIB(*ALLUSR) ACCPTH(*YES)
SAVDLO DLO(*ALL) FLR(*ANY)
SAV OBJ(('/*') ('/QSYS.LIB' *OMIT)
('/QIBM/ProData' *OMIT)
('/QDLS' *OMIT) UPDHST (*YES)
(QOpenSys/QIBM/ProdData' *OMIT)) UPDHST(*YES)

In 22 option OMIT QIBM QOpenSys .. the thing that i don't understand is if i use option 21 when i restore , how the system don't restore QIBM QOpenSys ecc ecc ?
Instead if i would use option 23, QIBM QOpenSys ecc ecc are not saved at the origin ..
Thanks



-----Messaggio originale-----
Da: Steinmetz, Paul [mailto:PSteinmetz@xxxxxxxxxx]
Inviato: mercoledì 26 giugno 2019 13:48
A: 'Midrange Systems Technical Discussion' <midrange-l@xxxxxxxxxxxxxxxxxx>
Cc: 'gio.cot' <gio.cot@xxxxxxxxxxx>
Oggetto: RE: Migration data to new IBM i

I recently completed a similar migration.
My thoughts were similar, but separating and only saving/restoring user data got way too complicated and risky.

Either
save 21 / restore 21
or
using BRMS
Full system save / then recover your system.

Paul

-----Original Message-----
From: MIDRANGE-L [mailto:midrange-l-bounces@xxxxxxxxxxxxxxxxxx] On Behalf Of gio.cot via MIDRANGE-L
Sent: Wednesday, June 26, 2019 7:39 AM
To: midrange-l@xxxxxxxxxxxxxxxxxx
Cc: gio.cot
Subject: Migration data to new IBM i

Hi all

Doe's some has got a guide to plan migration user data from an old IBM i to a new IBM i ? i have some doubt about save and restore USER IFS folder and files ; for the library i have not problem i can you use *ALLUSR parameter, but for the IFS object ? i can't save olny user folder/files .. or not

Thanks in advance

P.S. some time ago, i saw a redbook as guide to this operation .. can some have the title/link ?



---
Questa e-mail è stata controllata per individuare virus con Avast antivirus.
https://www.avast.com/antivirus
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: MIDRANGE-L@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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@xxxxxxxxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: https://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxxxxxxxx
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


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.