gdrummer83 (4/11/2016)

---

I have been using Asigra for a little over 2 years. I like the interface and think it's pretty streamlined and to the point. Not only that, it's Cloud-based. You have the option to also save a local copy for speed and in case something happens to the cloud site.

The SQL Server backup allows you to run a DBCC before each backup, stop on DBCC errors and also backup transaction logs. These are all optional. You have a few database dump policies are well for a full dump: always, differential or incremental. you can also choose to backup the pipe or buffer. Buffer will save locally. Pipe will not take additional space. It will read from the pipe on the source db. If you db is too big to be dumped to a file on either the db server or the buffer.

I have never had to restore a db as of yet, but the process is pretty simple. It lets you restore any day (of course) and each db associated w/the db, i.e. master, model, instance... etc...

One great feature is retention. You can setup for as much or little copies of the data you want. Now if you are worried about filling your storage, Asigra uses block-level technology, meaning when you backup every night, you will only backup changes made to the data, not the whole db/file. This also goes for if you already have the same system files for other database backups. It is smart in the fact it only keeps 1 copy of files.

Hope this helps!