RE: Moving large libraries to another system:

sounds like someone needs to breakup a library if they can....



On Fri, 11 Jan 2002 barsa@barsaconsulting.com wrote:

>
> Object connect doesn't work well with large objects.  Also, under the
> covers it makes two additional copies of the object/libraries/etc. being
> moved.  The first copy is the internal save file, the second occurs when
> the save file is replicated to the other system.
>
> Al
>
> Al Barsa, Jr.
> Barsa Consulting Group, LLC
>
> 400>390
>
> 914-251-1234
> 914-251-9406 fax
>
> http://www.barsaconsulting.com
> http://www.taatool.com
>
>
>
>
>
>
>                     Chris Whisonant
>                     <chris.whisonant@comp       To:     
>midrange-l@midrange.com
>                     orium.com>                  cc:
>                     Sent by:                    Subject:     RE: Moving large 
>libraries to another system:
>                     midrange-l-admin@midr
>                     ange.com
>
>
>                     01/11/02 04:57 PM
>                     Please respond to
>                     midrange-l
>
>
>
>
>
>
> Would SAVRSTLIB work in your situation?
>
> "The SAVRSTLIB command saves and restores the entire library; this
> includes the library description, the object descriptions, and the
> contents of the objects in the library.  For job queues, message
> queues, output queues, data queues, and logical files, only the
> object definitions are saved and restored, not the contents.
> Logical file access paths can be saved and restored by specifying
> ACCPTH(*YES).  The contents of a save file can be saved by using the
> Save Save File Data (SAVSAVFDTA) command.  By specifying
> SAVFDTA(*YES) on the SAVRSTLIB command, the contents of a save file
> can be saved and restored." (From the online help for savrstlib command.)
>
> -----Original Message-----
> From: midrange-l-admin@midrange.com
> [mailto:midrange-l-admin@midrange.com]On Behalf Of Matt Patee
> Sent: Friday, January 11, 2002 4:47 PM
> To: midrange-l@midrange.com
> Subject: Moving large libraries to another system:
>
>
>
> I looked in the archives and did not find anything very apparent. I would
> appreciate any suggestions:
>
> Without using tape (don't ask), what is the best way to transfer a large
> library (40gb) from one system to another? It doesn't have to be fast, but
> I need it to not affect the performance of my production system (where I'm
> sending from).
>
> I tried FTP, but it ended up slowing the production box. Any help would be
> appreciated.
>
>
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~
> Matthew Patee
> Midrange Systems Manager
> ABM Industries
> (415) 351-4309
> fax:(415) 351-4331
>
> _______________________________________________
> 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.
>
> _______________________________________________
> 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.
>
>
>
>
>
> _______________________________________________
> 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.
>