ahsay cloud backup suiteahsay-dn.ahsay.com/document/v7/7500/customer/pdf/guide_cbs_admi… · ahsay...

Ahsay Cloud Backup Suite

V7

Administrator’s

Guide

Ahsay Systems Corporation Limited

8 December 2015

Ahsay Cloud Backup Suite Administrator’s Guide

Ahsay Systems Corporation Limited V7.0.2

Ahsay Cloud Backup Suite

Administrator’s Guide

Copyright Notice

© 2015 Ahsay Systems Corporation Limited. All rights reserved. The use and copying of this product is subject to a license agreement. Any other use is prohibited. No part of this publication may be reproduced, transmitted, transcribed, stored in a retrieval system or translated into any language in any form by any means without priori written consent of Ahsay Systems Corporation Limited Information in this manual is subject to change without notice and does not represent a commitment on the part of the vendor, Ahsay Systems Corporation Limited does not warrant that this document is error free. If you find any errors in this document, please report to Ahsay Systems Corporation Limited in writing. This product includes software developed by the Apache Software Foundation (http://www.apache.org/).

Trademarks

Ahsay, Ahsay Cloud Backup Suite, Ahsay Online Backup Suite, Ahsay Offsite Backup Server, Ahsay Online Backup Manager, Ahsay A-Click Backup, Ahsay Replication Server, Ahsay BackupBox Firmware, Ahsay Universal Backup System, Ahsay NAS Client Utility are trademarks of Ahsay Systems Corporation Limited. Microsoft, Windows, Microsoft Exchange Server and Microsoft SQL Server are registered trademarks of Microsoft Corporation. Oracle and Java are registered trademarks of Oracle and/or its affiliates. Other names may be trademarks of their respective owners. Oracle, Oracle 8i, Oracle 9i, Oracle 10g, Oracle 11g are registered trademarks of Oracle Corporation. Lotus, Domino, Notes are registered trademark of IBM Corporation. Red Hat, Red Hat Enterprise Linux, the Shadowman logo and JBoss are registered trademarks of Red Hat, Inc. www.redhat.com in the U.S. and other countries. Linux is a registered trademark of Linus Torvalds. Apple and Mac OS X are registered trademarks of Apple Computer, Inc. All other product names are registered trademarks of their respective owners.

Disclaimer

Ahsay Systems Corporation Limited will not have or accept any liability, obligation or responsibility whatsoever for any loss, destruction or damage (including without limitation consequential loss, destruction or damage) however arising from or in respect of any use or misuse of reliance on this document. By reading and following the instructions in this document, you agree to accept unconditionally the terms of this Disclaimer and as they may be revised and/or amended from time to time by Ahsay Systems Corporation Limited without prior notice to you.

http://www.apache.org/


Ahsay Systems Corporation Limited V7.0.2

Revision History

Date Description Type of modification

10 Nov 2015 First revision for AhsayCBS v7.0 New

08 Dec 2015 New Monitor section in chapter 11 New


[Ahsay Systems Corporation Limited i

Table of Contents 1 Overview ............................................................................................................................ 1

1.1 Conventions ............................................................................................................... 1 1.2 Definitions, Acronyms and Abbreviation .................................................................. 1

1.3 System Requirements................................................................................................. 3 2 Quick Start ......................................................................................................................... 4 3 Backup Components .......................................................................................................... 5

3.1 Backup Server ............................................................................................................ 5 3.2 Backup Clients ........................................................................................................... 6

3.2.1 AhsayOBM ............................................................................................................ 6 3.2.2 AhsayACB ............................................................................................................. 6

3.3 Replication Server ...................................................................................................... 7

3.4 Redirector ................................................................................................................... 7 4 Hardware Requirements..................................................................................................... 8

4.1 Overview .................................................................................................................... 8 4.2 Server Requirements .................................................................................................. 9

4.2.1 AhsayCBS on Physical Machine ........................................................................... 9 4.2.2 AhsayCBS on Virtual Environment..................................................................... 10

4.2.3 AhsayCBS on Cloud Environment ...................................................................... 10 4.2.4 Setting Up a Standby Server ................................................................................ 10

4.3 Storage Requirements .............................................................................................. 12

4.3.1 Redundant Disk Setup for Physical and Virtual Storage ..................................... 12 4.3.2 Dedicate Storage on AhsayCBS .......................................................................... 12

4.3.3 Physical Storage ................................................................................................... 13 4.3.4 File System Tuning for Virtual Storage Environment ......................................... 13

4.3.5 Cloud Storage....................................................................................................... 14 5 Network and Firewall Settings......................................................................................... 15

5.1 Overview .................................................................................................................. 15 5.2 Network.................................................................................................................... 15

5.2.1 Use a Static IP Address ........................................................................................ 15 5.2.2 Network Load Balancing Configuration .............................................................. 15

5.3 Firewall .................................................................................................................... 16

5.3.1 Settings ................................................................................................................. 16 5.3.2 Expose Only TCP Port 80 and 443 to the Public ................................................. 16

5.3.3 Restricting Access on Administration Panel........................................................ 16 5.3.4 Replication Using Cross Over Cable ................................................................... 16

6 Deployment ...................................................................................................................... 17 6.1 Installation................................................................................................................ 17

6.1.1 Windows .............................................................................................................. 17 6.1.2 Linux/FreeBSD/Solaris x86 ................................................................................. 20

6.2 Upgrade/Migration ................................................................................................... 22

6.2.1 Upgrade/Migration from version 6 ...................................................................... 22 6.2.2 Auto upgrade and OEM handling ........................................................................ 22

6.3 Uninstall ................................................................................................................... 23 6.3.1 Windows .............................................................................................................. 23 6.3.2 Linux/FreeBSD/Solaris x86 ................................................................................. 25

7 Backup Server Configuration .......................................................................................... 27 7.1 License ..................................................................................................................... 27


[Ahsay Systems Corporation Limited ii

7.1.1 Licensee Name and License Key ......................................................................... 27

7.1.2 Automatic License Renewal ................................................................................ 28 7.1.3 Evaluation Expiry ................................................................................................ 29 7.1.4 Offline License Activation ................................................................................... 29 7.1.5 License Management Portal ................................................................................. 30

7.2 Setup email/report .................................................................................................... 31

7.3 Setup Predefined Destinations ................................................................................. 32 7.4 Create Users ............................................................................................................. 33

7.4.1 General users ........................................................................................................ 33 7.4.2 System users......................................................................................................... 34

7.5 Free trial ................................................................................................................... 35

7.6 Languages ................................................................................................................ 35 8 Advance Backup Server configuration ............................................................................ 36

8.1 Auto Save ................................................................................................................. 36

8.2 Proxy ........................................................................................................................ 36 8.3 Logging .................................................................................................................... 36

8.3.1 SNMP ................................................................................................................... 36 8.3.2 Windows Event .................................................................................................... 37

8.4 File Explorer ............................................................................................................ 37 8.5 Runtime Options ...................................................................................................... 37

8.6 User Group ............................................................................................................... 37 8.7 Policy Group ............................................................................................................ 37 8.8 Windows Active Directory Integration .................................................................... 38

9 Configure Replication ...................................................................................................... 39 9.1 Sending Data ............................................................................................................ 39

9.2 Accepting Data......................................................................................................... 40 10 Configure Redirector ....................................................................................................... 42

10.1 Hosting a Redirector ................................................................................................ 42 10.2 Joining Redirector .................................................................................................... 43

11 Operation.......................................................................................................................... 44 11.1 Monitoring ............................................................................................................... 44

11.1.1 Setup a Read-only Admin Account for Operators ........................................... 44 11.1.2 Build in Monitoring Tools ............................................................................... 44 11.1.3 Enable thirty monitoring tools ......................................................................... 44

12 Advanced AhsayCBS Configuration ............................................................................... 45 12.1 Listening to non-standard TCP/IP Port .................................................................... 45

12.2 Listening to a single IP address ............................................................................... 45 12.3 Restricting access to system page by IP address ..................................................... 45

12.4 Secure connection with AhsayCBS ......................................................................... 45 12.4.1 Installation a trusted SSL certificate ................................................................ 45 12.4.2 Renew a trusted SSL certificate ....................................................................... 46 12.4.3 Wild card SSL certificate with redirector setup ............................................... 46

13 Branding the AhsayCBS .................................................................................................. 48

13.1 Brand the AhsayCBS interface ................................................................................ 48 13.2 Prepare the branding for the AhsayOBM/AhsayACB ............................................. 49

14 API ................................................................................................................................... 51 15 Further Information .......................................................................................................... 52 Appendix .................................................................................................................................. 53

Appendix A Supported Language Code ........................................................................... 53 Appendix B Supported Time zone ................................................................................... 54


[Ahsay Systems Corporation Limited iii

Appendix C Product Documentations .............................................................................. 56

Appendix D Error Code 1011 and 1012 ........................................................................... 57 Appendix E Differences between AhsayCBS with the v6 versions ................................ 59


Ahsay Systems Corporation Limited 1

1 Overview

1.1 Conventions

A list of notations that are used throughout this document.

Convention Descriptions Example

Bold Important Information WARNING: You must

check the timestamp of server.xml before

proceeding to step2.

Italic Folder Path or File Path /usr/local/cbs/conf

[] Graphical Interface Elements [Manage Log]

%% Filepath in Windows format %CBS_HOME%

$ Filepath in Linux/Unix/BSD format

$CBS_HOME

italic Command mkdir /usr/local/cbs

Notation that are used specifically for API section:

Convention Descriptions

<Text Inside angle

brackets>

Placeholder for which you must supply a value.

[Text inside square

brackets]

Optional items.

{Text insides braces} Set of required items; choose one.

Vertical bar (|) Separator for mutually exclusive items; choose one.

Ellipsis (…) Items that can be repeated.

1.2 Definitions, Acronyms and Abbreviation

Term/Abbreviation Definition

AhsayCBS Ahsay™ Cloud Backup Suite

AhsayOBM Ahsay™ Online Backup Manager

AhsayACB Ahsay™ A-Click Backup

CBS_HOME The install location of AhsayCBS.

Windows C:\Program Files\AhsayCBS

Linux/FreeBSD/Solaris /usr/local/cbs/



CBS_HOME_BAK The backup location of AhsayCBS. It is used temporary during the install/upgrade process.

Windows C:\Program Files\AhsayCBS.bak\

Linux/FreeBSD/Solaris /usr/local/cbs.bak/

CONF_HOME The directory to store AhsayCBS configuration files.

Windows %CBS_HOME%\conf

Linux/FreeBSD/Solaris $CBS_HOME/conf

USER_HOMES The directories where AhsayCBS store the AhsayOBM

& AhsayACB users accounts.

The default location is: %CBS_HOME%\users

POLICY_HOME The directory where AhsayCBS store its system users and group policy information.

Windows

%CBS_HOME%\system\policy

Linux/FreeBSD/Solaris $CBS_HOME\system\policy

SYSTEM_HOME The directory where AhsayCBS store its system information.

Windows

%CBS_HOME%\system\ Linux/FreeBSD/Solaris

$CBS_HOME\system\

WEBAPPS_HOME Location of the webapps directory inside the installation directory of AhsayCBS.

Windows %CBS_HOME%\webapps.

Linux/FreeBSD/Solaris

$CBS_HOME\webapps



WEBAPP_HOME_BAK A backup of the webapps directory inside AhsayCBS.

Windows %CBS_HOME%\webapps.bak

Linux/FreeBSD/Solaris

$CBS_HOME\webapps.bak

RECEIVER_HOME The location where the replicated data is stored for a particular replication receiver.

JAVA_HOME The location where JAVA is installed

1.3 System Requirements

Please refer to the following articles

FAQ: Ahsay Software Compatibility List (SCL) for version 7.3 or above (5001) FAQ: Ahsay Hardware Requirement List (HRL) for version 7.3 or above (5000) for the system requirements of AhsayCBS.

It is recommended to install AhsayCBS on server grade O/S and

hardware platform. For evaluation purposes, the installation on Windows 7 or Windows 8 platforms would be fine.

https://forum.ahsay.com/viewtopic.php?f=169&t=13492




2 Quick Start

If you are setting up AhsayCBS for evaluation or you are new to AhsayCBS. You can download the AhsayCBS quick start guide and follow the instruction to setup the AhsayCBS.

http://www.ahsay.com/download/download_document_cbs-quick-start.jsp



3 Backup Components

AhsayCBS consists of 5 core software components. AhsayOBM and AhsayACB are backup software for installing on servers, desktops or laptop computers

that you need to backup. AhsayCBS is the server software which bundles a Backup Server, Replication Server and Redirector. Backup Server is the

module that will host all the AhsayOBM/AhsayACB backup users and their backup data. Replication Server is the module to provide additional backup of the Backup Server, while the Redirector is the module to provide your backup

environment with high scalability solution.

3.1 Backup Server

AhsayCBS is a web base centralised management console for administrator or

users to manage backup and restore. Administrator can create backup user accounts, manage group policies, and keep track of system performance and

healthiness.

Administrator can create sub-admin or resellers account so that they can manage the backup users by themselves. In addition, non-admin operator accounts with read only permission can be created to help administrator to

monitor daily backup and restore jobs, and system activities.



AhsayCBS is also a platform for backup clients to perform backup and restore. All the backup data are compressed and encrypted before uploading to the

Backup Server, while the restore process would require downloading the compressed and encrypted data onto the client computer for decryption and

uncompression.

To ensure all backup data is not the only backup copy hosted on the Backup Server, AhsayCBS comes with replication feature to replicate the backup data offsite to another Replication Server hosted in another location.

3.2 Backup Clients

3.2.1 AhsayOBM

AhsayOBM is a versatile backup application that backup databases,

applications and virtual machines to local and offsite destinations, e.g. local storage, on-premises backup server or backup server located in datacenter,

and cloud storage. All the backup data are compressed and encrypted before uploading to the


uncompression. AhsayOBM allows the creation of multiple backup sets, and backup databases

and virtual machines such as VMware, Hyper-V, Microsoft Exchange Database Availability Group (DAG), Microsoft Exchange Database, Microsoft Exchange

Mailbox, Microsoft SQL Server, Oracle Database, Lotus Domino/Notes, MySQL, and Windows Bare Metal with our dedicated backup modules.

3.2.2 AhsayACB

AhsayACB is an advanced yet easy-to-use desktop and laptop backup

software for backing up data to local and offsite destinations, e.g. local storage, on-premises backup server or backup server located in datacenter,

and cloud storage. All the backup data are compressed and encrypted before uploading to the


uncompression.



3.3 Replication Server

Replication Server offers close to real time replication of the Backup Server,

so that when your live Backup Server is out of service, you can switch the Replication Server into Backup Server so as to keep your backup service

uninterrupted. Alternatively, you can also choose to restore the backed up data from Replication Server when your Backup Server machine is recovered.

3.4 Redirector

With the use of Redirector in conjunction with multiple Backup Server machines, it forms a cloud backup architecture for servicing as many backup

customers as needed with a single public URL. All backup users will use the single URL as the initial contact server, even though they reside on different

Backup Servers under different URLs. Thus, an online backup provider can add new Backup Server machines to serve new customers, or relocate existing backup accounts from one Backup Server to another easily without

the need for the existing users to reconfigure the backup server address in AhsayOBM or AhsayACB.



4 Hardware Requirements

4.1 Overview

The AhsayCBS should be deployed on a machine supporting 64-bit multiple CPU and multiple cores environment. A 64-bit operating system will allow

AhsayCBS to run on a 64-bit Java JRE platform, as 64-bit Java is capable of supporting sufficient capacity for future business expansion, to meet the need

of existing customers and to support new AhsayCBS server features. If you are deploying the storage locally, you are required to setup storage

with redundant setup, such as RAID 5 or RAID 6. This is important especially when you are delivering a backup service with good disk performance as well

as good fault tolerance. When you deploy the AhsayCBS, please consider to assign a dedicated disk

for the system home, user home and replication home. It is not suggested to install AhsayCBS on a system disk, as the pending replication transaction logs

files may fill up the system drive and cause the operating system becomes unstable, and may even crash your AhsayCBS.

When you are considering to make a durable system for the AhsayCBS, please also consider to setup a standby server outside the same building/data

centre. In case the AhsayCBS is required to shutdown for maintenance, you can switch your backup service to the standby server.

For more information on the storage settings and cloud setup, please refer to the following section.



4.2 Server Requirements

4.2.1 AhsayCBS on Physical Machine

When you deploy a physical machine, please consider to purchase a more powerful machine. This will reduce the need for frequent hardware upgrades, which will require service down time for data migration.

It is a good idea to ensure your AhsayCBS server is equipped with some

redundancy features, i.e. power supply, and is connect it to a UPS (Uninterupterable Power Supply).

In this example, a physical machine is configured with the following setup:

Processor Intel® Xeon® CPU @ 2.8GHz

Physical Memory 16GB

Operating System

Windows 2008 R2 SP1

Server A rack mount server with several hot swap hard disk bays. E.g.: a 12 bay

rack mount server filled with 4TB hard disks.

Additional Disk Storage Connect a Direct-Attached Storage (DAS) with e.g.: a 12 hard disk bays filled

with 4TB hard disks via the SCSI interface, extra SCSI controller card required.

With the above setup, it should be able to handle 100 users with around

30TB of storage and a total of 1000 backup sets. With this server setup, it is not yet reaching the server’s physical limitation. There are still other factors that may limit the growth of users, e.g.: network bandwidth. Also, it is easier

to manage from administration point of view.

Assumptions: Each user has round 300GB of backup data, with constant 3% of

changes daily.

Each user account has configured 10 backup sets. These backup sets could be run on different machines and backup to the AhsayCBS at the

same time. AhsayOBM/AhsayACB backup clients are enhanced to utilize multiple threads

for backup and restore. It is recommended to keep the maximum number of



concurrent backup jobs on the AhsayCBS to 1000, to avoid potential performance problems.

4.2.2 AhsayCBS on Virtual Environment

It is more flexible when you deploy AhsayCBS on virtual machine environment, as you can increase memory size, process cores according to

the actual need. If VM snapshots are not required, please try to delete or reduce the amount

of snapshots stored in your disk.

Please also check on the storage requirement on virtual environment.

4.2.3 AhsayCBS on Cloud Environment

To host an AhsayCBS on cloud, the basic requirement would be similar with setting up a physical machine. It is more flexible when you need to increase

memory size, process cores, disk space. In addition, you will need to take the running cost of an server instance and network usage, which are considered

as a hidden cost for the setup. You can consider hosting a cloud server instance such as Amazon or Azure.

4.2.4 Setting Up a Standby Server

To ensure you have a backup of your Backup Server in the event of any hardware issues. We recommend setup a replication to replicate your Backup

Server to the Replication Server. In case you need to shutdown your Backup Server for maintenance, you can

simply switch your Replication Server to the Backup Server, and change the DNS record from your current Backup Server to the Replication Server.

The hardware requirement of the Replication Server would be similar as your

Backup Server and usually configured with more storage than your Backup Server.

Although both Backup Server and Replication Server are bundled in AhsayCBS, both backup and replication services are activated post

installation. It is not recommended to configure and use both services on one machine, as

they will compete for system resources, i.e. CPU, memory and storage. This could affect the performance and stability of your backup service. Also, it will

http://docs.aws.amazon.com/AWSEC2/latest/UserGuide/get-set-up-for-amazon-ec2.html

https://azure.microsoft.com/en-us/documentation/articles/cloud-services-how-to-configure/



completely defeat the purpose of Replication Server as a backup or standby server to your Backup Server.

Please also check the details on the replication setup.



4.3 Storage Requirements

When you are setting up storage for your AhsayCBS, please consider the

following:

the choice of the type of RAID to fit your requirement (for local physical server or virtual environment)

dedicate storage location for the system, user home and replication

home the choice of physical storage, virtual and cloud storage

In the following sections, we shall describe more in details.

4.3.1 Redundant Disk Setup for Physical and Virtual Storage

Refer to our previous example in the physical machine section, we would

recommend to setup a rack mount server with several hard disk bays and/or attach a DAS for future expansion.

When you are setting up a rack mount server with 10 4TB hard disks, you may have concerns whether formatting the disk volume with RAID 5 or RAID

6. The following table listed out the differences between the 2 disk array setup.

RAID 5 RAID 6

Total capacity Around 36TB Around 32TB

Fault tolerance 1-drive failure 2-drive failure

Speed gain 9x read speed 8x read speed

As the cost of hard disk has reduced a lot nowadays, it is strongly recommended to format your disk volume with RAID 6 that maximizes the

protection.

4.3.2 Dedicate Storage on AhsayCBS

When you partition the disk in your new server, please consider to setup

dedicate virtual disk volumes for operating system, application system, user homes and replication home (if Replication Server is enabled). It is a common practice that application system home, user homes and replication

homes are not located in the system volume, which may fill up easily and cause the system unstable.

Space required for application system home with replication setup



If you have replication setup on the Backup Server, please consider to dedicate a volume for the application home with sufficient disk space to store

the transaction log. As there is no exact formula for estimating the size of the application home, the amount of space used for the transaction log is

dependent on:

i. The period of time that the replication reached the replay mode ii. The amount of daily backup data uploaded to your backup server

For example, if daily customer backup jobs generate an average of 20GB of data. Your previous replication takes about 5 days to the replay mode, and

then your application home partition will require at least 100GB (20GB x 5 days) of free disk space.

This is only a general rule of thumb, this estimation does not take into consideration the growth of daily backup data, or the accumulation of backup

data on the backup server which will result in a longer time to reach replay mode.

Setup multiple dedicated disks for each replication receiver

If your Replication Server has setup several replication by multiple Backup Server, it is recommended that each receiver is located on it own individual

disk. The advantages of this type of setup, is it will minimize the I/O on each disk and therefore improve replication performance.

Also, if one of the Backup Servers suffers an outage, there is the option of swapping the disk to the affected Backup Server.

4.3.3 Physical Storage

If you plan to have physical backup server, you are expected to have a fast local backup storage such as local hard disks, DAS or SAN. It is a solution for

your business which wants to host the backup data with your physical backup server in your server room or data center.

Please avoid using network storage such as NAS, share drive on another computer as the backup efficiency is low and you may need additional setup

on the usage permission on the storage.

4.3.4 File System Tuning for Virtual Storage Environment

If your backup server and user’s data are hosted on a virtual environment, you need to check on the followings to make sure the performance has been

optimized.



When you setup a disk to attach on a virtual machine, please consider to choose the “thick provisioning” option or the “allocate all disk space” option.

This is because the choose of “thin provision” or non “allocate all disk space” option may slow down disk performance when data growth.

Please also consider to run the user home on a dedicated virtual disk, which

is configured on fast and non-busy physical disks.

4.3.5 Cloud Storage

If you consider to host a service instance on cloud, you need to setup cloud storage for your user home, predefined destination or replication home as

well.



5 Network and Firewall Settings

5.1 Overview

In this section, we shall further discuss on the network and firewall settings required for the AhsayCBS, include the access to the web interface, license

activation, backup and restore process, email port settings and replication port settings.

As a prerequisite, a fixed remote IP and internal IP are required for the AhsayCBS. Also, the firewall should support the TLSv1 cryptographic protocol.

5.2 Network

5.2.1 Use a Static IP Address

The use of dynamic IP addresses for AhsayCBS domain names may result in an unstable backup service, or replication process restarting whenever the IP

address re-cycles.

A static IP address will ensure the remote IP address sent by AhsayCBS to the Ahsay license server will remain the same during daily routine license checks. This will avoid potential license errors, i.e. 1011 or 1012 license

errors which could result of the automatic shutdown of your AhsayCBS service.

It is strongly recommended to use a static IP address for your AhsayCBS server to ensure a stable and reliable backup service.

5.2.2 Network Load Balancing Configuration

For AhsayCBS servers which are configured with network load balancing, i.e. a dual WAN router or Round Robin routing. A static route should be

configured for your AhsayCBS server connection to the Ahsay license server (lic.ahsay.com). This will ensure the remote IP address sent by AhsayCBS to the Ahsay license server will remain the same during daily routine license

checks. This will avoid potential license errors, i.e. 1011 or 1012 license errors which could result of the automatic shutdown of your AhsayCBS

service. In addition, any switching between the two network connections will cause

connection problems between Backup Server and Replication Server due to the change in IP address. This will result in the replication process restarting

itself.



5.3 Firewall

5.3.1 Settings

After you have finished setting up your AhsayCBS server, please ensure you have updated your firewall settings to allow network traffic through the following ports:

Port Description

80 HTTP port for incoming backup and restore traffic, browsing the AhsayCBS web interface.

443 HTTPS port for incoming backup and restore traffic, browsing the AhsayCBS web interface.

25 Outgoing SMTP port to the SMTP server.

Any incoming

TCP port(s)

Any incoming TCP port(s) used by the receiver(s) on the

Replication Server, e.g. 9444, 9445…

5.3.2 Expose Only TCP Port 80 and 443 to the Public

It is recommended to expose only TCP port 80 and 443 to the public on your

firewall. Please consult the user’s manual of your firewall for more information on how to do so.

5.3.3 Restricting Access on Administration Panel

For security reasons, we would recommend that the Administration Panel of AhsayCBS must be hidden from public access, i.e. it should be exposed to local area network only, or you may restrict a range of IP addresses to access

your AhsayCBS management console. For further information, you can follow our instructions in the following chapter “Restricting access to system page

by IP address”.

5.3.4 Replication Using Cross Over Cable

It is not recommended to setup a Backup Server and a Replication Server using a cross over cable for replication. As from our experience this setup will

result in connection and performance issues.

If the Backup Server and the Replication Server are located on the same site they should be connected via a switch.



6 Deployment

6.1 Installation

Before you install your AhsayCBS, please also reference to the following sections.

Hardware Requirements

Network and Firewall Settings

6.1.1 Windows

1. Download the cbs-win.exe from our website.

2. Run the downloaded installer.

3. Choose the language, then click [OK] to continue.

4. Click [Next] to continue.

5. Read the license agreement. Select “I agree the agreement” if you agree, then click on [Next] to continue the installation.

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



6. Choose the installation directory, then click [Next] to continue.

7. Click [Next] to continue.

8. Enter the ports to be used by AhsayCBS. By default, the ports are 80 and 443 (Http and Https respectively). If these ports have been used by



other applications, eg. Microsoft IIS, Apache or other applications. Please use alternative ports such as 8080, 8443, then click [Next] to

continue.

9. Click [Install] to start the installation.

10. Click [Finish] to complete the installation.



6.1.2 Linux/FreeBSD/Solaris x86

Assumption: ifconfig is already configured on the Linux server.

1. Download the installation filer (cbs-nix.tar.gz) from our website.

2. Logon as root user in the Linux machine.

3. Define the directory you would like to install the software by setting

CBS_HOME environment variable. For example, to install AhsayCBS to /usr/local/cbs , please do the followings:

# CBS_HOME=/usr/local/cbs;export CBS_HOME

4. Copy the installation file (cbs-nix.tar.gz) to %CBS_HOME% and untar it.

# mkdir $CBS_HOME

# cp cbs-nix-tar.gz $CBS_HOME

# cd $CBS_HOME

# gunzip cbs-nix.tar.gz

# tar -xf cbs-nix.tar

Once the untar process has completed, please check that the directory

listing is similar to the image below.

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



5. Install and startup the AhsayCBS service by the following command:

# /usr/local/cbs/bin/install.sh

After executing the command, you should see the following output.

Note: It has been found on some systems, the installation may appear

to pause after displaying “Starting AhsayCBS service”. If this occurs, please press the space bar to complete the installation.



6. AhsayCBS should be started automatically. To verify that, please point your web browser to http://<your-backup-server>/ .

6.2 Upgrade/Migration

6.2.1 Upgrade/Migration from version 6

AhsayCBS has been totally re-designed from the ground upwards to provide

the best cloud backup solution with changes to core functions, such as file storage system, indexing, backup set features, replication, group policy, system user and branding.

We strongly recommend that you clone your current setup to a non-

production environment that will allow you to learn, understand and test the upgrade scenario thoroughly.

You also need to aware the new changes and allow sufficient time to communicate any possible changes and implications to your clients regarding

the changes to their backups in v7. For more details, please refer to our upgrade and migration guide for details.

6.2.2 Auto upgrade and OEM handling

Since the branding and generation of new installers can be handled through the AhsayCBS management console. You can refer to chapter 4.3 and

chapter 5 of our upgrade and migration guide for details.

http://www.ahsay.com/download/download_document_cbs-upgrade.jsp

http://www.ahsay.com/download/download_document_cbs-upgrade.jsp



6.3 Uninstall

This section outlines all the steps required to uninstall AhsayCBS from the

system.

6.3.1 Windows

For Windows platform, there are 2 methods to perform uninstall of AhsayCBS.

If the installation was performed using the installer (cbs-win.exe file) then it is recommended to use Method 1 to perform uninstall. If the patch file was used for the installation, please use Method 2 to uninstall.

Method 1 – Auto Uninstallation

1. Go to [Start Menu] -> [Programs] -> [AhsayCBS] -> [Uninstall].

2. The uninstall wizard will be shown on the screen.

3. Click [Yes] to start uninstalling AhsayCBS.



4. Once the uninstall has completed, the system would show the following

dialog box. Please click on the [OK] to continue.

The system would automatically open a window to the installation path, so that the USER_HOME, SYSTEM_HOME and POLICY_HOME can be copied/backed up if required.

5. AhsayCBS is now removed from your system.

Method 2 – Manual Uninstallation

1. Open command prompt and change the working directory to %AhsayCBS_HOME%\util\bin

cd "c:\Program Files\AhsayCBS\util\bin"

2. Run the following command within the command prompt would remove

the service for AhsayCBS:

service.exe –r <Service Name>



Where:

Parameter “-r” means removing the service and parameter.

<Service Name> - is the name of the service.

For example, in our case, we should run the following command:

A message of “AhsayCBSServer removed” as shown below will be

displayed on the screen to advise that uninstall of the service has been successful.

3. Backup the files that you would like to keep, e.g. USER_HOME, SYSTEM_HOME and POLICY_HOME.

4. Remove the %AhsayCBS_HOME% directory if necessary and AhsayOBSR is now removed from your system.

6.3.2 Linux/FreeBSD/Solaris x86

To uninstall AhsayCBS from a Linux, Solaris or FreeBSD system, please follow the steps below.

1. Logon as root to the Linux/Solaris/FreeBSD machine.

2. Move to the $AhsayCBS_HOME directory and run the uninstall script

using the command shown below.

cd /usr/local/cbs

sh ./bin/uninstall.sh



3. The following output would appear after running the script. The script would stop AhsayCBS service and also remove the startup script so that

the service will not start at boot up.

4. Make a backup of your existing $SYSTEM_HOME, $USER_HOME and $POLICY_HOME directories to another computer if necessary.

5. Remove the $AhsayCBS_HOME directory from the system. Once done, AhsayCBS will now be removed from your system.



7 Backup Server Configuration

7.1 License

This chapter describes how you can use the [System Settings] -> [License] page to manage software license of AhsayCBS.

7.1.1 Licensee Name and License Key

When you click the [System Settings] -> [License] link on the AhsayCBS, the [Backup] license panel will appear. You can use the form available on this panel to activate the software.

Please remember the following notes when you enter your licensee name and

your license key:

Both [Licensee Name] and [License Key] are case sensitive and they

must be entered EXACTLY as stated in your software receipt. If possible, please use copy and paste shortcuts (CTRL-C and CTRL-V)

to enter both the [Licensee Name] and [License Key] into the field provided to avoid typographical error.

There is a connection test button underneath the license field entry box to test the connection to our license server. The testing result will be popped up on the screen.

The AhsayCBS server is required to access internet and connect our license server lic.ahsay.com using the https protocol. Please ensure

firewall settings is enabled and the TLSv1 setting is allowed. If a proxy server is required to access the Internet from AhsayCBS,

please setup the proxy setting in the [System Settings] ->

[Advanced] -> [Proxy] page. Access to the internet is required because the license key must be activated by our license server

before it is usable. If internet connection is not available in your environment, you can

use the offline activation method to activate your license. Please

contact us to activate your offline license file if you run into this situation.

One license key can only be used on one machine once it has been activated. If you use the same license key to activate another copy of AhsayCBS on another server, you will get an "Internal Error

1011" or "Internal Error 1012" message. You can still run this copy of AhsayCBS for another 7 days without any problems but it will

stop working after this grace period. Please contact us to re-activate your license key if you run into this situation.



To activate license

1. Open the AhsayCBS from your browser eg: http://<your-backup-server>

2. Login the AhsayCBS with the default password, i.e. “system”

3. To activate the license, click on the [License] button.

4. Click on the [Backup] tab.

5. If you are evaluating the AhsayCBS, you can use the evaluation license provided in the page. Go to step 7.

6. If you have a purchased license, copy and paste the licensee name, license key into the relavent field.

7. Click on [Update] button.

8. Click [Save] to save the settings on the AhsayCBS.

Note:

If you are using the evaluation license, you will be able to evaluate the

AhsayCBS for 60 days. If you need to purchase the license CAL, you can contact our sales for more information.

7.1.2 Automatic License Renewal

If AhsayCBS is under a monthly leasing plan, the license key will have an

expiry date of 30 days. Upon expiration, the license key will be renewed automatically.

In the event of any problems during the license renewal process, i.e. AhsayCBS is not able to connect to the Ahsay License server. The expired

license key will have a grace period of 14 days. AhsayCBS can still function normally using the expired license for an extra 14 days before the service is

automaticially shutdown. The 14 days grace period is to allow sufficient time to resolve any license related problems.

https://help.ahsay.com/



7.1.3 Evaluation Expiry

After the evaluation period, the evaluation key will expire and the AhsayCBS

will automatically be stopped. Although the service will still be alive, AhsayOBM and AhsayACB cannot do backups anymore.

If you want to continue using AhsayCBS, you can contact our Sales Team via our forum.

7.1.4 Offline License Activation

Offline License Activation is used to activate the AhsayCBS license for servers that do not have internet connection.

After you have finished installing the AhsayCBS, please open the web management console and go to the backup server license page ([System

Settings] -> [License]). On that page, you should be able to see the [Off-line License Request] in the middle of the page. Please click on the [Generate] button to generate the offline license request file.

This file is an encrypted file that contains all the information required for the

activation process, e.g. MAC address and local IP address, and it will prompt for the location to save the offline license request file.

When the offline license request file is ready, please send it to our Support team via email. An offline license file will then be generated and sent back to

you. The offline license file is the license file used in the offline license activation process.

After you have received the offline license file, you would need to import it to the AhsayCBS to complete the offline activation process. Before importing the

offline license files to AhsayCBS, you must ensure that it is placed in the system home folder of AhsayCBS. Then, you should logon to the AhsayOBS

web interface to import the license from the backup server license panel (i.e. [System Settings] -> [License] -> [Backup] -> [Import License]. Click on the [Browse] button and select the offline license file from AhsayCBS system

home. Click on the [Off-line Update] button to complete the process. If there is no error message shown on the License panel, the Offline License

Activation process is completed successfully.

http://www.ahsay.com/jsp/en/contact/kbQuestion.jsp



7.1.5 License Management Portal

The Ahsay License Management Portal is for partners to:

Consolidate purchased Backup Server licenses into License Pool(s). Flexibly generate and update Backup Server license(s) as requirement

change. Improve efficiency on use of Backup Server licenses by sharing CALs

(Client Access License) in license pool among multiple Backup Server instances.

With the Ahsay License Management Portal , partners can place purchased

Backup Server licenses (Poolable License) into a pool to be shared among multiple Backup Server instances. This process is called converting Poolable

License into Pooled License. For example,

If you have the following 2 licenses:

LICENSE001 - 50 ACB and 80 OBM LICENSE002 - 20 ACB and 30 OBM

You can put these 2 licenses into a single license pool so that you can

generate a new license with a maximum of 70 ACB and 110 OBM license CALs or any number of new licenses within these available license CALs.

For more information about the Ahsay License Management Portal, please refer to the following forum articles:

FAQ: Ahsay License Management Portal Overview

FAQ: How to create a Pool Key from a License Pool

http://lic.ahsay.com/als/sp/login.do

http://lic.ahsay.com/als/sp/login.do





7.2 Setup email/report

The [SMTP Server] settings under the [System Settings] -> [Basic] -> [Email]

page defines the various email setting that AhsayCBS will use to generate email reports to backup system administrator and backup users.

SMTP Servers Multiple SMTP servers can be setup for AhsayCBS. If the first SMTP server is

unavailable, the next SMTP server will be used.

Note: If you don’t have an SMTP server, you can consider using a free SMTP such as gmail.

To avoid your report emails being filtered by the SMTP server or mail client,

you need to enter a valid report sender in the email settings.

Digital signing all outgoing email If you want to increase the security of the emails, you can digitally encrypt

those emails with the public key and it can only be opened by recipients who have the correct private key.

Note: Digitally signing an email is not the same as including a signature in

outgoing email, it is a digitally signed email which can come only from the owner of the digital ID. This provides verification of the sender’s

authenticity and also helps to prevent email tampering. You need to apply the digital ID from your organization’s administrator.

Administrator Contact

This entry defines the administrative contact of AhsayCBS. AhsayCBS will send usage, error and all critical system alerts to all email addresses defined here.



7.3 Setup Predefined Destinations

Predefined destination defines a list of local directories, FTP or cloud storages

in which the Backup Server, Replication Server, users and sub admin can be used to store backup or replication data. It can be defined in the AhsayCBS

management console > [System Settings] > [Basic] > [Predefined Destinations].

Before you create a user, you need to setup a user home. User home is a folder or path to store users’ backup data and settings, you can setup user

homes in [Backup/Restore] > [Basic] > [User home]. In addition, you can also create predefined destinations for your users to backup.

Setup a backup destination on cloud storage

We allow setting a backup destination on some common cloud storage, local hard disk and FTP servers. The setup method is similar on different cloud storage. We have selected Google drive for your reference.

Example (Google Drive):

1. Enter name of the backup destination.

2. Select “Single storage destination”.

Note: The option “Destination Pool” is defined from a number of single storage destination.

3. Select 'Google Drive' from the [Destination storage] drop down box.

4. If you do not have the Google Drive, please click on the link 'Sign up for Google Drive' to create an account.

5. Click [Add] to continue the setup.

6. A browser will popup and Google will ask for your permission to access the storage, click on "Allow".

7. On the browser, a code is displayed, copy it and paste into the create predefined destination page in the AhsayCBS.

8. Click [Add] to continue.



7.4 Create Users

7.4.1 General users

Before your client backup to the Backup Server, you need to create a backup account for your backup client. A backup account is a user profile which contains user’s account information, client type, backup modules and backup

set settings etc. A backup account can be created by administrator or registered via the backup client application.

You can create a new user account in [Backup/Restore] > [User, Groups & Policies] > [Backup User].

If your company purchased our product for internal use, as a system

administrator, you need to determine the following when you create a backup account: Backup client type, whether AhsayOBM or AhsayACB

The backup destination.

If you are a reseller of our product, you may require taking consideration on the below items when you create a user account:

Type of users, whether a “Paid” or “Trial” user. Backup client type, whether AhsayOBM or AhsayACB, and the module

subscribed. The backup destination and the subscribed quota. Payment method.

Selection of “Paid” or “Trial” User Type The selection of “Paid” or “Trial” user type would always refer to backup clients who wants to subcribe the backup service offered by our resellers.

These 2 user types differ in the following ways:

Trial users can only have a maximum backup quota of 100GB within the trial period.

Trial users subject to automatic removal as defined by the [Free Trial Registration] setting (though automatic removal can be disabled).

Other than the differences listed above, both trial and paid users are the same in all other areas.

Selection of AhsayOBM and AhsayACB

If the backup client machine requires to backup files only, such as a desktop computer or a notebook, then you can simply create an AhsayACB backup

account. Otherwise, you will need to setup AhsayOBM, because it comes with backup modules to perform Windows system backup, database backup and virtual machine backup.



Selection of Backup Destination In previous version, when you setup a local backup machine in your server

room or data center, you may consider storing all the backup data in your local hard disk or the storage device attached to the backup server. You may

experience user home migration when the storage device is full. Although you can expand your storage by adding more disks into your storage volume, you

may experience other limitations such as not enough hard disk bays or the hardware cannot support larger hard disk.

In AhsayCBS v7, we have provided other options such as storing your backup files on FTP servers, cloud storages such as Google cloud, Dropbox, Amazon.

7.4.2 System users

There are several types of system users that you can create in the AhsayCBS

to help you on monitoring the AhsayCBS or acting as a resller (sub admin) to keep your business growth. You can setup these systems users in [System

Settings] > [Basic] > [Administrative Access].

"Admin" role has the same privilege as the build-in "system" account. For example, you can assign this account for your administrator(s) to configure/administrate the AhsayCBS for you.

"Read-only Admin" role system user shares the similar accessibility as its

creator except with read permission only. "API" user has the full access right to the system, it has the same privilege

as the build-in "system" account. This account is created for programmers which required to put the API user name and password into their program

source. "Sub Admin" user has the full access right to the users that was created

under this sub admin and has the right to manage the backup and restore jobs/activity similar as the system administrator with less admin options.



7.5 Free trial

The [Free Trial Registration] settings under the [Backup/Restore] -> [Basic] -

> [Free Trial Options] page defines various free trial settings available in AhsayCBS.

Trial users do not count towards the maximum number of users allowed within AhsayCBS by the software license and there can be unlimited number

of trial users within AhsayCBS. However, each backup user can have a maximum backup quota of 100GB for a trial period of 90 days. After

expiration of the trial period, the backup quota will reset to a maximum of 500MB automatically.

To allow users to create a trial backup account from AhsayOBM or AhsayACB, please enable the [Enable Free Trial Registration] option. If this feature is

unchecked, the option to register for a trial account will not be available to end users.

The [Backup Quota] defines the maximum backup quota of trial backup accounts upon registration.

The [Add-on Modules] option defines whether you want to allow trial users to

have different add-on modules. The [User will be suspended] option defines after eg: 30 days, the trial users

will be suspended.

The [Remove User] option defines whether you want to remove trial backup users for certain number of days after registration. For example, you can use this option to tell AhsayCBS to remove trial backup users from the system

automatically after backup users have registered for 60 days.

7.6 Languages

In [System Settings] -> [Basic] -> [Languages], you can manage the

languages that will be availbel to your users. The default language will be used in all reports. You can simply drag your preferred default language to the top of the list.



8 Advance Backup Server configuration

8.1 Auto Save

When this feature is enabled in [System Settings] -> [Advanced] -> [Auto Save], the system will automatically save all the settings in this server to the

software vendor's cloud so that you can restore those settings in the future when needed.

The following are the system configuration that will be saved on the cloud:

Server configuration (server.xml, licenses) Backup Server Configuration

Replication Configuration Redirector Configuration Backup Server's User Profile

8.2 Proxy

The Proxy settings under the [System Settings] -> [Advanced] page defines whether AhsayCBS should use a proxy to gain access to the internet.

Two types of proxy, HTTP/HTTPS and SOCKS 4/5, are supported. You can use the [Proxy Host] and [Port] entries to define the location of your proxy server.

If the proxy server you are using requires user authentication, please use the

[Proxy Username] and [Proxy Password] entries to set the username/password for your proxy server.

Note: Please make sure there are no traffic restictions on the proxy server, which

could affect backup/restore performance.

8.3 Logging

In [System Settings] -> [Advanced] -> [Logging] page, we provided 2 types

of third monitoring support, SNMP and Windows Event Log.

8.3.1 SNMP

For the SNMP, you can download the MIB definition file and import to your SNMP application.



8.3.2 Windows Event

For AhsayCBS installations on Microsoft Windows platform which have the

"Windows Event Log" service enabled, all AhsayCBS system log information such as error, warning, and information message types will be also be written

to the Windows event logs. The backupserver administrator's can view the logs entires using the Windows event viewer. The event log name is limited to 8 characters.

8.4 File Explorer

The File Explorer in [System Settings] -> [Advanced] page allowed administrator or support staffs to check, download log files and configuration

files in your AhsayCBS. Three major paths are enabled to download.

AhsayCBS home AhsayCBS system home AhsayCBS user homes

8.5 Runtime Options

The runtime options in [System Settings] -> [Advanced] page allowed administrators to modify Java options such as Java heap size (maximum and

minimum), thread stack size and IP allowed to access the AhsayCBS management console.

8.6 User Group

User Group in [Backup/Restore] -> [Users, Group & Policies] is used in conjunction with Group Policies for governing the behaviour of client backup applications.

8.7 Policy Group

Policy Group in [Backup/Restore] -> [Users, Group & Policies] is designed to simplify administration and to reduce the effort required for managing groups

of backup users, e.g. security settings and backup set settings. It allows administrator to tailor features and services for different user groups.



8.8 Windows Active Directory Integration

When Windows Active Directory Authentication is enabled in [Backup/Restore]

-> [Users, Groups & Policies] -> [Windows Active Directory Integration], user authentication will be dispatched to Windows Active Directory (AD)

automatically if AhsayCBS fails to authenticate a user logon using its own records. This means that if an AD is presented in the network, it is only required to create a user account once in AD and the same user account can

also be used in AhsayCBS, because AhsayCBS will create this user account automatically after authenticating this logon using AD. The user account

created will be of "Paid" type and of "AhsayACB" backup client (unless the user logons using "AhsayOBM").



9 Configure Replication

Replication Server provides an additional layer of data protection by providing an offsite backup store for backing up data from either a single or multiple AhsayCBS servers. The Ahsay replication process is close to real-time and

hence this will reduce the probability of significant data loss in the event of an AhsayCBS outage.

It is specially designed for replicating AhsayCBS user home data to another AhsayCBS (Replication Server) or cloud storage. It is designed to provide

replication services for AhsayCBS only and it does not provide general replication service for other files within the system. This means that you

cannot use AhsayCBS replication to replicate your Windows/Linux/Unix server to another machine.

It is platform independent as the Replcation Server supports Windows, Linux, FreeBSD, or Solaris x86 platforms. This means that you can have AhsayCBS

running on Windows and another AhsayCBS running on Linux/FreeBSD/Solaris x86 or other possible combinations. It has the following benefits over using other external synchronizing software (e.g.

rsync or Microsoft Replication Services) in the context of replicating backup data on AhsayCBS to another server.

When a backup traffic arrives at the Backup Server, it is automatically put into the replication queue. Data in the replication queue are replicated to

another AhsayCBS (Replication Server) or predefined storage immediately. No replication schedules or extensive checking of whether each file should be

replicated are required.

9.1 Sending Data

Although both Replication Server and Backup Server modules in the

AhsayCBS. It is not recommended to configure and use both services on one machine, as it will completely defeat the purpose of Replication Server as a backup or standby server to your AhsayCBS.

To send the backup data to another AhsayCBS

1. Please configure a receiver account on another AhsayCBS first, refer to the next section for details.

2. In your AhsayCBS, enter [Replication] > [Sending Data] .

3. Turn on the “Replicate backed up data to another server or predefined

cloud storage”.

4. Select the option “To another AhsayCBS”.



5. Enter the host name, port, replication user name and password, the replication user name and password is the login credentials that was

created in another AhsayCBS in step 1.

6. Click the [Save] button.

To send the data to a predefined destination

1. You need to create a predefined destination in [System Settings] >

[Basic] > [Predefined Destination] first.

2. In your AhsayCBS, enter [Replication] > [Sending Data] .

3. Turn on the “Replicate backed up data to another server or predefined cloud storage”.

4. Select the option “To a predefined destination”.

5. Click the [Save] button.

Traffic limit

You can use setup the traffic limit in the same page to limit the amount of bandwidth used by replication traffic between specified times. Traffic Limit is

an optional setting.

Replicate individual backup sets

It is possible to select specific users and their backup sets from AhsayCBS to replicate on another AhsayCBS or the predefined destination, instead of just replicating all users on all the user homes.

9.2 Accepting Data

Before other AhsayCBS or previous version of backup server can replicate the data to this AhsayCBS, a receiver user account needs to be created.

Click into the [Replication] > [Accepting Data] > [Manage Receiver] to create

a replication user account in the AhsayCBS.

1. Click on the add button in Manage Receiver section.

2. Set the login name, password and alias.



Configure the source backup server settings

3. Select the source backup server host settings such as the http/https

protocol, source backup server host name and port mumber.

4. Select the source backup server version. If you select “7”, it means the

source backup server is a version 7 backup server, and you need to enter the system user name and the system password of the source backup server.

If you select “Before 7” as the backup server version, enter the bind to IP address and the replication port. “0.0.0.0” and “9444” are the

default values, you can assign a specific IP if you have multiple network cards, and for multiple backup server’s replication, an unique replication port number is required to set such as “9445”.

Retention Settings

5. Configure the restore point interval. It is the minimum number of days between each retention snapshot. A retention snapshot will be created

when data is received and time interval between current time and previous snapshot is over the specified period. No retention snapshot

will be created if data is not received even when time interval is over.

6. Configure the retention customization policy. It is the number of days the old copies of updated or deleted files are to be retained in the

retention area.

With the default settings ie, 30 days for the Restore Point Interval and 60

days for the Retention Customization Policy, a total of 3 restorable snapshots are available.



10 Configure Redirector

You are able to build a highly scalable backup system by enabling the High Scalability feature. With the feature enabled, you are able to use multiple backup servers with a single URL and all your customers will not know which

AhsayCBS is backing up on.

For example: The URL of your redirector is www.mybackup.com . All the AhsayCBS backup

servers are connected to this redirector and their name can be assigned as follows:

server1.mybackup.com server2.mybackup.com

server3.mybackup.com :

:

No matter where a customer is stored in one of these AhsayCBS servers, the

backup server URL in your client application should set to www.mybackup.com only. You can add AhsayCBS server to this redirector in

case the physical limit of this AhsayCBS server is reached. To setup this backup environment, you need to assign one of your AhsayCBS

server as a Redirector host, and all other AhsayCBS will be joining to this Redirector host.

10.1 Hosting a Redirector

First of all, you need to assign an AhsayCBS to be setup as a Redirector role. You need to register your Backup Server with the Redirector in AhsayCBS

management console > [Redirection] > [Hosting a Redirector].

1. Add a Backup Server in the Redirector, enter the login credentials and

host name, and the ports of that Backup Server.

2. Repeat the above steps until all the Backup Servers in your environment

are registered with the AhsayCBS with the Redirector role.

3. Option: You can dedicate one of the AhsayCBS (Backup Server) to host free trial users, by enabling this feature and assign one of your Backup

Server in the list.

http://www.mybackup.com/

http://www.mybackup.com/



10.2 Joining Redirector

To join your Backup Servers to a Redirector, please enter your AhsayCBS management console > [Redirection] > [Joining Redirectors] .

1. Turn on the high scalability feature.

2. Enter the host name, and port number of the Redirector machine.

3. Enter the login credentials to the Redirector machine.

4. Enter the Administrator Hostname, this is the host name of the

Redirector, and you can setup your backup clients with this administrative hostname.



11 Operation

11.1 Monitoring

11.1.1 Setup a Read-only Admin Account for Operators

For daily monitoring on the AhsayCBS management console, you can assign your staffs/operators with a read-only admin role account in [System

Settings] -> [Basic] -> [Administrative Access]. This read-only admin role system account share similar accessibility as its creator except with read

perssion only. They can help you to do monitoring on the backup and restore jobs, Live Activities on the AhsayCBS server, Administration logs and reporting etc.

11.1.2 Build in Monitoring Tools

In the AhsayCBS management console, we have developed some useful

monitoring pages for you or your operators to check on the live status of your AhsayCBS.

Dash Board - you can get a summary of the current status of your AhsayCBS. For example, you can check the announcement from us, a

summary of the backup error and warnings, system resource settings, CPU and memory usage, disk usage and live threads usage.

Live Activities – you can check on recent backup and restore status with the progress monitor in percentage, replication (both send and receive) and

redirection status.

Administration Logs – you can check on the SNMP logs, list of notifications/announcements/alerts, and activities log (system logs) and audit

trails. Backup/Restore Logs – you can check on a list of backup and restore jobs,

backup erross, backup set logs, and activities logs.

Replication Logs – you can check on both send and receiver logs, and activities logs.

Redirection Logs – you can check on the redirection activities logs.

11.1.3 Enable thirty monitoring tools

You can setup thirty monitoring tools such as SNMP and Windows Event Log (Windows only) in [System Settings] > [Administrator] > [Logging]. For

more details, please refer to our previous chapter.



12 Advanced AhsayCBS Configuration

12.1 Listening to non-standard TCP/IP Port

If you like to run your own web server, or some other services using port 80 and 433. On your AhsayCBS server, you can change the listening TCP/IP port

of AhsayCBS from port 80 and 443 to some other port numbers such as port 8080 and 8443, you can modify the connector settings from the AhsayCBS

management console > [System Settings] > [Basic] > [General] > [Connectors], and modify your new port in the connector settings.

12.2 Listening to a single IP address

If the backup server has more than one network interface installed or has

more than one IP address bind to a single network interface, you can configure AhsayCBS to use only a single IP address for backup services (by

default the TCP port of all IP addresses available within the system are used and open). This has the benefits of sparing other IP addresses for other applications, e.g. Apache Web Server or Microsoft Internet Information

Server (IIS). You can modify the connector setting from the AhsayCBS management console > [System Settings] > [Basic] > [General] >

[Connectors], and modify the IP address in the connector settings.

12.3 Restricting access to system page by IP address

For better security, you can restrict access to the AhsayCBS management

console by IP addresses. To do so, please add IP restriction in your AhsayCBS management console > [System Settings] > [Advanced] > [Runtime Options] > [IP Restriction]. You can enter a range of IPs or a specific IP in the restrict

IP settings.

12.4 Secure connection with AhsayCBS

12.4.1 Installation a trusted SSL certificate

Default installation of AhsayCBS enables SSL (Secure Socket Layer) support using a dummy certificate. For your own security, you are advised to replace the pre-installed dummy SSL certificate with a secure SSL certificate from a

trusted CA (Certificate Authority). To replace the non-secure dummy SSL certificate with a secure SSL certificate, please perform the following in your

AhsayCBS.



1. Enter [System Settings] > [Basic] > [General] > [SSL certificate].

2. Generate a CSR to apply the SSL certificate from your trusted CA.

3. When the SSL certificate is ready, import the SSL certificate.

12.4.2 Renew a trusted SSL certificate

When your SSL certificate is due to expire, you can renew your SSL cert via

your CA’s website. Your CA may ask you to use existing CSR that you submitted previously or submit a new CSR.

If you decided to use a new CSR, most likely the information on the old CSR is not up-to-date. Most CA will not consider this as a renew process

and you need to start from the beginning of a certificate process described in previous section.

If you purchase a renew SSL certificate with the existing CSR, wait for

your CA to sign the renew SSL certificate.

Note: The renewal process may be different for different CA. You need to follow your CA’s instruction on the renewal process.

The import step of a renewed SSL certificate is similar to the installation of a SSL certificate. Please perform the following in your AhsayCBS.

1. Enter [System Settings] > [Basic] > [General] > [SSL certificate].

2. Import the SSL certificate.

12.4.3 Wild card SSL certificate with redirector setup

In the Redirector with a number of Backup Servers setup scenario, you need to apply a wild card certificate for all your AhsayCBS servers. The application

of the wild card certificate is the same as a normal certificate except the common name needs to enter *.backup.com instead. To apply a wild card

certificate for all your AhsayCBS servers, please perform the following:

1. In the AhsayCBS with the Redirector role, enter [System Settings] > [Basic] > [General] > [SSL certificate].

2. Generate a CSR with the common name set to eg: *.backup.com , and apply the SSL certificate from your trusted CA.

3. When the SSL certificate is ready, import the SSL certificate.



4. Copy the SSL certificate, private key and the CA certificate file from your AhsayCBS_HOME/conf/cert folder and transfer to your AhsayCBS

with Backup Server role. They are named similar as the following:

Eg:

1449049185371.crt

1449049185371.key

1449049185371.ca

5. Import these 3 certificate files in one of your AhsayCBS (Backup Server role) in the [System Settings] > [Basic] > [General] > [SSL certificate].



13 Branding the AhsayCBS

This chapter will describe the steps to brand the AhsayCBS If you want a hassle free upgrade experience, you may consider to

subscribe our hassle free upgrade and branding service. Please check the service details on our website.

13.1 Brand the AhsayCBS interface

After you have installed the AhsayCBS, you can upload the graphics

1. Stop the AhsayCBS service

Windows

Stop the AhsayCBS service from the Services management console,

this can be reached from [Control Panel] > [Administrative Tools] > [Services]. Press the [Stop] button to stop this service.

Linux, Solaris x86 or FreeBSD

Run the command in AhsayCBS_HOME/bin/shutdown.sh

2. Open the properties file in “AhsayCBS_HOME\webapps\cbs\WEB-

INF\classes\cbs-jsp_en.properties” with a text editor such as Notepad ++

Note: The “en” in the file name cbs-jsp_en.properties refers to the

properties file for English language.

3. Search for the properties with Ahsay wordings and change it to your product name.

4. Start the AhsayCBS service

Windows

Start the AhsayCBS service from the Services management console, this can be reached from [Control Panel] > [Administrative Tools] > [Services]. Press the [Start] button to start this service.

Linux, Solaris x86 or FreeBSD

Run the command in AhsayCBS_HOME/bin/startup.sh

6. Login to the AhsayCBS management console.

7. Click in [System Settings] > [Basic] > [Administrative Access]

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_services_hassle-free-upgrade

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_services_rebranding_software-rebranding

http://www.ahsay.com/



8. Click on the system user or the reseller system user that you need to

brand the AhsayCBS.

9. Click on the [Rebrand Web Console] and upload the graphics.

Note: Please refer to the branding image specifications listed on the

image upload page.

10. Open the AhsayCBS management console in your browser. You will be

able to see the branded images and properties name from the interface.

13.2 Prepare the branding for the AhsayOBM/AhsayACB

To brand the AhsayOBM/AhsayACB

1. Login to the AhsayCBS management console.

2. Click in [System Settings] > [Basic] > [Administrative Access]



3. Click on the system user or the reseller system user that you need to brand the client.

4. Click on the [Branding Clients], you can custom the properties, apply the OBM, ACB settings, and upload OBM and ACB branding images.

Note: Please refer to the branding image specifications listed on the

image upload page.

5. Option: Click on the [Digital Signature] if you need to generate the

installers with your digital certificate.

6. Click on the [Build Installers], AhsayCBS will request our customization

portal to generate new installers.

7. Wait until the build installer progress to complete.

8. Download new installers from your AhsayCBS.

9. After you tested your installers, you can enable the client auto-update

or update your client manually. Please check the next chapter on how

to update your clients.



14 API

In this release, new APIs (now in JSON format) are introduced in the

AhsayCBS, if you have written API in previous version, please test and modify your API calls on AhsayCBS v7.5 in your testing environment first, so that it

will not affect your current CRM, billing systems etc when new AhsayCBS is upgraded. Please download the AhsayCBS API guide from our website for reference.

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_documentation_guides



15 Further Information

If you have any question or suggestion about this document, please send an email to our support team via our forum.

http://forum.ahsay.com/



Appendix Appendix A Supported Language Code Language Code Language ca Catalan

da Danish

de German

el Greek

en English

el Spanish

eu Euskara/Basque

fr French

iw Hebrew

hu Hungarian

ja Japanese

ko Korean

lt Lithuanian

nl Dutch

no Norwegian

pt_PT Portuguese (Portugal)

sv Swedish

tr Turkish

zh_CN Chinese (Simplified)

zh_TW Chinese (Traditional)



Appendix B Supported Time zone

Timezone String Timezone Name

GMT-11:00 (WST) Western Standard Time

GMT-11:00 (NUT) Niue Time

GMT-11:00 (SST) Samoa Standard Time

GMT-10:00 (HADT) Hawaii-Aleutian Daylight Time

GMT-10:00 (HST) Hawaiian Standard Time

GMT-10:00 (TKT) Tokelau Time

GMT-10:00 (HST) Hawaiian Standard Time

GMT-10:00 (CKT) Cook Islands Time

GMT-10:00 (THAT) Tahiti Time

GMT-09:00 (AKST) Alaska Standard Time

GMT-09:00 (GAMT) Gambier Time

GMT-08:00 (PST) Pacific Standard Time (North America)

GMT-07:00 (PDT) Pacific Daylight Time (North America)

GMT-07:00 (MST) Mountain Standard Time

GMT-07:00 (MDT) Mountain Day Time

GMT-06:00 (CST) Central Standard Time

GMT-06:00 (CDT) Central Daylight Time

GMT-06:00 (EAST) Easter Island Time

GMT-06:00 (GALT) Galapagos Time

GMT-05:00 (EST) Eastern Standard Time (North America)

GMT-05:00 (EDT) Eastern Daylight Time (North America)

GMT-05:00 (COT) Colombia Time

GMT-05:00 (ECT) Ecuador Time

GMT-05:00 (CDT) Central Daylight Time (North America)

GMT-05:00 (PET) Peru Time

GMT-05:00 (ACT) Atlantic/Proto Acre

GMT-05:00 (GMT-05:00) GMT -05:00

GMT-04:00 (AST) Atlantic Standard Time

GMT-04:00 (PYT) Paraguay Time

GMT-04:00 (VET) Venezuela Time

GMT-04:00 (GYT) Guyana Time

GMT-04:00 (ADT) Acre Daylight Time

GMT-04:00 (BOT) Bolivia Time

GMT-04:00 (AMT) Armenia Time

GMT-04:00 (CLT) Chile Time

GMT-04:00 (FKT) Falkland Islands

GMT-03:00 (ART) Argentina Time

GMT-03:00 (GFT) French Guiana Time

GMT-03:00 (BRT) Brasilia Time

GMT-03:00 (WGST) West Greenland Summer Time

GMT-03:00 (PMDT) Pierre & Miquelon Daylight Time

GMT-03:00 (UYT) Uruguay Time

GMT-03:00 (SRT) Suriname Time

GMT-02:00 (FNT) Fernando de Noronha Time

GMT-02:00 (GST) Gulf Standard Time

GMT-01:00 (EGST) East Greenland Summer Time



GMT+00:00 (GMT) Greenwich Mean Time

GMT+00:00 (WET) Western European Time

GMT+00:00 (WEST) Western European Summer Time

GMT+00:00 (IST) Israel Standard Time

GMT+00:00 (BST) Brazil Standard Time

GMT+00:00 (UTC) Coordinate Universal Time

GMT+01:00 (CET) Central European Time

GMT+01:00 (WAT) West Africa Time

GMT+01:00 (CEST) Central European Summer Time

GMT+02:00 (EEST) Eastern European Summer Time

GMT+02:00 (CAT) Central Africa Time

GMT+02:00 (SAST) Soft Africa Standard Time

GMT+02:00 (EET) Eastern European Time

GMT+02:00 (IDT) Israel Daylight Time

GMT+03:00 (EAT) East Africa Time

GMT+03:00 (AST) Acre Standard Time

GMT+03:00 (ADT) Acre Daylight Time

GMT+03:00 (MSD) Moscow Daylight Time

GMT+04:00 (AQTST) Aqtau Time

GMT+04:00 (AZST) Azerbaijan Summer Time

GMT+04:00 (GST) Gulf Standard Time

GMT+04:00 (GEST) Georgia Time

GMT+04:00 (AMST) Armenia Summer Time

GMT+04:00 (SAMST) Samara Time

GMT+04:00 (SCT) Seychelles Time

GMT+04:00 (MUT) Mauritius Time

GMT+04:00 (RET) Reunion Time

GMT+05:00 (TMT) Turkmenistan Time

GMT+05:00 (KGST) Kirgizstan Time

GMT+05:00 (TJT) Tajikistan Time

GMT+05:00 (PKT) Pakistan Time

GMT+05:00 (UZT) Uzbekistan Time

GMT+05:00 (YEKST) Yekaterinburg Time

GMT+05:00 (IDT) Indian Standard Time

GMT+05:00 (TFT) French Southern & Antarctic Lands Time

GMT+05:00 (MVT) Maldives Time

GMT+06:00 (MAWT) Mawson Time

GMT+06:00 (LKT) Lanka Time

GMT+06:00 (BDT) Bangladesh Time

GMT+06:00 (NOVST) Novosibirsk Time

GMT+06:00 (BTT) Bhutan Time

GMT+07:00 (ICT) Indochina Time

GMT+07:00 (JAVT) Java Time, Indonesia Time

GMT+07:00 (KRAST) Krasnoyarsk Time

GMT+07:00 (CXT) Christmas Island Time

GMT+08:00 (HKT) Hong Kong Time

GMT+08:00 (CST) Cuba Standard Time

GMT+08:00 (BNST) Brunei Time

GMT+08:00 (WST) West Samoa Time



GMT+08:00 (IRKST) Irkutsk Time

GMT+08:00 (MYT) Malaysia Time

GMT+08:00 (PHT) Philippine Time

GMT+08:00 (SGT) Singapore Time

GMT+08:00 (BORT) Borneo Time

GMT+08:00 (ULAT) Ulan Bator Time

GMT+08:00 (JAYT) Jayapura Time

GMT+09:00 (KST) Korean Standard Time

GMT+09:00 (JST) Japan Standard Time

GMT+09:00 (YAKST) Yakutsk Time

GMT+09:00 (PWT) Palau Time

GMT+10:00 (EST) Eastern Standard Time (Australia)

GMT+10:00 (DDUT) Dumont-d’Urville Time

GMT+10:00 (VLAST) Vladivostok Time

GMT+10:00 (ChST) Chamorro Standard Time

GMT+10:00 (PGT) Papua New Guinea Time

GMT+10:00 (TRUST) Truk Time

GMT+11:00 (MAGST) Magadan Time

GMT+11:00 (VUT) Vanuatu Time

GMT+11:00 (KOSST) Kosrae Time

GMT+11:00 (NCT) New Caledonia Time

GMT+11:00 (PONT) Ponape Time (Micronesia)

GMT+12:00 (NZST) New Zealand Standard Time

GMT+12:00 (ANAST) Anadyr Time

GMT+12:00 (PETST) Petropavlovsk-Kamchatski Time

GMT+12:00 (FJT) Fiji Time

GMT+12:00 (TVT) Tuvalu Time

GMT+12:00 (MHT) Marshall Islands Time

GMT+12:00 (NRT) Nauru Time

GMT+12:00 (GILT) Gilbert Island Time

GMT+12:00 (WAKT) Wake Time

GMT+12:00 (WFT) Wallis and Futuna Time

Appendix C Product Documentations Please visit this link for the documentation of Ahsay Products.

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_downloads_documentation_guides



Appendix D Error Code 1011 and 1012 Internal Error 1011

This error could occur when one of the following conditions is true:

1. The license key has been used on more than one machine.

2. Change of network card of the server machine or moving the AhsayCBS system to a new server.

Solution: In the cases where the license key was used on a second server for testing

purposes, please use an evaluation key instead.

Alternatively, please shutdown the AhsayCBS service on the second server, and then contact our Support Engineer with your "License Name" and "License Key", and we shall update the license server to allow your key to be

used again.

In the cases where the network card of the server machine is changed, or an AhsayCBS relocation has been performed. Please also contact our Support

Engineer with your "License Name" and "License Key", and we shall update the license server to allow your key to be used again.

If the problem still persists, please ensure that there are no connectivity issues from the AhsayCBS server to the internet and that you can connect to

lic.ahsay.com with HTTPS from the AhsayCBS backup server. There is a connection test button underneath the license field entry box to test the connection to our license server. The testing result will be displayed next to

the test button.

Please also verify if the machine in concern contain any software that would create virtual MAC address, for example, VPN software. If yes, please disable them such software, and notify us again.



Internal Error 1012

Internal Error 1012 can occurs when one of the following conditions is true:

1. The license key has been used on more than one machine.

2. Change of the MAC address, local / remote IP address, or local port that AhsayCBS is installed on.

Solution: Persistent 1012 license errors can occur if your AhsayCBS server is operating

in a network environment where network traffic is routed to the internet via multiple external IP addresses. For example, network load balancing is

implemented using, i.e. a dual WAN router, Round Robin routing, or network card with multiple external IP.

For these cases, we would suggest setting up a static route for the server's connection to lic.ahsay.com, so that the remote IP address on the server will

remain the same every time a connection to lic.ahsay.com is established.



Appendix E Differences between AhsayCBS with the v6 versions

AhsayCBS has been totally re-designed from the ground upwards to provide

the best cloud backup solution with changes to core functions, such as file storage system, indexing, backup set features, replication, group policy, system user and branding. To understand the differences between AhsayCBS

and previous version of our product, please visit our website for details.

http://www.ahsay.com/jsp/en/home/index.jsp?pageContentKey=ahsay_products_backup-software_v6-v7-changes_cbs

ahsay cloud backup suiteahsay-dn.ahsay.com/document/v7/7500/customer/pdf/guide_cbs_admi… · ahsay...

Documents