Upgrading from S4-alpha12

[Matthieu Patou]

On 03/06/2012 10:13 AM, titantoppler at gmail.com wrote:
> Hi list,
>
> I'm attempting to upgrade from my (very old) installation of S4 alpha 12,
> to the current build of S4.
>
> After pulling down the latest source and compiling+installing, I'm doing
> the 'upgradeprovision --full' step to upgrade the database.
>
> However, I'm running out of space. Upon further investigation, I realised
> that this step seemed to be copying the 'sysvol' folder to a
> /usr/local/samba/private/backupprovision(some-random-letters). Since my
> users' data files are really huge, doing so fills out my hard disk really
> quickly.
>
> Why is this happening (meaning the need to copy the files) - I had thought
> the provisioning step would be upgrading the database only, without
> touching my files? Is there a way around that?
Because upgradeprovision is also changing acl on the sysvol part as they 
used to be very broken.

Try the attached patch and run with --db_backup_only, it should do just 
the backup of the DBs, If you have still issues try with --nontaclfix.

Matthieu

-- 
Matthieu Patou
Samba Team
http://samba.org

-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-s4-upgradeprovision-Add-options-to-do-a-DB-backup-on.patch
Type: text/x-patch
Size: 4918 bytes
Desc: not available
URL: <http://lists.samba.org/pipermail/samba-technical/attachments/20120306/9f2e56b7/attachment.bin>