Resources

#

Resources are the individual systems, services, or storage targets that Plakar Control Plane manages as part of a backup workflow. Examples of resources include S3 buckets, EC2 instances, PostgreSQL databases, virtual machines, and filesystems.

flowchart TB
  subgraph Inventories
    Managed["Managed inventory\n(AWS, Scaleway, ...)"]
    SelfManaged["Self-managed inventory"]
  end

  subgraph Resources
    R["Resource\nclass / subclass"]
  end

  subgraph Apps
    Source["Source\n(Back up content from here)"]
    Store["Store\n(Store backups here)"]
    Destination["Destination\n(Restore here)"]
  end

  Managed -->|"auto-discover"| R
  SelfManaged -->|"manually added"| R
  R --> Source & Store & Destination

All resources discovered across all inventories are available under Infrastructure -> Resources. From here a resouce can be assigned to either a source or a destination app. You can also filter resources by inventories or by resource class.

Resource settings

#

Resource settings can be updated from the Settings tab under each resource. For managed inventories, most settings are read-only since the resource is managed by the inventory. For self-managed inventories, all settings can be modified. Backup coverage can be modified for any resource regardless of inventory type.

Backup coverage tracks how many of your resources are protected by backups. If a resource does not need to be backed up (for example, a test database), you can exclude it from coverage using the Exclude from backup coverage. Excluded resources are omitted from protection status and coverage reporting.

Resource classification

#

Each resource is assigned a class and subclass that describe what kind of infrastructure it is.

The class describes the general category the resource belongs to, while the subclass identifies the specific implementation or provider. Plakar Control Plane uses this classification to determine which integrations are compatible with a resource.

Supported resources

#

The following pages document the supported resource types and the configuration required to use each one as a source, store, or destination.