Datasets administration




Overview

Domino administrators have four important responsibilities when managing Domino Datasets:

  1. periodically check the Datasets administration interface
  2. monitor and track storage consumption
  3. set limits on usage per-Dataset
  4. handle deletion of Dataset snapshots



Accessing the Datasets administration interface

To access the Datasets administration interface, click Admin from the Domino main menu to open the Admin home, then click Advanced > Datasets.

Datasets Admin Navigate




Monitoring Datasets usage

The Datasets administration page shows important information about Datasets and Snapshots usage in your deployment. There is a tab for Datasets and a tab for Snapshots. At the top of each you will find the following information:

  • total storage size used by all stored Datasets/Snapshots
  • the size of all storage used by Datasets/Snapshots marked for deletion

Note

The Datasets statistics include all Snapshots associated with a given dataset.

For each of the tabs, below the size statistics, there is a table of Datasets and Snapshots from the history of the deployment.

Datasets Admin Sizes Datasets

Datasets Admin Sizes Snapshots




Setting limits on Datasets usage

There are two important central configuration options administrators can use to limit the growth of storage consumption by Datasets.


Namespace: common
Keycom.cerebro.domino.dataset.quota.enabled
Value: boolean
Default: true
This option controls whether the various Dataset and Snapshot limits
described below are enforced.

Namespace: common
Keycom.cerebro.domino.dataset.quota.maxDatasetsPerProject
Value: number
Default: 5
This option controls the maximum number of local datasets that can be created
in a given project. Datasets marked for deletion are not active and do not count
towards this limit.

Namespace: common
Keycom.cerebro.domino.dataset.quota.maxActiveSnapshotsPerDataset
Value: number
Default: 20
This option controls the maximum number of active Snapshots for a
given Dataset. Snapshots marked for deletion are not active
and do not count against this limit.

Namespace: common
Keycom.cerebro.domino.dataset.quota.maxStoredSnapshotsPerDataset
Value: number
Default: 20
This option controls the total number of Snapshots of any status
for a given Dataset.

Namespace: common
Keycom.cerebro.domino.dataset.graceTimeForDeletion
Value: period
Default: 15 min
This option controls the delay before the delete operation is actually initiated
after a dataset or snapshot is confirmed for deletion by an administrator. This
gives admins an opportunity to still recover the dataset or snapshot if they
confirmed the deletion by mistake.

If a Dataset reaches one of the snapshot limits, attempting to create an additional snapshot will result in the oldest snapshot that is not tagged to be automatically marked for deletion.

When the per project limit on local Datasets is reached, users will not be able to create additional datasets. Administrators can authorize individual projects to ignore these limits with an option in the Hardware & environment tab of the project settings.

Datasets Admin Limit




Deleting Snapshots from Datasets

Administrators can delete entire Datasets or individual Snapshots at any time using the Delete action at the end of each row. Initiating this action will result in a confirmation dialog, and if you choose to confirm, the Dataset (and all associated Snapshots) or the individual Snapshot will be permanently deleted. If the action was initiated by mistake, an administrator can still recover a dataset or snapshot before the delete grace period (see above) expires the delete operation is initiated.

Note

The delete confirmation dialog will indicate what projects are using a given Dataset or Snapshot. Deleting Datasets that are used by a large number of projects can be disruptive since users will not longer have access to this data. You may want to consider notifying users when you think the impact of the deletion may be significant.

When a Dataset or a Snapshot is deleted, it will no longer be available for future executions. Executions that are in progress will also be affected if they attempt to read or write to the dataset that is deleted. To avoid disruptions, Domino recommends following a two-step process for Dataset and Snapshot deletion, where the user who owns the Dataset mark it for deletion, excluding it from any new executions that start. An administrator then takes the action to delete the Dataset or Snapshot, if appropriate. Non-administrator users can never permanently delete a Dataset or Snapshots on their own.

From the Datasets administration UI, you will have the option to Delete all marked datasets or Delete all marked snapshots and perform bulk delete confirmations. Alternatively, you can sort the tables by status to easily find all Datasets ot Snapshots marked for deletion.