An unexpected base image may be taken if:
- Dirty shutdown of the agent. If the protected machine has a dirty shutdown, AppAssure will automatically take a new base to ensure that the recovery chain is not corrupted by any potential errors that the machine could have due to the dirty shutdown
- The driver log file has been deleted (AALog_*.log). The file is located at [drive letter]:\System Volume Information folder.
- The driver failover file (AAFailover.md) has been deleted. The file is located at [drive letter]:\System Volume Information folder.
- WARNING: Quest strongly discourages users from manipulating driver files without the help of a trained engineer.
- Driver logging was disabled due to some troubleshooting steps. This might occur if the assuremc. exe utility was used in the environment during possible troubleshooting steps.
- The AppAssure filter driver (AAFsFlt) was unloaded. By unloading the filter driver AppAssure is unable to track changes on the volume and must start over with a new changelog and base image.
- Amount of changes in the log file is too large and the system runs out of memory while building a map of the changed data. This can happen to large file-servers with significant amounts of data.
- The source volume currently under protection has been extended or shrunk and the process was interrupted by a reboot or some other factor.
- A new encryption key was set for the agent. After the key has been added, a new base image will be taken.
- The encryption key has been removed for the agent. After removing the key, a new base image will be taken.
- The encryption key for the agent has been changed.
- There is not enough space on the agent’s volume to write driver log files.
- Improper permissions – the user protecting the agent does not have administrative privileges on the System Volume Information folder.
- Check-disk – if check disk is performed on the system volume or on the non system volume, an incremental snapshot should be taken. If corruption was found and repaired by check disk then a base may be taken.
- User Access – Access to the System Volume Information folder and MSInfo is blocked by a third party product.
- Third Party Product Interference – the volume is protected by another software product or the driver log file has been blocked by antivirus software.
- Formatting Error – the volume is marked or formatted as “dirty” after undergoing an improper shutdown.
- Environmental issues – different environmental issues may interfere with the software’s normal functionality.
- Another VSS-based backup solution is running on the agent machine
- Previous incremental recovery point is orphaned. Appassure will automatically create a new base image to ensure the future recovery points can be restored.
Note: Once a base image is triggered on a volume, there is no way to stop the base image and force an incremental snapshot. The base image must be completed and then new incremental snapshots can be taken after the base is complete.
Is your AppAssure or Rapid Recovery solution working as efficiently as possible? Learn more about our AppAssure and Rapid Recovery Health Check