Package filter not working for /jcr:system/jcr:versionStorage

[federicos727792]

Hi,

I'm trying to replicate content from one author to others. This is to implement a blue / green deployment strategy and also to use the same content in dev environments and also to generate incremental backups . I've read about the different options (vlt, grabbit, query-packager, hdd snapshot, etc.). The chosen solution is to generate packages dynamically. The idea is to also keep the different versions of the content. To that end I'm trying to generate a package that includes /jcr:system/jcr:versionStorage nodes, but I just can't make it work.

No matter what root path and pattern I use NOTHING ever makes it to the package. I'm using the package manager. The really puzzling thing is that clicking my package -> more -> Coverage lists all the nodes and properties I expect to be included, but when I build and list the content nothing is there, just:

Building package
A META-INF
A META-INF/vault
A META-INF/vault/config.xml
A META-INF/vault/filter.xml
A META-INF/vault/nodetypes.cnd
A META-INF/vault/properties.xml
A /.content.xml
A /_jcr_system
A /_jcr_system/.content.xml
- Aggregation status: 1 of 0 prepared, 0 collected
A META-INF/vault/definition/.content.xml
JCR documentation suggests that these nodes shouldn't behave differently. Also I couldn't find any permissions problem and in any case I'm using the admin user on a fresh installation. Here's a simple example that doesn't work:

Root path: /jcr:system/jcr:versionStorage

Any suggestions?

Thanks

[Hemant_arora]

Can you share error logs?

[federicos727792]

        Unfortunately there are no errors in the log.

[askdctm]

Hi,

Not pretty sure, but just wondering if there are too many nodes in there it might be taking time and we are checking while this is happening. 

[federicos727792]

> Not pretty sure, but just wondering if there are too many nodes in there it might be taking time and we are checking while this is happening. 

I'm not sure what you mean. But I can tell you a few things: 

• When specifying just /jcr:system/jcr:versionStorage and a patterns like (.*) it takes about 6-10 secs to complete.
• When specifying a narrower path (like /jcr:system/jcr:versionStorage/c0/4e) it finishes in 2-3 secs.

In any case it finishes and creates a mostly empty package. Is this useful?

[askdctm]

Hi,

When I try the same in my local instance, I get a similar message except for an additional entry "A //test_page29082.html.binary" and the package has corresponding files in the package. Not pretty sure, what is the problem here. May be change the log level to debug to see if there is any additional information that is getting into the log files.

[federicos727792]

This is an intriguing answer. A few clarifications:

1. What filter/s and pattern/s did you use to generate the package?
2. Did you try to install the package in another author? If you did, did you get the expected files under /content and /jcr:system/jcr:versionStorage? As a final test, are you able to see the different versions of a page when using the authoring interface?
3. Anything noteworthy in the logs?

I'll change the log level to debug and try again in my dev environment.

[federicos727792 · Accepted solution]

For reference I've confirmed that paths under /jcr:system/jcr:versionStorage are added under a .content.xml file and not as separate files. However they can't be installed on an author because since aem 6.1 it is a protected path. (https://docs.adobe.com/docs/en/aem/6-1/release-notes/deprecated-removed-features.html acl item)

Crx2oak seems to be the only working option.