This scenario is the most interesting for increasing logging capabilities, as acquisition is triggered by periodical event (once a month, once a week, etc…) before archiving the memory copies locally (e.g. a file share) as you’d normally do with logs. One of the main pain point reported from our users, before they adopting Comae DumpIt, was that several vendors have issues during memory acquisition for servers with more than 64GBs of RAM which prevented them to investigate large servers. In addition of file size optimization, this also allows the acquisition to be significantly faster by reducing the number of I/O operations to disk — especially when acquiring the memory from servers with a gargantuan amount of physical memory.