Ahsay and Korea-based HM SYSTEMS Sign Distribution Agreement

Ahsay and Korea-based HM SYSTEMS Sign Distribution Agreement

Ahsay Systems Corporation Limited and HM SYSTEMS CO., LTD. have signed a distribution agreement. HM SYSTEMS is an information technology company in Korea. Through the cooperation, Ahsay can more effectively expand its distribution channels in Korea. Under the distribution agreement, Ahsay has granted HM SYSTEMS an exclusive license to distribute, sell and deliver certain backup software products (the “Products”) under the trademarks and trade names of Ahsay HK as its distributor in Korea.

Details can be found at: http://en.acnnewswire.com/press-release/english/30753/ahsay-and-korea-based-hm-systems-sign-distribution-agreement

Interview of Ahsay’s CEO Published in Hong Kong Investment Times

Our CEO, Mr. Schubert Chong, has been interviewed by Phemey Pon, a famous asset management expert in Hong Kong. The article has been published yesterday in Hong Kong Investment Times. During the interview, Schubert has shared the success story of Ahsay, how Ahsay grows from a startup to a listed company, and his vision in the Company’s future development. He also shared his view on the 3 essential factors for a startup to become successful.

Here’s the article for your reading pleasure:

Interview of Ahsay's CEO, Mr. Schubert Chong

De-support of 32-bit operating system for AhsayCBS v7.7.0.0 or above

De-support of 32bit operating system for AhsayCBS v7.7.0.0 or above
Dear  Partners,

This serves as your formal notification that Ahsay will be officially de-supporting the use of 32-bit Windows and Linux O/S platforms for AhsayCBS v7.7.0.0 or above due to the lack of memory support of 32-bit operating systems which will limit the performance and scalability of our backup solution. As 64-bit servers have been generally available for over 10 years, we believe it is the right time to make this decision.

This does not apply to 32-bit O/S platforms installed with AhsayOBM/AhsayACB clients which will continued to be fully supported.

Partners who are currently using AhsayOBS/AhsayRPS/AhsayRDR v6 on 32-bit Windows and Linux O/S platforms will still continue to receive technical support from the Customer Service Team until the de-support of AhsayOBS/AhsayRPS/AhsayRDR v6.

Please feel free to contact our Customer Support Engineers for assistance at: http://www.ahsay.com/jsp/en/contact/kbQuestion.jsp

Ahsay Backup Software v7.7.2.0 Released

Ahsay Backup Software v7.7.2.0 Released

Ahsay Backup Software v7.7.2.0 has just been released. With this release, you can now view live replication status in AhsayCBS, generate consolidated report on the fly to save AhsayCBS storage, backup and restore Microsoft SQL Server with enhanced usability, offer 16 newly added languages to your users, and get over 30 bugs fixed. Before upgrade, please make sure you have read the “Limitation / Known issue of this version” listed in the Release Notes. For example, auto client software update from v7.7.0.0 to v7.7.2.0 and from Linux v7.5.0.0/v7.7.0.0 to v7.7.2.0 are not supported yet, etc. You can read the detailed Release Notes of v7.7.2.0 at here.

You can download this version at www.ahsay.com/download/

Make users upload encrypted encryption keys to AhsayCBS after backup

Hey administrators, in AhsayCBS v7, you can make your backup users upload their encryption keys in encrypted format to AhsayCBS after backup, so that if a user forgot or lost his/her encryption key, you can send the encrypted key file to us. We will then decrypt the key and send it back to the user’s contact email address.

Since the encryption key of a user’s backup set uploaded to AhsayCBS is in encrypted format, administrator won’t be able to know the actual user’s encryption key. Besides, the decrypted key will be directly sent to the user’s contact email address, the administrator won’t be able to get the decrypted key. Ahsay only has the encryption key but does not have the access to your user’s backup data. Therefore, the mechanism is totally secure.

Here are the steps:
Make users upload encryption keys to AhsayCBS after backup

Sending us user’s encrypted encryption key file for decryption should be your last resort. You should always educate your users about the importance and methods for keeping their keys safely. Here’s a best practice of encryption key management for your reference: https://forum.ahsay.com/viewtopic.php?f=192&t=14090

To understand the details of our Encryption Key Recovery Service, click here.

How to restore Multiple backup versions in a single restore operation

Hi there, do you know you can restore multiple backup versions within a single restore operation with our AhsayOBM and AhsayACB client backup applications? No? When you select the files to restore, most of us will overlook the pull-down menu under “Select what to restore”. In the menu, there’s an option of “Choose from ALL files”. When it is selected, you can select multiple versions of a backed up files to restore. The latest file will be shown in solid black color while previous versions will also be shown but in grey color. Simply select the versions you need to restore and complete the restore process. Then, you’ll find in the restore location that all the versions will be there. The latest backup version will have the file name as the original file, while the previous versions will have time stamps added to their filenames. Could be useful when you don’t know which backup version you actually need.

How to restore multiple versions in a single restore operation with AhsayOBM / AhsayACB

Predefined vs Standard Destination in AhsayCBS

It seems that many partners don’t quite understand the difference between a Predefined Destination and a Standard Destination in AhsayCBS. So, the following is a brief explanation.

A Predefined Destination is the storage that “AhsayCBS” will use for storing users’ backup data. E.g. if you’re an MSP and you want your users to backup their data to “your” Microsoft Azure cloud storage, that you should define your Microsoft Azure cloud storage as a “Predefined Destination” (Firstly create the destination in AhsayCBS > System Settings > Backup > Predefined Destinations, and then enable it through Policy Group > [A specific policy group] > Backup Set Settings > Predefined Destination). You can name a Predefined Destination as whatever name you prefer, e.g. “My-Storage-01″ in the example, which is a Google Drive storage but the actual storage is transparent to users. The Google Drive logo won’t be displayed on AhsayOBM/AhsayACB side.

A Standard Destination on the other hand is “your user’s” own storage. E.g. if you allow your users to backup to their own cloud storage such as Google Drive or Microsoft OneDrive, you should enable these “Standard Destinations” for them (enable them through Policy Group > [A specific policy group] > Backup Set Settings > Standard Destination) so that they can choose these destinations in the Destination setting when creating a backup set. Standard destinations will be displayed as their generic names on AhsayOBM/AhsayACB side, e.g.  Googld Drive / Microsoft OneDrive.

As you can see in the following example, My-Storage-01 is enabled under Predefined Destination; and Local Drive, Google Drive, and OneDrive are enabled under Standard Destination. On the AhsayOBM/AhsayACB side, the users will see these 4 options in Destination Storage selection menu when creating a backup set.

Example: Predefined vs Standard Destination in AhsayCBS

Example: Predefined vs Standard Destination in AhsayCBS

In case you still have questions on it, please contact our support for further clarification at: http://www.ahsay.com/support/