upgrade reference

[Ricky Nance]

It should also be noted that all your shares will need to be migrated
manually, and a lot of your old share options will not work. samba-tool
testparm should be helpful at that point.

On Wed, Jan 11, 2012 at 2:52 PM, Ricky Nance <
ricky.nance at weaubleau.k12.mo.us> wrote:

> It needs to be on the same machine, when you issue samba-tool domain
> samba3upgrade --dbdir=/var/lib/samba --targetdir=/usr/local/samba
> /etc/samba/smb.conf the dbdir is the old s3 files, the target dir is
> where it should put the s4 database, and finally you have your old s3
> smb.conf file. Unless you want to see a BUNCH of output make sure logging
> is off in your s3 config.
>
>
> On Wed, Jan 11, 2012 at 2:37 PM, Aaron E. <ssureshot at gmail.com> wrote:
>
>> Charles,
>>
>> I am running debian based flavor. I have samba4 / bind 9.8 build on my
>> test box working with a new provision which Ill blow away..
>>
>> Can it pull the information through a network or does everything have to
>> be installed on the same server?
>>
>> Essentialy all I would need to do is get ldap and samba functioning and
>> restore the database from my production box. Which shouldn't take too long
>> but I would rather not have to install what I won't need. I'm anal
>> retentive when it comes to installed packages in production..
>>
>>
>>
>>
>> On 01/11/2012 02:47 PM, Charles Tryon wrote:
>>
>>> I've had some success doing some test migrations, though I don't have all
>>> my pieces put together yet.
>>>
>>> Are you running on a Debian based system or a Red Hat (CentOS, Fedora,
>>> etc)
>>> based system?  There are obviously some package differences, as well as
>>> startup script differences.
>>>
>>> I am actually trying to do the conversion from one server to another,
>>> which
>>> presents some different challenges.  For one thing, I still have a load
>>> of
>>> other services on the old server that I can't get rid of right away.
>>>  Also,
>>> that box is pretty suck on packages from several years ago, which is why
>>> it's still running Samba 3.0.9!!
>>>
>>> In my case, I do NOT have an LDAP server, so I am pulling from a tdb
>>> database for my users.  I wouldn't say this is better or worse than LDAP,
>>> but it does mean you do things a little differently.
>>>
>>> I've found that I can copy my /etc/samba and /usr/lib/samba directories
>>> from my production server to the new test server and then run the
>>> conversion.
>>>
>>>
>>>
>>>
>>>
>>> On Wed, Jan 11, 2012 at 1:12 PM, Aaron E.<ssureshot at gmail.com>  wrote:
>>>
>>>  I'm finally getting back to some testing now that EOY is over. The last
>>>> I
>>>> worked with upgrade testing was running the myldap.py upgrade script, I
>>>> have seen that the samba-tool can now provide an upgrade path and I'd
>>>> like
>>>> to run some tests.
>>>>
>>>> I'm looking for information to read up on using this tool.
>>>>
>>>> I currently have an s3 domain with an openldap backend. When I run
>>>> samba-tool ? I don't seem to see anything relevant to an upgrade. This
>>>> is
>>>> the latest git as of a week ago.
>>>>
>>>> Any reading material is greatly appriciated along with examples if you
>>>> have them.
>>>>
>>>> Thanks
>>>> Aaron
>>>>
>>>>
>>>>
>>>
>>>
>>
>
>
> --
>
>
>


--