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

Shaun Anderson SAnderson at convergeone.com
Thu Aug 18 19:11:02 BST 2016


Correct.  We are upgrading their existing configuration and want to switch to CES provided Samba.  

They are using Samba 3.6.24 currently on RHEL 6.6.  

Here is the head of the smb.conf file:
===================================================
[global]

   workgroup = SL1
   netbios name = SLTLTFSEE
   server string = LTFSEE Server
   realm = removed.ORG
   security = ads
   encrypt passwords = yes
   default = global
   browseable = no
   socket options = TCP_NODELAY SO_KEEPALIVE TCP_KEEPCNT=4 TCP_KEEPIDLE=240 TCP_KEEPINTVL=15
   idmap config * : backend = tdb
   idmap config * : range = 1000000-9000000
   template shell = /bash/bin
   writable = yes
   allow trusted domains = yes
   client ntlmv2 auth = yes
   auth methods = guest sam winbind
   passdb backend = tdbsam
   groupdb:backend = tdb
   interfaces = eth1 lo
   username map = /etc/samba/smbusers
   map to guest = bad uid
   guest account = nobody
=====================================================

Does that make sense?


Regards,

SHAUN ANDERSON
STORAGE ARCHITECT
O 208.577.2112
M 214.263.7014

       

-----Original Message-----
From: gpfsug-discuss-bounces at spectrumscale.org [mailto:gpfsug-discuss-bounces at spectrumscale.org] On Behalf Of Christof Schmitt
Sent: Thursday, August 18, 2016 11:50 AM
To: gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Subject: Re: [gpfsug-discuss] Migrate 3.5 to 4.2 and LTFSEE toSpectrumArchive

Samba as supported in Spectrum Scale uses the "autorid" module for creating internal id mappings (see man idmap_autorid for some details).

Officially supported are also methods to retrieve id mappings from an external server: 
https://www.ibm.com/support/knowledgecenter/en/STXKQY_4.2.1/com.ibm.spectrum.scale.v4r21.doc/bl1adm_adfofile.htm

The earlier email states that they have a " .tdb backend for id mapping on their current server. ". How exactly is that configured in Samba? Which Samba version is used here?

So the plan is to upgrade the cluster, and then switch to the Samba version provided with CES? Should the same id mappings be used?

Regards,

Christof Schmitt || IBM || Spectrum Scale Development || Tucson, AZ
christof.schmitt at us.ibm.com  ||  +1-520-799-2469    (T/L: 321-2469)



From:   Shaun Anderson <SAnderson at convergeone.com>
To:     gpfsug main discussion list <gpfsug-discuss at spectrumscale.org>
Date:   08/17/2016 06:52 PM
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




_______________________________________________
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.


More information about the gpfsug-discuss mailing list