Backup Sizes - Fixed?

[Robert141]

Hi All,

I hope you can help.

We have been using SurgarCRM Community Edition now for 3 years -- approx 5 users sending emails with plenty of attachments. The system is updated as and when updates are released.

I am starting to get somewhat concerned about back ups. Despite the years of use and additional content being added daily, the back up has remained constant at 2,097,152kb.

I currently initiate the back up from a remote client and then transfer the file to a removable drive. The backup takes around 20-30mins to complete.

I have recently tried to run the back up direct from the Linux server where Sugar resides to see if there was any difference. The file size seems to steadily climbs upto 2,097,152kb and then resets to zero after which the process repeats. I left this running for 4 hours -- it didnt stop or break the cycle.

Is this a sugar related issue or perhaps something to do with the server its on?

Thank you in advance for your help!

Rob

[sts]

For SugarCRM backups on Linux you could use a shell script like this:

#!/bin/bash
#
#
mkdir -p /root/backup
WOTAG=`date +%a`

rsync -az --delete --delete-after /var/www/sugar /root/backup

cd /root/backup
mysqldump -AaCceQ -usugarcrm -p*********** -R -r mysql.sql

tar cjf /backup/sugar.$WOTAG.tar.bz2 sugar
tar cjf /backup/mysql.$WOTAG.tar.bz2 mysql.sql

This should be called via cron job at least daily and creates two files (one for database contents and one for sugar directory) that should be copied/moved to another disk or server.

[Robert141]

Hi Stefan,

Thanks for your prompt reply. I have tried what you have suggested and I get the below back.

Any ideas?

Rob

--
rsync: link_stat "/var/www/sugar" failed: No such file or directory (2)
rsync error: some files could not be transferred (code 23) at main.c(977) [sender=2.6.9]
./sugarbackup: line 10: mysqldump: command not found
tar: /backup/sugar.Fri.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: sugar: Cannot stat: No such file or directory
tar: /backup/mysql.Fri.tar.bz2: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
tar: mysql.sql: Cannot stat: No such file or directory
--

[sts]

Hi Rob,

this script was an example and you'll have to change a few things to make it fit to your situation.
- E.g. the path to Sugar is in that example /var/www/sugar but is different in your installation.
- 'mysqldump' is a command of MySQL (I assume you're using this database) which is not found in your case: you should check where it is in your installation and set the path.
- The parameters of that command include a username and password of a database account (in case of that example 'sugarcrm' and '********'). Here you should use a user and password from your MySQL installation.