[gpfsug-discuss] Migrate 3.5 to 4.2 and LTFSEE toSpectrumArchive

Yaron Daniel YARD at il.ibm.com
Thu Aug 18 04:56:50 BST 2016


So - the procedure you are asking related to Samba.
Please check at redhat Site the process of upgrade Samba - u will need to 
backup the tdb files and restore them.

But pay attention that the Samba ids will remain the same after moving to 
CES - please review the Authentication Section.

 
Regards
 


 
 
Yaron Daniel
 94 Em Ha'Moshavot Rd

Server, Storage and Data Services - Team Leader  
 Petach Tiqva, 49527
Global Technology Services
 Israel
Phone:
+972-3-916-5672
 
 
Fax:
+972-3-916-5672
 
 
Mobile:
+972-52-8395593
 
 
e-mail:
yard at il.ibm.com
 
 
IBM Israel
 
 
 
 

 



From:   Shaun Anderson <SAnderson at convergeone.com>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   08/18/2016 04:52 AM
Subject:        Re: [gpfsug-discuss] Migrate 3.5 to 4.2 and LTFSEE to 
Spectrum        Archive
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



​We are currently running samba on the 3.5 node, but wanting to migrate 
everything into using CES once we get everything up to 4.2.


SHAUN ANDERSON
STORAGE ARCHITECT
O 208.577.2112
M 214.263.7014



From: gpfsug-discuss-bounces at spectrumscale.org 
<gpfsug-discuss-bounces at spectrumscale.org> on behalf of Yaron Daniel 
<YARD at il.ibm.com>
Sent: Wednesday, August 17, 2016 5:11 PM
To: gpfsug main discussion list
Subject: Re: [gpfsug-discuss] Migrate 3.5 to 4.2 and LTFSEE to Spectrum 
Archive 
 
Hi

Do u use CES protocols nodes ? Or Samba on each of the Server ?

  
Regards
 


 
 
Yaron Daniel
 94 Em Ha'Moshavot Rd

Server, Storage and Data Services- Team Leader 
 Petach Tiqva, 49527
Global Technology Services
 Israel
Phone:
+972-3-916-5672
 
 
Fax:
+972-3-916-5672
 
 
Mobile:
+972-52-8395593
 
 
e-mail:
yard at il.ibm.com
 
 
IBM Israel
 
 
 
 

 



From:        Shaun Anderson <SAnderson at convergeone.com>
To:        "gpfsug-discuss at spectrumscale.org" 
<gpfsug-discuss at spectrumscale.org>
Date:        08/18/2016 12:11 AM
Subject:        [gpfsug-discuss] Migrate 3.5 to 4.2 and LTFSEE to Spectrum 
Archive
Sent by:        gpfsug-discuss-bounces at spectrumscale.org



​I am in process of migrating from 3.5 to 4.2 and LTFSEE to Spectrum 
Archive.
 
1 node cluster (currently) connected to V3700 storage and TS4500 backend. 
We have upgraded their 2nd node to 4.2 and have successfully tested 
joining the domain, created smb shares, and validated their ability to 
access and control permissions on those shares. 
They are using .tdb backend for id mapping on their current server. 
 
I'm looking to discuss with someone the best method of migrating those tdb 
databases to the second server, or understand how Spectrum Scale does id 
mapping and where it stores that information.

Any hints would be greatly appreciated.
 
Regards,
 
SHAUN ANDERSON
STORAGE ARCHITECT
O208.577.2112
M214.263.7014

       
  


NOTICE:  This email message and any attachments here to may contain 
confidential
information.  Any unauthorized review, use, disclosure, or distribution of 
such
information is prohibited.  If you are not the intended recipient, please
contact
the sender by reply email and destroy the original message and all copies 
of it._______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss



NOTICE:  This email message and any attachments here to may contain 
confidential
information.  Any unauthorized review, use, disclosure, or distribution of 
such
information is prohibited.  If you are not the intended recipient, please
contact
the sender by reply email and destroy the original message and all copies 
of it._______________________________________________
gpfsug-discuss mailing list
gpfsug-discuss at spectrumscale.org
http://gpfsug.org/mailman/listinfo/gpfsug-discuss




-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0002.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0004.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/gif
Size: 1851 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0005.gif>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 14134 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0006.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/jpeg
Size: 2593 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0002.jpe>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11635 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0007.png>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Type: image/png
Size: 11505 bytes
Desc: not available
URL: <http://gpfsug.org/pipermail/gpfsug-discuss_gpfsug.org/attachments/20160818/4c0cbb06/attachment-0008.png>


More information about the gpfsug-discuss mailing list