G2 System backup procedures

Installation instructions

• su {enter root password}
• Copy and paste the following commands:

cd /tmp
wget dstar.info/dist/g2_backup_installer
/bin/bash ./g2_backup_installer

[nj6n@k6vo ~]$ su
Password: 
[root@k6vo nj6n]# cd /tmp
[root@k6vo tmp]# wget -q dstar.info/dist/g2_backup_installer
[root@k6vo tmp]# /bin/bash ./g2_backup_installer

D-STAR Backup Script (g2_backup) Installer

Backing up current g2_backup script ...[Done]
Fetching backup script from dstar.info/dist / g2_backup ... [Done]

Would you like to have a copy of your backup emailed to you? (Y/n): Y

Enter the email address to backup data to: you@youraddress.com

Re-enter the email address to backup data to: you@youraddress.com

Installing cron.d entry: /etc/cron.d/dstar-backup ... [Done]

                   **** Important NOTE ****

Backup archive file will be created in /tmp at 04:35 every Sunday.

To create a backup manually:

       /dstar/scripts/g2_backup

A copy of the backup will also be sent to: you@youraddress.com

Backup script has been installed.

• The script will automatically run at 4:35 AM each Sunday.
• To run the script manually, log in or become "root" user and type: /dstar/scripts/g2_backup
• The installer creates the cron-tab entry "35 4 * * * root /bin/bash /dstar/scripts/g2_backup" in /etc/cron.d/dstar-backup
• The script may be configured to back up to an alternate location such as a USB disk or flash drive
• Update the value of BACK_TAR= and replace /tmp/backup.tar.gz with your alternate location, for example, "/media/BACKUP/g2-backup.tar.gz

D-STAR Gateway Re-Installation Instructions

These procedures are designed to enable a gateway administrator to recover from a catastrophic failure of their gateway system. While it is possible to create a replica of your current system using these procedures, it is imperative that you DO NOT run two instances of your gateway at the same time on the production network.

1. IMPORTANT: Do NOT run two instances of your gateway at the same time!
2. If the gateway you are restoring is still online, shut it down now!
3. Re-install CentOS version 5.x per ICOM Installation Instructions.
4. Re-install bind domain name server software per ICOM instructions using ds_bind-install script.
5. Re-install gateway software per ICOM Instructions using dstar_gw-install script.
• Do NOT edit the dsipsvd or dsgwd configuration files, these will be restored.
• Do NOT run the add_user_mng.sh script as the databases will be restored also.
6. Log in as root with the password you created in step 3.
7. Restore the backup files created by the gw_backup script.
   • cd /
   • tar -xvzf backup.tar.gz
8. Re-install updates 1, 2, and 3.
9. Restore the postgres database:
   • Make sure Postgres is running: /sbin/service dstar_gw status
   • If not, start it with /sbin/service dstar_gw restart
   • rm -f /home/postgres/*.csv
   • cp /dstar/backups/*.csv /home/postgres/.
   • Insert the Original ICOM G2 Installer CDROM in the CDROM Drive.
   • It should automatically mount to the path /media/ICOM.
   • NOTE: If you mount it manually, adjust the following commands accordingly.
   • /media/ICOM/dstar_db-backup ALL write

   • [root@k6vo ICOM]# ./dstar_db-backup ALL write
        ALL 091126_102539 /home/postgres
        TRUNCATE TABLE
        VACUUM
        COPY 588
        TRUNCATE TABLE
        VACUUM
        COPY 16331
        TRUNCATE TABLE
        VACUUM
        COPY 13540
        TRUNCATE TABLE
        VACUUM
        COPY 596
        TRUNCATE TABLE
        VACUUM
        COPY 16519
        TRUNCATE TABLE
        VACUUM
        COPY 4
        TRUNCATE TABLE
        VACUUM
        COPY 4
        *** finished ***
        

10. Re-install DStarMonitor.
• Note: DSM Installation Script should give you the option to (U)pdate, choose "U".
11. Re-install dplus
• Note: dplus configuration file and dv audio files will be restored in a later step.
12. Reboot your system.
13. Verify normal operation. Note, it may take 30 minutes to an hour before dplus linking works again.