Terminology

These are the terms defined by the project:

Storage: It is the server / location where the client stores the backup.

Client: It is the client for the backup server, which suffers backups and perform all works.

Server: Its where is centered all the settings and the server that organized all events.

User Account: In both the server and the storage exists user accounts, these accounts are used by the client to access the resources of the WebS API from the server or storage.

Storage Components

Repository: The repository is a container of images that store information related to backups, each repository have a name, a location on the storage physical disk and a maximum size. A job is always set to a specific repository, when this repository fills to the maximum size. The job will report that storage does not have enough space to store the backup. Unless the job is set to auto-discover a repository, so that will try to use the first free repository configured in storage.

Repository Image: Each repository can have one or more images. Each image stores the backup entries in FLAT format (no rating folders). Each image can have a maximum SIZE. When the image reaches the size limit, the storage creates a new image.

Repository Entry: Each image can contain one or more entries, each entry is pre-allocated before it is stored within the image and represents a client file.

Server Components

Client: It is the client for the backup server, which suffers backups and perform all works. Each client has an ID that used by the Client Daemon to connect in the server.

Client Config: Are the settings for each client, when the client initializes these settings are synchronized.

Client Group: One or more clients may be within a group of clients, groups can be associated with individual jobs.

Job: These works, they can be executed in the client, in the server or in the storage. Each job has a name, a schedule and the particular settings.

Schedule: It is possible to set up multiple schedules and applies each schedule to a job individually.

Operation: When a job executes, it generates an operation, each operation can contain events, entries, progress of the entries, the operation also has flags and a state.

Entry: Each operation may have one or more entries. The entries are the files that begin copied by the operation.

Event: Each operation can generate one or more events, recording the state of the operation and the state of an entry.

Operation Flag: A flag indicates what the operation is, the flags can be: None, Full, Incremental, Delta, Echo, Restore, Purge