Table of Contents

Ahsay Backup

See also Other Ahsay pages in this wiki

See also Ahsay Licensing

See also Ahsay Backup with Multiple Machines per Account

See also Ahsay Disaster Recovery

Pricing

http://download.ahsay.com/sales/notice_20120921.pdf

http://download.ahsay.com/sales/ASC_OEM_On-Site_Edition.pdf

Check Versions

Clients

Web Interface → Manage Log → Backup Job

Server

Web Interface → Manage System → Software License

Upgrade OBSR

Upgrade Guide: https://forum.ahsay.com/viewtopic.php?f=94&t=9775

:!: If you are using RDR, upgrade that first.

:!: If not doing a major version upgrade, see below for patches and hotfixes.

Begin the upgrade:

# Declare locations
OBS_HOME=/opt/obs; export OBS_HOME
OBS_HOME_BAK=/opt/obs.bak; export OBS_HOME_BAK

# Stop services
/etc/init.d/obsr stop

#Create backup less user data - you should back it up too if you can
tar -czvf /root/obs_backup.tgz --exclude="/opt/obs/user/*" /opt/obs

# Uninstall the old version leaving data and configuration intact
sh $OBS_HOME/bin/uninstall.sh

# Delete old folder if it exists and rename $OBS_HOME to $OBS_HOME_BAK
rm -rf $OBS_HOME_BAK
mv $OBS_HOME $OBS_HOME_BAK
mkdir $OBS_HOME

# Move into $OBS_HOME, download the latest version and extract it
cd $OBS_HOME
wget http://ahsay-dn.ahsay.com/current/obsr-nix.tar.gz
tar -xzvf obsr-nix.tar.gz

# Delete a couple of large log files in order not to fill the root partition
rm -f $OBS_HOME_BAK/logs/catalina.out.*

# Copy original files into the upgrade installation
/bin/cp -avr $OBS_HOME_BAK/conf/*.xml $OBS_HOME/conf/
/bin/cp -avr $OBS_HOME_BAK/logs $OBS_HOME/
mv $OBS_HOME_BAK/user $OBS_HOME/
/bin/cp -avr $OBS_HOME_BAK/system $OBS_HOME/
mv $OBS_HOME_BAK/rps-system $OBS_HOME/
mv $OBS_HOME_BAK/rcvshome $OBS_HOME/

sh $OBS_HOME/bin/install.sh

Finally, logon to the AhsayOBS Web Management Console and press the Update button here:

Manage System → Software License → Update

:!: Note that these upgrade instructions do not include handling customizations such as branding.

:!: Note that AUA must be reenabled after an upgrade.

Release Notes

After upgrading to the latest version, check the Release Notes to see if there are any hotfixes you need to appy:

http://www.ahsay.com/download/customer/document/aobs-release-notes.htm

Patch or Hotfix

https://forum.ahsay.com/viewtopic.php?f=22&t=10215

# Declare locations
OBS_HOME=/opt/obs; export OBS_HOME

# Stop services
/etc/init.d/obsr stop

# Install patch/hotfix
cd $OBS_HOME
wget http://download.ahsay.com/support/hot-fixes/6/obsr-nix-hotfix.zip
unzip obsr-nix-hotfix.zip    #or obsr-nix-patch.zip - overwrite all files
rm obsr-nix-hotfix.zip

# Restart services
/etc/init.d/obsr start

Applying Hotfix to Clients

https://forum.ahsay.com/viewtopic.php?f=22&t=9789

cd $OBS_HOME/webapps/obs/liveUpdate/
wget http://download.ahsay.com/support/patchset/6/obc-app-upgrade-patch.zip
unzip obc-app-upgrade-patch.zip        # overwrite all files

Auto Update Agent (AUA)

:!: You can kick off the update on the client by restarting the AUA service.

:!: You can see the client versions easily In the web admin: Manage Log → Backup Job

Select Clients for AUA

Manage User → Auto Update → All

Enable AUA

OBS_HOME=/opt/obs; export OBS_HOME
cd $OBS_HOME
mv webapps/obs/liveUpdate/index.xml.disable webapps/obs/liveUpdate/index.xml

Customize AUA

vim webapps/obs/liveUpdate/index.xml

Performance

Downloads and Docs

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_latest-software_download-ahsayobs-ahsayrps

Move OBS to New Hardware

http://pedia.ahsay.com/article.aspx?article=1786&p=16

Do a Centos 6 Minimal Install

Partitioning

During the installation, you might use manual partitioning like:

PartitionSizeMountpointFilesystem
/dev/sda1200MB/bootext4
/dev/sda215GB/ext4
/dev/sda32GBn/aSwap
/dev/sda4Rest of first disk/opt/obs/userext4
/dev/sdb1All of second disk/mnt/obs_homes_1ext4
/dev/sdc1All of third disk/mnt/obs_homes_2ext4

Install Latest Updates

yum update -y
reboot

Install Needed Tools

yum -y install wget vim-enhanced ntp acpid

Configure Networking

See Static IP Address.

Verify the hostname and IP address are set in /etc/sysconfig/network and in /etc/hosts.

Configure Timekeeping

Linux Timekeeping

chkconfig ntpd on
service ntpd start

Configure SElinux

Set selinux to Permissive mode and set the system to relabel on the next reboot:

vim /etc/selinux/config

SELINUX=permissive

echo 0 >/selinux/enforce
touch /.autorelabel
sestatus -v

Configure Bash Shell

cat >> ~/.bash_profile << EOF

alias ll='ls -l'
alias la='ls -A'
alias l='ls -CF'
alias ls="BLOCK_SIZE=\'1 ls --color=auto"
alias free="free -m"
export GREP_OPTIONS='--color=auto'
PS1='\[\033[00;36m\]\u\[\033[00m\]@\h:\[\033[05;33m\]\w\[\033[00m\] \$ '
export HISTCONTROL=ignoredups
EOF

Firewall

:!: Expose only TCP port 80 and 443 (Ahsay) plus UDP 123 (NTP) to the public.

CentOS Firewall

The built-in CentOS firewall only allows port 22 (SSH) by default and blocks all other traffic.

iptables -I INPUT 3 -p udp --dport 123 -j ACCEPT
iptables -I INPUT 3 -p tcp --dport 443 -j ACCEPT
iptables -I INPUT 3 -p tcp --dport 80 -j ACCEPT

/sbin/service iptables save
iptables --line-numbers -nL

Arno's Firewall

If your backup server has an interface directly connected to the Internet, you should consider Arno's Firewall.

Disable the built-in firewall:

service iptables stop
service ip6tables stop
chkconfig iptables off
chkconfig ip6tables off

Arno's Firewall

I don't remember what these very important notes were for:

NAT_LOCAL_REDIRECT=1
NAT_FORWARD_TCP="80>209.104.9.38~9080 443>209.104.9.38~9443"

Install OBS

OBS_HOME=/opt/obs; export OBS_HOME
mkdir $OBS_HOME && cd $OBS_HOME
wget http://ahsay-dn.ahsay.com/current/obsr-nix.tar.gz
tar -xzvf obsr-nix.tar.gz
sh $OBS_HOME/bin/install.sh

First Login

Login to the new backup server using a web browser. Use a fully qualified domain name, an IP address won't work. That means you must have DNS configured or have a 'hosts' file entry for the FQDN to resolve properly.

The default username/password is system/system - change them to 'admin' and your own password:

Manage System → Server Configuration → Login Name

Filesystem Tweaks

Depending on how you partitioned the drive when you installed the OS, you may need to add a new logical volume for OBS to use. Ideally, the OBS 'homes' will be separate from the host OS so if a disk is filled, the server won't crash.

Assuming the entire installation disk was used as a LVM PV (physical volume), this command will use the rest of it to create a new LV (logical volume) for OBS 'homes':

lvcreate -n lv_obs_homes -l 100%FREE vg_backup

mkfs.ext3 /dev/vg_backup/lv_obs_homes

Edit /etc/fstab and add add a line to mount the new LV with the 'noatime' option:

vi /etc/fstab

/dev/mapper/vg_backup-lv_obs_homes    /mnt/obs_homes       ext3    defaults,noatime    0 0

mkdir /mnt/obs_homes/{system,user}

Manage System → Server Configuration → System Home

Manage System → Server Configuration → User Homes

Copy Data

rsync -av /usr/local/obs/system root@192.168.1.6:/opt/obs/

rsync -av /usr/local/obs/user root@192.168.1.6:/opt/obs/

Add Additional Storage

https://help.ahsay.com/display/2/kb/article.aspx?aid=2437&n=1&docid=67930

Install a new disk drive, then create one large GPT partition and format it:

echo ';' | sfdisk /dev/sdx

mkfs.ext3 /dev/sdx1

You want to mount the new space using the disk's UUID as a best practice. Run this command after the format has finished to determine the UUID:

blkid

Edit /etc/fstab to mount the new partition with the 'noatime' option.

vi /etc/fstab

# additional storage for OBS
/dev/mapper/vg_backup-lv_obs_homes           /mnt/obs_homes         ext3    defaults,noatime    0 0
UUID=40a09cc6-47d7-4061-b93b-a30d45659075    /mnt/obs_homes_2       ext3    defaults,noatime    0 0
UUID=299dc4c1-0652-47d3-bbe5-bcf1788647d0    /mnt/obs_homes_3       ext3    defaults,noatime    0 0

mount -a
mount

Then you can assign the new space for user homes in the web interface:

Manage System → Server Configuration → User Homes

Data Validation

http://forum.ahsay.com/viewtopic.php?t=5746

Configuration Archival

http://www.ahsay.com/jsp/en/home/index.jsp?kw=&pageContentKey=ahsay_products_ahsayobs_features_configuration-archival

Manage System → Routine Job → Configuration Archival

The Configuration Archival feature is designed to faciliate a quick and simple recovery of an AhsayOBS server after an outage so as to minimize the down time of backup service.

With this feature enabled, a copy of AhsayOBS configuration settings will be backed up to Ahsay™ License Server everyday so that when a disaster strikes, the backup server administrator is able to download the backed up AhsayOBS configurations from the Ahsay™ License Server and restore them quickly onto a new AhsayOBS machine.