[Samba] Upgrading system on file server
Bayardo Rivas - Open Soluciones
bayardo.rivas at opensoluciones.com
Thu Mar 17 12:25:34 MDT 2011
I am using LDAP, we still auth with /etc/passwd and /etc/shadow.
We need to upgrade Suse, we were upgrading only Samba but now it's a
must to upgrade Suse for other reasons.
Why do i have to backup "private" and "lock" directories??
El 17/03/2011 12:16 p.m., Gaiseric Vandal escribió:
> You should build a 2nd box with Suse 11.3- you can configure it as a
> DC either in same or test domain to make sure it works OK. If you
> have LDAP as a backend, configure a BDC is possible.
> Is the purpose of the upgrade to upgrade Suse or to upgrade Samba? if
> you just want to upgrade samba you may wish to compile from source?
> Run testparm -v to see the location of your private directory and
> locks directory. make sure those directories are backed up.
> I would also backup /etc/passwd and /etc/shadow file (maybe the whole
> /etc directory.)
> On 03/17/2011 01:45 PM, Bayardo Rivas - Open Soluciones wrote:
>> I have an old version of Suse runing a Samba. I will upgrade this box
>> from Suse 9.3 -> Suse 11.3. I know that there are a lot of risk but
>> my top fear is about Samba. This is a production server and network
>> users authenticate with this server. We do not have roaming profile,
>> but I know that if I install from scratch I lose my domain, SID
>> number changes and I have to reconfigure all the clients and this is
>> not an option.
>> So, I will try to upgrade the box with the installation disks, but
>> if I get problems and I am forced to install from scratch, what do I
>> have to do to keep my domain working and don't lose the conection
>> between the domain and clients and keep it transparent for clients?/
>> Any suggestions are welcome.
More information about the samba