How to manage Hot backup Or Manage Disaster Recovery in CQ

- Yogesh Upadhyay

There are various approach, I am listing them with pros and cons

Approach 1: Use clustering, but direct the requests only to one node. In case of problems with this node just switch over to the other node. Essentially this is an active-passive scenario.

+ proven technology, documented and fully supported feature

+ automatic fail over easily possible

- additional license cost

- Latency issue might effect performance

- Managing cluster is sometime difficult


Read the complete post at the Adobe CQ/Adobe WEM blog.

CRX 2.3: snapshot backup

-- Jörg Hoh

About a year ago I wrote an improved version of backup for CRX 2.1 and CRX 2.2. The approach is to reduce the amount of data which is considered by the online backup mechanism. With CRX 2.3 this approach can still be used, but now an even better way is available.

A feature of the online backup — the blocking and unblocking of the repository for write operations — is now available not only to the online backup mechanism, but can be reached via JMX.



Read the complete post at Things on a Content Management System blog.

New CQ best practice articles now live!

- Samartha Vashishtha, Content and Community Lead @ Adobe

We’ve just published the following three CQ best practice articles:

These articles are the first few in the CQ best practices series. In the days to come, we’ll post more best practices, tips, tricks, and troubleshooting information that you can apply to your work.

Stay tuned!


Read the original post at The Doc Fox.