<< Click to Display Table of Contents >> Navigation: Peer Global File Service Help > Terminology |
Before getting started, it is important to have a good understanding of key concepts and terminology used throughout this help system.
Term |
Definition |
---|---|
Two or more file servers that hosts data sets that are in active use, as opposed to an active-passive environment where only one file server hosts active data. Made possible by real-time file synchronization to keep all file servers in sync. |
|
Agent |
See Peer agent |
A job type where a single participating host has a designated set of folders and files to be replicated to a cloud storage device. |
|
A set of client and server services that allow an organization using Microsoft Windows servers to organize many distributed SMB file shares into a distributed file system. |
|
A namespace that enables you to group shared folders located on different servers into one or more logically structured namespaces. |
|
A Windows Server feature that allows multiple SMB shares across different file servers (and even locations) to be combined into a single unified namespace. DFS Namespaces simplifies access to files, especially in large, distributed environments. When combined with Peer file synchronization technology, DFS Namespaces can provide redundancy to file shares across file servers and locations. |
|
A type of job that enables the creation and management of DFS namespaces. |
|
A single operation performed by a user on a file server. |
|
The process of redirecting previously displaced users from a secondary file server back to the primary after a failure state has been resolved. |
|
The process of redirecting users from one file server to a secondary in the event of a failure. |
|
An event that is triggered from the opening or closing of a file. |
|
An event that causes a file to be changed in some way, for example, file modify, file delete, file rename, file attribute change. |
|
A type of job that combines file synchronization with distributed file locking to prevent version conflicts across multiple active file servers. |
|
A communication session made up of two or more hosts, each with a designated root of folders and files that are to be shared or collaborated on. A collaboration session coordinates the primary functions of file locking and synchronization. |
|
A type of filter used to include or exclude specific files from replication and locking. |
|
A file collaboration condition that exists when two users open a file at the same time, and both hold exclusive locks on the file. |
|
A type of job that involves real-time and/or scheduled copying of files and folders from one file server to another. |
|
A type of job that involves multi-directional real-time replication so that two or more file servers are always up to date with each other. |
|
Three types of filters: file, folder, and list. |
|
See list filter. |
|
A type of filter used to include or exclude specific folders (and the files they contain) from replication and locking. |
|
A communication mechanism used between Peer Management Center and all connected Peer Agents to ensure that Peer Agents are alive and responsive. Heartbeats share information about the Peer Agent host server with Peer Management Center, aid in verifying when a Peer Agents is no longer available, and signal when a disconnected Peer Agent has reconnected. All heartbeat information is sent through the Peer Management Broker. |
|
A server that a Peer Agent is installed upon. When active in a job, it is called the host participant or participating host. |
|
The steps executed whenever a job is started in Peer Management Center. The steps for an initialization process are different for each job type. |
|
The background process that occurs at the start of a file collaboration session, where the directory watch set is recursively scanned on all participating hosts, file conflict resolution is performed, and any files that require updating are synchronized with the most current copy of the file. |
|
A type of filter used to show or hide information from various views in Peer Management Center. |
|
A server running the Peer Agent. Can manage storage devices or a DFS namespace. |
|
In file synchronization and collaboration, the master host will always win in a split-brain scenario. |
|
Leverages the same real-time event detection that powers all job types to detect and alert administrators to malicious user and application behavior. For more information, see: https://kb.peersoftware.com/tb/introduction-to-peer-med. |
|
A participant consists of an Agent and the volume/share/folder to be replicated. The server that the Agent is installed upon is called the host participant or simply host. Applies to File Collaboration, File Replication, and File Synchronization jobs. |
|
A lightweight piece of software that is installed on Windows Servers to perform the storage and file management functions used by the entire Peer Global File Service solution suite. Typically installed on or alongside the file servers that will be managed by Peer Management Center. |
|
The focal component of Peer Global File Service. Responsible for configuration, management, and monitoring of Peer Agents and the various solutions configured in Peer Global File Service. Peer Management Center runs as three parts: a Windows Service that is always running, along with a rich client application and a web server component, both used for configuration and monitoring. |
|
The central messaging system of Peer Global File Service. The Peer Management Broker serves to connect Peer Management Center and Peer Agents, forming a Peer Management Center "network" that can be cast over local or wide-area networks via TCP/IP. One or more Peer Management Brokers are deployed in a Peer Management Center environment. |
|
A file that has been removed from a File Collaboration or File Synchronization job as a result of a lock or replication conflict that could not be automatically resolved. This file will not be deleted from any location but will be ignored while it remains in quarantine. An administrator or help desk user must manually remove files from quarantine. |
|
Requirement for a minimum of two participants must be available and connected. If that number dips to one or less, quorum will not be met. Applies to File Collaboration, File Replication, and File Synchronization jobs. |
|
A key technology that backs all job types in Peer Management Center. Peer Management Center receives notifications as end users interact with the file servers that are being monitored. These notifications will usually result in replication or locking between file servers. |
|
The initial process of comparing data sets on two or more file servers to ensure that they match. As differences are discovered, replication will occur to bring each file server “in sync” with one another. |
|
Smart data seeding helps to efficiently integrate a host that has been disconnected for a long period of time or a new host into a File Collaboration job. Such existing hosts or new hosts with pre-seeded data (using methods like shipping a drive or server) should be set as Seeding Targets within a collaboration job. When the scan starts, non-Seeding Targets will become the masters and bring the Seeding Targets up to date. Stale updates, deletes, and renames will NOT be brought back from the Seeding Targets. All local real-time activity will be quarantined. Once that initial scan is complete, the Seeding Targets will become full participants with real-time enabled. For more information on Smart Data Seeding and its potential options, see Smart Data Seeding or contact support@peersoftware.com. |
|
Server Message Block or Common Internet File System, an application-layer protocol used for providing shared access to file data and other networked resources. |
|
The file server hosting a file from which file access or change event originated. |
|
One or more Management Agents of file servers where file access and change events will be propagated to. |
|
Transport Layer Security, a successor to Secure Socket Layer (SSL) that secures network traffic between a client and server. |
|
A UNC path can be used to access network resources and MUST be in the format specified by the Universal Naming Convention. A UNC path always starts with two backslash characters (\\). |
|
Individual sections of Peer Management Center's user interface, each providing unique information and control. Examples: Main view, Jobs view, Agent Summary view, Alerts view, Job Alerts view. |
|
Shadow Copy is a technology included in Microsoft Windows that allows taking manual or automatic snapshots of computer files or volumes, even when they are in use. It is implemented as a Windows service called the Volume Shadow Copy service. |
|
The root folder and all subfolders on a file server that are being scanned and/or monitored by a File Collaboration, File Replication, File Synchronization, or Cloud Backup and Replication job. |