Skip to main content

MFT Bitmap Is Corrupted

Thread needs solution
Forum Member
Posts: 24
Comments: 57

We're running into this issue occasionally on some of our VMs.  When it happens, it causes the backup to be huge (because it's forcing sector-by-sector mode).

2018-09-04T20:02:37:215-07:00 140461253666560 xxxxxx: User is running command. Command=Backing up virtual machine disks; User=; clientProfileID=; clientSessionID=xxxxxx
2018-09-04T20:02:38:091-07:00 140461253666560 xxxxxx: Pending operation 163 started: 'Saving partition structure (Hard disk 1)'.
2018-09-04T20:02:38:097-07:00 140461253666560 xxxxxx: Pending operation 166 started: 'Creating partition image (System Reserved (sd?1))'.
2018-09-04T20:02:38:296-07:00 140461253666560 xxxxxx: Changed Block Tracking (CBT) information has been successfully retrieved: 2901671936 bytes are changed.
2018-09-04T20:02:38:511-07:00 140461253666560 xxxxxx: Changed Block Tracking (CBT) information has been successfully retrieved: 2901671936 bytes are changed.

2018-09-04T20:02:38:666-07:00 140461253666560 xxxxxx: Error 0x7002e: Forced sector-by-sector mode.
| trace level: information
| channel: tol-activity#FF7A4F8B-DAF4-44B8-8253-9359E23072CD
| line: 0xa5695862aaf8e7de
| file: e:/226/core/resizer/backup/backup.cpp:1153
| function: BackupPartitions
| volume: C:
| fstype: NTFS
| $module: disk_bundle_lxa64_10330
|
| error 0x70018: MFT bitmap is corrupted.
| line: 0xef8b1618a4c0dd9c
| file: e:/226/core/resizer/ntfs/fs_ntfs_misc.cpp:62
| function: Load
| $module: disk_bundle_lxa64_10330

2018-09-04T20:02:38:678-07:00 140461253666560 xxxxxx: Pending operation 166 started: 'Creating partition image (No label (sd?2))'.
2018-09-04T20:45:17:941-07:00 140461253666560 xxxxxx: I/O statistics for device 'xxxxxx': 225199069184 bytes read, 0 bytes written.
2018-09-04T20:45:17:941-07:00 140461253666560 xxxxxx: Closing virtual hard disk file 'xxxxxx.vmdk'.
2018-09-04T20:45:29:765-07:00 140461253666560 xxxxxx: Command has completed successfully. Command=Backing up virtual machine disks;

I remember this was an issue in prior versions of Acronis, but it's still happening on the latest version (Acronis Backup 12.5 build 10330). 

This is happening on Windows Server 2008 R2 VMs and Windows Server 2012 R2 VMs.  We're running on VSphere 5.5.

https://kb.acronis.com/content/36993 is pretty old and as far as I know the issue was supposed to be fixed.  But we're still encountering the problem.  The problem seems to be completely unrelated to VM usage.  The backups run at night when no one's using the VMs.

 

If this is an intermittent issue, and if there's no easy fix, can we at least get some retry logic set up?

Upon encountering the MFT bitmap is corrupted error, either:

  1. Stop and retry within the same backup attempt a fixed number of times before continuing in sector-by-sector mode.
  2. Throw the error upward and cancel the entire backup attempt.  Retry the entire job (or don't) according to the retry behavior set in the the job settings.
  3. Create a separate retry setting for this specific error, and let users specify a number of attempts and an action to take after that number is hit.  The action would be to either to continue in sector-by-sector mode (as in #1) or to throw the error (as in #2).
0 Users found this helpful
Acronis Program Manager
Posts: 22
Comments: 3767

Hi Brian,

The KB you refer to was describing a specific case when file system inside the VMware snapshot was in inconsistent state in case there is specific VSS writer running inside the guest OS -> this in turn causes backup engine to detect this corruption and fail over to sector-by-sector mode. The root cause here is occasional inconsistency inside the VMware snapshot which has to deal with VSS handling specifics (some VSS writers may continue updating data in the snapshot, while VMware reports snapshot state as completed one and this happens occasionally).

To avoid intermittent huge backups generation I'd recommended to actually force "sector-by-sector" mode in the backup plan settings for affected VMs. What would happen in this case is that there will be no dependency on particular system state inside the VMware snapshot and the disk changes will be retrieved always from CBT. As the result the incremental backups will be of normal size. Both files/folders recovery and entire VM recovery should work properly from such backups.

The huge size occurs because the previous backup was not in sector-by-sector mode, while the next one is in this mode and this causes CBT tracking obsolete. In other words if the backup mode changes between normal and sector-by-sector then it causes huge archive size -> the solution is to avoid this change by enforcing "sector-by-sector" mode.

Thank you.

Beginner
Posts: 3
Comments: 2

Hi,

I have similar  problem , Client Os - Server 2008 R2 - Physical Machine gets restarts while backup and failed. .

Refer below Logs

2019-03-24T09:15:15:119+05:00 8580 I0135003A: User is running command. Command=Backup plan 'SSPPL-NAS-FILESRV-OFFSITE'; User=SPINSIEGER\administrator; clientProfileID=3D6DA455-0A5C-26C9-1875-BE9212220F46; clientSessionID=55ECE0B0-12D6-4027-9D9D-9B076F786BA7; tenantID=00000000-0000-0000-0000-000000000000
2019-03-24T09:15:29:591+05:00 5604 I0135003A: User is running command. Command=Backing up; User=SPINSIEGER\administrator; clientProfileID=3D6DA455-0A5C-26C9-1875-BE9212220F46; clientSessionID=55ECE0B0-12D6-4027-9D9D-9B076F786BA7; tenantID=00000000-0000-0000-0000-000000000000
2019-03-24T09:15:29:670+05:00 5604 I00000000: I00000000: Backup Inclusions list:

2019-03-24T09:15:29:670+05:00 5604 I00000000: I00000000: E:

2019-03-24T09:15:29:671+05:00 5604 I00000000: I00000000: Archive: //192.168.2.214/FILESRV-OFFSITE/\server2k11.spinsieger.com-FB2C4C79-AF8C-432B-9C7E-962E473D0DD1-1D5572A9-E6B2-4C5B-B8AB-DFA90E22C8DDA

2019-03-24T09:15:30:464+05:00 5604 I00000000: Using ar_io_local to open '\\192.168.2.214\FILESRV-OFFSITE\' with token 0000000000001EBC
2019-03-24T09:15:30:700+05:00 5604 I00000000: Create Full Backup From NTFS (E:)To file file://192.168.1.214/FILESRV-OFFSITE/server2k11.spin.com-FB2C4C79-AF8C-432B-9C7E-962E473D0DD1-1D5572A9-E6B2-4C5B-B8AB-DFA90E22C8DDA.tibxCompression HighExclude Files matching maskMatch criterion *\System Volume Information\*{3808876B-C176-4e48-B7AE-04046E6CC752}; ...Ask for the first media No
2019-03-24T09:15:30:802+05:00 5604 I000101F8: Pending operation 163 started: 'Saving partition structure (Hard disk 1)'.
2019-03-24T09:15:30:807+05:00 5604 I000101F8: Pending operation 166 started: 'Creating partition image (No label (E))'.
2019-03-24T09:15:35:611+05:00 5604 I000101FA: Locking partition E:...
2019-03-24T09:20:08:469+05:00 5604 I00100000: Volume Tracker has failed to find changes on volume 'E:'.
2019-03-24T09:20:08:470+05:00 5604 I0007002E: Error 0x7002e: Forced sector-by-sector mode.
| trace level: information
| channel: tol-activity#CCD1827B-B661-4749-AF96-FC7BFA32D8F3
| line: 0x8ba4fa0bac28c12e
| file: e:\21\core\resizer\archive3\backup_partition.cpp:987
| function: resizer::Archive3ImageBuilder::BackupPartitions
| volume: E:
| fstype: NTFS
| $module: disk_bundle_vsa64_11010
|
| error 0x70018: MFT bitmap is corrupted.
| line: 0xef8b1618a4c0dd9c
| file: e:\21\core\resizer\ntfs\fs_ntfs_misc.cpp:62
| function: resizer::NTFSProcessor::FileRecord::Load
| $module: disk_bundle_vsa64_11010

 

Please advise.

 

Forum Support specialist
Posts: 0
Comments: 2016

Hello Muthuraj.

Have you already tried running chkdsk for E: partition? 

Please follow this KB article for detailed instructions.

Beginner
Posts: 3
Comments: 2

Hi ,

Thanks for your reply .

This issue not happening if i my backup location is Local USB HDD. Only it's arise if My backup location is Tape or NAS .

 

 

Forum Support specialist
Posts: 0
Comments: 2016

Hello Muthuraj,

if checkdisk reports everything OK with E drive, I can suggest that you try a workaround that helped another customer with alike disk error: https://forum.acronis.com/forum/acronis-backup-117/backup-and-recovery-115-backup-fails-read-error

Beginner
Posts: 1
Comments: 7

Hi, 

It's been 1-2 years since I have the problem described above. I gave up on trying to fix it but it is becoming very frustrating so i decided to contact you.

2019-07-03T21:32:42:631+03:00 140076360492800 I0007002E: Error 0x7002e: Forced sector-by-sector mode.
|trace level: information
| channel: tol-activity#1A0F0559-4791-4F5E-B81F-81A73CAAD218
| line: 0xa5695862aaf8e7de
| file: e:/21/core/resizer/backup/backup.cpp:1153
| function: BackupPartitions
| volume: C:
| fstype: NTFS
| $module: disk_bundle_tape_off_glxa64_11010
| error 0x70018: MFT bitmap is corrupted.

The server I back up is a virtual machine (vmware 5.5) Win2012 R2 Active Directory and it has a lot of shared files on it. During the backup task, nobody is connected to the server, so there's no chance for the server to be in heavy load.

Additionally, this happens every now and then, in random instances. If it happens, it takes 1-2 retries to complete successfully, that is to complete without forcing the sector-by-sector mode.

Shadow copies are disabled on that server.

I have also tried to chckdsk the C: volume.

I have also tried to disable the Shadow Copy Optimization Writer by creating the %ALLUSERSPROFILE%\VMware\VMware Tools\vmbackup.conf file.

For testing purposes, the last days i copied the VM on another ESXI host (5.5), i ran the chkdsk on the guest again, and after 3-4 tries with the backup task the problem came back.

I also backup 5 more servers (win2012, win7, win2003) and none of them has any problem.

Any other suggestions?

 

Forum Support specialist
Posts: 0
Comments: 2016

Hello Thanasis,

welcome to Acronis forums!

The log that you shared indicates the errors on volume C. However since you noticed that already did chkdsk C: /r (please make sure that you run chkdsk with /r flag!), there could be another reason.

These messages may appear in rare cases when the virtual machine is under high load during the backup. In these cases there may be a situation when there is data recorded in NTFS journal which is not yet flushed to the volume - the file system, therefore, is recognized as corrupt since Acronis products are unable to read the NTFS journal properly and require that the data is flushed to disk in order to read from it. This situation forces the sector-by-sector backup mode.

In this case, as a workaround, we suggest that you backup this server by installing the respective Agent for Windows inside this vm.

At any case, we strongly recommend that you open a case with Acronis Support Team for this issue investigation. You will be requested to collect Acronis System Report from the server in question.

Beginner
Posts: 1
Comments: 7

Hi there Maria, 

I ran the chkdsk following the /r parameter.

What does it change if i install the Agent for Windows inside the vm? What are the disadvantages?

 

Forum Support specialist
Posts: 0
Comments: 2016

Hi Thanasis.

What does it change if i install the Agent for Windows inside the vm?

Installing the Agent inside the VM allows working directly with VSS of the guest OS, not via VMWare tools service on the host.

As a disadvantage I could mention that a backup of this VM will be written over a network to the host which could low the backup speed.

Beginner
Posts: 1
Comments: 7

Where can i find that Agent in order to install it on the Win2012 server?

I'm using the All-in-One VMware appliance Acronis 12.5 9010

Forum Support specialist
Posts: 0
Comments: 2016

Hello Thanasis.

This Agent is available as a component in the installation file of your Acronis Backup 12.5. Please run this installation file, click Customize installation settings and select Agent for Windows to be installed there. Please look through the respective chapter in the product documentation for more details.