That's fine if it deletes the package, but does it actually uninstall
it? I know you can install a package through Package Manager and after a
while delete it. It shouldn't actually uninstall it - but remove the
package from /etc/packages. However, I'm wondering if the same can be
done without recou...
Yes, I've used the Disk Usage report.That's the tough part, relating
this to an event - Going from 400G to 600G. But oddly enough we are
growing about 2G every hour - but at least it is recoverable through FDS
GC. We are experiencing, since our 6.5.12 upgrade, problems with our
indexes and we've fin...
It does clean up binaries. It works just fine. We to nightly revision
cleanup on all 4 (1 author, 3 publish).It just seems really odd we are
sitting at about 620G shared when our author instance is around 320G
itself. I'm just looking to find a way of relating the blob ids back to
their related AEM ...
I guess my question would then be a bit more general... How does it
compile a list of unused ones?I typically run mark-sweep = true on all 3
publish instances and author. I then run mark-sweep= false on author to
clean it all up. There must be a list consolidated somewhere (DS maybe?
cached?) that h...
It does work. That's not the issue I'm having. I notice that we have
spiked about 150G somewhere in the past 2 months and I'm trying to
figure out why. So, I'd like to figure out a way I can validate all the
blobids in the FDS against the repositories and not the other way
around. Do you know if the...
Marking each AEM instance for file datastore GC is one thing. But I'm
wondering if there is a way, maybe with oak-run that I don't know about,
that can do the reverse: get all the blob ids in the File Data Store and
check against each AEM instance and mark any unused files.So for
example... if I man...
What I do for local environments and our on-premise is to pass in the
resource (bookemark it) to take me directly to the crxde
might also ask... have you actually set up the publish instance? I see
you are new to AEM so...