That's a way to do it, you do need to reduce max and offline reorg the
database after the conversion to get everything to run at 100% speed
without wasted database space after the conversion
I prefer to upgrade the old server to 7.1.7 and replicate the data from
tape/VTL/whatever to the new server running the containerpool, it works
much beter than an export in my opinion, you have more control and it's
much faster.
If an upgrade isn't an option I would export to a filepool as Matthew
suggested and convert that to a containerpool, be sure you have enough
database space to hold the filepool metadata since it's about twice as much
as the containerpool data and when you convert you need space for both
types of metadata until you do your reorg and reduce max. Oh, you can
reduce max at certain points during the conversion to reclaim some slack
space on the database.
On Wed, Nov 29, 2017 at 6:40 PM, Matthew McGeary <
Matthew.McGeary AT potashcorp DOT com> wrote:
> Node replication would be the only real way to go directly to the
> container pool.
>
> You could define the file-class pool on the same storage directories as
> the new container pool, so that once you land everything and convert, you
> have two pools but don't waste any storage.
>
> __________________________
> Matthew McGeary
> Senior Technical Specialist - Infrastructure Management Services
> PotashCorp
> T: (306) 933-8921
> www.potashcorp.com
>
>
> -----Original Message-----
> From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf
> Of
> Loon, Eric van (ITOPT3) - KLM
> Sent: Wednesday, November 29, 2017 10:01 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: [EXT SENDER] [ADSM-L] Moving archive data to a directory container
>
> Hi guys!
> We are migrating our clients from a version 6 server to a new 7.1.7 server
> with a directory container pool. Switching clients is easy, just updating
> the option files and they will start a new backup cycle on the new TSM
> server. But a lot of clients also store long term archives. I can't think
> of a way to move the archives from the v6 server to the v7 server since
> import is not supported to a directory pool. The only trick I can come up
> with is defining a file pool on the v7 server, moving all archives in here
> and converting it to a directory container afterwards, but I need extra
> storage for it and I end up with two directory pools (at least until all
> archives are gone) and that is not what I want...
> Does anybody else know some trick to move these archives?
> Thanks for any help in advance!
> Kind regards,
> Eric van Loon
> Air France/KLM Storage Engineering
>
> ********************************************************
> For information, services and offers, please visit our web site:
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.klm.
> com&d=DwIFAg&c=tBK9IFHToo3Ip4kInV6npfSphg9iMZSnuvLLtDL_h5E&r=
> 9B53f9OJCAaZMdwQs8Rx4OInzZ1vusLF8Ft4jfrywjo&m=S9QLT9cTnOfkB2BTaZyDF_
> kGAtfzMnQibS2mOIu3TwA&s=rv0g65y9vujKE7SdQFc7zspq6wHCYNRQ94RdB4lUYFE&e=.
> This e-mail and any attachment may contain confidential and privileged
> material intended for the addressee only. If you are not the addressee, you
> are notified that no part of the e-mail or any attachment may be disclosed,
> copied or distributed, and that any other action related to this e-mail or
> attachment is strictly prohibited, and may be unlawful. If you have
> received this e-mail by error, please notify the sender immediately by
> return e-mail, and delete this message.
>
> Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its
> employees shall not be liable for the incorrect or incomplete transmission
> of this e-mail or any attachments, nor responsible for any delay in receipt.
> Koninklijke Luchtvaart Maatschappij N.V. (also known as KLM Royal Dutch
> Airlines) is registered in Amstelveen, The Netherlands, with registered
> number 33014286
> ********************************************************
>
|
