Koozali.org: home of the SME Server

script help - shutdown smtp for backup

Olsen

script help - shutdown smtp for backup
« on: December 10, 2004, 07:14:13 PM »
Is there a way I can halt all smtp and network activity during backups?  Currently, if an object on the server is busy, the object does not get backed up by my tapeware.  How can I do this?  I am a novice when it comes to linux..... any help.....

In the holiday spirit...Bryan

Offline mrjhb3

  • *
  • 1,188
  • +0/-0
    • John Bennett Services
script help - shutdown smtp for backup
« Reply #1 on: December 11, 2004, 05:52:12 AM »
You could try this:

/etc/rc.d/rc7.d/S85smtpfront-qmail stop
backup
/etc/rc.d/rc7.d/S85smtpfront-qmail start

If you do, please let me know the results.

JB
......

Olsen

script help - shutdown smtp for backup
« Reply #2 on: December 13, 2004, 05:31:47 PM »
I need to create some kind of job that runs automatically because we have backups that occur nightly at 12am....hence, I am not here to shutdown the smtp or the network activity......

Any ideas?

Offline mrjhb3

  • *
  • 1,188
  • +0/-0
    • John Bennett Services
script help - shutdown smtp for backup
« Reply #3 on: December 13, 2004, 07:17:25 PM »
exactly, so create 2 cron jobs.  One to shut down smtp, then one to re-start it.
......

Olsen

script help - shutdown smtp for backup
« Reply #4 on: December 13, 2004, 07:45:39 PM »
How do I create cron jobs?  (....never done it)

Olsen

script help - shutdown smtp for backup
« Reply #5 on: December 13, 2004, 11:40:40 PM »
I have figured out how to create a cron job.  Now, what are the contents of the folder "rc7.d"?

My problems is this, if an object on the server changes during backup, the program rejects the object because it has changed.  

I assume that if I can terminate all network activity and smtp activity during the backups, that should solve my problems.  However, I dont know the service names to stop.  I want to put the commands in a text file and have the cron job execute the commands in the text file.  I should be able to create two text files, one containing all of the shutdown commands, and one that contains the startup commands.  Can anyone offer some guidance to the commands I need to include in the text file?

Thanks!

Olsen

script help - shutdown smtp for backup
« Reply #6 on: December 14, 2004, 04:39:12 PM »
I figure I need to shutdown the following services during backup

httpd-e-smith
squid
qmail
smtpfront-qmail
imap
popd

Does anyone know how I can do this in a script?????

Offline mrjhb3

  • *
  • 1,188
  • +0/-0
    • John Bennett Services
script help - shutdown smtp for backup
« Reply #7 on: December 15, 2004, 03:21:11 AM »
Been a way for a bit.

I believe all you need is in this directory

/etc/rc.d/rc7.d

Use the info I posted about and stop the services, backup, then start them again.

I'm real interested if this works for you with tapeware.  I looked at tapeware a while back, but didn't get a chance to dig into it.  One of the things I am interested in is the process of doing a complete restore from a failure.  Do you plan on testing this?

JB
......

Olsen

script help - shutdown smtp for backup
« Reply #8 on: December 15, 2004, 05:09:56 AM »
I have attempted to create a file that will execute about 9 commands shutting down various services in the init.d file.  I am going to see how the backup works after that.  If the shutdowns do not solve the problem, I am back to the drawing board.  

As for tapeware, it has been a very solid backup method for us.  We outgrew the server-manager backup to desktop method and needed a more efficient way to backup server data.  We do incremental backups during the week and do full backups on friday.  The restore should be a snap.  All you should need to do is reinstall SME and all of the packages and additional rpms, then restore all of the configuration and email files, then all of the user data from the tape backup.  It is highly recommended that you reinstall SME when system failure occurs.  I do not plan on testing the full restore, but if I do, I will be sure to let you know.  

As of now, I am crossing my fingers and hoping that the cron jobs solve my immediate issue.  I will keep everyone posted.....

Olsen

script help - shutdown smtp for backup
« Reply #9 on: December 15, 2004, 04:52:40 PM »
Ok, here are my results.

The cron job worked at shutting down the following services in the init.d file

httpd-e-smith
squid
qmail
smtpfront-qmail
imap
popd

The cron job I created to restart the services also worked.  

However, it did not result in a flawless backup I am still having issues with the following data....
******************************************************
\etc\samba
                        secrets.tdb : Ver : 101 - Data did not compare correctly

\var\cache\samba
                    connections.tdb : Ver : 101 - Data did not compare correctly
                           wins.dat : Ver : 101 - Data did not compare correctly

\var\lib\rrd
                     drive_hda1.rrd : Ver : 101 - Data did not compare correctly
                     drive_hda3.rrd : Ver : 101 - Data did not compare correctly
                   host_gateway.rrd : Ver : 101 - Data did not compare correctly
                     iface_eth0.rrd : Ver : 101 - Data did not compare correctly
                     iface_eth1.rrd : Ver : 101 - Data did not compare correctly
                     processors.rrd : Ver : 101 - Data did not compare correctly
                         sysmon.rrd : Ver : 101 - Data did not compare correctly
                       sysmon.stats : Ver : 101 - Data did not compare correctly

\var\log\dnscache
                            current : Ver : 026 - Data length mismatch

\var\log\httpd
                         awstats_lr : Ver : 101 - Data did not compare correctly

\var\log\sa
                               sa14 : Ver : 026 - Data length mismatch

\var\log\tinydns
                            current : Ver : 026 - Data length mismatch

\var\log
                cron.20041208011207 : Ver : 026 - Data length mismatch
            messages.20041208011207 : Ver : 026 - Data length mismatch

\var\spool\lpd\lj4000
                          status.pr : Ver : 026 - Data length mismatch
******************************************************
Can anyone help me identify what I missed...Thanks!

Offline CharlieBrady

  • *
  • 6,918
  • +3/-0
script help - shutdown smtp for backup
« Reply #10 on: December 17, 2004, 04:02:07 AM »
Quote from: "mrjhb3"
exactly, so create 2 cron jobs.  One to shut down smtp, then one to re-start it.


No, cron isn't the way to do it. Put one action script in the pre-backup event directory (or a symlink to one) and one in the post-backup directory. The action script could disable smtp, or disable networking altogether, depending on how draconian you wished to be.

in pre-backup:

#! /bin/sh
svc -d /service/smtpfront-qmail

In post-backup

#! /bin/sh
svc -u /service/smtpfront-qmail

I've seen sites where backup takes over 12 hours though - is the cure here worse than the disease?

Offline dilligaf

  • *
  • 266
  • +0/-0
    • http://www.willcraft.com
Re: script help - shutdown smtp for backup
« Reply #11 on: December 17, 2004, 04:02:00 PM »
Quote from: "Olsen"
Is there a way I can halt all smtp and network activity during backups?  Currently, if an object on the server is busy, the object does not get backed up by my tapeware.  How can I do this?  I am a novice when it comes to linux..... any help.....

In the holiday spirit...Bryan

I have tapeware on lots of servers, and manage and review their logs daily.
IMO you get what you get.
For example you learn what to look at when you review the logs, and explain to the user, or learn your self what items are acceptable with respect to being busy, on not found etc.
I would not stop services.
A little further explanation, some of our server installs the server does not do e-mail. So all we backup are the ibays, and the home dir. Clean logs every time, unless someone leaves a file open etc.
I have used tapeware for many years, and it is a great product.
Dan

Olsen

script help - shutdown smtp for backup
« Reply #12 on: December 17, 2004, 04:15:12 PM »
Yes, my efforts to stop services to obtain "clean" backups was not totally necessary.  The items not being backed up were not business critical items.  I just wanted to finally get a successful backup with no warnings.  I have found out that it is unlikely that our server will not have any errors using tapeware.  I am going to take your advice, Thank you!