[gpfsug-discuss] A net new cluster

[Christopher Black]

I was under the impression that AFM could not move between filesystems in the same cluster without going through NFS, but perhaps that is outdated. We’ve only used it in the past to move data between clusters. Could someone with more experience with AFM within a cluster comment? Our goal is to keep the same namespace/path for the users (and ideally keep the same filesystem name) by switching all clients to point to new cluster after a subset of (active) data had been migrated.

Best,
Chris

From: <gpfsug-discuss-bounces at spectrumscale.org> on behalf of Marc A Kaplan <makaplan at us.ibm.com>
Reply-To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date: Friday, March 29, 2019 at 3:05 PM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] A net new cluster

I don't know the particulars of the case in question, nor much about ESS rules...
But for a vanilla Spectrum Scale cluster -.

1) There is nothing wrong or ill-advised about upgrading software and then creating a new version 5.x file system... keeping any older file systems in place.

2) I thought AFM was improved years ago to support GPFS native access -- need not go through NFS stack...?

Whereas your wrote:

 ... nor is it advisable to try to create a new pool or filesystem in same cluster and then migrate (partially because migrating between filesystems within a cluster with afm would require going through nfs stack afaik) ...






________________________________
This message is for the recipient’s use only, and may contain confidential, privileged or protected information. Any unauthorized use or dissemination of this communication is prohibited. If you received this message in error, please immediately notify the sender and destroy all copies of this message. The recipient should check this email and any attachments for the presence of viruses, as we accept no liability for any damage caused by any virus transmitted by this email.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20190329/a449eea2/attachment-0002.htm>