[gpfsug-discuss] ESS GL2 data to new ESS3500

[Wahl, Edward]

If you are wanting seamless: Create a new pool in your existing file system, a new placement policy, and a use a movement policy to move the old data between the pools.  The new placement policy will ensure new data is only written to the new location.
Then when the old GL2 pool is empty you can remove it/offline it/whatever.

Ed Wahl
Ohio Supercomputer Center

From: gpfsug-discuss <gpfsug-discuss-bounces at gpfsug.org> On Behalf Of Walter Sklenka
Sent: Thursday, June 13, 2024 3:37 AM
To: gpfsug-discuss at gpfsug.org
Subject: Re: [gpfsug-discuss] ESS GL2 data to new ESS3500

Hi ! We want to migrate data from an old ESS GL2 ( 5. 0. 5 ) to ESS3500 solution. (5. 1. x) I wanted to ask is there any way to migrate the data with gpfs methods? We heard that you cannot create a rg on an ess3500 when it´s nodes become member

Hi !
We want to migrate data from an old ESS GL2  ( 5.0.5 ) to ESS3500 solution. (5.1.x)
I wanted to ask is there any way to migrate the data with gpfs methods?
We heard that you cannot create a rg on an ess3500 when it´s nodes become  member of the old cluster because of GNR Version mismatch
I thought I can create new rg on ess3500  , create vdisksets and nsds , then add the disks to a filesystem based on vdisks of old rgs
I there really no way to transfer with gpfs methods? (like mmadddisk (new vdisks(nsds)  of 3500  , and then mmdeldisk the old nsds(vdisks)
So if you run into this situation you have to create a new cluster?









Mit freundlichen Grüßen
Walter Sklenka
Technical Consultant

EDV-Design Informationstechnologie GmbH
Giefinggasse 6/1/2, A-1210 Wien
Tel: +43 1 29 22 165-31
Fax: +43 1 29 22 165-90
E-Mail: sklenka at edv-design.at<mailto:sklenka at edv-design.at>
Internet: www.edv-design.at<https://urldefense.com/v3/__http:/www.edv-design.at/__;!!KGKeukY!xkRcZsb39z7b8HmphS6na-u1wA0kFpCfi5vYypCr8U5tcLA4e3itM_uAi5dOwO9eMYqOQLLR1glrjk4XgBfFZEi-Pa5e$>

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20240613/dc0b8480/attachment.htm>