We are currently using AEM 6.0 and it is currently pointing to NFS storage for repository and segment store data. Can we create another AEM 6.0 instance and point that also to same NFS location?
Solved! Go to Solution.
Hi Anantha -
A few answers to your question. First of all, I'm sure others have likely advised as much, but you'll definitely want to upgrade this installation as urgently as possible off of AEM 6.0 to AEM 6.5 with the latest service pack. In addition to being EOL since 2018, AEM 6.0 was also the first version to use Oak, and was prone to a number of issues that affected stability as I'm sure you've noticed. Additionally, any of the clustering options you'll see noted & documented (such as using MongoMK for author) will not be documented or workable with AEM 6.0.
Next - with AEM 6.0, this was before Adobe had separated the Segmentstore and the Datastore. The Segmentstore contains the whole running state of that ONE instance of AEM (configurations, hostname, deployed code, content, etc) so cannot be shared with any other instance.
There ARE ways of using a shared Datastore, which are gone over in this doc: Configuring node stores and data stores in AEM 6 | Adobe Experience Manager
However, the decisions you make on sharing the datastore (or externalizing the datastore) have to be made at the time that AEM instance is FIRST started. Once you've started it, the die is cast and you can't then reconfigure it. So, if you're already going to be starting it up newly, you may want to evaluate that as a point in time to consider a 6.5 upgrade.
Hope that helps.
Hi,
It's technically possible to point multiple AEM instances to the same NFS location for the repository and segment store data. However, doing so is not recommended and can lead to significant issues, including data corruption and inconsistent repository states.
Consider upgrading to new versions of AEM, since AEM 6.0 is quite old and newer version supports more advanced clustering and data sharing mechanisms, such as Oak clustering with MongoDB or RDBMS.
Data stores can be shared, but not the Segment store.
If you have a need for multiple author instances, consider using MongoDB.
Hi Anantha -
A few answers to your question. First of all, I'm sure others have likely advised as much, but you'll definitely want to upgrade this installation as urgently as possible off of AEM 6.0 to AEM 6.5 with the latest service pack. In addition to being EOL since 2018, AEM 6.0 was also the first version to use Oak, and was prone to a number of issues that affected stability as I'm sure you've noticed. Additionally, any of the clustering options you'll see noted & documented (such as using MongoMK for author) will not be documented or workable with AEM 6.0.
Next - with AEM 6.0, this was before Adobe had separated the Segmentstore and the Datastore. The Segmentstore contains the whole running state of that ONE instance of AEM (configurations, hostname, deployed code, content, etc) so cannot be shared with any other instance.
There ARE ways of using a shared Datastore, which are gone over in this doc: Configuring node stores and data stores in AEM 6 | Adobe Experience Manager
However, the decisions you make on sharing the datastore (or externalizing the datastore) have to be made at the time that AEM instance is FIRST started. Once you've started it, the die is cast and you can't then reconfigure it. So, if you're already going to be starting it up newly, you may want to evaluate that as a point in time to consider a 6.5 upgrade.
Hope that helps.
Views
Likes
Replies