Ahsay Offsite Backup Server

Transcription

1 v6 Administrator s Guide Ahsay Systems Corporation Limited 5 June 2015

2 Ahsay Offsite Backup Server 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 ( Trademarks Ahsay, 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. 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. Ahsay Systems Corporation Limited V6.25.1

3 Revision History Date Descriptions Type of modification 08 Apr 2011 First revision for AhsayOBS v6.3 Release New 26 Feb About Group Policy Modified Manage Policy Group Modified Exclude File Size Over Policy New Exclude Network Share Policy New 25.9 Getting User Information Modified List Policy Groups Modified 28 Feb Get Backup Set Modified 24 Jun System Requirements Modified 5.3 Evaluation Expiry and Free Edition Modified 11.1 Create Backup User Modified 17.5 AutoUpdate Limitations Modified 17.7 Enable AutoUpdate on AhsayUBS Modified 26 Further Information Modified 08 Aug Modifying User Profile Typo 12 Aug Get Backup Set Modified 07 Oct Import pfx certificate into Java Modified keystore Appendix G Applying SSL certificate(pfx) New to the Java keystore with OpenSSL 27 Oct Reseller Web SSL Certificate Typo Installation 24.1 Listening to non-standard TCP/IP Typo Port 24.2 Listening to a single IP address Typo 12 Dec Restricting access to system page Typo by IP address Copyright Notice Modified 20.1 Installing a trusted SSL certificate Modified 26 Mar Definitions, Acronyms and Modified Abbreviation 5.1 Licensee Name and License Key Modified 30 Mar Get Backup Set Modified Ahsay Systems Corporation Limited V6.25.1

4 Table of Contents 1 Overview Conventions Definitions, Acronyms and Abbreviation System Requirements Quick Start Getting started Best Practices and Recommendations AhsayOBS Hardware Requirements AhsayOBS Server Configuration AhsayOBS Java Heap Size Setting How many concurrent connections on AhsayOBS are allowed? AhsayOBS QPS Settings Use a Static IP Address Scheduling of Backup Jobs on AhsayOBS Enable Replication on AhsayOBS AhsayOBS Server Scaling Anti-Virus Software on AhsayOBS Enable CRC Checking Running AhsayOBS as a non-root user Expose only TCP port 80 and 443 to the public Restricting Access on Administration Panel System Resources AhsayOBS File System Tuning Network Load Balancing Configuration AhsayOBS Reseller Panel and AhsayRDR AhsayOBS Service on AhsayUBS Server with ZFS AhsayOBS and AhsayRDR with Wild Card SSL Certificates Maximum Number of Backup Sets for a Backup User Account Server Configuration User Languages Setting System Login Name/Password Host Name System Home, Policy Home and User Home Directories Single Level Access System Setting Proxy Setting Windows Active Directory (AD) Authentication Setting Redirector Language Setting Features Setting Permission Updated Files Moved Files Auto User Home Allocation Welcome Free Trial Setting Use Windows Event Log Configuration Recovery [Ahsay Systems Corporation Limited i

5 Setup AhsayOBS Configuration Files Configuration Archival File Limits Configuration Archival Storage Retention Backup Process Restoring Configuration Files Software License Licensee Name and License Key Automatic License Renewal Evaluation Expiry and Free Edition Offline License Activation License Management Portal Managing Routine Job Backup Report Online Restore Report Setting Change Report Missed Backup Report Inactive User Report Off-line Backup Reminder Backup Quota Reminder Trial User Reminder Usage Report Error Report Replication Error Report Inactive User Removal Retention Policy Rebuild User Storage System Log Removal Debug Log Removal Cyclic Redundancy Check (CRC) Checking Configuration Archival Managing Replication Managing Other Options In-File Delta Settings for all AhsayACB users Block Size Minimum Size Delta Merge In-File Delta Type Upload Full File Adgroups Advertisements Managing System Diagnosis Manage System User (Reseller Panel) My Profile / Edit System User SMTP Settings Customize Interface Customize Reseller Reports Add System User List / Remove System User Recovering a System User/Non-admin Password [Ahsay Systems Corporation Limited ii

6 10.7 Reseller Backup User Account Restrictions Reseller Web SSL Certificate Installation Auto Update Change Ownership Migrating users from administrator to reseller Matched host transfer Mismatched host transfer Reminder Suggestions and Best Practice Common error messages Managing Backup Users Create Backup User List / Remove Backup User Broadcast messages to backup users Managing User Profile Managing Backup Set Initiating Backup from AhsayOBS Browsing User Backup File Reviewing User Backup Report Reviewing User Storage Statistics User Log Group Policy Management About Group Policy Best Practices for using Group Policy Group Policy Limitations and Restrictions List Policy Control User Group List User Manage User Group Policy Group Manage Policy Group Shared Quota Policy Backup Set Setting Policy Backup User Policy Control Global Filter Policy Exclude File Size Over Policy Exclude Network Share Policy Shared Backup User Policy System Users Policy Control Delta Merge Technology Introduction Delta Merge Policy Delta Merge Process Delta Merge Queue Limitations Delta Merge Examples Account Lockout Configuration Account Lockout Rules Unlocking Accounts [Ahsay Systems Corporation Limited iii

7 14.4 Account Lockout on AhsayOBS/AhsayRDR Account Lockout on AhsayOBM/AhsayACB Account Lockout Auditing Multiple Thread Support Create a Read Only or Non Admin System User AutoUpdate How it works Using AutoUpdate Customizing AutoUpdate Forcing an extra AutoUpdate AutoUpdate Limitations AutoUpdate Changes Attributes Changes Multiple AhsayOBM/AhsayACB Versions Selection Multiple Host Selection Backup User Account Selection Enable AutoUpdate on AhsayUBS Backup / Restore files using off-line media Seed loading backup files (Import) Saving backup files to off-line media (Export) High Availability & Load-Balancing Configuration Secure connection with AhsayOBS Installing a trusted SSL certificate Renew a trusted SSL certificate Import pfx certificate into Java keystore Enforcing SSL to the web interface Install code signing cert with the restorer applet Monitoring System Activities Reviewing System Log Reviewing Backup Log Reviewing Restored File Log Reviewing Backup Error log Reviewing Replication Log Reviewing Advertisement Log Branding AhsayOBM & AhsayACB Customization Portal Branding AhsayOBS Welcome Page Different welcome pages for different domains Customizing the company logo displayed Customizing the Look and Feel of the web interface Customizing all text of the web interface Customizing reports Localizing the software Advanced Configuration Listening to non-standard TCP/IP Port Listening to a single IP address Restricting access to system page by IP address External API References Overview [Ahsay Systems Corporation Limited iv

8 25.2 Limitations IP Restrictions User Authorization Adding User Modifying User Profile Deleting User Listing Users Getting User Information Adding a Backup Set Deleting a Backup Set Listing Backup Sets Get Backup Set Updating a Backup Set Listing Backup Jobs Listing Backup Job Status Getting Backup Job Report Getting Backup Job Report Summary Listing Backup Files Getting User Storage Statistics Listing Users Storage Get License Get Replication Mode Send Forgot Password Delete Backup File Add Advertisement List Advertisements Modify Advertisement Delete Advertisement Add AdGroup List AdGroups Modify AdGroup Delete AdGroup Run Backup Get Backup Job Progress Add User Group List User Groups Modify User Group Delete User Group List Policy Groups Add User Groups to Policy Group Delete User Group from Policy Group List Backup Job Mode List System Users Additional APIs Further Information Appendix Appendix A Supported Language Code Appendix B Supported Time zone Appendix C Product Documentations Appendix D Error Code 1011 and [Ahsay Systems Corporation Limited v

9 Appendix E How can I rebuild an AhsayOBS server from scratch Appendix F How to start up AhsayRPS as AhsayOBS Appendix G Applying SSL certificate(pfx) to the Java keystore with OpenSSL [Ahsay Systems Corporation Limited vi

10 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 obra.jar before proceeding to step2. Italic Folder Path or File Path /usr/local/obs/conf [] Graphical Interface Elements [Manage Log] %% Filepath in Windows format %OBSR_HOME% $ Filepath in Linux/Unix/BSD $OBSR_HOME format italic Command mkdir /usr/local/obs Notation that are used specificially for API section: Convention <Text Inside angle brackets> [Text inside square brackets] {Text insides braces} Vertical bar ( ) Ellipsis ( ) Descriptions Placeholder for which you must supply a value. Optional items. Set of required items; choose one. Separator for mutually exclusive items; choose one. Items that can be repeated. 1.2 Definitions, Acronyms and Abbreviation Term/Abbreviation AhsayOBS AhsayRPS AhsayRDR AhsayOBM Definition Ahsay Offsite Backup Server Ahsay Replication Server Ahsay Redirector Server Ahsay Online Backup Manager AhsayACB OBSR_HOME Ahsay A-Click Backup The install location of AhsayOBS & AhsayRPS. Ahsay Systems Corporation Limited 1

11 Windows C:\Program Files\AhsayOBS and AhsayRPS Linux/FreeBSD/Solaris /usr/local/obs/ OBSR_HOME_BAK The backup location of AhsayOBS & AhsayRPS. It is used temporary during the install/upgrade process. Windows C:\Program Files\AhsayOBS and AhsayRPS.bak\ Linux/FreeBSD/Solaris /usr/local/obs.bak/ CONF_HOME The directory to store AhsayOBS & AhsayRPS configuration files. Windows %OBSR_HOME%\conf Linux/FreeBSD/Solaris $OBSR_HOME/conf USER_HOMES The directories where AhsayOBS and AhsayRPS store the AhsayOBM & AhsayACB users accounts. The default location is: %OBSR_HOME%\users POLICY_HOME The directory where AhsayOBS and AhsayRPS store its system users and group policy information. Windows %OBSR_HOME%\system\policy Linux/FreeBSD/Solaris $OBSR_HOME\system\policy SYSTEM_HOME The directory where AhsayOBS and AhsayRPS store its system information. Windows %OBSR_HOME%\system\ Linux/FreeBSD/Solaris $OBSR_HOME\system\ WEBAPPS_HOME Location of the webapps directory inside the installation directory of AhsayOBS & AhsayRPS. Ahsay Systems Corporation Limited 2

12 Windows %OBSR_HOME%\webapps. Linux/FreeBSD/Solaris $OBSR_HOME\webapps Ahsay Offsite Backup Server WEBAPP_HOME_BAK A backup of the webapps directory inside AhsayOBS and AhsayRPS. Windows %OBSR_HOME%\webapps.bak Linux/FreeBSD/Solaris $OBSR_HOME\webapps.bak RECEIVER_HOME JAVA_HOME The location where the replicated data is stored for a particular replication receiver. The location where JAVA is installed 1.3 System Requirements Please refer to the FAQ: Ahsay Software Compatibility List (SCL) for version 6.3 or above (2323) for system requirements of AhsayOBS v6. It is recommended to install AhsayOBS on server grade O/S and hardware platform. However, for evaluation purposes installation on Windows XP or Windows 7 platforms would be fine for testing. Ahsay Systems Corporation Limited 3

13 2 Quick Start This chapter describes the minimum steps required to start using AhsayOBS. Please consult the information in the following chapters for a complete reference to all features available in AhsayOBS. 2.1 Getting started To setup your AhsayOBS, please do the followings: Setup Your Backup Server 1. Point your browser to 2. Login as AhsayOBS administrator. The default login name and password are system and system respectively. 3. Set your hostname. Ahsay Systems Corporation Limited 4

14 Enter a resolvable hostname for your backup server (e.g. backup.yourcompany.com) into the [Host Name] text field. Although you can supply an IP address here, it is preferable to use a hostname instead. If you are using custom TCP port for HTTP/HTTPS connection (i.e. non 80 or 443), you need to append the custom port number to the [Host Name] field. e.g. backup.yourcompany.com:8080 If you are not using custom TCP port, open a browser on the backup server and type in the value of [Host Name] as an URL and check if you get the backup server homepage. If you are not able to connect to the webpage, please try until you can reach it and put this value in the [Host Name] field. 4. Set the [User Homes] directory. [User Homes] refers to directories where AhsayOBS stores the backup files and backup log for all its users. You should set [User Homes] to directories where there are lots of free spaces. 5. Set your SMTP Server. Enter a resolvable hostname (or an IP address) of your SMTP server into the [SMTP Server] text field. There is a test button at the end of each SMTP settings to test the connection. The testing result will be displayed next to the test button. If your SMTP server is not running on standard SMTP ports (i.e. port 25), you can append your custom port number to your SMTP server address to use this server e.g. mail.your-company.com:8025. Ahsay Systems Corporation Limited 5

15 You are only required to enter the [Login Name] and [Password] if your SMTP server enquires user authentication when sending s. Note: SMTP server with Transport Layer Security (TLS) is not supported. 6. Press the [Update] button. 7. Enter your license key (You can skip this step if you are evaluating this software). 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. Enter the licensing information printed on [End User License Agreement] printout into the text field provided in the [Manage System] -> [Software License] panel. Please note that both [Licensee Name] and [License Key] are case sensitive. Note: By default AhsayOBS service listens to port 80 for http and port 443 for https. Please make sure your servers firewall is configured to allow incoming access via these ports. Add Backup User You need to add backup user to the system before you can start backing up data to AhsayOBS. To add a backup user to the system, please do the followings: 1. Click the [Manage User] link available at the top menu and choose [Add user]. 2. Enter the user information for the new user account into the form provided. Ahsay Systems Corporation Limited 6

16 Key Login Name Password Alias Time zone Language Backup Client Advertise Group Type Description Login Name of the new account. Password of the new account. Another name of the new account. Time zone of the new account Preferred language for report of the new account. Choose AhsayOBM client or AhsayACB client. Choose whether advertisements are displayed at the bottom of the AhsayOBM/AhsayACB client Trial User Account of this type will be deleted from the system after an inactivity period of 30 days by default. Paid User Account of this type will stay within the system until it is removed form the system by administrator. Welcome User Home address of the new account. Check this option to send a welcome to the user. The top directory where the software stores backup files and all other information for the new account. Ahsay Systems Corporation Limited 7

17 Backup Quota Bandwidth Add-on modules Backup Quota of the new account. Bandwidth throttling for this user account. Add-on modules for this user account. 3. Press the [Add] button to create the user. 4. The account is now ready. Login and Run Backup 1. Point your browser to 2. Click the [User Login] link at the top. 3. Login with the login name and password you have created in previous section. 4. Follow the [Quick Start] information available in the User s Guide to install the AhsayOBM or AhsayACB onto users computer to start backing up data. Ahsay Systems Corporation Limited 8

18 3 Best Practices and Recommendations Ahsay Offsite Backup Server This chapter lists out all best practices and recommendations which you should consider before deploying AhsayOBS to a production environment. 3.1 AhsayOBS Hardware Requirements AhsayOBS should be installed on a machine supporting 64 bit multiple CPU and multiple cores. A 64 bit Operating System will allow AhsayOBS to run on a 64 bit Java JRE platform, as 64 bit Java is capable of supporting larger Java heap size settings. This type of configuration will provide sufficient capacity for future business expansion, to meet the needs of exisiting customers, and to support new AhsayOBS server features. A more powerful machine will also reduce the need for frequent hardware upgrades, which will require service down time for data migration. It is a good idea to ensure your AhsayOBS server is equipped with some redundancy features, i.e power supply, network card, and is connect it to a UPS (Uninterupterable Power Supply). 3.2 AhsayOBS Server Configuration One of the most important factors in determining backup and restore performance is the disk performance of your AhsayOBS server. Poor backup and restore performance can be attributed to: i. The use of network drives for AhsayOBS system and user homes. ii. iii. The use of a single large disk or volume for multiple AhsayOBS user homes Inadequate balancing of the disk I/O across multiple physical drives To improve performance of your AhsayOBS server, you should consider using: i. A separate drive dedicated for your O/S installation ii. A separate local dedicated for your AhsayOBS installation home iii. A separate local drive for each individual AhsayOBS user home iv. A separate local drive for AhsayOBS system home v. Distribute user accounts across multiple user homes to balance the I/O load vi. Your AhsayOBS service should be running on a dedicated machine It is not recommended to use the O/S partition or drive as the AhsayOBS system or user home. If the O/S partition runs out of Ahsay Systems Corporation Limited 9

19 space, this will cause your O/S to become unstable and may even crash your AhsayOBS server. 3.3 AhsayOBS Java Heap Size Setting Due to features such as CRC checking, delta merging, support for image, Hyper-V, VMware backupsets AhsayOBS v6 may require more Java memory Although, there is no exact forumula for calculating the correct Java heap size setting for any given AhsayOBS server. In general a maximum Java heap size (-Xmx) setting of at least 2048M is recommended, assuming AhsayOBS is running on a 64 bit Operating System. When setting the maximum Java heap size for AhsayOBS please ensure this value does not exceed 50% of the RAM on the server, to allow sufficient memory for O/S processes and operations. It is not recommended to set excessively high values for the maximum Java heap size, as this could result in AhsayOBS performance issues during internal Java VM garbage collection or memory recycling routines. 3.4 How many concurrent connections on AhsayOBS are allowed? This is a common question and there is no exact formula for calculating the maximum number of user accounts or the number of concurrent connection on any AhsayOBS server. As it is dependent on many factors such as but not limited to: i. AhsayOBS server hardware ii. The composition or mix of users accounts, i.e. AhsayOBM or AhsayACB users iii. The number of backupsets per a user account iv. The type of backupsets per user account v. The backup behavior of each user vi. The number of concurrent backup jobs vii. The disk I/O on the AhsayOBS viii. Network bandwidth Also, AhsayOBM/AhsayACB v6 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 OBS to 1000, to avoid potential performance problems. Note: When the number of concurrent connection increase, the performance on the AhsayOBS may be turn down. To increase the performance, we Ahsay Systems Corporation Limited 10

20 would recommend modifying the maxthreads value in the %OBS_HOME%\conf\server.xml in the AhsayOBS. If you want to support multiple concurrent connections more than 100, you can configure the maxthreads value based on the following formula maxthreads = Y x 3 (Y= the number of concurrent connections) Otherwise you are not required to modify the maxthreads value. For example, the number of concurrent connection is 150, the suggested value of the maxthreads is 450. (Assuming the network environment between the AhsayOBS and AhsayOBM/AhsayACB is good, and AhsayOBS home on local hard disk with good disk I/O.) 3.5 AhsayOBS QPS Settings To ensure user accounts are evenly distributed across your user home drives. It is recommended you configure your QPS settings, this can be under via your AhsayOBS web console under [Manage System] -> [Server Configuration] -> [Auto User Home Allocation]. The QPS settings for each user home drives should not be set to unlimited or Not Used. For AhsayOBS servers with multiple user homes, you should consider a QPS setting of 50% to 70% for each user home drive. This will prevent user accounts being concentrated onto one drive, which may cause the drive to run out of disk space very easily. This could result in data corruption on the affected user home(s). Also, an even distribution of user accounts across your AhsayOBS user homes will improve backup performance, by spreading the disk I/O load. 3.6 Use a Static IP Address The use of dynamic IP addresses for AhsayOBS domain names may result in an unstable backup service whenever the IP address re-cycles. A static IP address will ensure the remote IP address sent by AhsayOBS to the Ahsay license server will remain the same during daily routine license checks. This will avoid potential license errors, i.e or 1012 license errors which could result of the automatic shutdown of your AhsayOBS service. Ahsay Systems Corporation Limited 11

21 It is strongly recommended to use a static IP address for your AhsayOBS server to ensure a stable and reliable backup service. 3.7 Scheduling of Backup Jobs on AhsayOBS To improve overall backup performance we recommend that scheduled backup jobs (by default starts at 09:00pm) should not be confined to a few start times. The start times of scheduled backup jobs should be evenly distributed throughout the day to avoid potential performance bottlenecks on your AhsayOBS server. 3.8 Enable Replication on AhsayOBS To ensure you have a backup of your AhsayOBS server in the event of any hardware issues. We recommend enabling replication on your AhsayOBS server to a separate AhsayRPS server. 3.9 AhsayOBS Server Scaling To cope with business and or data growth, instead of upgrading to new hardware to support additional users and data, which could involve a lengthy data migration process. Your backup service capacity can be upgraded using an AhsayRDR solution. The advantage of using AhsayRDR is it allows you to expand your backup service easily by adding new AhsayOBS servers to the current setup with minimal interruption to your backup service Anti-Virus Software on AhsayOBS If you have anti-virus software installed on your AhsayOBS server, please make sure the user home and system home drives are excluded from scanning, as this may interfere with normal AhsayOBS operation Enable CRC Checking It is strongly recommended the CRC checking on AhsayOBS is enabled to ensure the integrity of the backup files. Ahsay Systems Corporation Limited 12

22 3.12 Running AhsayOBS as a non-root user Ahsay Offsite Backup Server If you are running AhsayOBS on Linux, you are advised to run the AhsayOBS service as non-root user. (AhsayOBS service is run under root by default). This minimizes the impact of damages that could be done on the system in case the system has been compromised by hackers 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 Restricting Access on Administration Panel For security reasons, we would recommend that the Administration Panel of AhsayOBS/AhsayRPS 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 AhsayOBS/AhsayRPS management console. For further information, you can follow our instructions in the following chapter Restricting access to system page by IP address System Resources Extra system resources may required for the following backup set types: Windows System Backup Windows 2008 System State Shadow Protect Microsoft Exchange Microsoft SQL Server Oracle Database Lotus Domino Server VMware ESX/ESXi VMware Server Microsoft Hyper V In most cases, the file size of a single file in these backup set types are large, therefore extra system resources (such as memory and disk space) are required for using the delta merging feature. For user homes containing backupsets with delta merge enabled. It is recommended to maintain at least 30% to 40% free disk space. Ahsay Systems Corporation Limited 13

23 3.16 AhsayOBS File System Tuning In order to ensure optimal performance from an AhsayOBS server file system, please ensure that you: 1. Use local drives instead of network drives, i.e. iscsi, NFS, SAMBA etc 2. Tune your file system. For example, for NTFS, run the followings: fsutil behavior set disable8dot3 1 fsutil behavior set mftzone 2 fsutil behavior set disablelastaccess 1 fsutil behavior set memoryusage 2 3. Turn off drive indexing [on MS Windows O/S this is used for faster searching] feature for each system and user home drive(s). 4. For Linux/Unix mount points consider mounting them using noatime Network Load Balancing Configuration For AhsayOBS 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 AhsayOBS server connection to the Ahsay license server (lic.ahsay.com). This will ensure the remote IP address sent by AhsayOBS to the Ahsay license server will remain the same during daily routine license checks. This will avoid potential license errors, i.e or 1012 license errors which could result of the automatic shutdown of your AhsayOBS service AhsayOBS Reseller Panel and AhsayRDR If the Reseller Panel feature is enabled on your AhsayOBS server and you plan to configure AhsayOBS as part of an AhsayRDR setup both AhsayOBS and AhsayRDR must be on v or above. For backup users accounts created by resellers, AhsayOBM/AhsayACB v or above clients are only supported AhsayOBS Service on AhsayUBS Server with ZFS For AhsayOBS service which are running on an AhsayUBS (v or above) server and is configured with ZFS volume(s). It is strongly recommended to install at least 4 GB RAM, as ZFS volumes require relatively large amount of memory to run. The amount of memory Ahsay Systems Corporation Limited 14

24 required is dependent on the size of the ZFS volume and the amount of I/O activity AhsayOBS and AhsayRDR with Wild Card SSL Certificates For AhsayRDR servers installed with a wild card SSL certificate, all member AhsayOBS servers belonging to this setup must be installed with the same wild card SSL certificate. Otherwise AhsayRDR will not be able to connect to any member AhsayOBS server installed with a different wild card SSL certificate via https Maximum Number of Backup Sets for a Backup User Account Although there are no restrictions on the maximum number of backup sets that can be created on a backup user account. For administration purposes it is recommended that each backup user account have no more than 10 backup sets. Ahsay Systems Corporation Limited 15

25 4 Server Configuration This chapter describes how you can use the [Manage System] -> [Server Configuration] page (shown below) to manage the configuration of your backup server. Ahsay Systems Corporation Limited 16

26 Key Login Name/Password Host Name System Home Policy Home User Homes Single Level Access Description Username and password of the system account. A resolvable hostname of this server (e.g. backup.your-company.com). Although you can supply an IP address here, it is preferable to use a host name instead. The directory where AhsayOBS stores its system information. The default directory for [System Home] is %OBSR_HOME%\system. Normally, you do not need to modify the value of this setting unless you want to store this information elsewhere. The directory where AhsayOBS stores its system user and group policy information. The default directory for [Policy Home] is %OBSR_HOME%\system\policy. Normally you do not need to modify the value of this setting unless you want to store this information elsewhere. The directories where AhsayOBS store the backup files and backup log for all its users. You should set [User Homes] to partition where there is lots of free space. It determines whether system user has been restricted access to own created system users and backup users. Auto Lock User The backup user will be locked automatically after 3 consecutive invalid login attempts via AhsayOBS web console, Redirector web console and backup client console. SMTP Server Report Sender Administrative Contact Language of System Reports Use Proxy The SMTP server that AhsayOBS will use to deliver its reports. The name of address that will be used as a sender for all outgoing s. The name(s) and address (es) of the system administrator. System reports (e.g. Daily Usage Report and Daily Error Report) will be delivered to these mailboxes. The language which will be used in all system reports. Whether to use proxy to access the internet. Ahsay Systems Corporation Limited 17

27 Type Proxy Host/Port The type of proxy to be used (HTTP / SOCKS). Proxy server host and port number. Proxy Username/Password Use Windows Active Directory (AD) Authentication Domain Name Domain Controller IP Remove AhsayOBS account Use Redirectory(RDR) Protocol Hostname/Port Login Name/Password Administrator Hostname Use Windows Event Log Language Settings Feature Settings Permission updated files Moved Files Auto User Home Proxy user name and password if user authentication is used. Whether to use Windows Active Directory Authentication. The domain name to be used for AD authentication. The IP address of the domain controller. Whether to delete AhsayOBS user account when AD user account is disabled/deleted. Whether to use redirector. The type of protocol to be used (HTTP/HTTPS) Redirector host and port number. System username and password for the redirector. The host name/ip address that backup users created by administrator will be used to contact this server via redirector (e.g. redirector.company.com) When this option is enabled, this backup server writes the system log message to Windows Event Log. This feature is only valid in Windows platform. It determines whether different languages are enabled. It determines whether the [HELP], restore link and install link should be available to users. It determines whether the existing files are copied to retention area before updating the permission settings. It determines whether the existing files are copied to retention are before updating the file paths. Maximum QPS Ratio can be changed. Ahsay Systems Corporation Limited 18

28 Allocation Welcome Enable Free Trial Registration Backup Quota Add-on Modules Remove User Configuration Recovery It determines if welcome will be sent to new users and other options on welcome s. Whether to enable free trial user registration. The default backup quota of trial users The default modules available to trial users Whether to remove trial users and the length of trial period. System settings, policies and user profiles of a preferable date can be recovered. Date Dates of configuration can be recovered. At most 30 copies of configuration will be archived. Path Mode Refresh Restore Destination of recovered configuration. Mode of configuration recovery. If "Auto" is selected and OBS user home is empty, the configuration including system settings, policies and user profiles will be decrypted and downloaded to their original locations. If "Manual" is selected, the configuration will be decrypted and downloaded to destination path. Reload archival dates Download configuration to the destination path and perform configuration recovery in either "Auto" or "Manual" mode. 4.1 User Languages Setting The language of the web interface can be easily changed to another language by: 1. Click the [Select Language] link available on the top right hand corner of the web interface. 2. Select the language of your choice. 3. All text messages from the original window are now displayed in the language you have just selected (see example below). Ahsay Systems Corporation Limited 19

29 The languages currently supported by AhsayOBS are listed in Appendix A. You can limit the list of languages available to users by using the [Manage System] -> [Server Configuration] -> [Language Setting] options. If you uncheck all checkboxes for all languages available in [Manage System] -> [Server Configuration] -> [Language Setting], the [Select Language] will no longer be available on the top right hand corner of the web interface (you need to refresh the top menu bar to see the change). Users will not be able to change the language of the web interface. Ahsay Systems Corporation Limited 20

30 4.2 System Login Name/Password The [Login Name] and [Password] setting under the [Manage System] -> [Server Configuration] page sets the login name and password (the default username is system password is system) that you would use to logon the system administration console. Users are strongly recommended to change both the login name and password to something other than Ahsay Systems Corporation Limited 21

31 the default setting to reduce the possibility of unauthorized access to the AhsayOBS. 4.3 Host Name The [Host Name] setting under the [Manager System] -> [Server Configuration] page sets the hostname of the backup server. This entry will be used as a reference to the backup server in all reports. Please enter a hostname/ip address (a public hostname/ip address if you expect backup request originating from the internet). Please make sure the [Host Name] entry is resolvable from the backup server itself. This means that if you enter backup.yourcompany.com into the [Host Name] entry, you can access the backup system welcome page via If you are running AhsayOBS on custom TCP port (i.e. Not Port 80 and Port 443), please append your custom TCP port number to the [Host Name] entry. For example, if you are running AhsayOBS on TCP Port 8080 for HTTP, please enter backup.your-backup.com:8080 as your [Host Name] entry (Please do not enter the customer TCP Port for HTTPS, e.g. 8443, into the [Host Name] field as it will not work). 4.4 System Home, Policy Home and User Home Directories The [System Home], [Policy Home] and [User Homes] setting under the [Manage System] -> [Server Configuration] page sets the system home directory, policy home directory and user home directories for AhsayOBS ( the default values are %OBSR_HOME%\system, %OBSR_HOME%\system\policy and %OBSR_HOME%\user). The system home directory for AhsayOBS defines a directory in which AhsayOBS will store all its system information. The policy home directory for AhsayOBS defines a directory in which AhsayOBS will store all its system users and group policy information. The user home directories for AhsayOBS define a list of directories in which AhsayOBS can be used to store the user folder for each backup user. Each user folder contains the backup setting as well as all backup data owned by this particular user. AhsayOBS can be configured with multiple user home directories, this allows for the distribution of user accounts across different hard disk partitions or different hard disks. This enables server administrator s to easily distribute the I/O loading across multiple drives, which helps to improve overall backup server performance. Also, the support of multiple user homes will allow for Ahsay Systems Corporation Limited 22

32 easy expansion of the server storage. For example, if you want to add more storage to AhsayOBS, you can simply add another hard disk to the system and add the path to this new drive (e.g. E:\ or E:\Users) to the [User Homes] setting. You can then add new backup users or move existing backup users to this user home drive. Backup users created by the AhsayOBM or AhsayACB Free Trial Registration wizard will always use the first [User Homes] entry as the user home to create backup users. If you want to offer free trial to your users and have enabled the Free Trial Registration option on the [Manage System] -> [Server Configuration] page, please make sure that there is enough free space available in the first entry of the [User Homes] settings to avoid running out of free space. 4.5 Single Level Access The [Single Level Access] settings under the [Manage System] -> [Server Configuration] page defines system user access restriction to own created system users, backup users and backup users of system users. This restriction does not apply to system administrator. If you uncheck [Single Level Access] checkbox, system user can access all descendant system users and backup users System Setting The [ System Setting] settings under the [Manage System] -> [Server Configuration] page defines the various setting that AhsayOBS will use to generate reports to backup system administrator and backup users. The [ System Setting] -> [SMTP Server] -> [Host Name] entry defines the SMTP server that will be used by AhsayOBS to deliver its reports. If you are using a SMTP server that is not running on SMTP standard TCP port (port25), please append your customer TCP port number for SMTP service to the [SMTP Server] -> [Host Name] entry (e.g. mail.yourcompany.com:8025). You are only required to fill in the [SMTP Server] -> [Login Name] and [SMTP Server] -> [Password] entry if the SMTP server you are using required user authentication before accepting mail delivery requests. There is a test button at the end of each SMTP settings to test the connection. The testing result will be displayed next to the test button. Multiple SMTP servers can be setup for AhsayOBS. If the first SMTP server is unavailable, the next SMTP server will be used. The [ System Setting] -> [Report Sender] entry defines the Mail-From address that appears in all outgoing s generated by AhsayOBS. Ahsay Systems Corporation Limited 23

33 The [ System Setting] -> [Administrator Contact] entry defines the administrative contact of AhsayOBS. AhsayOBS will send daily usage and error report and all critical system alerts to all addresses defined here. Note: 1. Since , we support GMAIL with secure SMTP. 2. SMTP on Exchange 2007 or above with administrator as login account is not allowed. When you setup the SMTP settings, you can either use another normal user account with mail box enabled and relay permissions, or leave the login name and password field in the SMTP authentication as empty. 4.7 Proxy Setting The [User Proxy] settings under the [Manage System] -> [Server Configuration] page defines whether AhsayOBS 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. 4.8 Windows Active Directory (AD) Authentication Setting When Windows Active Directory Authentication is enabled, user authentication will be dispatched to Windows Active Directory (AD) automatically if AhsayOBS 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 AhsayOBS, because AhsayOBS will create this user account automatically after authenticating this logon using AD. When this user logons to AhsayOBS, AhsayOBS will use Free Trial Registration settings above (even if it is not enabled) as the template of user profile (i.e. backup quota and add-on modules settings, but not Microsoft Exchange Mailbox which will be disabled by default) to be created. The user account created will be of Paid Ahsay Systems Corporation Limited 24

34 type and of AhsayACB backup client (unless the user logons using AhsayOBM ). To enable this feature, simply check the box of [Use Windows Active Directory (AD) Authentication] under the [Manage System] -> [Server Configuration] page (by default it is enabled). To synchronize AhsayOBS and AD, removal of users can be configured. If you want to delete/disable AhsayOBS user account when the user is removed from AD, you can check the boxes in the section of [Remove AhsayOBS Account]. You can have both options checked and create your own standard. For example, setting [After a user account has been deleted from AD for 20 days, AhsayOBS will delete this user account automatically] and [After a user account has been deleted from AD for 10 days, AhsayOBS will disable this user account automatically], can results that when the user account is removed from AD after 10 days, the user account will be disabled and after 10 more days, the user account will be deleted. WARNING: AhsayOBS servers with Windows Active Directory Authentication enabled are not supported in an AhsayRDR environment. 4.9 Redirector The [Use Redirector (RDR)] settings under the [Manage System] -> [Server Configuration] page defines whether the current AhsayOBS is used behind a redirector. If AhsayOBS is a member machine of an AhsayRDR setup, you must specify the AhsayRDR settings In order to setup AhsayOBS v6 in an AhsayRDR environment, you must use AhsayRDR v6. Note: For users connection to the AhsayOBS user console or connection to the AhsayOBM/AhsayACB client agent though AhsayRDR, the hostname must be configured exactly as the AhsayRDR hostname configured in the Use Redirector (RDR) > Hostname setting. WARNING: Ahsay Systems Corporation Limited 25

35 Please make sure on the AhsayRDR server the UserConsole filter in the %RDR_HOME%\webapps\rdr\WEB-INF\web.xml" file is amended to include the IP address range of all member AhsayOBS servers, as by default the range setting is Otherwise the affected AhsayOBS member servers will not be able to connect to AhsayRDR. <filter-name>userconsole</filter-name> <filter-class>com.ahsay.rdr. <init-param> <param-name>range1</param-name> <param-value>localhost</param-value> </init-param> <init-param> <param-name>range2</param-name> <param-value> </param-value> </init-param> </filter> 4.10 Language Setting The [Language Setting] settings under the [Manage System] -> [Server Configuration] page defines the list of available languages on the web interface Features Setting The [Feature Setting] settings under the [Manage System] -> [Server Configuration] page defines whether some customizable features on the web interface should be enabled or not. Ahsay Systems Corporation Limited 26

36 Key Show Help link Show Restore link Show Install link Description It defines whether the [Help] link should appear at the top right hand corner of the web administration console (user interface only). It defines whether the [Restore] link should appear at the top right hand corner of the web administration console (user interface only). It defines whether the [Install Software] link should appear at the top right hand corner of the web administration console (user interface only) Permission Updated Files The [Permission Updated Files] settings under the [Manage System] -> [Server Configuration] page defines whether AhsayOBS should make a copy of the file to the retention area before the file permission changes. When this option is set, all backup accounts will use more retention space but allows the users to restore the same file with various permissions. When this option is not set, the permission changes are updated to the backup file directly. No copies of the previous version(s) will be available for restore. Ahsay Systems Corporation Limited 27

37 4.13 Moved Files The [Moved Files] settings under the [Manage System] -> [Server Configuration] page defines whether AhsayOBS should make a copy of the file to the retention area before the file path is updated, i.e. the files is moved to another location. When this option is set, all backup accounts will use more retention space but allows the users to restore the same file with the correct location. When this option is not set, the file path changes are updated to the backed up file directly. No copies of the previous version(s) will be available for restore Auto User Home Allocation The [Auto User Home Allocation] settings under the [Manage System] -> [Server Configuration] page defines the quota ratio for each user home. AhsayOBS will automatically select the user home to be used for auto user allocation and trial user registration based on the quota ratio. AhsayOBS will always use the first user home with a QPS ratio smaller than the value defined by the system user Welcome The [Send welcome to new users] settings under the [Manage System] -> [Server Configuration] page defines whether AhsayOBS should send a welcome to new users. If this option is checked, it will send an to the new users. The [Include encrypted password in welcome ] settings under the [Manage System] -> [Server Configuration] page defines whether AhsayOBS should include the encrypted password in the welcome . When this option is checked, the encrypted password will send with the welcome to the new users Free Trial Setting The [Enable Free Trial Registration] settings under the [Manage System] -> [Server Configuration] page defines various free trial settings available in AhsayOBS. Trial users do not count towards the maximum number of users allowed within AhsayOBS by the software license and there can be unlimited number of trial users within AhsayOBS. However, each backup user can have a maximum backup quota of 100GB for a trial period of 30 days. After Ahsay Systems Corporation Limited 28

38 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 (see below) 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 [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 AhsayOBS to remove trial backup users from the system automatically after backup users have registered for 60 days Use Windows Event Log For AhsayOBS installations on Microsoft Windows platform which have the Windows Event Log service enabled. When this feature is selected all AhsayOBS system log information, i.e. error, warning, and information message types will be also be written to the Windows event logs. The backup Ahsay Systems Corporation Limited 29

39 server administrator s can view the logs entires using the Windows event viewer. The event log name is limited to 8 characters. The ID for each message type is shown in the following table. Type ID Information 201 Warning 305 Error Configuration Recovery AhsayOBS Configuration Recovery feature available from AhsayOBS v onwards. It is designed to faciliate a quick and simple recovery of an AhsayOBS server after an outage, to ensure minimum down time of backup service. By allowing the backup server administrator to install a new AhsayOBS instance on another machine, using the backed up AhsayOBS server configuration downloaded from the Ahsay License Server (ALS). In order to backup AhsayOBS server configuration files the backup server administrator, can schedule daily Configuration Archival backups of critical AhsayOBS server configuration files to the ALS, e.g. system configuration files in the %OBS_HOME%\CONF folder, Policy Home and User Home folders. The Configuration Archival feature is available to AhsayOBS servers using paid license keys (including keys generated from License Management Portal) and with a valid "Free Upgrade Until" date. This feature is disabled for AhsayOBS servers using evaluation license keys. Ahsay Systems Corporation Limited 30

40 Setup The AhsayOBS Configuration Recovery feature is disabled by default. To enable this feature go to the server configuration page [Manage System] -> [Routine Job] -> [System Job] -> [Configuration Archival] and select Enable and press the [Update] button. The default AhsayOBS configuration backup time is at 12:30 PM. For AhsayOBS servers using evaluation license keys or where the "Free Upgrade Until" date has already expired, this option will be automatically disabled until license key maintenance is renewed. For license keys where the "Free Upgrade Until" has expired, the configuration files which have been previously uploaded to ALS are still available for restore via the Configuration Recovery feature AhsayOBS Configuration Files The following is a list of critical AhsayOBS configuration files which are backed up to the ALS by the daily Configuration Archival backup job. CONF folder \%OBS_HOME%\conf\ acb-config.xml, afc.opt, autodiscovery.xml, autoupdate.bdb, debug.props, keystore, lfsconfig.xml, license.xml, obs.xml, obsr.opt, rps.xml, rpslicense.xml, rpsrecv.xml, rpssend.xml, server.xml POLICY HOME \%PolicyHome%\ policygroup.xml, sysuser.xml, usergroup.xml, AcbGlobalFilter\db\Profile.xml, defaultacbuser\db\profile.xml, Ahsay Systems Corporation Limited 31

41 USER HOME %userhome1% %userhome2%.. \%User Home%\ defaultuser\db\profile.xml, ObmGlobalFilter\db\Profile.xml The home folder and Profile.xml for all backup user accounts: %Userhome%\test1 %Userhome%\test1\db %Userhome%\test1\db\Profile.xml %Userhome%\test2#12345 %Userhome%\ test2#12345\db %Userhome%\ test2#12345\db\profile.xml Configuration Archival File Limits Each Configuration Archive file is limited to 6MB after compression per an upload. For example, a 6MB compressed file can contain configurations files from an AhsayOBS server with the following setup: Number of backup user = Number of system user = 150 Number of user group = 500 Number of policy group = 250 Average number of backup sets per backup user = 10 If after the configuration file is compressed, the file size exceeds 6MB, the Configuration Archival job will not upload the file to ALS. The exact nature of the error will be shown in the AhsayOBS system log. The following example shows the compressed files exceeded 6MB. Ahsay Systems Corporation Limited 32

42 Configuration Archival Storage Retention Ahsay Offsite Backup Server The ALS allows each license key to store a maximum of 30 days of configuration file backups at any one time. When the Configuration Archival backup job uploads the configuration file on the 31 st day, the ALS will immediately delete the existing configuration file uploaded on the 1 st day and so forth. To check how many backup snapshots are available on the ALS, on the AhsayOBS web console go to [Manage System] -> [Server Configuration] - > [Configuration Recovery]. Click on the [Refresh] button and select the Date combo box. WARNING: ALS will only keep one snapshot of the Configuration Archive backup file per day. If there are more than one Configuration Archive backup jobs are run within a 24 hour period, ALS will only keep a copy of the latest snaphot Backup Process Once the Configuration Archival system job is enabled and the daily backup time configured. AhsayOBS will automatically perform a backup of the configurations files to the ALS. For each Configuration Archival backup job: 1. The AhsayOBS configuration files are copied to the %OBS_HOME%\temp folder. 2. The files are compressed and encrypted using an AES 256bit encryption algorithm. Ahsay Systems Corporation Limited 33

43 3. The compressed file is renamed according to the following format dr- YYYY-MM-DD.zip.gz and AhsayOBS uploads the file to ALS using https protocol. 4. After a successful backup the dr-yyyy-mm-dd.zip.gz file is then removed from the %OBS_HOME%\temp folder. WARNING: The encryption key used by AhsayOBS to encrypt the configuration file is a secret key and cannot be changed by the backup server administrator. Once the AhsayOBS configuration files are uploaded to ALS, the backup server administrator cannot manually remove these files from ALS. The Configuration Archival backup job statuses are recorded in the AhsayOBS system log. When a Configuration Archival backup job has completed successfully, the following messages will be shown in the AhsayOBS system log: To verify the current backup of configuration files are available on the ALS, on the AhsayOBS web console go to [Manage System] -> [Server Configuration] -> [Configuration Recovery]. Click on the [Refresh] button to show the latest snapshot available on the ALS. Backup Error Handling If the Configuration Archival backup job encounters any connection issues to the ALS, AhsayOBS will attempt to reconnect to the ALS again upload the configurations file after 15 minutes. The following messages will be shown in the AhsayOBS system log: Ahsay Systems Corporation Limited 34

44 In total AhsayOBS will retry three times in 15 minute intervals to establish a connection to ALS before the backup job is aborted. First Retry Second Retry Third Retry Ahsay Systems Corporation Limited 35

45 If the Configuration Archival backup job does not successfully upload the configuration file to ALS after the third retry, the backup job for the current day will end. AhsayOBS will run the Configuration Archival backup job again on the following day at the scheduled time Restoring Configuration Files To restore the configurations files from ALS to AhsayOBS, open the web management console and go to the server configuration page [Manage System] -> [Server Configuration] -> [Configuration Recovery]. The [Path] is the destination path where the restored configuration files will be saved on the AhsayOBS server. After the configuration file is restored from the ALS, when Configuration Recovery is perfomed using Manual mode. The default setting for the [Path] is %OBS_HOME%\SYSTEM_HOME\dr. The AhsayOBS server configuration can be restored from ALS by: 1. Clicking the [Refresh] button to obtain a list of the configuration file snapshots stored on the ALS. 2. Use the [Date] option, to select the configuration file snapshot to be restored. 3. Select the recovery mode in the [Mode] option. i. If "Auto" mode is selected, AhsayOBS will download the selected configuration file snapshot from ALS. It will be automatically decrypted and copied to their original locations, only if the AhsayOBS user home(s) are empty. ii. If "Manual" mode is selected, the configuration files will be decrypted and downloaded to the destination path. The restored files will have to be manually copied to new AhsayOBS user home(s). 4. Click [Restore] button to execute the configuration recovery process. 5. The restored AhsayOBS configuration settings will take effect after the AhsayOBS service is restarted. Ahsay Systems Corporation Limited 36

46 When a Configuration Recovery has been performed successfully, the following messages will be shown in the AhsayOBS system log: WARNING: i. The Configuration Recovery feature does not support recovery of AhsayOBS system configuration on a cross O/S platform environment, i.e. configuration files from a Windows AhsayOBS cannot be recovered to a Linux/FreeBSD/Solaris AhsayOBS vice versa. ii. To perform a Configuration Recovery to a new AhsayOBS installation the license key from the original AhsayOBS server must be applied. iii. The new AhsayOBS server must be able to connect to the Ahsay License Server (ALS) in order to perform a Configuration Recovery. Ahsay Systems Corporation Limited 37

47 5 Software License This chapter describes how you can use the [Manage System] -> [Software License] page (shown below) to manage software license of AhsayOBS. Ahsay Systems Corporation Limited 38

48 Key License Name License Key Connection Test Company Name Contact Name Contact Contact Number AhsayOBM Description Business name of the licensee License Key to activate this software. Please enter [License Key] as a printed on the [Software License Agreement] into the text field provided. Test the connection between AhsayOBS and license server. The company name used for contact. The name of the contact person. The address of the contact person. The phone number of the contact person. The maximum number of the AhsayOBM backup account allowed. The following may be displayed when there are some special arrangement on your AhsayOBM license CAL: ( number ) - The number in the round bracket is the quota of AhsayOBM used by the AhsayACB. ( number ) - The number in the round bracket is the quota used by Microsoft Exchange Server Database Availability Group One AhsayOBM license CAL with one Exchange Server Add-on Module is deducted from each installation of the AhsayOBM on the DAG environment. AhsayACB User Add-on Modules The maximum number of the AhsayACB backup accounts allowed. It shows whether different client side add-on modules are enabled for AhsayOBM/AhsayACB. You need to have a new license key to enable these modules. Quota the total number of licenses of a particular module available. Used the total number of licenses of a particular module assigned to users. Available the total number of license of a particular module available for future use. Server Add-on It shows whether different server side add-on modules are Modules enabled for AhsayOBS/AhsayRPS. You need to have a new Ahsay Systems Corporation Limited 39

49 license key to enable these modules. Ahsay Offsite Backup Server Product Name Product Version Expiry Date Free Upgrade Until Max Quota Name of the licensed product. Version number of the licensed product. The date when the current license key will expire. You will not be able to use AhsayOBS after this date. The last date you are allowed to upgrade to the latest AhsayOBS available. You will not be able to upgrade to any software release after this date with your current license key. The maximum quota for each backup user supported. Ahsay Systems Corporation Limited 40

50 5.1 Licensee Name and License Key When you click the [Manage System] -> [Software License] link available at the top menu, the [Software License] panel will appear (see above). 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 typo 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 displayed next to the test button. The AhsayOBS 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 AhsayOBS, please setup the [proxy setting] in the [Manager Server] 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. 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 AhsayOBS on another server, you will get an Internal Error 1011 or Internal Error 1012 message. You can still run this copy of AhsayOBS 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. 5.2 Automatic License Renewal If AhsayOBS 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. AhsayOBS is not able to connect to the Ahsay License server. The expired license key will have a grace period of 14 days. AhsayOBS can still function normally using the expired license for an extra 14 days before the service is automaticially shutdown. The 14 day grace period is to allow sufficient time to resolve any license related problems. Ahsay Systems Corporation Limited 41

51 5.3 Evaluation Expiry and Free Edition After the evaluation period, the evaluation key will expire and the AhsayOBS will automatically be stopped. Although the service will still be alive, AhsayOBM and AhsayACB cannot do backups anymore. You should get the following screen when it happens: If you want to continue using AhsayOBS, you can press the [Buy Licenses Online] button to purchase new licenses or contact our Sales Team via our Ahsay Forum. However, if you have not yet decided to purchase our product, you are welcome to apply for a free license. To apply for a free license, please input all contact details (including [Company Name], [Contact Name], [Contact Address], [Contact Phone Number]), and then press the [Request for free license] button. An will be sent to your account in a short time. Ahsay Systems Corporation Limited 42

52 Within the , you will have the licensee name and license key received. Copy and paste the values to the fields on the page of [Manage System] -> [Software License] respectively. After that, press the [Update] button at the end of the page. Then you should be able to continue to use AhsayOBS. If you have created some backup users in AhsayOBS before, you may get the following message on the license page: Ahsay Systems Corporation Limited 43

53 The system prompts that the quota is exceeded, because generally free version of AhsayOBS has more limitations on number of users, modules and features than evaluation version. When it changes to Free Edition, the extra users will be suspended and the user accounts will stop functioning. Users to be suspended are chosen randomly. We would recommend that you should remove/suspend the extra users before switching to Free Edition. After you have purchased a new license, you can apply the licensee name and license key as described in previous sections. You can then re-activate the users by using the tools in [Manage User]. For more information on [Managing User], please refer to the section of Managing User in this document. 5.4 Offline License Activation Offline License Activation is a new feature added to AhsayOBS since v It is used to activate the AhsayOBS license for servers that do not have internet connection. In order to use the offline license activation, you must first install AhsayOBS v or above. After you have finished installing the AhsayOBS, please open the web management console and go to the license page ([Manage System] -> [Software License]). On that page, you should be able to see the [Advanced Option] link near the bottom right hand corned. Please click on that link to display the offline license options. Ahsay Systems Corporation Limited 44

54 The offline license options should now be shown on the screen. The next step in the offline license activation process is to generate an 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. To generate the offline license request file, please press the [Generate] button under the [Advanced Option] under of the license page. The offline license request file will then be generated and it will prompt for the location to save the offline license request file. Ahsay Systems Corporation Limited 45

55 When the offline license request file is ready, please send it to our Support team via . 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 AhsayOBS to complete the offline activation process. Before importing the offline license files to AhsayOBS, you must ensure that it is placed in the system home folder of AhsayOBS. Then, you should logon to the AhsayOBS web interface to import the license from the [Software License] page (i.e. [Manage System] -> [Software License]) and click on the [Advanced Option] link. Press on the [Browse] button and select the offline license file from AhsayOBS system home. Click on the [Offline Update] button to complete the process. If there is no error message shown on the [Software License] page, the Offline License Activation process is completed successfully. 5.5 License Management Portal The License Management Portal is an online license management tool. It provides a convenient method for partners to manage their AhsayOBS license keys online. For more information on this feature, please refer to the online documentation on the License Management Portal. Ahsay Systems Corporation Limited 46

56 6 Managing Routine Job This chapter describes how you can use the [Manage System] -> [Routine Job] page (shown below) to manage number of system routine jobs of AhsayOBS. When you click the [Manage System] -> [Routine Jobs] link available at the top menu, the [Routine Jobs] panel will appear. You can use the form available on this panel to define your preferences of how you want different system routine jobs to run. Key Backup Report Online Restore Report Setting Change Report Missed Backup Report Description Hourly job sending backup reports to users whose backup job have completed within the last hour. Hourly job sending online file restoration reports to users who have performed and completed an online file restoration action within the last hour. Hourly job sending setting change reports to users who have updated their backup setting within the last hour. Hourly job checking whether any scheduled backup job has been missed for all backup users and sending missed backup reports to users who have missed their backup jobs. Inactive User Report Daily job sending inactive user reports to users if their accounts have been inactive for more than 7 days. Ahsay Systems Corporation Limited 47

57 Off-line Backup Reminder Backup Quota Reminder Trial user Reminder Usage Report Error Report Replication Error Report Inactive User Removal Retention Policy Job Rebuild User Storage System Log Removal Debug Log Removal Cyclic Redundancy Check (CRC) Checking Force to check all backup files Configuration Archival Daily job sending off-line backup reminders to users who have set the off-line backup option and have not performed a backup for the required number of days. Daily job sending backup quota reminders to users whose storage quotas are above a certain percentage. Daily job sending trial user reminders to users whose trial account are about to expire. Daily job sending system usage reports to system administrators. Daily job sending system error reports to system administrators. Daily job sending replication error reports to system administrators Daily job deleting all trial accounts that have been inactive for 60 days. Daily job removing obsolete files from the retention area according to each user s retention policy setting. Weekly job rebuilding all users storage information by walking through all users backup files. Daily job removing system logs older than this number of days from the system. Daily job removing debugging logs older than this number of days from the system. Routine job that will run at 2 nd and 4 th Saturdays of every month. It will verify the CRC of the files backed up to the server. If selected the CRC job will check all backup files regardless of last checked date. Daily job sending system settings, policies and user profiles to a secure remote storage. Ahsay Systems Corporation Limited 48

58 Note: It is strongly recommended you enable the CRC checking so that regular file integrity checks are made on the backup data files. 6.1 Backup Report The [User Report] -> [Backup Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Backup Report] routine job. The role of the [Backup Report] routine job is to send backup reports to users who have finished one of their backup jobs within the last hour. The backup report is scheduled to run every 57 minutes past the hour. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. 6.2 Online Restore Report The [User Report] -> [Online Restore Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Online Restore Report] routine job. The role of the [Online Restore Report] routine job is to send online file restoration reports out to users who have performed and completed an online file restoration action within the last hour. The online restore report is scheduled to run every 58 minutes past the hour. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. 6.3 Setting Change Report The [User Report] -> [Setting Change Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Setting Change Report] routine job. The role of the [Setting Change Report] routine job is to send reports out to users who have updated their profiles or backup set within the last hour. The setting change report is scheduled to run every 59 minutes past the hour. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. Ahsay Systems Corporation Limited 49

59 6.4 Missed Backup Report The [User Report] -> [Missed Backup Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Missed Backup Report] routine job. The role of the [Missed Backup Report] routine job is to send reminder notice to users who have missed one of their scheduled backup jobs. AhsayOBS defines a scheduled backup job to be a missed backup job if there is no backup run 6 hours after a backup has been scheduled. The missed report is scheduled to run every 56 minutes past the hour. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. 6.5 Inactive User Report The [User Report] -> [Inactive User Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Inactive User Report] routine job. The role of the [Inactive User Report] routine job is to send a reminder notice to users who have been inactive on the system. This job will run daily as defined by the [Daily at] setting, the default start time is 09:20 AM. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. 6.6 Off-line Backup Reminder The [User Report] -> [Off-line Backup Reminder] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Off-line Backup Reminder] routine job. The role of the [Off-line Backup Reminder] routine job is to send a reminder notice to users who have set the off-line backup option in their backup sets but failed to backup for a certain amount of time. This job will run daily as defined by the [Daily at] setting, the default start time is 09:25 AM. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. 6.7 Backup Quota Reminder The [User Report] -> [Backup Quota Reminder] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Backup Quota Reminder] routine job. The role of the [Backup Quota Reminder] routine job is to send a reminder notice to users whose storage quota usage has hit a pre-defined percentage, the default quota usage setting is more than 90%. Ahsay Systems Corporation Limited 50

60 This job will run daily as defined by the [Daily at] setting, the default start time is 09:05 AM. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. Please also set the pre-defined percentage of storage divided by quota that will trigger this reminder. 6.8 Trial User Reminder The [User Report] -> [Trial User Reminder] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Trial User Reminder] routine job. The role of the [Trial User Reminder] routine job is to send a reminder notice to users whose trial accounts that their account will expire. The default setting is to send reminder reports 25 days after trial account registration. This job will run daily as defined by the [Daily at] setting, the default start time is 09:50 AM. If you want your users to receive these reports, please select the [Enable] option. Otherwise, select the [Disable] option. Please also set the number of days after registration that the users should get this reminder. 6.9 Usage Report The [System Report] -> [Usage Report] setting under the [Manage System] - > [Routine Job] page defines the setting of the [Usage Report] routine job. The role of the [Usage Report] routine job is to send usage report, which contains a statistics of all backup users activities, to the administrative contacts of AhsayOBS. This job will run daily as defined by the [Daily at] setting, the default start time is 09:55 AM. If you want the administrative contacts of AhsayOBS to receive the usage report, please select the [Enable] option. Otherwise, select the [Disable] option Error Report The [System Report] -> [Error Report] setting under the [Manage System] - > [Routine Job] page defines the setting of the [Error Report] routine job. The role of the [Error Report] routine job is to send error report, which contains a full listing of all system and backup errors, to the administrative contacts of AhsayOBS. This job will run daily as defined by the [Daily at] setting, the default start time is 09:15 AM. If you want the administrative contacts of AhsayOBS to Ahsay Systems Corporation Limited 51

61 receive the error report, please select the [Enable] option. Otherwise, select the [Disable] option Replication Error Report The [System Job] -> [Replication Error Report] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Replication Error Report] routine job. The role of the [Replication Error Report] routine job is to send the replication error report, which contains the list of errors appear during the replication process. This job will run daily as defined by the [Daily at] setting, the default start time is 00:00 AM. If replication is enabled on AhsayOBS and you want the administrative contacts of AhsayOBS to receive the replication error report, please select the [Enable] option. Otherwise, select the [Disable] option Inactive User Removal The [System Job] -> [Inactive User Removal] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Inactive User Removal] routine job. The role of the [Inactive user Removal routine job is to remove inactive trial users (i.e. no logon or backup traffic from this user) from AhsayOBS as defined by the Free Trial Setting. This job will run daily as defined by the [Daily at] setting, the default start time is 09:35 AM. If you want this job to run, please select the [Enable] option. Otherwise, select the [Disable] option Retention Policy The [System Job] -> [Retention Policy] setting under the [Manage System] - > [Routine Job] page defines the setting of the [Retention Policy] routine job. The role of the [Retention Policy] routine job is to delete files from the retention area for each user according to the retention policy of each backup set of each backup user. This job will run daily as defined by the [Daily at] setting, the default start time is 09:40 AM. If you want this job to run, please select the [Enable] option. Otherwise, select the [Disable] option. Note: The retention policy job would retain data in accordance to the retention policy configured for the corresponding backup set. A formula is used to determine which file should be "retained" in "Days" unit, at "00:00" of each day (NOT the system routine job execution time). For a backup set with a 7 Ahsay Systems Corporation Limited 52

62 'days' retention policy, the system routine job would retain modified / deleted data of the past 7 days (oldest data being uploaded after 00:00, 7 days ago). WARNING: Disabling the Retention Policy job could result in: i. User accounts exceeding there quota limits and therefore interrupting normal backup operations. ii. AhsayOBS user home(s) drives running out of space, which could result in your AhsayOBS becoming unstable and or cause data corruption Rebuild User Storage The [System Job] -> [Rebuild User Storage] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Rebuild User Storage] routine job. The role of the [Rebuild User Storage] routine job is to recalculate all users storage information (e.g. data area file size/number, retention area file size/number) by traversing through all backup files for all users within the system. The job is designed to run weekly and will run at the time defined by the [Every WEEKDAY at] setting, the default start time is every Sunday at 09:30 AM. If you want this job to run, please select the [Enable] option. Otherwise, select the [Disable] option. Note: i. As the Rebuild User Storage job is relatively I/O intensive job, it is recommended to schedule this job to run during off peak periods. ii. When a rebuild user storage is run on a user account with active backupsets, the calculations for the storages statistics may not reflect the actual storage used as all active backupsets are skipped System Log Removal The [System Job] -> [System Log Removal] setting under the [Manage System] -> [Routine Job] page defines the setting of the [System Log Removal] routine job. The role of the [System Log Removal] routine job is to remove all system logs (i.e. all information under the System Home, e.g. system error logs or backup error logs) from AhsayOBS after the [Keep Logs For] number of days. Ahsay Systems Corporation Limited 53

63 This job is designed to run daily and will run at the time defined by the [Daily at] setting, the default start time is 09:45 AM. If you want this job to run, please select the [Enable] option. Otherwise, select the [Disable] option Debug Log Removal The [System Job] -> [Debug Log Removal] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Debug Log Removal] routine job. The role of the [Debug Log Removal] routine job is to remove all debugging logs (e.g. access logs and web application context logs) from AhsayOBS after the [Keep Logs for] number of days. This job is designed to run daily and will run at the time defined by the [Daily at] setting, the default start time is 09:10 AM. If you want this job to run, please select the [Enable] option. Otherwise, select the [Disable] option Cyclic Redundancy Check (CRC) Checking The [System Job] -> [Cyclic Redundancy Check (CRC) Checking] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Cyclic Redundancy Check (CRC) Checking] routine job. The role of this routine job is to check the CRC of the backup files on every 2 nd and 4 th Saturdays every month, the default start time is 12:00 AM. The Cyclic Redundancy Check (CRC) Checking job will check all new files on AhsayOBS. When the CRC job checks a file it will update the file header with an AhsayOBS CRC next check date. This is calculated as (random number of 0 to 60) days, so for existing files which have been checked previously. The next CRC check on the file will be performed after 180 to 240 days. During this checking, it will check the followings things: The file size of the backup file with the size stored in the header of backup file. The CRC value of the backup file with the checksum value stored in the header of the backup file. Files will be deleted if it is found to be invalid or corrupted in the retained area and current folder. Other affected files in the delta chain may also be deleted. To configure the Cyclic Redundancy Check (CRC) Checking job to validate all files regardless of the last checked date, please check the [Force to check all backup files] option. Ahsay Systems Corporation Limited 54

64 WARNING: Using the [Force to check all backup files] option could result in performance issues with your AhsayOBS server. This option may impact on backup and restore performance Configuration Archival The [System Job] -> [Configuration Archival] setting under the [Manage System] -> [Routine Job] page defines the setting of the [Configuration Archival] routine job. The role of the [Configuration Archival] routine job is to backup critical AhsayOBS configuration files (e.g. CONF folder, Policy Home and User Home) and upload them to the Ahsay License Server (ALS). At most 30 days of configuration files will be kept on the ALS. This job is designed to run daily and will run at the time defined by the [Daily at] setting, the default start time is 12:30 PM. This job is disabled by default. Ahsay Systems Corporation Limited 55

65 7 Managing Replication The replication module is managed by the [Manage System] -> [Replication Config] page. For more information about this feature, please refer to the Ahsay Replication Server. Also, please refer to the AhsayOBS and AhsayRPS Setup Guide for information on how to install the AhsayRPS to work with AhsayOBS. Ahsay Systems Corporation Limited 56

66 8 Managing Other Options This chapter describes how you can use the [Manage System] -> [Other options] page (shown below) to manage the advertisements for all users and default In-File delta setting for AhsayACB users. Key In-file setting Block Size delta Description Select this option to enable and use in-file delta technology for all AhsayACB clients. The in-file delta block size used to detect changes within a file. A smaller block size should produce a smaller delta file but requires more processing power. The default setting of [Auto] will choose the optimal block size for each file based on the file s original file size. Minimum Size Delta Merge In-File Delta Type The minimum size setting defines the smallest file size to apply the in-file delta. To enable delta merging on all users. The In-File delta type to use for calculating the delta file: Incremental this option uses the previous uploaded full or incremental file to calculate the delta. It produces the smallest delta for upload but requires the most time and processor power to restore. Differential this option always uses the latest uploaded full file to calculate the delta. It Ahsay Systems Corporation Limited 57

67 Upload Full File produces a larger delta but allows for the fastest restore. The upload full file setting determines when the full file should be uploaded to the server instead of the delta. It depends on either of the following rules being true: Maximum No. of Delta the total number of deltas uploaded since the last full file. The default setting is 100 deltas. Delta Ratio the ratio of the Delta Size divided by the Full file size. The default setting is 50%. Adgroup for all AhsayACB and AhsayOBM users Advertisements An adgroup groups multiple advertisements into a logical unit which can then be assigned to different users. All advertisements within an adgroup will be presented to all users who have been assigned to this adgroup. Click the [Add] link to add new advertisements. Note: The compression type option for AhsayACB is not configurable, new AhsayACB users created with AhsayOBS version 6.9 or above will use the Fast compression setting for default. Fast compression has less compression ratio, the size of the backup should be larger than those pre-existing AhsayACB users with same amount of backup data. Pre-existing AhsayACB customers will use normal compression settings. 8.1 In-File Delta Settings for all AhsayACB users The [In-File delta settings for all AhsayACB users setting under the [Manage System] -> [Other Options] page defines a global setting of In-File Delta Technology for all AhsayACB clients. Select this option to enable In-File Delta Technology for AhsayACB clients. 8.2 Block Size The [Block Size] setting defines the size of data block being used to detect changes between the last full backup file and the file being backed up. In general, the smaller the block size, the more likely a matched data block can be found, hence produces a smaller delta file but will require more processing power to detect these changes. On the other hand, In-File delta backup running with a larger block size will run faster but this will generally produce a larger delta file. Ahsay Systems Corporation Limited 58

68 The default setting [Auto] will select the optimal block size for each file depending on the size of the file. The [Auto] setting will set the block size according the following criteria: File Size Block Size < 2 GB 4 KB 2 GB to 8 GB 8 KB > 8 GB 16 KB 8.3 Minimum Size The [Minimum Size] setting defines the smallest file size a file (the default value is 25 MB) must have before the use and application of in-file delta backup technology. If the size of a file being backed up is smaller than the [Minimum File Size] setting, in-file delta backup technology won t be applied to this file and the whole file, instead of just the delta file, will be uploaded to the backup server. For backupsets which contain relatively small files, the [Minimum Size] should be increased. As it is not necessary to perform in-file delta backup on small files because backing up the full file doesn t take too long anyway. The advantage of backing up the full file is it will reduce the amount of time required to restore, i.e. the restore of one small full file is much quicker than the restore a small file with associated incremental delta s. 8.4 Delta Merge The [Delta Merge] setting under the [Manage System] -> [Other Options] page defines a global setting of delta merging for all AhsayACB clients. This setting is disabled by default. If delta merge is enabled, it is recommended to use the in-file delta type Incremental. WARNING: When the delta merge option is enabled and the in-file delta type Differential is selected. The Delta merge feature will not merge differential delta files with the full file. Delta merge will only work if there are pre-exisitng incremental delta files in the delta chain. Once the incremental delta s are merged, the delta merge feature will no longer merge files in the delta chain. Ahsay Systems Corporation Limited 59

69 8.5 In-File Delta Type The [In-file Delta Type] setting defines the way In-File Delta files are handled. There are two different versions as follows: Incremental In-File Delta All delta files are generated with respect to changes made since the last incremental backup. This means that the last full backup file and all related incremental delta backup files are required to restore the latest snapshot of a backup file. The full backup file, its checksum file and all incremental delta files are always stored in the data area. This means that these files are not affected by the setting of the retention policy and will always be kept on the backup server. But for backupsets with delta merge enabled, the retention policy setting is also used by the delta merge feature to determine when AhsayOBS will merge the full and incremental delta files into a new full file. Differential In-File Delta All differential delta files are generated with respect to changes made since the last full backup file. This means that only the last full backup file and the last differential delta file are required to restore the latest snapshot of a backup file. The other intermediate differential delta files are only required if you want to restore intermediate snapshots of a backup file. The advantage of a differential In-File delta backup is that a corrupted differential delta file would only make one particular snapshot of a backup file non-recoverable. All other snapshots can still be recovered using the remaining differential delta files. The full backup file, its checksum file and the last delta file uploaded (if more than one delta files have been uploaded to the backup server) is always stored in the data area. This means that these files are not affected by the setting of the retention policy and will always be kept on the backup server. It is done this way because all these files are required to get the latest snapshot of the backup file and they should not be removed from the backup server by the retention area cleanup routine. All other intermediate delta files are stored in the retention area. 8.6 Upload Full File The [Upload Full File] setting defines when to upload a full file instead of a delta file. No. of Delta The [No. of delta] setting defines the maximum number of delta files from the same full backup file to be generated and backed up to the backup server Ahsay Systems Corporation Limited 60

70 before a full backup (the whole file) of this file is uploaded to the backup server instead. For example, if you have created 100 delta files from the full backup file already and this [No. of delta] setting is set at 100, the next backup will upload a full backup file (the whole file) instead of just the delta file. However, if the [No. of delta] setting is set to unlimited. It will keep generating delta files and uploading these delta files to the backup server until the other delta setting condition (delta ratio exceeded) forces a full backup. This setting is here to make sure that there will always be a full backup file after a certain number of delta files have been generated. Delta Ratio The [Delta Ratio] setting is defined as the file size of a delta file (the file size of the delta file generated by AhsayOBM on the client computer) and divided by the file size of its full backup file (the file size of the backup file on the disk of client computer), i.e. the percentage of changes detected between the last full backup file and the current file. If the delta ratio calculated from the size of the generated delta file and the size of the full backup is greater than the [Delta Ratio] setting, the whole file, instead of just the delta file, will be backed up to the backup server. It is done this way because the difference between backing up the whole file and the delta file is not significant and it is better to upload the whole file instead. The default setting of [Delta Ratio] is 50%. This means that if the changes detected within a file are more than 50%, the whole file, instead of the delta file will be backed up and uploaded to the backup server. It is recommended for backupsets where the full file size(s) are relatively small: 1. The [No. of delta] settings be kept to a low value 2. The [Delta Ratio] setting should be less than 50% 3. The [Minimum Size] setting should be increased to more than 25 MB This will minimize the probability of future restore problems caused by invalid or corrupted delta files. 8.7 Adgroups An adgroup groups multiple advertisements into a logical unit which can then be assigned to different users. All advertisements within an adgroup will be presented to all users who have been assigned to this adgroup. To add a new adgroup, type the name of the adgroup in the empty field located under [Adgroup for all AhsayACB and AhsayOBM users] and next to Ahsay Systems Corporation Limited 61

71 the [New] text. Press the [Update] button at the bottom and a new adgroup will be created. 8.8 Advertisements The [Advertisements] setting defines the advertisements and related information that is displayed at the bottom of all AhsayACB clients. Key Add Description Click this link to add a new advert. Show Advertisement Log Click this link to view the advertisement log. Name Text Start Date Popularity Hits Time Move Target Remove The name of the advertisement. Click the link to edit this ad. The text to be displayed at the bottom of the AhsayOBM/AhsayACB client. The data when this ad was created. Calculated value to indicate which ad. Is the most popular. The value is calculated as the percentage of [Hit for this ad.] divided by [Total Hits]. The Hits counter indicates the number of times this ad. has been clicked. These counters are only updated if the option Enable Tracking is set. The three values are [Hits within 1 day] / [Hits within the last 7 days] / [Hits within the last 30 days]. The number of seconds to display the ad. The display sequence of the adverts. Click this link to test the advertisement s URL. This will open a browser and displays the URL web page. Click this link to delete the ad. Ahsay Systems Corporation Limited 62

72 Add New Advertisement Click the [Add] link to add new advertisements. Enter the ad. information into the form provided. Key Name Assigned Adgroups GIF Image Flash Image Text Text Animation Description The name of the advertisement. It determines if the advertisement should be included in the adgroup(s). The full pathname of the image file to be displayed at the bottom of the AhsayOBM / AhsayACB client. The image size should be 468 x 60, and the format should be in GIF. The full pathname of the flash image file to be displayed at the bottom of the AhsayOBM / AhsayACB client. The image size should be 468 x 60. Flash player must be available on the client s machine in order to display the image. The text to be displayed at the bottom of the AhsayOBM / AhsayACB client. Setting to define whether the text should scroll. Scroll Left text scrolls from right to left. Scroll Right text scrolls from left to right. None do not scroll text. Text Alignment Setting to define the text alignment. Ahsay Systems Corporation Limited 63

73 Left text is aligned left. Center text is centered. Right text is aligned right. Ahsay Offsite Backup Server URL Enable Tracking Seconds The URL of the ad. If the user clicks the ad. in AhsayOBM / AhsayACB, a browser will open and displays this web page. When selected, every time the user clicks the advert in the AhsayOBM / AhsayACB client, a Hits counter is incremented. The number of seconds to display the ad. Ahsay Systems Corporation Limited 64

74 9 Managing System Diagnosis This chapter describes how to manage the function in the [Manage System] - > [System Diagnosis] page. The default inspection type on this page is the showing the System Information, such as operating system, physical memory, heap size usage and number of threads on the server. This information is useful for administrator to check on the current health status of the AhsayOBS server and it is also useful for troubleshooting purpose. Key Operating System Description The version of the operating system that the AhsayOBS hosted on. Eg: Windows 2003, Windows XP. Architecture The CPU architecture (ISA) series for computer processors. Number Processors Of Number of independent actual processors in a single computing component. Committed Virtual Memory Amount of virtual memory guaranteed to be available to the running process. Total Memory Physical Total amount of random-access memory (RAM). Ahsay Systems Corporation Limited 65

75 Free Memory Physical Amount of free RAM available on the operating system. Total Swap Space Free Swap Space Current Heap Size Total amount of storage space in the hard disk drive that is used for virtual memory. The amount of free space in the hard disk drive that is used for virtual memory. Amount of memory currently occupied by the Java heap. Maximum Size Live Threads Peak Heap The maximum limit of Java heap size. Current number of live daemon and non-daemon threads. The highest number of live threads since Java Virtual Machine (VM) started. Daemon Threads Current number of live daemon threads. Total Started Threads Total number of threads started since Java VM started, including daemon, non-daemon, and terminated threads. When the [System Files] inspection is selected, the following screen will be shown. You can click into the folder path to navigate on your AhsayOBS server and you can click on the download icon to download the file/folder. You have the option to download the file in Zip format or no compression format. For example, if your file that you need to open is only several hundred Kbytes, you can use the no compression option. If the file size is several Mbytes, or Ahsay Systems Corporation Limited 66

76 even Gbytes in size, or you are going to download the whole folder, you should use the Zip option. The download file will be renamed as *.zip and you need to unzip it by eg: Winzip. Also if the download file is in Zip format, the download speed will be much faster than no compression format. Key Size Last Modified Description Size of the file (unzip). The last modified date of the file. Ahsay Systems Corporation Limited 67

77 10 Manage System User (Reseller Panel) This chapter describes how you can use different function under the [Manage System User] menu to manage the system users or resellers within AhsayOBS. The [Manage System User] feature allows backup server administrators to create three types of system users, Admin, Sub Admin and Non-Admin. System users with the Admin role have full control to manage all the system systems, policy sttings and backup user accounts. System users with the Sub Admin role have full control to managing their own backup user accounts. While Non-Admin system users only have read only access to the backup user accounts created by the Sub Admin system user. System users or resellers can independently manage there own group policy settings. Please refer to the chapter Group Policy Management for further details. The backup server administrator can utilize system user accounts depending on the environment where the AhsayOBS server is deployed. 1. If AhsayOBS is deployed as an internal company backup service. The backup server administrator can create system user account with "Sub Admin" role for each department to manage their own backup users. 2. If AhsayOBS is deployed as a commercial backup service. The backup server administrator can create a system user account with "Sub Admin" role for each of their resellers to manage their own clients. Each system user (Sub Admin) or reseller account on AhsayOBS supports the following customization features. 1. The look and feel of AhsayOBS web console along with the customized logos. 2. Customized logo for the reports sent to backup users. 3. Customized user guide. 4. Report can be sent via a system users own SMTP server. Each backup client type, i.e. AhsayOBM, AhsayACB can have its own designated report sender and reply address. 5. Each system user or reseller can install there own web SSL certificate. From AhsayOBS v onwards each system user (Sub Admin) or reseller account has full control in deploying client side upgrades for each backup user account under their control. Ahsay Systems Corporation Limited 68

78 10.1 My Profile / Edit System User When you click the [Manage System User] - > [My Profile] link available at the top menu, the [My Profile] form will be shown. You can then update system user profile to the system by submitting this form to AhsayOBS. The panel will display differently depending on the role of current login system user. Admin Role The build-in system account is defined as Admin role. Admin role user has the highest authorization level, all the AhsayOBS settings, backup users settings can be accessed or modified by Admin role users at all times. From , new Admin role user can be added via the AhsayOBS management console > Manage System User > Add System User The above user has the Admin role and it 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 AhsayOBS for you. Ahsay Systems Corporation Limited 69

79 Non Admin Role Non Admin role system user shares the similar accessibility as its creator except with read permission only (Descendant system users and backup users of its creator could be accessed). If Non Admin role system user needs to have the same User Control Policy Settings as its creator, remember to add the Non Admin role system user in the same user group as its creators. For example, you may assign your operators to login the AhsayOBS to check on the backup reports and AhsayOBS system logs etc, without worrying that they will modify any settings on the AhsayOBS accidentally. Sub Admin Role Sub Admin role system user can access all descendant system users and backup users. When Single Level Access is enabled, system users are restricted to only accessing their own created system users, backup users of system users. Please refer to the chapter Single Level Access for further details. Ahsay Systems Corporation Limited 70

80 Note: 1. Backup user accounts created by sub admin system users are only supported by AhsayOBM and AhsayACB v or above clients. 2. Backup user accounts created by sub admin system users running in an AhsayRDR setup, are only supported by AhsayOBM and AhsayACB v or above clients. 3. For sub admin with a different hostname setting than the default system account, all backup accounts created by that sub admin must use the corresponding hostname when logging into the AhsayOBM/ACB client or web interface. 4. If your domain name has already mapped with the port name eg :8080 backup.backupvault.com the port number 8080 is not required in the client connection settings. Summary of the privileges of Admin, Sub-Admin and Non-Admin users Role Description Admin Sub-Admin Non-Admin General System Settings Read only * Connectivity Testing * System Diagnosis * System Logs Read only Read only Read only User Management (Profile, Read only AutoUpdate, Report) Backup Set Management Read only Ahsay Systems Corporation Limited 71

81 Run Backup Restore via restorer applet Delete file via restorer applet Group Policy Management Read only System User Management Read only * It is valid that the Non-Admin is created by the Admin but not valid if the Non-Admin is created by the Sub-Admin SMTP Settings [SMTP Settings] is available for Sub Admin role system user only. When [SMTP Settings] is enabled, user reports and system reports for current Sub Admin role system user and the associated backup users will be sent through system user defined SMTP server instead of default SMTP server defined at [Manage System] -> [Server Configuration] panel. The report sender contact information can be separated for OBM and ACB backup clients. A maximum of one report sender contact information can be defined for each backup client type. Note: SMTP server with Transport Layer Security (TLS) is not supported Customize Interface [Customize Interface] is available for Sub Admin" role system users only. This option allows Sub Admin role system users to customize their AhsayOBS web interface, documentation and company logo in report with their own branding. The default customization files are compressed into custom.zip file and can be downloaded from the key section (circled in RED). It consists of three folders for different customization formats: 1. css for web style sheets. 2. gif for AhsayOBS web interface logos. 3. pdf for documentation. When updating the contents of the custom.zip file, please be careful not to change the folder structure or the folder names otherwise the customization cannot be applied to AhsayOBS. The custom.zip should only contain the following folders: -->css -->gif Ahsay Systems Corporation Limited 72

82 -->pdf The language code is enforced on.css and.pdf customization files. Please specify language code and appended it to the end of the file (e.g. jsp_en.css, jsp_da.css, obs-admin-guide_en.pdf, obs-admin-guide_da.pdf), system default settings will be used if language code cannot be found from uploaded files. Previous uploaded customized file can be downloaded again for further modification (circled in BLUE). AhsayOBS reseller customization will be effective once custom.zip is uploaded from [Manage System] -> [Manage System User] -> [%system_user%] -> [Upload Customization File]. Please refer to the section Branding AhsayOBS in this document for the use of customization files. A description of all fields above is provided in the following table. Key Login Name Role Password Description Login Name of current system user. Role of the current system user. Password of the current system user used to logon to web interface. Ahsay Systems Corporation Limited 73

83 Name Host Name SMTP Server Report Sender Upload Customization File report contact name of the current system user. address of the current system user. A resolvable hostname of dedicated for the current system user. (e.g. backup.company.com). Although you can supply an IP address here, Login name cannot be duplicated under the same host name. The SMTP server that AhsayOBS will use to deliver its reports to current system user and backup users of current system user. The name and address that will be used as a sender for all outgoing mails to backup users of current system user. A maximum of two different report senders can be defined for AhsayOBM and AhsayACB users separately. Upload AhsayOBS web customization file custom.zip to the system. Once the custom.zip file has been successfully uploaded to the reseller or system user account, the files will be uncompressed and saved under the %OBSR_HOME%\system\policy\SystemUser\%systemuser% folder along with a copy of the custom.zip file. Ahsay Systems Corporation Limited 74

84 Customize Reseller Reports In addition to modifying the look and feel of the AhsayOBS web console, each reseller can customize "logo" and "home page link" for the following reports: 1. Backup Job Reminder Report 2. Backup Quota Reminder Report 3. Backup Report 4. Error report 5. Forgotten Password Report 6. Inactive User Report 7. New User Report 8. Offline Backup Reminder Report 9. Setting Change Report 10.Trial User Reminder Report In order to customize the reports, please replace the "default.large.gif" found in the gif folder of the custom.zip file, with the reseller customized logo and rename it to "default.large.gif" Ahsay Systems Corporation Limited 75

85 The following is an example of a customized reseller New User report: The customized reseller logo will appear on the top left hand corner of each report. 1. The logo is linked to the IP Address/URL of particular resellers AhsayOBS web console, when the logo is double clicked the resellers AhsayOBS web console will be loaded on the machines default web browser. 2. The installation wizard link will load the AhsayOBM/AhsayACB installation page using the resellers IP Address/URL Add System User When you click the [Manage System User] -> [Add System User] link available at the top menu, the [Add System User] panel will be shown. This panel allows Admin role user to add an Admin, Sub Admin and Non Admin role user to the AhsayOBS. A Sub Admin role user can also create Sub Admin and Non Admin role user using this panel. This panel is similar to the [My Profile] page under [Manage User] setting, except that user has the choice to select the [Role] on this page. The SMTP settings will be inherited to its associated users. Ahsay Systems Corporation Limited 76

86 10.5 List / Remove System User When you click the [Manage System User] -> [List System User] link located at the top menu, the [List System User] panel will appear. This panel allows you to list and access all other system users within your authority. You can use the alphabet categories at the top of the user listing to filter the listing to show those users whose login name starting with a certain alphabet. You can also use the [ALL] function to list all system users. When you click the [Login Name] link available on the system user list, the [System User Settings] panel will appear for system user profile editing. When you click the [Role] link available on the system user list, the system user list will be filtered again by the selected system user. When you click the chain of system user list link under the alphabet categories (circled in RED), the system user list will be filtered again by the selected system user. Some definitions of the fields related are shown in the following table: Key Chain of System User Login Names Login Name Role Name Host Name Backup User Description It is shown by click on the role column in the [Manage System Users] Page. You can filter a list of accessible system users of the selected system user by clicking on the login name link on the chain. Login Name of the system user. Clicking [Login Name] link to access system user profile. Role of the system user. Select system user by clicking [Role] link to filter accessible system users of selected system user. report contact name of the system user. address of the system user. Host name/ip address assigned to the system user. Display in AhsayOBM and AhsayACB icons to indicate Ahsay Systems Corporation Limited 77

87 system user has one or more backup users. Clicking on the icon to view the list of backup users owned by the selected system user. Owner Remove The owner of the corresponding system user. To remove a system user from the system, just press the link next to the system user that you would like to remove. The recycling bin disappears when the system user has created one or more system users or backup users. For sub admin accounts the link will only be visible if there are no existing dependencies for the sub admin accounts, i.e. system and backup users created by this account. If you wish remove a sub admin account, you will need to remove all system and backup users accounts by this particular sub admin account Recovering a System User/Non-admin Password The Admin Role user can reset any Admin (except the build-in system user), Sub Admin and Non Admin role user s password via the AhsayOBS web console [Manage System] -> [Manage System User] -> [List System User ] -> [%system_user%] -> [System User Settings] -> [Password], then enter a new password and press the [Update] button. Alternatively, the server administrator can reset any Admin (except the build-in system user), Sub Admin and Non Admin role user password using the following procedure: Ahsay Systems Corporation Limited 78

88 1. Open the %OBS_HOME%\system\policy\sysUser.xml file in a text editor. 2. Locate the entry for the affect system user or non admin account: <user name="reseller1" password="6zoyxcjlonxyyiu2ejiuaw==" role="reseller" hashed-pwd="y" contact-name="reseller 1" contact ="reseller@ahsaymail.local" host-name=" " uid="13512" enable-smtp-setting="y"> <smtp-server host-name=" " login-name="" password=""/> <report-sender name="reseller 1 Manager" ="reseller@ahsaymail.local" obm="y" acb="y"/> <interface-customization enable="y"/> 3. Change the hashed-pwd="y" to hashed-pwd="n" 4. Change the password="6zoyxcjlonxyyiu2ejiuaw==" to password="%new_password%" The %New_Password% must be in clear text. 5. Restart your AhsayOBS service for the changes to take effect Reseller Backup User Account Restrictions Each Admin role user or reseller is allowed to create their own backup user accounts. However, Admin role users or resellers on an AhsayOBS server which share the same hostname, they cannot create backup user accounts with identical user names. If an Admin role user or reseller tries to create a backup user account whose username already exists under another reseller, the account creation will not be permitted. The example shows a system user reseller2 creating a backup user account test2, which has already been created by another system user reseller1. The following error will be shown on the AhsayOBS web console: Ahsay Systems Corporation Limited 79

89 10.8 Reseller Web SSL Certificate Installation It is possible to install an individual web SSL certificate for each reseller on AhsayOBS. In order to install a web SSL cert for a reseller, each reseller must be assigned an individual IP address. Example 1: A customer wants to setup an AhsayOBS server with the following configuration. 1. AhsayOBS server with URL main.xyzbackup.com which resolves to local IP address using ports 80 and Reseller 1 is assigned a URL res1.xyzbackup.com which resolves to local IP address using ports 80 and Reseller 2 is assigned a URL res2.xyzbackup.com which resolves to local IP address using ports 80 and 443. Each individual URL; main.xyzbackup.com, res1.xyzbackup.com, and res2.xyzbackup.com will have its own web SSL certificate. 1. Make copies of the default %OBS_HOME%\conf\keystore file i. %OBS_HOME%\conf\keystore_res1 for Reseller 1 ii. %OBS_HOME%\conf\keystore_res2 for Reseller 1 2. Edit the server.xml file <Connector address=" " port="80" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" /> <Connector address=" " port="443" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" Ahsay Systems Corporation Limited 80

90 enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" SSLEnabled="true" scheme="https" secure="true" keystorefile="conf/keystore" keystorepass="changeit" clientauth="false" sslprotocols="tlsv1" /> <Connector address=" " port="80" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" /> <Connector address=" " port="443" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" SSLEnabled="true" scheme="https" secure="true" keystorefile="conf/keystore_res1" keystorepass="changeit" clientauth="false" sslprotocols="tlsv1" /> <Connector address=" " port="80" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" /> <Connector address=" " port="443" maxhttpheadersize="8192" socketbuffer="65536" maxthreads="1000" minsparethreads="100" maxsparethreads="8192" maxkeepaliverequests="100" enablelookups="false" redirectport="443" acceptcount="200" connectiontimeout="60000" disableuploadtimeout="true" URIEncoding="utf-8" SSLEnabled="true" scheme="https" secure="true" keystorefile="conf/keystore_res2" keystorepass="changeit" clientauth="false" sslprotocols="tlsv1" /> Create new entries in the server.xml for Reseller 1 ( ) and Reseller 2 ( ). Ensure that each entry for https refers to a unique keystore file keystorefile="conf/keystore" keystorefile="conf/keystore_res1" keystorefile="conf/keystore_res2" 3. To install the individual web SSL certificates for each reseller, please refer to the instructions in Installing a trusted SSL certificate Auto Update Each reseller can manage the Auto Update of their own backup users and those of their own sub resellers from the AhsayOBS web console under the [Manage User] -> [Auto Update] page. The backup users accounts displayed include account created by the reseller and sub resellers, by default all backup users are selected for auto update. In addition to displaying the list of backup users, when Auto Update is enabled on AhsayOBS. Both the latest available upgrade versions for AhsayACB and AhsayOBM are shown. Ahsay Systems Corporation Limited 81

91 If the Auto Update feature is disabled on AhsayOBS the [Manage User] -> [Auto Update] page, will display the status Auto Update is disabled. Both the latest available upgrade versions for AhsayACB and AhsayOBM will not be shown. Note: If the Auto Update feature is disabled on AhsayOBS, the reseller(s) will have to contact the AhsayOBS server administrator to enable this feature Change Ownership Users can be relocated between different system administrator and reseller, or relocate between reseller and reseller on the AhsayOBS management console > [Manage System User] > [Change Ownership] page Ahsay Systems Corporation Limited 82

92 Migrating users from administrator to reseller Ahsay Offsite Backup Server To transfer users from administrator to reseller, please try the following steps: 1. Select the Transferor from the dropdown list to Administrator 2. Select the reseller from the Transferee dropdown list (eg: Bob) 3. Select the user to transfer by checking the check box next to the user. (eg: John) and press the [Update] button. Ahsay Systems Corporation Limited 83

93 4. User John disappeared because it is no longer under the Administrator s user list. Transfer completed. Note: 1. notification will not be turned on, as the user transfer is within the same host. 2. Backup users can be transferred between the same or different hosts. Section shows you how the user is transferred within the same host, while section shows you how the user is transferred between hosts. Ahsay Systems Corporation Limited 84

94 Matched host transfer The above example in section demonstrates how to transfer a user between matched hosts. They are all in the same host name eg: third.backup.com. You need to select the radio button Show Matched Hosts and you can transfer users within the same host name. Matched host transfer has less impact to backup user (ie, user does not require to change the connection host). Below is a diagram to illustrate how the user s ownership is transferred under a matched host. Backup user ownership can be transferred to the same hosts without notification Mismatched host transfer When a user is required to transfer between a different host name, eg: third.back-up.com to fourth.back-up.com Ahsay Systems Corporation Limited 85

95 1. In AhsayOBS management console > [Manage System User] > [Change Ownership] page 2. Select the radio button Show All Hosts 3. Select the Transferor from the dropdown list to Bob In this example, Bob has a few users and wants to transfer user Tim to reseller Claude. 4. Select the reseller from the Transferee dropdown list to Claude Ahsay Systems Corporation Limited 86

96 5. Select the user to transfer by checking the check box next to the user. (eg: Tim), you can see the Notify check box on the right hand side is also checked. 6. Click on the [Update] button. (A notification will be sent to backup user Tim to remind using a new connection host. All services will resume normal only after backup user relogin with new connection host.) 7. User Tim disappeared because it is no longer under the Bob s user list. Transfer completed. Ahsay Systems Corporation Limited 87

97 Note: notification can be disabled by unchecking the notify check box, user cannot connect to the backup server until the hostname setting is changed on the AhsayOBM/AhsayACB on the user machine. Below is a diagram to illustrate how the user s ownership is transferred under a mismatched host. Ahsay Systems Corporation Limited 88

98 Backup user s ownership can be transferred even when hosts are mismatched. The above example shows reseller Bob and Claude are under two different hosts, user Tim will receive notification and must re-login AhsayOBM/AhsayACB to allow the changes effective Reminder A notification will be sent to backup user when Notify option is selected. This reminds backup user to change their current backup connection settings to new connection settings on the AhsayOBM/AhsayACB. The reminder will only be sent when backup account is transferred successfully. Ahsay Systems Corporation Limited 89

99 The message [ChangeOwnership.send ] will be logged in the system log and user log when the is send to Tim Suggestions and Best Practice 1. When the system is running other process simultaneously on the backup user account, such as the following list of operations, change of ownership cannot be performed. - Backup (including server initiated backup jobs) - Restore - Rebuild (including on the fly rebuild, single user rebuild or weekly storage rebuild) - Delta merge - Delete files or backup set using AhsayOBM/AhsayACB or restore applet - Undelete - Retention policy - CRC job - Configuration archival - Delete backup file using API - Delete backup set using API - Delete backup data using API - Modify backup user using API 2. If a user is using CDP, user should disable the CDP before the ownership transfer. After the change ownership process, user must re-login to the AhsayOBM/ AhsayACB to enable the CDP. 3. Backup user account cannot be transferred if a duplicated account already exists on the transferee (reseller). 4. Backup user cannot be transferred if the user home is locked by external factor eg: file level access to the original user home. Ahsay Systems Corporation Limited 90

100 5. If the transferred user has been replicated to the the AhsayRPS server, after the change ownership process, the replicated user will be moved to the retention area on the RPS and the whole user folder of the newly ownership changed user will be replicated to the AhsayRPS again. This will affect users when the replication is running in UNSYNC and SYNC mode. If it is already in LOGGING mode, only the changes (e.g. folder rename, cloned policies) will be replicated to AhsayRPS. Please reserve enough disk space on the AhsayRPS. 6. When a user is transferred, all associated user groups and policy groups will be cloned under transferee to preserve the settings and uploaded data. Due to the current limitation, when another user under the same policy group is transferred, a new policy group will be cloned again on the reseller s policy group and this will end up duplicated policy groups. If you move the users one by one, it could end up with many duplicated policy groups, administrator or resellers are required to manually re-apply users to the dedicated policy group after user transfer and remove all those duplicated policy groups Common error messages Error Transferee cannot be empty The host name of transferee cannot be empty User xxx is running Backup operation. Ownership transfer cannot be proceed until the operation finished. User xxx is running some operations. Ownership transfer cannot be proceed until all operations finished. User xxx ownership transfer cannot be proceeded. The backup user, xxx, already exists in the system user, yyy Description No Transferee is selected. Transferee has no host name entry in the reseller s setting. Backup user cannot be transferred when user is running a backup operation. Backup user cannot be transferred when running multiple operations. Actual reason can refer to the AhsayOBS system log. Backup user cannot be transferred when user home is locked by external factor, eg file system is locked. A system administrator cannot transfer a backup user to a reseller because a duplicate user name already exists. E The backup user, xxx, has been Backup user cannot be transferred because transferee (reseller) is holding a backup client Ahsay Systems Corporation Limited 91

101 reserved. Please contact the System Administrator for assistance. Login Name xxx is used User xxx ownership transfer is in progress. with the same login name. Note: is the reseller s ID. Backup user cannot be transferred because transferee (System Administrator) is holding a backup client with the same login name. Backup users can only be transferred at most one transferee at a time. Ahsay Systems Corporation Limited 92

102 11 Managing Backup Users This chapter describes how you can use all pages under the [Manage User] menu to manage the backup users within AhsayOBS Create Backup User When you click the [Manage User] -> [Add User] link available at the top menu, the [Add User] form will appear (see below). You can then add a backup user to the system by submitting this form to AhsayOBS. A description of all fields above is provided in the following table. Key Login Name Password Alias Time zone Language Backup Client Assigned Adgroups Description Login Name of the new backup user. Password of the new backup user. Another name of the new backup user. Time zone of the new backup user. Preferred language for all reports of the new backup user. Choose AhsayOBM client or AhsayACB client. Choose whether advertisements are displayed at the bottom of the backup client. Ahsay Systems Corporation Limited 93

103 Type Either [Trial] or [Paid] type. Trial accounts and paid users differ in the following ways: 1. Trial users can only have a maximum backup quota of 500MB within the trial period. 2. 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. Welcome User Home address of the new backup user. Define whether a welcome should be sent to the new user address. The top directory where the software stores backup files and all other information for the new account. If you want this user to be in another partition (or in another drive), please add another user home to AhsayOBS by using the [Manage System] -> [System Configuration] page. If you want to setup your user home directories to a network drive, please do refer to FAQ: How do I add user storage to my AhsayOBS? (2437) for more information. Backup Quota Bandwidth Add-on Modules Backup Quota of the new account. Bandwidth allowed for the new account. Whether to enable any of the add-on modules to the new backup user. The [Microsoft Exchange Mailbox] text field defines the number of exchange mailboxes that is allowed to be backed up under this user account. Ahsay Systems Corporation Limited 94

104 11.2 List / Remove Backup User When you click the [Manage User] -> [List User] link available at the top menu, the [List User] panel will appear. You can use the alphabet categories at the top of the user listing to limit the listing to show only those users whose login names starting with a certain alphabet. You can also use the [All] function available to list all users within the system. To remove a user from the system, just press the would like to remove. link next to the user you Key Search By User Add-on modules Login Name (Alias) Registration Date Trial Expiry Date Used/Quota (%) Owner Description Define whether alphabetically search should be applied to [Login Name] or [Alias]. Indicates the add-on modules for this account. Login Name of this account. Click the link to see account details. The name in blankets is the alias, and the icon indicates the client type (AhsayOBM or AhsayACB). Date when this account was created. The expiry date of trial users. If it expires, the user account will be suspended. Paid users will show Never Expire in this field. The used/allocated quota (and the quota usage percentage) of this backup user. Owner of this backup user. Ahsay Systems Corporation Limited 95

105 Remove Export Users Usage Statistics to CSV Broadcast Message Remove this backup user. Export all users usage statistics to a.csv file. Use this option if you want to broadcast messages to backup users Broadcast messages to backup users After you press the [Broadcast Message] link on the top right hand corner of the [Manage User] -> [List User] panel, you will be brought to the [Broadcast Message] page. You can use this page to broadcast messages to different types of backup users. Key From To Description Sender of this message Broadcast message to the following users types: All all backup users Paid backup users of [Paid] user type Trial backup users of [Trial] user type AhsayOBM User - backup users of AhsayOBM client type AhsayACB User backup users of AhsayACB client type Admin backup administrator, i.e. address defined on the [Manage System] -> [System Configuration] -> [Administrator Contact] list (useful if you want to test the Ahsay Systems Corporation Limited 96

106 broadcast feature before sending the message out to all users). Subject Message Text/HTML Attachment Subject of this message Content of this message The content type of this message, i.e. whether content should be considered as plain text or HTML. A file to be broadcasted with this message Managing User Profile After you press the user name link on the [Manage User] -> [List User] panel, you will be brought to the [User Profile] for this particular user. You can use this panel to update the profile of this user. Ahsay Systems Corporation Limited 97

107 This panel is no different to the [User Profile] panel that users will see when they logon to the user areas except that you can now update the [Type], [Quota] and [Add-on Module] (shown in RED) entries on this page. Click the [File Validation Option] link to rebuild this user s storage information. When a rebuild user jobs is started, AhsayOBS will check if there is an active job running on the backupset before a rebuild is performed on the backupsets. If a backup job is active, the rebuild user storage job will skip rebuilding the active backupset, this will be recorded in the AhsayOBS system log. The information message [info][system][bfsmanager.rebuilduserbfs] The rebuild is skipped on the running backup set ESXi4( ) of user test1 is recorded when a backupset is skipped. From AhsayOBS v onwards, for the single user rebuild feature backup users or backup server administrators will have the option of selecting either: i. Rebuilding all backup sets under the backup user account or ii. Rebuilding a single backup set under the backup user account By default the single user rebuild will rebuild all backup sets under a backup user account. Ahsay Systems Corporation Limited 98

108 To perform a single user rebuild of a specific backup set, click on the Backup Set combo box and select the desired backup set. When a rebuild of a single backup set is completed, the following message will be shown in the AhsayOBS system log: The system log entries will specify that AhsayOBS has Finished single backup set rebuild. Note: i. When a rebuild user storage is run on a user account with active backupsets, the calculations for the storages statistics may not reflect the actual storage used as all active backupsets are skipped. ii. For issues relating to incorrect storage statistics, please make sure the rebuild user storage job is run when no backup jobs are active. Ahsay Systems Corporation Limited 99

109 iii. iv. If all backup sets under a user accounts need to be rebuilt, it is recommended that a single rebuild user storage job is started at least 45 minutes after the completion of the last backup job. If a single user rebuild is run for a single backup set, the Last Check date and time will also be updated. You can reset a user password by entering a new password in [User Profile] - > [Password] -> [New] entry and press the [Update] button. Even though the user password has been updated, both old and new passwords will be temporarily valid, until the user connects to AhsayOBS via AhsayOBM/AhsayACB with the new password. This is because a copy of the user s old password is still saved on the client machine. It s required by AhsayOBM/AhsayACB scheduler service to connect to AhsayOBS in order to run scheduled backups in the interim period. The [Microsoft Exchange Mailbox] text field defines the number of exchange mailboxes allow to be backed up under this backup account. The [Max] message indicates the maximum number of remaining licenses available. The [Bandwidth] option allows you to set a maximum network usage for all running backup sets of this particular backup account. All backup sets will share the same bandwidth defined by this setting. If you have set the bandwidth to be 128kbits/second and there are two backup sets running at the same time, each backup set will share roughly half of the bandwidth assigned, i.e. 64kbits/second. The [Notes] field allows you to attach some other information, e.g. telephone number or billing address, with this backup account. Any updates made to the user profile will trigger: i. A Settings Change Report will be sent to the user (if the routine job is enabled). ii. A log entry of the change will be recorded in the [Manage System] - > [Manage Log] -> [System Log] iii. A log entry of the change will be recorded in the [Manage System] - > [Manage User] -> [%USERNAME%] -> [User Log] Ahsay Systems Corporation Limited 100

110 11.5 Managing Backup Set After pressing on the link of the selected user on the [Manage User] -> [List User] panel, a [Backup Set] link is now available in the extended user menu. You can review the backup sets setting of this particular user by clicking the [Backup Set] link. To update the backup set setting of this particular user, just make the required changes on the form below and press the [Update] button. Setting Online Restore IP Restriction At the bottom of the [Backup Set] panel, you should be able to find the [Online Restore IP Restriction] section. If you would like to restrict online file restore of this backup set to only a subset of trusted IP addresses, you just need to enter the trusted IP addresses here. Once you have entered some IP addresses into the IP restriction list, online file restore request originating from IP addresses into the IP restriction list, online file restore request originating from IP addresses not listed on this list will no longer be able to restore any files from this backup set. (You can use the IP range of to disable online restore completely). Ahsay Systems Corporation Limited 101

111 Global Backup Set Values The following values are only valid for Group Policy enforcement and default backupsets only, do not use these values in normal backupsets. Ahsay Systems Corporation Limited 102

112 11.6 Initiating Backup from AhsayOBS Ahsay Offsite Backup Server While end users can initiate backup jobs from their computers by using manual or scheduled backup jobs from AhsayOBM or AhsayACB. The AhsayOBS server administrator can initiate a backup job from AhsayOBS web console. In order to initate a backup job go to the [Manage User] -> [Run Backup], and you will have something similar in the following screenshot: Some definitions of the fields related are shown in the following table: Key No. Login Name (Alias) -> Backup Set Backup is pending Backup Type Used / Quota (%) Owner Description Number count of user. The login name of the user with the alias bracketed behind. If there is any backup set, the name of the backup set will be shown under the user login name. Yes if the backup job is pending after pressing [Run Backup]; Otherwise No. Type of backup. For files only backup, the backup type will be empty. The used data size of the user on the server and the total quota of data size that the user can use. The percentage of used size over quota is bracketed behind. Owner of this backup user. Ahsay Systems Corporation Limited 103

113 Last Backup The creation time of the latest backup. In order to use this feature: The AhsayOBM/AhsayACB scheduler service must be running on the client machine and can connect to the AhsayOBS server. The Run scheduled backup on computers named field on the backupset must be filled in with the correct computer name of the client machine. To initate a backup job from AhsayOBS, check the box next to each of the required backupsets.then press the [Run Backup] button at the bottom of the page. The status of [Backup is pending] of the chosen backup sets will be changed to Yes, and after a short time AhsayOBM/ AhsayACB will start backing up the data sources from the specific machine. When the backup is finished, the status of [Backup is pending] will become No, and the [Last backup] will be update with date and time of the last backup job Browsing User Backup File You can click the [File Explorer] link available at the extended [Manage User] menu to invoke the [File Explorer] panel. You can use this panel to browse and restore user s backup files. This panel is the same [File Explorer] panel that users would see when they click the [File Explorer] link after they have logged on to the system. Please refer to the User s Guide for information on how to restore users backup files. Ahsay Systems Corporation Limited 104

114 11.8 Reviewing User Backup Report You can click the [Report] link available at the extended [Manage User] menu to invoke the [Report] panel. You can use this panel to review users backup activities. This panel is the same [Report] panel that users would see when they click [Report] link after they have logged on to the system. Please refer to the User s Guide for information on how to review users backup activities. To review CDP backup reports instead of selecting the backup time, select (CDP), as CDP backup jobs are constantly active the job status prior to the daily cut off at 12:00 AM is Backup not yet finished Ahsay Systems Corporation Limited 105

115 11.9 Reviewing User Storage Statistics Ahsay Offsite Backup Server You can click the [Statistics] link available at the extended [Manage User] menu to invoke the [Statistics] panel. You can use this panel to review users storage statistics. This panel is the same as the [Statistics] panel that users would see when they click the [Statistics] link after they have logged on to the system. Please refer to the User s Guide for information on how to review user storage statistics. User statistics are calculated on a daily basis by the Usage Report system job. If the Usage Report is disabled or if your AhsayOBS service is offline when the Usage Report system job is due to run, no user statistics will be calculated for those days. AhsayOBS cannot calculate user statistics for past days which have been missed User Log You can click the [Statistics] link available at the extended [Manage User] menu to invoke the [User Log] panel. You can use this panel to review the user specific activities on the AhsayOBS server. A copy of user related activities can also be seen in the AhsayOBS system log, under [Manage System] -> [Manage Log] -> [System Log]. Ahsay Systems Corporation Limited 106

116 12 Group Policy Management This chapter describes how you can use the [Manager Group Policy] menu to manage your user groups on AhsayOBS. Term Policy Control Policy Group User Group Descriptions Areas that are affected by group policy A group of preset policy control objects A group of users About Group Policy The Group Policy feature is designed to simplify administration and to reduce the effort required for managing backup users, e.g. security settings and backup set settings. It allows backup server administrator a greater degree of flexibility in tailoring features and services to target specific customer segments. User Groups When Group Policy is implemented on AhsayOBS, the backup user accounts will be conslidated into common user groups. Each user group will have its own set of policy groups which govern behaviour of the backup clients. The types of features that can be configured from a policy group are restricting or hiding certain functions or features on AhsayOBM/AhsayACB user interface or the AhsayOBS web console. For example, a backup service provider wishes to offer customers a cut rate service plan, i.e. OBM Basic Plan, which consists of fixed quota limit and where customer cannot change backupset settings. The service provider will create a user group on AhsayOBS called OBM Basic Plan. To customize the features for each group, a policy group will need to be created called OBM Basic Plan Policy, which will contain a group share quota setting and a Policy Control Setting for AhsayOBM to disable access to some AhsayOBM controls. [OBM Basic Plan Policy] [OBM Basic Plan] Once the policy group OBM Basic Plan Policy is assigned to user group OBM Basic Plan, it will be effective immediately. Any AhsayOBM users that are assigned to the OBM Basic Plan group will be governed by the OBM Basic Plan Policy settings. Ahsay Systems Corporation Limited 107

117 Policy Controls The policy controls which can be customized for each user group are: 1. Shared Quota Settings A maximum quota or Shared Size can be specified for each user group via a policy group setting, each backup user assigned to the user group will automatically be allocated a portion of this quota, according to the Maximum percentage of shared size for each user value. 2. Backupset Configuration Define a default backupset for AhsayOBM/AhsayACB users who belong to the group. Define an enforcement backupset for AhsayOBM/AhsayACB users who belong to the group. When an Enforcement backupset is configured for a backupset type, it will over overwrite all settings on any pre-exisiting backupset types. 3. Policy Control Setting The Policy Control Setting allows the backup server administrator to customize the user interface for AhsayOBM/AhsayACB and AhsayOBS user web console interface according to each user group. 4. Global Filter Setting This setting defines a global file filter for AhsayOBM and AhsayACB backupsets which belong to the user group. The backupsets which can be configured with global filtering on AhsayOBM are restricted to File, CDP, Lotus Domino, and Lotus Notes backupsets. When a global filter is applied to a user group, any the pre-existing backupset filters will be overwritten by the global filter. 5. Exclude File Size Over Setting This setting defines the file size restriction for each individual file in a backup. When it is applied to a user group, any file size over the threshold will be excluded during backup. Ahsay Systems Corporation Limited 108

118 6. Exclude Network Shares This setting defines the network share restriction for each backup. When it is applied to a user group, all network shares will be excluded during backup Best Practices for using Group Policy In order to avoid any confusion and for better AhsayOBS server administration, it is recommended to keep the group policy design as simple as possible: 1. One-to-One relationship between policy and user group. Each policy group should only be applied to one user group. 2. One-to-One relationship between user account and user group. Each user should only belong to one user group. 3. Active user accounts should not be transferred between user groups. 4. New user groups and policies should be thoroughly tested before they are implemented on a production server. 5. A separate policy should be created for each type of policy type. E.g. A policy name AhsayOBS Read-only Main Menu for policies that restrict the users to have Read-Only access on main menu. E.g. a user group named AhsayOBS System User Read-Only Main Menu for a user group with AhsayOBS Read-only Main Menu policy assigned. 6. The naming conventions for user groups and policies should be meaningful and easily distinguishable. Example: For a new user group called ACB Premium group which has some restrictions to the AhsayACB UI interface control and features. The associated policy group would be called ACB_Premium_UI. 7. Once a user group is operational, i.e. user accounts have been assigned and backups are running according to the policy settings, there should be no further policy changes. 8. For user groups defined with shared quota policy, please make sure the sum of the individual user backup quota does not exceed the shared size. For example, a group with a shared quota policy defined as, shared size of 500GB and maximum percentage of shared size for each user of 25% Ahsay Systems Corporation Limited 109

119 (125GB). Should only have a maximum of four backup users assigned to it (125GB x 4 users = 500GB). 9. Extreme caution must be excerised when assigning policies to user groups. As a policy will be effective and enforced as soon as it is assigned to a group, any errors in policy assignments could result in unforseen problems for all members of the affected user group. 10. Any backup user accounts which are using v5.5 AhsayOBM/AhsayACB clients on AhsayOBS v6 should not belong to any user groups. As they are not compatible with group policy features Group Policy Limitations and Restrictions 1. Each user group is restricted to only one shared quota policy. 2. Each user group is restricted to only one set of Default and Enforcement backupsets for each backupset type. 3. Each backup user account is permitted to have one Default Backup Set and one Enforcement Backup Set for each available Backup Set Type. 4. Only one Global Filter is allowed for each backupset type. 5. A backup user cannot be a member of more than one user group with shared quota policy enabled. 6. Only AhsayOBM and AhsayACB v6 or above clients support group policy. Ahsay Systems Corporation Limited 110

120 List Policy Control There are three main categories for policy control objects AhsayOBS, AhsayOBM, and AhsayACB. Each control object allows the backup server administrator to configure the controls or features which can be accessible or visible to the end user. All policy control objects can be found in the [Manage Group Policy] -> [Policy Control] Page. AhsayOBS A group of policy control objects used to control the behaviour of AhsayOBS. The control area defined on AhsayOBS policy control group is in the format of: [Menu Name] [Page Name] [Section Name] [Section Detail] (if any) E.g. The name of the policy to control the System Settings section on Server Configuration page under the [Manage System] menu is: Manage System Server Configuration System Settings Ahsay Systems Corporation Limited 111

121 AhsayOBM A group of policy control objects used to control the behaviour of AhsayOBM. The control area defined on AhsayOBM policy control group is in the format of: [Section Name] [Section Details] (if any) E.g. To restrict access to the Recycle Bin under Quota Usage section on the Main Frame, you should edit the settings in this policy: Quota Usage Recycle Bin AhsayACB A group of policy control objects used to control the behaviour of AhsayACB. The control area defined on AhsayACB policy control group is in the format of: [Section Name] [Section Details] (if any) E.g. To restrict access to the Recycle Bin under Quota Usage section on the Main Frame, you should edit the settings in this policy: Quota Usage Recycle Bin Ahsay Systems Corporation Limited 112

122 12.4 User Group List User When you click the [Manage Group Policy] -> [List User] Link available at the top menu, the [List User] panel will appear. An overview of user groups and owner on backup can be listed by default backup users are only shown. The system user list can also be listed by selecting the System user radio button near the top menu. Press the [Login Name] link to show the details of policy groups, user groups and owner on selected backup user. The system user detail can also be viewed by similar way. Ahsay Systems Corporation Limited 113

123 Manage User Group [User Group] panel is used to manage the user group s for both backup users and system users. Please click the [Manage Group Policy] -> [User Group] link to enter the [User Group] panel. The default view shows the available user groups for backup user. The user group list for system user can also be listed by selecting the System user radio button near the top menu. The user group feature can be used obtain information on how many users accounts have been assign to a user group. Ahsay Systems Corporation Limited 114

124 You can use the combo box to list the number of existing user groups defined. After selecting the desired user group all user accounts assigned to this group will be displayed. Ahsay Systems Corporation Limited 115

125 Create user group Please follow the instructions below to create a user group: 1. Go to the [User Group] panel. 2. Select the user group type, i.e. Backup user or System user. 3. Press the [Add] button. 4. Change the default name to a more descriptive user group name. 5. Press the [Updated] button to complete the process. Ahsay Systems Corporation Limited 116

126 Remove an existing user group To remove a user group, please do the followings: 1. Go to the [User Group] panel. 2. Select the user group from the drop down list. 3. Press the [Remove] button to remove the user group. WARNING: The remove user group feature will remove the selected user group from AhsayOBS even if: i. There are active user accounts assigned to the group ii. There are active policies assigned to the group All member user accounts upon removal of the user group will be automatically unassigned. Once unassigned, the user accounts will retain the policy restrictions of the removed user group. It is strongly recommended prior to removing a user group, to ensure that all member user accounts are re-assigned first. Ahsay Systems Corporation Limited 117

127 Assign Users to a user group Please follow the instructions below to assign users to a specific user group: 1. Go to the [User Group] panel. 2. Select a user group from the dropdown box. 3. Click the [Assign users] link located in the [Users] section to go to the user list. This option is only shown when the list is empty. 4. If the list is not empty, please click on the [Edit] link in the [User] section. 5. Select users from the user list by checking the checkboxes and vice versa. 6. Press the [Update] button to add selected backup users to backup user group. Ahsay Systems Corporation Limited 118

128 Remove Users from a user group To remove users from a user group, please do the followings: 1. Go to the [User Group] panel. 2. Select a user group from the dropdown box. 3. Press the link next to the backup user you would like to remove or press the [Edit] link located in the [Users] section to enter the user list section. Note: You can use the alphabet categories at the top of the backup user list to limit the list to show only those backup users whose login name starting with a certain alphabet. You can also user the [Owner] link to limit the listing to show backup users belong to the selected owner. Ahsay Systems Corporation Limited 119

129 12.5 Policy Group Manage Policy Group When you click the [Manage Group Policy] -> [Policy Group] link available at the top menu, the [Policy Group] form will appear. This is used to define policies for backup users or system users. The default view shows the available Policy Groups for backup user. The Policy Groups list for system user can also be listed by selecting the System user radio button near the top menu. Ahsay Systems Corporation Limited 120

130 Create a policy group To create a new policy group, please do the followings: 1. Go to the [Policy Group] form. 2. Select the backup user type, i.e. Backup user or system user 3. Change the name to a more descriptive policy group name. 4. Press the [Update] button to save the changes. Remove an existing policy group Please do the followings to remove a policy group: 1. Go to the [Policy Group] form. 2. Select the policy group from the drop down list. 3. Press the [Remove] button to remove the policy. Below is a table showing the available policy types that can be assigned to a policy group. Policy Group Type Backup User System User Available Policy Types - Shared Quota Policy Control - Backup Set Setting Policy Control - Backup User Policy Control - Global Filter Policy Control - Exclude File Size Over Policy Control - Exclude Network Share Policy Control - Share Backup Users Policy Control - System User Policy Control Ahsay Systems Corporation Limited 121

131 Shared Quota Policy Shared Quota Policy is available for Backup User Policy Group only. It is used to define a maximum storage limit for a particular group, which is evenly allocated to each individual backup user within the group. Each backup user is allocated a fixed percentage of the total storage limit. The advantage of using a share quota policy is it will simplify user home storage management. For example, if users for a group where assigned an individual user home drive, this setting will ensure the backup users cannot user more disk space than is physically available on the drive. Assign Shared Quota Policy to a policy group 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Click the [Show Options] link at the right side of the [Shared Quota Setting] section. The information of shared quota policy will be shown. 4. Check the checkbox next to the [Disk quota share]. 5. Fill in the [Shared Size] and [Maximum percentage of shared size for each user] field. 6. Press [Update] button to save the changes. Reset Disk quota share 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Click the [Show Options] link at the right side of the [Shared Quota Setting] section. The information of shared quota policy will be shown. 4. Uncheck the checkbox next to the [Disk quota share] to reset it to default. 5. Press [Update] button to update the changes. When implementing a shared quota policy, you need to take into account any additional users assigned to the group will result in the reduction of backup quota for existing users and therefore impact on the backups operation of Ahsay Systems Corporation Limited 122

132 these users. So the shared size will have to be adjusted in order to ensure sufficient space for the additional users. For example, if Group VIP was assigned a shared size of 100GB, with a maximum percentage of 20% for each user in the group. Initially 5 AhsayOBM users are assigned to Group VIP, the backup quota for each individual user will be 20GB. For this setup each user can fully utilize their individual backup quotas without affecting others in the group. But if another 5 users were assigned to Group VIP, they too will be allocated 20GB each of backup quota. This will mean if all users fully utilize their backup quota s (10 users X 20GB = 200GB), it will exceed the shared size of 100GB. In this scenario, the first 5 backup users to who fully utilize their backup quotas, will cause the other 5 users backup jobs to fail with a Group Quota Exceeded. Please contact us to increase your quota. error. Ahsay Systems Corporation Limited 123

133 Backup Set Setting Policy Backup Set Setting Policy is available for Backup User Policy Group only. It is used to pre-define the backup settings for backup users. This helps to pre-fill backup settings when backup users creates a new backup set (called Default Backup Set ) whereas other helps to enforce backup setting to backup users. This is known as an Enforcement Backup Set. Default Backup Set Note: User cannot assign a higher level default backup set to a lower level policy group, i.e. If a user (User1) is created by a sub-admin role system user, and there is a default backup set policy (Policy 1) created by a admin role system user. Policy 1 cannot be assigned to User1. Ahsay Systems Corporation Limited 124

134 Enforcement Backup Set Create a Pre-defined Backup Setting Policy 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Click the [Show Options] link at the right side of [Backup Set Setting] section to show the information of [Default Backup Set] and [Enforcement Backup Set] sub-sections. 4. If you are going to create a Default Backup Set, click the [Edit] link next to [AhsayOBM Users] or [AhsayACB Users] in the [Default Backup Set] sub-section to show the default backup set form. Otherwise, click the [Edit] link next to the [AhsayOBM Users] or [AhsayACB Users] in the [Enforcement Backup Set] sub-section to show the enforcement backup set form. 5. Click the [Add] button to create a new backup set. 6. Fill in the necessary field(s) in the backup set form and click the [Update] button to save the changes. Ahsay Systems Corporation Limited 125

135 Remove a Pre-defined Backup Setting Policy 1. Go to the [Policy Group] form. 2. Click the [Show Options] link at the right side of [Backup Set Setting] section to show the information of [Default Backup Set] and [Enforcement Backup Set] sub-sections. 3. To delete a Default Backup Set setting, click the [Edit] link next to [AhsayOBM Users] or [AhsayACB Users] in the [Default Backup Set] sub-section. Otherwise, click the [Edit] link next to [AhsayOBM Users] or [AhsayACB Users] in the [Enforcement Backup Set] sub-section. 4. Select the backup set from the drop down list. 5. Click the [Remove] button to remove it from the system. Ahsay Systems Corporation Limited 126

136 Assign a Pre-defined Backup Set to a Default Backup Setting policy 1. Go to the [Policy Group] form. 2. Click the [Show Options] link at the right side of [Backup Set Setting] section to show the information of [Default Backup Set] and [Enforcement Backup Set] sub-sections. 3. Select the pre-defined backup set from drop down. 4. Click the [Update] button to save the changes Backup User Policy Control Backup User Policy Control is available to Backup User Policy Group only. It is used to restrict the backup users access privileges on AhsayOBS, AhsayOBM and AhsayACB. By default, full access privilege is granted. A summary of access permission is listed below: Permission R W E D Meanings Read Write Execute Delete Ahsay Systems Corporation Limited 127

137 Edit Policy Control 1. Go to the [Policy Control] form. 2. Click the [Show Options] link at the right side of [Policy Control Setting] section to show the permission information on [AhsayOBS], [AhsayOBM] and [AhsayACB] sub-sections. 3. Click the [Edit] link next to the [Group] drop down list to go to the policy control selection. 4. Select the Policy Control that you would like to edit by checking the checkbox on the left side of the Policy Control ID, and the corresponding RWXD checkboxes will be enabled. 5. To assign access permission to a Policy Control, select/de-select the checkbox under the RWXD section. Policy Type Read-only Editable Editable and Executable Modifiable Full Hidden Permission R RW RWE RWD RWED All checkboxes are unchecked 6. Click the [Update] button to save the changes. Ahsay Systems Corporation Limited 128

138 Remove Policy Control 1. Go to the [Policy Control] form. 2. Click the [Show Options] link at the right side of [Policy Control Setting] section to show the permission information on [AhsayOBS], [AhsayOBM] and [AhsayACB] sub-sections. 3. Press the link next to the policy control that you would like to remove. 4. The Policy Control is now removed from the system. Ahsay Systems Corporation Limited 129

139 Global Filter Policy Global Filter Policy is applied to system users only. It is used to set predefined backup filter to backup users. Create global filter policy 1. Go to the [Policy Control] form. 2. Click on the [Show Options] link in the [Global Filter] section. 3. Click the [Edit] link next to [AhsayOBM Users], [CDP Filter for OBM Users] or [AhsayACB Users]. 4. Click the [Add] button to create a new policy. 5. Select the [Operating System] and [Type], then press the [Update] button. 6. Fill in the required information shown in the page. 7. Press the [Update] button to save the changes. Ahsay Systems Corporation Limited 130

140 Delete global filter policy 1. Go to the [Policy Group] panel. 2. Click the [Edit] link next to [AhsayOBM Users], [CDP Filter for OBM Users] or [AhsayACB Users]. 3. Select the policy from the drop down box. 4. Press [Remove] button to remove it from the system Exclude File Size Over Policy Exclude File Size Over Policy is available for Backup User Policy Group only. It is used to define a file size restriction during backup for a particular group, which is allocated to each individual backup user within the group. Files in all backup sets under the backup user will be restricted. Assign Exclude File Size Over Policy to a policy group 1. Go to the [Policy Control] form. 2. Select a Backup User Policy Group form the drop down list. 3. Check the checkbox next to the [Exclude File Size Over]. 4. Fill in the [Exclude File Size Over] field. 5. Press [Update] button to save the changes. Reset Exclude File Size Over Policy 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Uncheck the checkbox next to the [Exclude File Size Over] to reset it to default. 4. Press [Update] button to update the changes. Ahsay Systems Corporation Limited 131

141 Exclude Network Share Policy Exclude Network Share Policy is available for Backup User Policy Group only. It is used to define network shares restriction during backup for a particular group, which is allocated to each individual backup user within the group. Network shares in all backup sets under the backup user will be restricted. Assign Exclude Network Share Policy to a policy group 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Check the checkbox next to the [Exclude Network Share]. 4. Press [Update] button to save the changes. Reset Exclude Network Share Policy 1. Go to the [Policy Group] form. 2. Select a Backup User Policy Group from the drop down list. 3. Uncheck the checkbox next to the [Exclude Network Share] to reset it to default. 4. Press [Update] button to update the changes Shared Backup User Policy Shared Backup User Policy is only available to System Users Policy Group. It helps Sub Admin role system users to share their backup users provided they are under the same creator. Ahsay Systems Corporation Limited 132