Overview

By default, CentreStack stores data in the file system in the directory C:\CentreStack. This article explains the directory structure of the C:\CentreStack folder and its subfolders.

Details

When the CentreStack server is first installed the Default Tenant is set to use the C:\CentreStack directory for "Backend Storage". Backend Storage is used for "per-user" data and for storing file system data that is synced from remote file servers via the CentreStack Server Agent. The Backend Storage for the Default Tenant can be seen in the Tenant Dashboard:

When CentreStack is first installed the C:\CentreStack directory will contain two subdirectories, Documents and Pictures:

1. Default Tenant

Scenario 1.1

Suppose the cluster admin switches to the file browser mode and uploads a file named ClusterAdminRoot.txt to the "root" of their per user directory:

This file will exist as "C:\CentreStack\ClusterAdminRoot.txt":

Scenario 1.2

Suppose the cluster admin uses the CentreStack file browser to upload a file named "ClusterAdminDocuments.txt" into their Documents folder:

This file will be stored as "C:\CentreStack\Documents\ClusterAdminDocuments.txt":

Scenario 1.3

Suppose a team folder named "Default1" is created in the Default Tenant and the Default Tenant Storage options is used:

Suppose the tenant admin uploads a file named "Default1TeamFolder.txt" to the new Default1 Team Folder:

This file will be stored as something resembling: "C:\CentreStack\43811DCD-8C5A-4EF9-B903-2EEA9CE88487\gsync_Default1\Default1TeamFolder.txt@m#243793451^81ffa7a0-b614-4f6f-993e-7a7d6b7b3fa9":

The "C:\CentreStack\43811DCD-8C5A-4EF9-B903-2EEA9CE88487" directory will contain team folders for the Default Tenant but not team folders for additional tenants. There may be other subdirectories elsewhere in the tree with the ID 43811DCD-8C5A-4EF9-B903-2EEA9CE88487 that are specific to each tenant. Each of these directories can be thought of as the  "Team Folder Root Container" for a given tenant.

Notice that the subdirectory "C:\CentreStack\43811DCD-8C5A-4EF9-B903-2EEA9CE88487\gsync_Default1" corresponds to the new Default1 Team Folder. The text "gsync_" is always prepended to the Team Folder names. Because file revisions are enabled by default, the file is created with its original name appended with the @ sign plus additional information that allows the system to identify the version information. A file containing *@m*" is a modified file, while a file containing "*@d*" indicates a deleted file that has not yet been purged. 

Scenario 1.4

Suppose a user is created in the default tenant:

 If the new user STORAGE page is displayed then the Storage Folder is displayed similar to: "41ed6c26-d5f8-424f-a311-bb4ff88140e5/d548dd92-5c69-4848-9c99-77a38f8cf58b" which can be seen in the Backend Storage:

The "C:\CentreStack\41ed6c26-d5f8-424f-a311-bb4ff88140e5" directory is the CentreStack "User Home Storage Container" for the Default Tenant. There may be other directories elsewhere in the tree with the ID 41ed6c26-d5f8-424f-a311-bb4ff88140e5 that are specific to each tenant. Each of these directories can be thought of as the "User Home Storage Container" for a given tenant. All per-user directories will exist as subdirectories under these directories in each tenant.

If this user uploads "UserOneDefaultPerUser.txt" to their Documents directory in the CentreStack file browser:

It will be stored as "C:\CentreStack\41ed6c26-d5f8-424f-a311-bb4ff88140e5\d548dd92-5c69-4848-9c99-77a38f8cf58b\Documents\UserOneDefaultPerUser.txt"

2. Tenant 2

Suppose the cluster admin creates a new tenant named "Tenant2":
And the tenant is created with the option Automatically assign a sub-folder from cluster default tenant:

As soon as the first additional tenant is created with the Automatically assign a subfolder from cluster default tenant option then the C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E is created:

C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E can be thought of as the "Additonal Tenant Storage Container". Each tenant created with the Automatically assign a subfolder from cluster default tenant option will have a sub-directory specific to that tenant created under C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E. 

Scenario 2.1

Suppose the tenant admin of the Tenant2 tenant switches to the file browser mode and uploads a file named Tenant2AdminRoot.txt to the "root" of their per user directory:

 It may be difficult to determine which sub-directory under C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E is associated with Tenant2. In order to make this determination, search for Tenant2AdminRoot.txt in File Explorer:

Then right click on the search results and select Open file location from the context menu:

File Explorer will display the actual storage location, C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E\ce0feee0-95b3-453e-85af-a93fde9aa417:

C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E\ce0feee0-95b3-453e-85af-a93fde9aa417 can be thought of as the "Tenant Root Container" for the Tenant2 tenant. The tenant admin's documents are stored as file and folders directly under this folder. 

Scenario 2.2  

Suppose another user is created in Tenant2 named user.two@tenant2.com:

 The Storage Folder for this user can be examined:

Notice that a second 41ed6c26-d5f8-424f-a311-bb4ff88140e5 directory has been created (or "User Home Storage Container"), this time under the "Tenant Root Container" for the Tenant2 tenant (..\ce0feee0-95b3-453e-85af-a93fde9aa417):

And the cf803bc0-1f81-492f-b3ff-f5942f0507bc sub-directory corresponds to the per-user data for user.two@tenant2.com.

If user.two@tenant2.com signs in and uploads a file named UserTwoTenant2PerUser.txt to their Documents folder:

 This file will be stored as: 

"C:\CentreStack\D8F45A62-81AA-49D8-AB63-7A0BA7CC682E\ce0feee0-95b3-453e-85af-a93fde9aa417\41ed6c26-d5f8-424f-a311-bb4ff88140e5\cf803bc0-1f81-492f-b3ff-f5942f0507bc\43811DCD-8C5A-4EF9-B903-2EEA9CE88487\gsync_Documents\UserTwoTenant2PerUser.txt@m#243885635^cf803bc0-1f81-492f-b3ff-f5942f0507bc"

If this long pathname is split into its components then this table could be used to describe the components of the pathname: