Mundy

IT Knowledge Base

User Tools

Site Tools


Sidebar

Contact me at dan@mundy.co for any feedback or suggestions.


My other sites:

Search all my sites:

altaro_vm_backup

Altaro VM Backup




Logging

  • In Altaro software, Operation History, the Operation Time is the start of the operation. If you want to see the end time, ie when it was actually logged, you can add the “Duration” to the Operation Time.
  • In Windows Event Logs, Application, you can create a filter to show the following event sources: Altaro VM Backup, Altaro VM Backup Controller, Altaro VM Backup Engine, Altaro VM Backup Hyper-V Host Agent, Altaro.HyperV.WAN.RemoteService
  • In Windows Event Logs, the log date is when the error was recorded, and will have a text description that has the operation start time. This can be more helpful, as you'll probably want to sort the events by what time something went wrong, rather than what time it started the operation

Schedules

Observations:

  • Within each schedule, all of the VMs will first back up, and then off-site copy
  • There is no way to change the order of a schedule, therefore if you want to ensure a particular VM is backed up first, you'll need to add it into it's own schedule
  • Because this VM is in it's own schedule, it will back up, and then off-site copy, and you must wait for both to complete before the next schedule will run (i.e. in the overall picture, it will not back up all VMs before doing the offsite copy)

Increased backup concurrent per Hypervisor. Previously only one Backup and one Offsite Copy could run concurrently on each Hypervisor. This has now been increased to 4 Backups and 1 Offsite copy concurrently which will result in faster overall performance and shorter durations to complete an entire backup schedule.

Altaro Support Center | Version 7.1 Build 7.1.4

Restore

Observations:

  • When you use Restore, and change the restore-path to a different location, it will automatically create the subfolder based on the VM name that you chose in the restore job. Ie if you restored RDS01 to alternate location: C:\ClusterStorage\CSV01 and with a new name of RDS02, then it will create the folder C:\ClusterStorage\CSV01\RDS02\ (don't restore to C:\ClusterStorage\CSV01\RDS02, or it will create C:\ClusterStorage\CSV01\RDS02\RDS02\)

Upgrading to Altaro V7

New Data Structure for DeDup feature

  • Backups will now be stored in a folder called AltaroV7
  • Old backups not deleted, ie you will need to have room for both, at first, or delete/move the old backup files first, otherwise it will fill the disk and fail.

    Make sure you don't delete the last copy of your backups, just in case the worst happens and you need to use the backup after deleting it and before a new backup is successful!

Observations from TMC:

  • Deleted backup files from a disk in the offsite rotation, and offsite copy tasks started failing. There was a pop-up inside Altaro at the time of backup saying “something along the lines of, offsite files not found, will need to start from scratch, do you want to?” (kind of annoying, of course we want to, especially if the disk is blank! I wasn't there at 11:50am to click the OK so the offsite copy failed…)

Stuff I need to re-read and understand better

Adds a new feature to optimize disk space used for backups.   Since the release of Altaro VM Backup v7, as old backup versions are deleted by the version retention policy, subsequent backups will automatically reuse unused free space. This new feature allows users to shrink their backup data files to free up disk space without waiting for subsequent backups to reuse the space you can use this Wizard.

Altaro Support Center | Version 7.2 Build 7.2.0

altaro_vm_backup.txt · Last modified: 2018/04/09 09:56 (external edit)