Mail Archive Search: <+subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Moving\s+archive\s+data\s+to\s+a\s+directory\s+container\s*$/>

Results:

References: [ +subject:/^(?:^\s*(re|sv|fwd|fw)[\[\]\d]*[:>-]+\s*)*\[ADSM\-L\]\s+Moving\s+archive\s+data\s+to\s+a\s+directory\s+container\s*$/: 13 ]

Total 13 documents matching your query.

1. [ADSM-L] Moving archive data to a directory container (score: 1): Author: "Loon, Eric van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>; Date: Wed, 29 Nov 2017 16:00:50 +0000; 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 ne; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00082.html (10,871 bytes)
2. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Marc Lanteigne <marclanteigne AT CA.IBM DOT COM>; Date: Wed, 29 Nov 2017 16:41:43 +0000; 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,; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00083.html (11,793 bytes)
3. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Chavdar Cholev <chavdar.cholev AT GMAIL DOT COM>; Date: Wed, 29 Nov 2017 19:10:46 +0200; create server to sever comm and export import node... it should work.... hth Chavdar On Wednesday, November 29, 2017, Marc Lanteigne <marclanteigne AT ca.ibm DOT wrote:; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00084.html (13,621 bytes)
4. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Marc Lanteigne <marclanteigne AT CA.IBM DOT COM>; Date: Wed, 29 Nov 2017 17:24:23 +0000; Not to a directory container pool, only to a traditional pool. - Thanks, Marc... ________________________________________________________ Marc Lanteigne Accelerated Value Specialist for Spectrum Prot; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00085.html (13,938 bytes)
5. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Matthew McGeary <Matthew.McGeary AT POTASHCORP DOT COM>; Date: Wed, 29 Nov 2017 17:40:06 +0000; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00086.html (12,493 bytes)
6. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>; Date: Wed, 29 Nov 2017 19:46:35 +0100; 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; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00087.html (14,182 bytes)
7. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: "Loon, Eric van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>; Date: Thu, 30 Nov 2017 10:52:17 +0000; Hi Stefan! In my case I can't upgrade the old source server since it's running a too old RedHat release... Kind regards, Eric van Loon Air France/KLM Storage Engineering That's a way to do it, you do; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00088.html (16,553 bytes)
8. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: "Loon, Eric van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>; Date: Thu, 30 Nov 2017 11:15:13 +0000; Hi Marc, I didn't know you can convert a storagepool into an already existing containerpool, thanks. I think I will remove some directories from the containerpool to make room for a new filepool. I w; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00089.html (15,016 bytes)
9. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Marc Lanteigne <marclanteigne AT CA.IBM DOT COM>; Date: Thu, 30 Nov 2017 12:10:52 +0000; Hi Eric, I'd look into the replication first though. It 'should' work going from 6.3 to 7.1 (the other direction would not). Try with a small test node. - Thanks, Marc... ____________________________; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-11/msg00090.html (15,956 bytes)
10. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: "Loon, Eric van (ITOPT3) - KLM" <Eric-van.Loon AT KLM DOT COM>; Date: Thu, 7 Dec 2017 10:27:58 +0000; Hi guys, Just to let you know: the trick to export to a file pool and convert it afterwards won't work... You cannot specify a different storagepool in the export node command, so the export will go; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-12/msg00008.html (14,459 bytes)
11. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Thu, 7 Dec 2017 15:04:35 +0100; Hi Eric, 1- on the target copy the domain, change copygroup destinations to filepool, act poli 2- on the target, reg node on the copied dom 3- export node filed=whatever replacedefs=n merge=yes 4- on; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-12/msg00009.html (16,670 bytes)
12. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Remco Post <r.post AT PLCS DOT NL>; Date: Thu, 7 Dec 2017 18:29:29 +0100; ps, if you receive some data during the import, it will get in the container pool with the conversion -- Met vriendelijke groeten/Kind Regards, Remco Post r.post AT plcs DOT nl +31 6 248 21 622; /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-12/msg00010.html (17,874 bytes)
13. Re: [ADSM-L] Moving archive data to a directory container (score: 1): Author: Stefan Folkerts <stefan.folkerts AT GMAIL DOT COM>; Date: Sun, 10 Dec 2017 09:36:51 +0100; Yup, that's the trick, it seems Remco and I wear the same t-shirt. :-); /usr/local/webapp/mharc-adsm.org/html/ADSM-L/2017-12/msg00011.html (17,618 bytes)

Current List: 1 - 13
Page: [1]