Anchor utilizes two separate storage mechanisms to allow for scalability and rapid-access:
- File store—contains compressed and encrypted raw binary data. File stores can become quite large as systems scale in size.
- Root store—made up of various SQLite databases that contain file and folder metadata. Each root type (Personal root, Team Share root, and Backup root) is assigned to its own SQLite database.
As a file store grows in size, you might need to migrate the file store to a new location. During these instances, you can temporarily set the file store to read-only. For complete instructions on migrating a file store to a new location, please reference the Migrating One File Store Location to Another Location Knowledgebase article.
It is important to note that the root stores will still be written to as root databases are modified, but no new databases will be created. Additionally, file stores will still be modified as files are purged and revisions are trimmed. However, no new data will be written to the file stores.
Setting a File Store to Read Only
- On your server, navigate to C:\PostGreSQL9.1\bin\pgAdmin3.
- Click pgAdmin3, which launches the PostGreSQL9.1 program.
- Within the menu bar, click the Tools menu item and select Connect. Enter the password to the PostgreSQL user account.
Note: Your PostgreSQL user password is listed in the [portal] section of your Anchor config.ini file ([target drive]:\Anchor Server\conf\config.ini).
- Using the Object Browser window, navigate to Servers > (localhost:5432) > Databases > portal > Schemas > public > Tables.
- Right-click the file_store_location table and select View Data > View Top 100 Rows.
- In the status column, change the value to readonly.
- Save your changes.
- Start the Anchor server service.