FileCloud Server is sometimes called on-premises. This is because you are using the storage space you have locally in your infrastructure to store the files managed by FileCloud Server.
- Managed Disk Storage is just a path to the location where the user files are stored locally and can be accessed directly by FileCloud Server
- When you specify the path to managed storage, you allow FileCloud complete control over the management of user content
- Managed storage can be a path to file systems, a local hard disk, and Storage Area Network (SAN) or Network Area Storage (NAS) disks
When setting up FileCloud, a critical setting is the path where FileCloud stores its files.
Setting up Managed Storage Path for Local Storage is only needed if you are using FileCloud Local Storage.
If you are using Amazon S3 or OpenStack, you don't need to set this path.
In the following section, to display more information, click on a step.
To configure the storage path:
- Use the Admin Attention Required dialog for the initial setup.
On initial login into the Admin Portal, if the storage path is not set or not writable, an "Admin Attention Required" dialog is shown as below.
Type in the path to the storage location in the box. You can click on the "Check Path" button to verify that the path exists and write permissions are available. Click on "Apply" button to set the storage path correctly.
Example Paths for Windows Installs: "c:\data", "e:\fileclouddata"
Example Path for Linux Installs: "/opt/fileclouddata"
2. Use the Admin portal to manage storage path changes.
Managing the Storage Path
To set or change storage path, open the FileCloud Admin Portal and then open the Settings->Storage Tab. Set the path as needed (for example on Windows c:\filecloud, or on Linux /opt/filecloud) and finally save the settings. Note that making this change after users have started uploading the files to the system will make many files missing unless the original files are carefully copied over to the new location.
Do not change the storage path to the new location without copying over ALL folders and file that exist in the old path. Not copying the old data might lead to data loss.
3. After setting the path, you can rerun the install checks.