Koozali.org: home of the SME Server

Legacy Forums => Experienced User Forum => Topic started by: paulmancan2 on April 04, 2005, 10:55:05 PM

Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 04, 2005, 10:55:05 PM
Am I correct that there are automatic mysqldumps taken by e-smith? I don't see anything cron'd to this effect except for my own nightly dumps that I setup.

On the weekend I signal event post-upgraded and my database went back what seems to be a few days! I'd like to know how this happened. I looked at bug allegation 0000055 (which also refers to a seemingly non existant bug id 0000032) but not to clear on this.

Thanks for any help!
Title: Re: post-upgrade effect on MySQL ?
Post by: raem on April 05, 2005, 01:58:30 AM
paulmancan2

> Am I correct that there are automatic mysqldumps taken by e-smith?

msqldumps are part of the built in backup system, either backup to desktop or backup to tape.

If you don't manually run the backup to desktop then it's not being done.
If you run the scheduled backup to tape then it is being done.

If you use some other backup system, you best check that mysql dumps are being done,
eg backup2ws contrib, only the 911 backup job does mysql dumps, any other backup jobs you create do not include the database dumps.



> On the weekend I signal event post-upgraded and my > database went back what seems to be a few days!

Did you follow this with a reboot, perhaps you made some earlier changes that had not taken effect because of no reboot which now have taken effect.
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 05, 2005, 04:53:57 AM
OK. I do indeed have backup2ws enabled. However I kind of forgot about this (had other backup mechanisms) and it was backing up to a share that no longer exists.

There is however a dump sitting in
/home/e-smith/db/mysql

Where would this come from and what relation does it have to the post-upgrade?

Thanks!
Title: post-upgrade effect on MySQL ?
Post by: raem on April 05, 2005, 11:26:04 AM
paul

> I do indeed have backup2ws enabled......it was
> backing up to a share that no longer exists.
> There is however a dump sitting in
> /home/e-smith/db/mysql

That gets dumped by the backup script and should be deleted after the backup is done.
Possibly the backup job never completed due to the non existent share and left an orphaned dump file.
Title: post-upgrade effect on MySQL ?
Post by: boss_hog on April 05, 2005, 03:22:09 PM
Hey paulmancan2,
if you need a nice simple way to get a MySQL dump off site to an alternate location, there is a nifty little program from sourceforge:
AutoMySQLBackup VER 2.2

Very simple to set-up(IMO), it will back-up some or all(you choose) of the mysql DB's, it then e-mails (you choose) a .gz of the dump. Then it puts a copy on the localhost to the dir that you decide. It also does weekly and monthly dumps, it is a slick little program.

For what it's worth, I use a tape back-up done daily, and the AutoMysql', to get the database's off-site. My 2 sites are small and simple, so, the DB's are pretty tiny.
Hope this helps.
Joe
Title: post-upgrade effect on MySQL ?
Post by: CharlieBrady on April 05, 2005, 04:55:38 PM
Quote from: "paulmancan2"
OK. I do indeed have backup2ws enabled. However I kind of forgot about this (had other backup mechanisms) and it was backing up to a share that no longer exists.

There is however a dump sitting in
/home/e-smith/db/mysql


Please file one or more bug reports with the author of the backup2ws contrib.
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 05, 2005, 10:22:17 PM
Thanks guys. Will post bug.
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 06, 2005, 04:08:18 AM
I'm not really concerned with this problem, I will simply get rid of backup2ws and use the other methods I have. Charlie the contribs bugtracker suggests posting non core issues to this forum lol. Is there any benefit to anyone if I post this bug? If so perhaps you can tell me the appropriate place?

Thanks Ray for your explanation and boss_hog for his suggestions.
Title: post-upgrade effect on MySQL ?
Post by: CharlieBrady on April 06, 2005, 04:11:59 AM
Quote from: "paulmancan2"

Charlie the contribs bugtracker suggests posting non core issues to this forum lol. Is there any benefit to anyone if I post this bug? If so perhaps you can tell me the appropriate place?


Inform the contrib author that there is a problem, and provide all the details you can. You might mention the "pre-backup" and "post-backup" events.
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 06, 2005, 11:05:58 PM
Am I correct that there is no member list available here and that I basically have to google a contrib author's name and try and track them down?
Title: post-upgrade effect on MySQL ?
Post by: raem on April 07, 2005, 12:51:44 AM
paulmancan2

Is this what you want ?

Darrell May is the author of backup2ws, his web site is at
http://www.myezserver.com/
Forums for user feedback at
http://myezserver.com/phpBB2/

and re sme server
http://myezserver.com/phpBB2/viewforum.php?f=9
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 07, 2005, 12:53:31 AM
Thanks Ray. Really there is no way to get such info from this site right?

Also do you have any info on jprice?
Title: post-upgrade effect on MySQL ?
Post by: raem on April 07, 2005, 01:44:32 AM
paulmancan2

> Really there is no way to get such info from this site right?

You can click on the users names in the Who's Online box, then you can change the user ID number in the URL to see different users. I don't see an index as such.

Generally you can look inside an rpm to see if the creator has left some details. eg
download something from here
http://www.ibiblio.org/pub/Linux/distributions/smeserver/contribs/jprice/beta/e-smith-advworkgroup/

open the rpm in mc and read the /INFO/PACKAGER section
the email for James Price is there.
Title: post-upgrade effect on MySQL ?
Post by: paulmancan2 on April 07, 2005, 02:38:28 AM
Good first tip.

The second, I feel like an idiot for not looking in there. Thanks for your patience.