Estimated reading time: 15 min
In the following, information and methods about the copying, troubleshooting and disaster scenarios of Tegsoft system under the titles of backup, backup types, access to backups and roleback are given below. The content specified here is managed and used by the Server Maintenance application.
Backup can be defined as database backup. Backup stores necessary datas for working system efficiently.These files are media files(Announcement and Hold musics), history datas(CDR records, Agent action history) and current datas(contact records, order informations). If a problem occurs on system, system can be rollback from these files. The backup process can be performed at any time or automatically by the system.
From Tegsoft, to set backup time, follow this PBX Managemet–>Server Settings. In Archive/Backup group Backup Time (hh: mm): 02:30) is set as a default. This backup time can be changed by the user. Tegsoft backups automatically every day at the specified Backup time.
Real time backup is the storage of all data processed on the system as a recoverable file until the following command runs.
For Real Time Backup:
There are 2 types of backup file in Tegsoft.
Backup files that contais all datas are created in DATE-SERVER MAC ADDRESS.tgz format. That backups contains everything done on the system.
Backup files that contais configuration datas are created in DATE-V2-SERVER MAC ADDRESS.tgz format. These backups contain the data required for the operation of the system (customer representative, extension definitions, user definitions, etc.), media files (IVR announcements, hold music, etc.).
Backups are divided into 2 different groups in Tegsoft. These are:
Tegsoft server contains all the backups of the system for the last 7 days on its own disk.
These backups can be accessed with this 2 ways:
Example backup file name: 20141020-21:21:21:41:41:41.tgz
Tegsoft server contains the last 7 days of the system’s configuration backups on its own disk and on the remote Tegsoft Backup servers.
These backups on disk can be accessed with this 2 ways:
Example backup file name: 20141020-V2-21:21:21:41:41:41.tgz.
Access to backups under Tegsoft Backup Servers is described in detail in Server Maintenance step 1.2.2 under Remote Backups.
Rollback is a process that can be performed in case of database damage or at any time via Tegsoft. If database was damaged, the system opens the Recovery Operations screen automatically when try to login Tegsoft.
There are two procedures to rollback below.
Backup files should be checked regularly. Control procedure as follow.
\ TEGSOFT_IP \ backup that contains daily backup files should be accessible to windows share for local backup check.
A software checks the backups that sent to the data center every morning at 08:00. After this checking, Alarm mail is created for the backups that have not reached to data center. The Alarm means that there is no backup in the data center for the server related and in case of a failure, restore operation can not be performed from data center. Having backup files at data center provides crucial advantages about restore scenario in the event of disaster level failure.
Apply these control steps below to access backups to data center correctly to provide technical checks.
The www.tegsoft.com name should be resolved to the IP address correctly.
command –> host www.tegsoft.com
If the result of command is “www.tegsoft.com has address 220.127.116.11”, DNS Check result is successful. So, move to second check topic.
If the result of command is “Host www.tegsoft.com not found: 3(NXDOMAIN)”, “NO DNS SERVER FOUND”, “Time out” or similar error message, there is error on DNS setting.
The local DNS Server value must be fixed. The correct value for DNS Value in “Server Settings” from Tegsoft web screen should be entered.
DNS settings must be adjusted until the DNS Check result is successful.
If the download of ping.html with wget command is successful as follows, the HTTP access check result is successful.
–2014-10-28 19:59:14– https://www.tegsoft.com/ping.html Resolving www.tegsoft.com… 18.104.22.168 Connecting to www.tegsoft.com|22.214.171.124|:80… connected. HTTP request sent, awaiting response… 200 OK Length: 912 [text/html] Saving to:
ping.html' 100%[==============================================================================================================>] 912 --.-K/s in 0s 2014-10-28 19:59:15 (79,1 MB/s) -ping.html’ saved [912/912]
Otherwise, network access should be checked.
echo TEST > a.txt
scp -i /root/.ssh/customer -P 2222 -o UserKnownHostsFile=/dev/null -o StrictHostKeyChecking=no a.txt [email protected]:/home/customer/Warning: Identity file /root/.ssh
If the command output results in file transfer as follows, the SCP Access control result is SUCCESSFUL.
Warning: Permanently added 'www.tegsoft.com,126.96.36.199' (RSA) to the list of known hosts. a.txt 100% 1 0.0KB/s 00:00
If the command output is like “file transfer didn’t end up”, “access error” etc, SCP access check result is unsuccessful. Communication infrastructure should be checked.
Warning: Identity file /root/.ssh/customer not accessible: No such file or directory. ssh: connect to host www.tegsoft.com port 2222: No route to host lost connection
Was this article helpful?