Topic: Problem with customizing backuptodesktop script

[kam]

Hello,
I've read a lot about backup to desktop and 2gb limit, but this didn't help me
So, I customized the backup script to work from command-line and it creates an tgz archive on e-smith server box. I launch it from crontab. But it works only with files smaller than 2gb. If the archive is bigger, crontab errorlog reports samba limit exceeded (Sorry, now I can't write exact error message reported). I can't understand what is the problem. I use SME 5.6 (which uses ext3 and supports BBBIIIGGGG files). Maybe somewhere SME has config parameter which limits the filesize.....

Thank you in advance.

[kam]

The error message is exactly:
8320 File size limit exceeded

[Ray Mitchell]

If you search on backup (all dates) and backup2ws you should find a lot of references to this issue.
Even though ext3 supports BIGGG files, this large file support does not help you when doing compressed backups using rar & samba. There is some inherent limitation in how samba handles tgz files (or something similar to that) and that is where the 2Gb problem arises.
You will still have the 2Gb backup size limit problem even using sme v5.6.

Why don't you take the easy way out and use Darrell May's excellent backup2ws, this already has built in support for splitting the backup file into chunks less than 2Gb (as specified by the user). see contribs.org
Just watch out if you want to do a restore from the 911 job there is a bug that needs manual overide to fix it see
http://forums.contribs.org/index.php?topic=17397.msg67749#msg67749

Hope this helps
Ray

[kam]

I just would like to know (if somebody knows) is there any parameter   set to limit filesize and who reads it (tar, gzip, perl's open func, some e-smith lib func,...) so gzip stopped at 2gb. Yes, I read about backup2ws, but I want to do my backups into a sigle file into second hard drive on my SME server box. My archive files saved on ext3 fs, which supports big files (ulimit said unlimited size), into a dir, which isn't samba shared dir, so I think there is config option for this limitation.
Feel free to don't get me an answer, do it just if somebody have a workaround.

Thanks.