As we are using
Alfresco Community v5.0.0
(d r99759-b2) schema 8022
so may I know if this version already support moving content store to a separate NAS from a shared SAN?
just change configuration to point to new content store directory ?
how to MIGRATE the existing content store to the new path ?
as you know NAS is not as fast as SAN, so any IOPS or disk latency requirement on use with Alfresco Community v5.0.0 ?
any NAS data thoughput requirement fir Alfresco to work well ?
Solved! Go to Solution.
Good morning.
Backup the following subdirectories of the Content Services dir.root directory using whatever tools you’re comfortable with (rsync, xcopy): contentstore contentstore.deleted (optional) solr6Backup
Link.
Copy those directories and paste it in the new path (in your NAS).
Cheers,
Cristina.
Good morning.
I'm not expert on this topic, but i want to share with you some thoughts:
First at all: you need to know the main differences between NAS or SAN. Check this post, please. And, please make special attention on his last presentation. You have here a lot of details you need to know in advance.
If you are finally moving to NAS, it's not complicated: edit your alfresco-global.properties, dir.root should point to your NAS driver.
Then in addition, please be sure your architecture is 100% validate by Alfresco: Alfresco Supported Platforms
And one last recommendation: please make a backup of your production instance, and try first in a test environment (don't touch directly production without any previous test!).
Cheers,
Cristina.
"If you are finally moving to NAS, it's not complicated: edit your alfresco-global.properties, dir.root should point to your NAS driver."
dir.root should point to your NAS driver , yes I know, this is what peple in this forum keep saying but it seems TOO simple.
but this probably work for NEW content as it is talking to new path.
What about old/existing informatoin? how can we migrate old content to NAS ?
but this probably work for NEW content as it is talking to new path. What about old/existing informatoin? how can we migrate old content to NAS ?
You need first o make a backup of your existing contentstore and restore it in your new path on your NAS.
Please do it first in a non production environment.
Cheers.
we are using Windows server For alfresco, so the copy and past will work?
and once copy and paste the old content to the new path Alfresco can read that back automatically ?
what permission is need on the new path for it to work ?
how about the Alfresco DR solution?
our Alfresco setup on top of VM, can I setup the same VM on both PROD and DR site, while the DR one stop all the time (cold standby).
when DR needed, just copy the content store to the smae patch in the DR site, assuming DR site Afresoc has the same infrastucture ?
during daily operation, just schedule a task to keep copying new data from PROD content store path to DR content store path and overwrite any existing same files (DR alfresco is offline anyway?)
@cristinamr wrote:but this probably work for NEW content as it is talking to new path. What about old/existing informatoin? how can we migrate old content to NAS ?You need first o make a backup of your existing contentstore and restore it in your new path on your NAS.
Please do it first in a non production environment.
Cheers.
Very informative post. I really do hope and pray this stuff works!
"You need first o make a backup of your existing contentstore and restore it in your new path on your NAS."
hi,
So backup and store here means, just copy everything in the contentstore and paste it to the new location?
Good morning.
Backup the following subdirectories of the Content Services dir.root directory using whatever tools you’re comfortable with (rsync, xcopy): contentstore contentstore.deleted (optional) solr6Backup
Link.
Copy those directories and paste it in the new path (in your NAS).
Cheers,
Cristina.
tks.
Ask for and offer help to other Alfresco Content Services Users and members of the Alfresco team.
Related links:
By using this site, you are agreeing to allow us to collect and use cookies as outlined in Alfresco’s Cookie Statement and Terms of Use (and you have a legitimate interest in Alfresco and our products, authorizing us to contact you in such methods). If you are not ok with these terms, please do not use this website.