User Tools
Table of Contents
Ahsay Backup Client Issues
See also Ahsay Backup with Multiple Machines per Account
See also Other Ahsay pages in this wiki
http://kasperk.it/ahsay/ahsay-obm-clean-restart-client
Remember to choose HTTPS for SSL encryption of communications between backup client and backup server.
Use the FQDN (fully qualified domain name) for the hostname.
Seed Load
OBM Linux Client
http://eval.ahsay.com/obs/jsp/user/wizard/install/index.jsp?os=unix.jsp
http://peakbackup.blogspot.com/2008/01/here-are-some-nice-to-knows-about.html
Uninstall
sh /usr/local/obm/bin/uninstall.sh
Install
Log into machine to be backed up giving yourself web management access in the process:
ssh -X -l root hostname.example.com
If you see an error in forwarding X11, it should go away after the next step. This is important to be able to run the GUI interface (below). You will have to log out, then back in for X11 (graphics) forwarding to work properly.
Install necessary libraries for a headless Linux server as client:
yum install libXi libXp libXtst Xvfb xorg-x11-xauth
Install OBM:
cd ~ wget http://obs2.virtualarchitects.com/obs/download/obm-nix.tar.gz mkdir /usr/local/obm cd /usr/local/obm tar -xzvf ~/obm-nix.tar.gz ./bin/install.sh >install.log cat install.log # look for errors ps -ef | grep obm chkconfig --list |grep obm
For all Linux/Unix backup jobs, it is suggested to verify the Temporary Directory and to exclude it from being backed up.
| Temporary Directory | /root/.obm/temp |
|---|---|
| Exclude the following files/directories | /root/.obm |
SME Server Additional Notes
http://wiki.contribs.org/X11_Forwarding_on_SME
On 64-bit SME 8 servers, you may have to install the requisites with this command:
yum install libXi libXp libXtst Xvfb xorg-x11-xauth --enablerepo=base --enablerepo=updates
You will need to enable X forwarding:
mkdir -p /etc/e-smith/templates-custom/etc/ssh/sshd_config/ cd /etc/e-smith/templates-custom/etc/ssh/sshd_config/ echo X11Forwarding yes > 50X11Forwarding echo X11UseLocalhost no > 50X11UseLocalhost expand-template /etc/ssh/sshd_config /etc/init.d/sshd restart
On SME Servers, which use runlevel 7, you must also enable automatic startup with these two commands:
ln -s /etc/rc.d/init.d/obmaua /etc/rc7.d/S99obmaua ln -s /etc/rc.d/init.d/obmscheduler /etc/rc7.d/S99obmscheduler
You also need to run these pre and post backup commands in order to back up the MySQL databases properly:
Pre-Backup Command
| Name | Dump MySQL |
|---|---|
| Command | su - root -c “signal-event pre-backup” |
| Working Directory | / |
Post-Backup Command
| Name | Delete Dumped Files |
|---|---|
| Command | su - root -c “signal-event post-backup” |
| Working Directory | / |
Create and Run Backup Jobs
Use the GUI method if you can, but don't fight it.
Use the Text Console method if you can't use the GUI (Configurator.sh)
Use the Web Console method only if you have to.
Be sure to edit the backup sets afterwards in the web interface to verify these settings:
- Backup sources as appropriate
- Backup schedule as appropriate
- Run scheduled backup on computers named field must have a hostname
- Retention period set to 90 days
- Compression type normal
- Local copy (L1 backup) on or off
- Local copy has separate retention settings
- Use a separate backup job if L1 captures more files
- Pre and post scripts
- Dump MySQL maybe
GUI Method
This also works on headless Linux backup client servers with the prerequisite packages (listed above) installed.
Assuming you forwarded X in the SSH command line (-X) when you connected to the Linux backup client machine, we start the GUI interface like this:
sh /usr/local/obm/bin/RunOBC.sh
If you get errors with X11 forwarding:
- Make sure the requisite packages listed above are installed on the headless host.
- Make sure the SSH daemon on the headless host to be backed up has X11 Forwarding enabled
- Restart the SSH daemon if a change was made
vim /etc/ssh/sshd_config X11Forwarding yes service sshd restart
Text Console Method
We start the text interface like this:
sh /usr/local/obm/bin/Configurator.sh
You can run a previously created job like this:
sh /usr/local/obm/bin/RunBackupSet.sh "BACKUP_SET_NAME"
Web Console Method
You can create a backup account and backup job using the web interface, but it's easier and more common to use the client software on the backup client machine.
You may want to enable the Trial feature of your OBS. This makes it very easy to create new accounts and backup jobs all from the client machines.
OBM Windows Client
http://eval.ahsay.com/obs/jsp/user/wizard/install/index.jsp?os=windows.jsp
Download from http://obs1.sonoracomm.com
- Weekly System State Backup → Microsoft Windows System Backup
- Nightly MSSQL Backup → MS Exchange Server Backup
- Nightly Files Backup → File Backup
C:\Documents and Settings C:\Program Files\CYMA C:\Program Files\QuickPen C:\Users
Hyper-V
Customization
Small Business Server (SBS)
See also Ahsay Backup - Microsoft Exchange
See also Ahsay - Microsoft SQL Server Backup
Suggested Backup Jobs Configuration
- Turn off circular logging
- Do full backups on MS Exchange
| Ahsay Backup Type | Run | Time | Notes |
|---|---|---|---|
| File Storage | Daily | 1 to 6 AM | Separate jobs for each major section |
| Full Exchange Image | Friday | 9 PM | Do full Exchange backups only |
| Database Backup | Daily | 8 PM | Do complete database backups only |
| MS Windows System Backup | Friday | 7 PM | C drive only |
Backup Exclusions
Windows
C:\hiberfil.sys
C:\Pagefile.sys
C:\Program Files\*
C:\RECYCLER
C:\System Volume Information
C:\Windows\*
${App_Data}\Avg7
${App_Data}\Avg8
${App_Data}\Kaspersky Lab
${App_Data}\McAfee
${App_Data}\McAfee.com
${App_Data}\Microsoft
${App_Data}\Sophos
${App_Data}\Symantec
*\*.tmp
*\Application Data\Macromedia\*
*\Application Data\Mozilla\*
*\Local Settings\Application Data\Microsoft\*
*\ntuser.dat
Linux
/dev /lost+found /proc /sys /tmp /var/empty /var/lock /var/run /var/spool /var/tmp
