Thanks! However I tried this just now (and before), and the Revision Clean Up begins, but completes after a few seconds with "succeeded". My repository is growing daily still, and eventually will fill up the filesystem after a few weeks, so either the Revision Clean Up is not working, or there is some other out-of-the box feature of CQ6 that slowly causes the filesystem that CQ6 resides on to get full (8 new 256MB data*tar files are created daily, and old ones are not reclaimed). Any suggestions...

Justin, can you provide the documentation that describes this? I just want to make sure that this is a supported backup method.

What is the way then to create online backups in CQ without shutting down the application?

Why is blocking writes not necessary? What practical way is there then to have a clean backup of Oak & TarMK without shutting down the CQ application? With CQ 5.5/5.6 the blockRepositoryWrites command conveniently allowed for a system adminstrator to do a point-in-time volume snapshot, capturing the repository state for that point in time. What similar method in CQ6 is there for this? And I am not referring to the old way of doing online CQ backups which basically copies the entire repository to...

Thanks Justin. How is blocking repository writes, or its equivalent done in Oak then?

I have the same problem. Its odd that a new release of CQ6 would have a bug to cause the disk to be full after some days.