How to setup a backup job?
It's a two step process.
Step one – installation of a smart agent on the VM to be protected
Step two – adding the VM to be protected to as a Protected machine.
Smart Agent installation – The agent is deployed at first connection. The VM has to have an internet access in order for the remote deploy to work since the web version of the agent is used in this case. The prerequisites are checked and downloaded if not already present in the VM. If your VMs can't have an internet access, you may also download the full version of the agent from your license portal and do a manual installation from within the VM itself.
On the image bellow you can see the deployment of smart agent remotely.
The deployment window can be closed while the task will continue running in the background. You can click on the image to see larger view.
Protection of VMs – I deliberately talk about “protecting” a VM when discussing AppAssure 5, rather than the process of creatin a VMware backup job, because the two are different. The VMware process invokes the creation of snapshot of a VM through vSphere (ESX/ESXi) > then backup of a VM is created by the backup software, and the snapshot of the VM is committed. All of this is orchestrated through the vSphere.
Appassure 5, on the other hand uses its Smart Agent to invoke VSS to create snapshots, not at the hypervisor level, but at the OS level. Microsoft Volume Shadow Copy Service (VSS) freezes and quiesces application data to disk and captures the file system consistent and an application-consistent backup.
Once the VM is added as “protected VM” the default backup schedule with snapshots at the Appassure's Core level is created. The incrementals are stored in the storage location that we setup at the beginning. The default retention policy can be changed in the Configuration > Retention policy window.
When you change, for example, the Recovery Points value, the colors and bars dynamically adjust to match, so you're able to see the retention period time line graphically. This is cool.
After deploying agents to the VMs you wish to protect, you can specify how to protect them. It's straighforward process. You go into Home > Protect Machine. And you add a VM to be protected. That's it! From that point on, every 60 min by default, a new snapshot is taken via VSS. The firs one is full, then incremental thereafter.
On my screenshot below you can see that I have already added a couple of my VMs. [Click on the image to enlarge].
Using the nearby “Protect Cluster” button, you can protect a cluster of machines. The “cluster” is meant to be Microsoft cluster (not VMware vSphere cluster). You can protect cluster of machines with with MS Exchange 2007 – Single Copy Cluster (SCC) or Cluster Continuous replication. For Exchange 2010 DAG (Database availability group). And also for MS SQL – 2005, 2008, 2008 R2 Single Copy Cluster (SCC).