Catalog domain: entities and attributes
The Guardium catalog tracks where every archive or backup is sent. The catalog domain presents catalog details.
Entry entity
| Attribute | Description |
|---|---|
| Aggregator | Aggregator from which archive or backup was created. |
| Audit Process Description | Description of the audit process that was archived/backed up. |
| Comment | User added comment. |
| Disk Space | |
| From Date | Start date of the data that is archived. |
| Global ID | Unique ID. |
| Guardium version | Version of managed unit. |
| Run Number | Audit process results run number. |
| Step | Entry can archived and purged, or archived not purged. If the archive has a catalog entry location, then also where it's archived stored the credentials. |
| Timestamp | Last time table was updated. |
| To Date | End date of the data that is archived. |
| Type | Data or audit process result can also be a system backup. |
Location Entity
How to determine what days are not archived
catalog entry
Use a query (Tools tab > Report Building > Report Builder > query Location View) that can be modified to create a report showing the files that are archived. This report lists all the files with archive dates. Dates not on this report indicate that those dates have not been archived. Run archive for the dates not on the list, if required.
| Attribute | Description |
|---|---|
| Host | Host name where backup/archive is stored. |
| Path | Path to backup/archive files. |
| Retention | |
| User Name | User that has access to this location. |
Used By entity
| Attribute | Description |
|---|---|
| Mount Event | |
| Mount Time | |
| Request Count | |
| Used By |
Destination entity
| Attribute | Description |
|---|---|
| Class ID | The system name. Can also be a storage system, ESM, Amazon, and so on. |
| System Type | related |