The Windows backups get failed randomly because of the inconsistent file system even when the file system is clean before taking backups.
A snapshot taken in the 'live' file system, which is actively used, causes degradation of the file system on the snapshot.

Cluster accounting failed at 22502 (0x57e6): missing cluster in $Bitmap

ERROR: Filesystem check failed! Windows wasn't shutdown properly or inconsistent filesystem. Please run chkdsk /f on Windows then reboot it TWICE.

Fatal: Execution of ntfsclone -q -s -O /onapp/backups/m/e/mehxeoqqhrcnti /dev/sde1 > /tmp/onapp-tmp-ntfsclone-sdk.log 2>&1 || ( cat /tmp/onapp-tmp-ntfsclone-sdk.log; rm -f /tmp/onapp-tmp-ntfsclone-sdk.log; exit 1 ) failed


Consider using a new feature Backup Plugin System that enables integration of third-party backup management services into OnApp. In case that it is not an option for you, the ntfsclone wrapper can be used as an alternative to take backups, restore, and provision and is based on the dd utility.

When using the wrapper, the backup tasks complete successfully regardless of the file system state (provided that there are no other issues that may cause failures).

  1. Download the ntfsclone wrapper and install it on the backup servers or compute resources provided that there are no backup servers in the cloud. Run the following commands:

    #NTFSCLONE_PATH=`which ntfsclone`
    #curl -s > $NTFSCLONE_PATH
    #chmod +x $NTFSCLONE_PATH
  2. Change the following variables in the script, if needed:


To make the changes permanent on CloudBoot backup servers/compute resources:

  1. In Control Panel, locate the the CloudBoot tftpboot config directory by its MAC address and copy the ntfsclone wrapper into it:

  2. Add these commands to the custom config file:

    NTFSCLONE_PATH=`which ntfsclone`
    cp /.rw/ $NTFSCLONE_PATH
    chmod +x $NTFSCLONE_PATH
  3. Run these commands manually or reboot the compute resource to apply the changes.