Not to a directory container pool, only to a traditional pool. - Thanks, Marc... ________________________________________________________ Marc Lanteigne Accelerated Value Specialist for Spectrum Protect 416.478.0233 | marclantei...@ca.ibm.com Office Hours: Monday to Friday, 7:00 to 16:00 Eastern
Follow me on: Twitter, developerWorks, LinkedIn -----Original Message----- From: Chavdar Cholev [mailto:chavdar.cho...@gmail.com] Sent: Wednesday, November 29, 2017 1:18 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Moving archive data to a directory container create server to sever comm and export import node... it should work.... hth Chavdar On Wednesday, November 29, 2017, Marc Lanteigne <marclantei...@ca.ibm.com> wrote: > Hi, > > You might be able to use node replication to move the data from the > old server into the new server. > > If you go with the import into a filepool method, you don't need two > directory container pools, you can convert the filepool into the > existing container pool. > - > Thanks, > Marc... > ________________________________________________________ > Marc Lanteigne > Accelerated Value Specialist for Spectrum Protect > 416.478.0233 | marclantei...@ca.ibm.com <javascript:;> Office Hours: > Monday to Friday, 7:00 to 16:00 Eastern > > Follow me on: Twitter, developerWorks, LinkedIn > > > -----Original Message----- > From: Loon, Eric van (ITOPT3) - KLM [mailto:eric-van.l...@klm.com > <javascript:;>] > Sent: Wednesday, November 29, 2017 12:18 PM > To: ADSM-L@VM.MARIST.EDU <javascript:;> > Subject: [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=jf_iaSHvJObTbx-siA1ZOg&r=hMBqtRSV0jXgOdXEmlNk_- > O9LHkPCGSh9PJBRSlL8Q4&m=MHcroyMTlfnvImqh8Xh27U_KSsiOrHx1DbJnIMM3kLo&s= > 7tfcdgEk2ax4u5oKCXjTNUIys5evvzyXrdwJ2_hzr0o&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 > ******************************************************** >
