• State Verified Answer
  • Locked Locked
  • Replies 10 replies
  • Subscribers 27 subscribers
  • Views 15227 views
  • Users 0 members are here
Options
Related
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Failed on: Determining Data to Send

Corrigun
over 7 years ago

I am getting the following error from the "C" partition of a Windows 2008r2 DC on the first backup. The reserve partition and the data partition seem to not have this problem.

It appears that Dell has a KB about this and even though we have three Dell SonicWalls with current service contracts it will not let me read the KB after logging in.

https://support.software.dell.com/appassure/kb/177780

We do have Symantec Appassure running on the server being backed up but had AA backing it up prior to the upgrade to RR. If this will not work I need to know now before we pay for the license.

Parents
  • +1 over 7 years ago
    The fact that AppAssure was able to take a backup, is actually a problem. The code was changed between AA and RR so that it would block backups in this scenario. The reason being that a backup in AA of a system with a volume offset problem would result in a full restore (export or BMR) failing. This is because the partition is actually larger than the underlying physical disk. So during a restore of the full partition, it would fail since the partition is trying to be written to a disk that is smaller than it is.

    A partition offset problem like this simply means that the last volume on that disk is larger than the physical disk and so has logical blocks of data that have no underlying physical component. To fix this, all you should need to do is shrink the last volume on the disk that is failing to backup. Or if this is a virtual machine, expand the disk in your hypervisor (but don't increase the partition size). In the case of a system disk, you usually have a System Reserved Partition and a C volume. Shrink the C volume by the amount of the offset and then it will work. In most cases that shrink only needs to be a few MB.

    These partition offset problems are most commonly caused by physical to virtual conversions of the machine. They can also occur in standard windows installations where windows miscalculates (for some unknown reason) and makes the partition larger than it should be.
Reply
  • +1 over 7 years ago
    The fact that AppAssure was able to take a backup, is actually a problem. The code was changed between AA and RR so that it would block backups in this scenario. The reason being that a backup in AA of a system with a volume offset problem would result in a full restore (export or BMR) failing. This is because the partition is actually larger than the underlying physical disk. So during a restore of the full partition, it would fail since the partition is trying to be written to a disk that is smaller than it is.

    A partition offset problem like this simply means that the last volume on that disk is larger than the physical disk and so has logical blocks of data that have no underlying physical component. To fix this, all you should need to do is shrink the last volume on the disk that is failing to backup. Or if this is a virtual machine, expand the disk in your hypervisor (but don't increase the partition size). In the case of a system disk, you usually have a System Reserved Partition and a C volume. Shrink the C volume by the amount of the offset and then it will work. In most cases that shrink only needs to be a few MB.

    These partition offset problems are most commonly caused by physical to virtual conversions of the machine. They can also occur in standard windows installations where windows miscalculates (for some unknown reason) and makes the partition larger than it should be.
Children
No Data