To assign settings related to system identity and operation, navigate to the following page in the node's WebUI:
Configuration > System Settings
Notes on Configuration Mode (node role)
Each deployment must have at least one Master node. (By default, all nodes are masters and maintain their own security and configuration. When you add a subordinate, you must specify the master that will manage it.)
All configuration settings on the master are automatically propagated to the subordinates. After setting up the hostname and IP address information during installation, you do not need to configure any additional settings on the subordinates.
If you have two masters in the same CloudFS list, ensure that their encryption certificates are the same at all times, as all systems in the same CloudFS list must have the same encryption certificates.
Caution: Every time a subordinate is rebooted or the master configuration changes, the configuration of the subordinate is updated. If you change a node from a master to a subordinate, the current configuration is overwritten with the configuration from the new master. This can cause loss of user access to SMB/CIFS shares.
System Setting Options
The following table describes the system settings you can configure.
Configure as Key Master node
|Enable to make this node the authoritative source for managing the encryption key used by all nodes in the CloudFS. As a best practice, the Master node should also be the key master.|
|Private Site Mode||This mode is used for Dark Sites where your firewall cannot be enabled and there will be no communication going out of the box other than the cloud connect itself.|
Set the node hostname (maximum 15 characters). The name must be unique within the CloudFS. This rule simplifies administration and access to the managed nodes. Use the local DNS server at each site to return the IP address of the local node.
About changing the hostname: It is possible to change the hostname of a node after it has been deployed. Enter the new hostname in the field and click Save. After renaming you must rejoin the Active Directory domain. If you change the hostname, the filesystem name does change, so the name of the SMB/CIFS shares and NFS exports do not change.
|Address of node||Allows you to identify the location of the node in support emails and in the CloudFS UI.|
|Enter the contact name, phone number, and email for the person responsible for node administration.|
|Consistency Interval||Specify the interval after which all nodes within the CloudFS attempt to synchronize changes (60 seconds). Do not change this setting unless requested to do so by Panzura Support.|
|Cloud Object Size||Specify the drive file size from the dropdown list. Modifying the drive file size allows you to accommodate sites that may have less than the recommended 10Mbps network connection. This setting should be changed only with guidance from Panzura Support.|
|Select whether to enable or disable data compression for files that are moved to the cloud for storage. Default is enabled. Data compression can provide more efficient use of local and cloud storage and more efficient data transfers. There can be a slight performance improvement if data compression is not used. The trade-off is between efficient use of resources and performance. We recommend that you enable data compression globally in this section. If you have some specific data files that you do not want to compress (because they are already compressed), you can override data compression for specific data sets in the Smart Cache section. See Setting Up Smart Cache.|
Select whether to enable or disable data deduplication for files that are moved into the cloud for storage. Data deduplication provides efficient use of local disk storage (cache) and long term storage (cloud storage). Default is enabled.
Enabling data deduplication on a node benefits other nodes as well because the results of data deduplication are shared across all the systems. Results of data deduplication are data-specific and require the use of CPU, memory, and disk I/O. It is not recommended for data sets that are already optimized and for those where appropriate duplication patterns cannot be detected (for example, for mpg files, audio files, encrypted files, or files that are already deduplicated). You can override data deduplication for specific data sets in the Smart Cache section. See Setting Up Smart Cache.
|Server Timeout||Specify how long a user WebUI session can remain idle before it times out. Default is 20 minutes.|
|Time and Date Settings|
CloudFS deployments require that all nodes and Active Directory servers have their clocks synchronized. For the most accurate time synchronization, use the Network Time Protocol (NTP) option and specify the same NTP server for all nodes and the Active Directory server.
For multi-site deployments, it is a requirement to have all nodes and Active Directory servers synchronize their time from the same NTP source (for example, pool.ntg.org). If the times are not synchronized, SMB/CIFS users will not be able to log in and obtain access to their SMB/CIFS shares.
Enable to obtain time settings from an NTP server:
|Time Zone||Select the time zone from the dropdown list.|
|Client Protocol Settings|
You can select the SMB/CIFS and NFS options only if those licenses are installed. You must activate the SMB/CIFS and/or NFS options for them to be displayed on the side menu in the WebUI.
Choose the file sharing protocols to be supported by the node:
|Enable NFS/Enable SMB||Enable the client protocols that you are using.|
|Automatically download new PFOS versions||Select to automatically download and install new PFOS versions when they are available.|
Automatically upload support logs to Panzura
|Select to automatically upload support logs to Panzura.|