Multi-Tier, Multi-Tenant
with Branding, API, Central Management
The whole Ahsay's solution is with flexible client-server architecture. AhsayCBS server-side centralized management console can be installed on your own backup server hosted in your datacenter, on cloud VM such as Microsoft Azure, or on backup appliances deployed in your customers' offices. Users' backup data can be stored on your own backup server, or on cloud storage such as Microsoft Azure, Amazon S3, etc., or the locally deployed backup appliances. The AhsayOBM / AhsayACB client agents are for installing on the servers, workstations that need to be backed up. With proper configuration, your customers' data will be automatically backed up or replicated to your managed storage.
The following are some common deployment options that our existing partners adopted:
Option 1: AhsayCBS and backup data hosted in your datacenter
Option 2: AhsayCBS and backup data hosted in Ahsay Germany Datacenter
Option 3: Deploy backup appliance at customer's site and replicate to your datacenter
Option 4: Deploy backup appliance at customer's site and replicate to dedicated replication appliance
If you have existing server hardware and storage facilities established in your datacenter, the easiest and the most cost effective way to start offering managed backup service to your end customers is to install and run AhsayCBS centralized management software in your existing hardware, and get your users' backup data stored on your datacenter's storage. Establish an AhsayCBS Replication Receiver in a secondary site to get your primary backup server replicated to this receiver.
On each of your customers' machine, either install AhsayOBM or AhsayACB client backup application. With proper configuration of backup schedules, AhsayOBM or AhsayACB will automatically backup to their local storage (e.g. a file server) and your datacenter.
For large initial backups, instead of backing up through the Internet, you can get the customer to seed the backup from their local machine to a portable hard drive and deliver it to your datacenter so that you can directly copy the seed to your backup server.
For casual data loss caused by accidental deletion, software failure, etc., your customers can quickly restore data from their local backup.
When a severe disaster strikes a customer's site, you can help them rebuild their hardware first, get AhsayOBM or AhsayACB installed on the new hardware, and then restore the backup data from your datacenter onto those new hardware through AhsayOBM and AhsayACB.
To speed up the restoration of large data, you can seed the backed up data to portable hard-drive from your datacenter and deliver it your customer's site instead of going through the Internet.
If your primary backup server failed, you can switch the AhsayCBS Replication Receiver into a backup server within 15 minutes so as to minimize the downtime of your backup service.
If you don't have any available server hardware and storage in datacenter, or you don't want to invest in and maintain any physical hardware for running your managed backup service, then you can deploy AhsayCBS on a cloud VM, and get your users' backup data stored on public cloud storage. The actual cloud storage used can be transparent to your customers, i.e. you can hide the name and logo of cloud storage by replacing them with generic icon and name.
Same as option 1, on each of your customers' machine, either install AhsayOBM or AhsayACB client backup application. With proper configuration of backup schedules and destinations, AhsayOBM or AhsayACB will automatically backup to their local storage (e.g. a file server) and your selected public cloud storage account, e.g. Azure Cloud Storage.
We suggest you to choose a cloud storage provider which allows you to seed data to the cloud storage with portal hard disk, e.g. Microsoft Azure. If so, for large initial backups, instead of backing up through the Internet, you can get the customer to seed the backup from their local machine to a portable hard drive, so that you can deliver the hard drive to your provider for seeding to your cloud storage account.
For casual data loss caused by accidental deletion, software failure, etc., your customers can quickly restore data from their local backup.
When a severe disaster strikes a customer's site, you can help them rebuild their hardware first, get AhsayOBM or AhsayACB installed on the new hardware, and then restore the backup data from your public cloud storage onto those new hardware through AhsayOBM and AhsayACB.
To speed up the restoration of large data, you can request your cloud storage provider to seed the backed up data to portable hard-drive from your cloud storage and deliver it your customer's site instead of going through the Internet.
You can increase the redundancy level of your cloud VM and storage by choosing geographic redundancy option to prevent data loss due to local cloud storage failure.
There are customers who prefer to have total ownership on their backup data and are reluctant to back up their data to third party's datacenter, i.e. your datacenter. To win these customers, you can offer them backup appliances with your rebranded AhsayCBS installed so that they can fully manage their backup system within their premises.
To eliminate data loss caused by on-site disasters, you can offer them offsite replication service to your datacenter (by creating individual receivers on your datacenter's AhsayCBS), so that when disaster strikes, you can help them recover the data from your replication server.
Your customer will be responsible for backup users creation and management on AhsayCBS. All the client machines will be backed up by AhsayOBM and AhsayACB to the locally deployed backup appliance.
For casual data loss caused by accidental deletion, software failure, etc., your customers can quickly restore data from their local AhsayCBS backup appliance.
When a severe disaster strikes a customer's site, you can help them rebuild a new backup appliance, restore their backup data and settings to the new appliance, and send it back to your customer for disaster recovery.
This is an advanced version of Option 3 by offering each customer a dedicated replication appliance hosted in your datacenter, so that if a customer's primary backup appliance fails, you can quickly deliver their dedicated replication appliance to them and convert it to a backup appliance to replace the failed one.