nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

Backup-Lucene-Indexes(Delete?, Move?)

zxcv1234

Due to the tiny space requirements I am working with currently we are in a pickle regarding space on the partition that is sharing the contentstore data as well as the lucene-Index data.

Content-Store.Deleted is cleared regulary to make sure space stays open but I am iffy to go in and mess with the index files (even the backup ones). The last thing I want to do is corrupt the index and require a rebuild. Our users probally would not like that.

I am a little confused due to the fact that the lucene-indexes that are labeled backup-lucene-indexes are dated 1 year more recent that the lucene-indexes.

Would anyone mind helping me understand if it is ok to move the backup-indexes to another location?
If this is not possible is the only possibility increasing the available space?

Find more posts tagged with

Comments

jonash

The backup-lucene-indexes is a backup copy of the Lucene indexes. It is generated nightly (by default) by Alfresco. It is safe to move it manually to a different location but it will be created again the next day in the old location.

To permanently move the backup of the indexes you can configure the location in alfresco-global.properties:

# The location for index backups
dir.indexes.backup=${dir.root}/backup-lucene-indexes
‍‍‍‍

You can also configure the location of contentstore.deleted with the following parameter:

dir.contentstore.deleted=${dir.root}/contentstore.deleted
‍‍‍

zxcv1234

Thank you for the response. Will a change in the alfresco-global-properties file require a restart of the Alfresco/Tomcat Instance?

That would explain the date being very recent. Looks like I will move the backup files to a place with more space and then change the default location for the backup and all should be well by tomorrow.

Thanks again for helping clear this up.

jonash

Yes, changing the configuration in alfresco-global.properties requires a restart of Alfresco.

If you are using the enterprise edition it is possible to change some parameters without restarting using JMX[1] or the Share admin console. You can do this for the index backup location but not for the content store location (if I remember correctly)

[1] http://wiki.alfresco.com/wiki/JMX