How to backup Microsoft SQL Server – Ahsay
Message us on Facebook
Existing Partner, login to

Partner Portal

AhsayCBS v
Release date:  
What's New
Download Free Trial

Microsoft SQL Server Backup Solution
Database & Transaction Log Backups. Rebrandable. Low Price

Ahsay brings you specialized SQL backup software that delivers enhanced functionality and ease of use. The Microsoft SQL server backup solutions by Ahsay will help you create a consistent and dependable back up strategy that works equally well across an organization's database environment. Coupled with cost-effective storage, our comprehensive server backup database and disaster recovery solution is the only backup solution you will ever need!

Using Ahsay Microsoft SQL Backup Module in conjunction with AhsayOBM client-side backup application is the easiest backup solution for Microsoft SQL Server.

  • Database hot backup

  • Transaction log backup

  • Fast multi-thread backup

  • In-File Delta incremental backup

  • Flexible scheduling

  • Unlimited retention

  • Secure 256-bit encryption

  • Local, LAN / WAN backup

How it Works

Deployment for Ahsay Microsoft SQL Server backup solution is simply a breeze. You just need to install AhsayOBM client backup application on the SQL Server that you intend to back up. A wizard will guide you through creating a backup set, including selection of backup mode (VSS or ODBC*), configuration of the backup source, backup schedule, retention policy, destination and encryption. Once the setup is done, the SQL Server databases will be automatically backed up to the selected destination(s), such as local storage, network share, your centralized backup server (AhsayCBS) and cloud storage, according to your defined schedule(s).

*v7.11 supports transaction log backup using ODBC method. Two backup methods are available for MS SQL Server, namely VSS and ODBC:

NOTE: Recommended free space on the temporary folder should be 150% of the total database size for one backup destination (based on default Delta ratio setting of 50%), 200% of the database size for two backup destinations, 250% of the database size for three backup destinations etc.



Learn more