Validating Database Archives

To verify the archives created for the database, use nuocmd show archives.

For example:

nuocmd show archives --db-name test
[0] nuoadmin1 : lsa:/var/opt/nuodb/archive/testlsa1 @ test [journal_path = ] [observer_storage_groups = []] RUNNING
  [SM] nuoadmin1:48007 [start_id = 0] [server_id = nuoadmin1] [pid = 175] [node_id = 0] [last_ack =  9.86] MONITORED:RUNNING

Each Storage Manager (SM) independently performs garbage collection on its archive to purge unused data. As a result, archive sizes may vary between SMs. The difference in archive size depends on the type of workload. Workloads that frequently create and drop tables and indexes can cause large temporary differences in archive sizes.

In rare scenarios when the SM is restarted, the normal garbage collection process may not purge all unused data from the archive. As a result, if one or more SM archives remain significantly larger than the others, it may be necessary to manually purge unused data from the archive to reclaim disk space.

Use nuoarchive check to validate all atoms in an archive and to identify and purge unused data that are no longer needed.