• State Not Answered
  • Locked Locked
  • Replies 9 replies
  • Subscribers 30 subscribers
  • Views 8120 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

C:\Program Files\AppRecovery\Core\CoreService\tracing.e2e file taking up space

sthomson_10326
over 5 years ago

The server I'm running Rapid Recovery on is having C: drive space issues.  I've already done everything I can to free up space including the usual Windows cleanups and moving some RR folders to another partition (\EventsDatabase and \RepositoryMetaData).  There is one file left, the tracing.e2e file noted in the subject which is 15.4Gb and last modified 11 days ago.  If I can move that file that should take care of the space issues permanently.  I couldn't find any knowledge base articles covering this, anybody know if this file can be moved?

  • 0 over 5 years ago

    Helloooooo... we're having the same issue too. How do you disable this?

  • 0 over 5 years ago

    For us the same, since upgrade to 6.2.1 we see that mounting a recovery point is taking lots off space on C:

  • 0 over 5 years ago

    This has been identified as a defect in Rapid Recovery. It is fixed in the latest release version 6.2.1. Please upgrade to that version to solve the issue going forward. If you cannot upgrade for some reason, that file can simply be deleted each time it grows to a size too large.

  • 0 over 5 years ago in reply to Tim Seymour

    No, this answer is not correct. We did NOT have this issue until upgrading to 6.2.1.

  • 0 over 5 years ago in reply to dandrews

    The original question was about the tracing.e2e file. That's what I'm talking about. That issue was fixed in 6.2.1, but more than likely you will have to delete the tracing.e2e file after upgrade to set it back to a small size. If you are still seeing this behavior, please create a support ticket so that our support team can investigate. 

    Mounting recovery points does consume space on the C volume by default. To mount a recovery point we create an index map of each mounted disk. This index map consumes 1 GB of space per 1 TB of total disk size on the disk being mounted. So if you have a 10 TB disk  and you mount the recovery point for that disk, it will create a 10 GB index map. It is based on total disk size not used space. So if you have a lot of big disks and you mount more than one recovery point at a time it can consume a lot of space.

    In your scenario, what files are consuming the most space?

     

  • 0 over 5 years ago in reply to Tim Seymour

    Mounting is not our issue. It was the tracing.e2e file. Stopping, deleting, and (re)starting worked. We were unaware if this file existed before or not as there was no space issue on the C: drive until we upgraded.

  • 0 over 5 years ago in reply to d verhoeven

    Hi Tim, about mounting the recovery points, I have never before noticed that it’s consuming such a lot off disk space. Our C-drive is just 100Gb big, and we are backing up 7,5 TB data. Last week I needed to mount 2 recovery points, and saw my disk space was to little to add the second mounting point. I Saw that with removing a mounting point, a lot off space came free.

  • 0 over 5 years ago

    Edit Core.Service.exe.Config in C:\Program Files\AppRecovery\Core\CoreService

    Search for e2e

    Edit the key <add name="sdt" type="System.Diagnostics.XmlWriterTraceListener" initializeData="tracing.e2e" />

    Simply add the path of where you want the tracing.e2e file to be, for example

    <add name="sdt" type="System.Diagnostics.XmlWriterTraceListener" initializeData="d:\tracing.e2e" />

    Stop Quest Rapid Recovery Core Service

    Delete the tracing.e2e from C:\Program Files\AppRecovery\Core\CoreService

    Restart Quest Rapid Recovery Core Service