server.
> > I will have to use replication instead. Thanks for all your help!
> > Kind regards,
> > Eric van Loon
> > Air France/KLM Storage Engineering
> >
> > -Original Message-
> > From: Loon, Eric van (ITOPT3) - KLM
> > Sent: donderdag
t;> created in the past on the source server.
>> I will have to use replication instead. Thanks for all your help!
>> Kind regards,
>> Eric van Loon
>> Air France/KLM Storage Engineering
>>
>> -Original Message-
>> From: Loon, Eric van (ITOPT3) - K
van (ITOPT3) - KLM
> Sent: donderdag 30 november 2017 12:15
> To: ADSM-L@VM.MARIST.EDU
> Subject: RE: Moving archive data to a directory container
>
> Hi Marc,
> I didn't know you can convert a storagepool into an already existing
> containerpool, thanks. I think I will
gards,
Eric van Loon
Air France/KLM Storage Engineering
-Original Message-
From: Loon, Eric van (ITOPT3) - KLM
Sent: donderdag 30 november 2017 12:15
To: ADSM-L@VM.MARIST.EDU
Subject: RE: Moving archive data to a directory container
Hi Marc,
I didn't know you can convert a storagepool
2 AM
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Moving archive data to a directory container
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 will ex
Marc
Lanteigne
Sent: woensdag 29 november 2017 17:42
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Moving archive data to a directory container
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'
kerts
Sent: woensdag 29 november 2017 19:47
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Moving archive data to a directory container
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
p.com
>
>
> -Original Message-
> From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of
> Loon, Eric van (ITOPT3) - KLM
> Sent: Wednesday, November 29, 2017 10:01 AM
> To: ADSM-L@VM.MARIST.EDU
> Subject: [EXT SENDER] [ADSM-L] Moving archive data to a director
er 29, 2017 10:01 AM
To: ADSM-L@VM.MARIST.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
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
@klm.com
> ]
> Sent: Wednesday, November 29, 2017 12:18 PM
> To: ADSM-L@VM.MARIST.EDU
> 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. Switch
c van (ITOPT3) - KLM [mailto:eric-van.l...@klm.com]
Sent: Wednesday, November 29, 2017 12:18 PM
To: ADSM-L@VM.MARIST.EDU
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
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
13 matches
Mail list logo
