AvePoint Knowledge Base DocAve and Governance Automation Database Management Guide

DocAve and Governance Automation Database Management Guide

Search and filter

KB Article ID: 10232

Product: DocAve 6 Suite,Governance Automation
Product Version: All
SharePoint Version: 2010,2013

Details:

The following table summarizes maintenance and recovery of DocAve 6 and Governance Automation databases, as well as what they are used by.

 

Database Name DocAve Cache Database
Used by DocAve Replicator
Functionality ​Stores job history, item modification history, dirty data information, design Information, etc.
Growth Rate

Depends on how many items need to be replicated.

When replicating 1,000,000 items from the source farm to the destination, the source Cache Database size is about 1 GB, and the destination Cache Database size is around 1.2 GB.
Recovery Model Simple
Is there a feature to automatically prune the records in the database (like job/data pruning)?

By default, Replicator has a schedule to run the pruning job every 7 days, and the cycle time is configurable in Replicator configuration file (data\SP2010\Replicator\SP2010Replicator.xml).

The pruning job will delete the orphan mappings, plans, MH records, etc. in Cache Database.
Comments If DocAve Cache Database is broken, the next incremental replication job will be performed as a full replication job, and the failed-try function will not work.

 

Database Name DocAve Stub Database
Used by DocAve Storage Manager and DocAve Connector
Functionality Stores stub information (path, Device ID, etc.)
Growth Rate Depends on how many stubs are stored in the database.
Recovery Model Simple
Is there a feature to automatically prune the records in the database (like job/data pruning)? Cannot be pruned, but can use Orphan BLOB Retention feature to delete the orphan stubs in database for freeing up disk space.
Comments Administrator should treat DocAve Stub Database similar to SharePoint content databases and back up it regularly. If the Stub Database is corrupted or cannot be connected, an end user would not be able to access any stub on the SharePoint site.

 

Database Name DocAve Control Database
Used by DocAve Control Service
Functionality Stores plan, job, settings information, data cache (for Granular Backup and Restore, Storage Optimization, Platform Backup and Restore).
Growth Rate

The plan size depends on how many nodes it contains.

For Granular Backup and Restore, use the following equation to estimate a job size:

2 KB+2 KB*N (N represents the number of site collections in a plan)

If the number of site collections in a plan is greater than 100,
N is 100; if it is smaller than 100, use the actual number as the value of
N.

For Replicator, use the following equation to estimate a job size:

2 KB+2 KB*N (N represents the number of mappings in a plan)

Data cache size depends on the number of site collections, and the frequency of jobs.
Recovery Model Simple
Is there a feature to automatically prune the records in the database (like job/data pruning)?

If the Job Pruning feature is enabled, DocAve will delete the expired job reports from the Control database.

Note that the data cache cannot be pruned.
Comments If the DocAve Control Database is corrupted, the DocAve GUI will not be accessed.

 

Database Name DocAve Auditor Database
Used by DocAve Report Service
Functionality Stores Auditor items.
Growth Rate 10,000 Auditor items will consume 5 MB – 10 MB disk space.
Recovery Model Simple
Is there a feature to automatically prune the records in the database (like job/data pruning)?
  • If the Auditor pruning job is enabled, DocAve will delete or export Auditor records regularly.
  • If the Job Pruning feature is enabled, Compliance Report jobs’ related data will be deleted accordingly.
    		•
    Comments If the DocAve Auditor Database is corrupted, Compliance Report, partial features of Usage Report, and Auditor Controller will not work.

     

    Database Name DocAve Report Database
    Used by DocAve Report Service
    Functionality
  • Stores history information for generating trend line.
  • Stores temporary data for exporting a report.
  • Stores DocAve Auditor data.
    		•
    Growth Rate
  • Depends on how many profiles DocAve contains and how often the collector job runs.
  • Depends on how many reports are generated.
  • Depends on DocAve access frequency.
    		•
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)?
  • After the exporting report job finishes, DocAve will delete the cache information from the database automatically. No pruning feature for historical data.
  • If Job Pruning feature is enabled, jobs’ related data will be deleted from DocAve Report database.
    		•
    Comments If the DocAve Report Database is corrupted, Report Center will not work.

     

    Database Name DocAve Migration Database
    Used by All DocAve Migration Products
    Functionality
  • Stores job details, job notification, and job statistics.
  • Stores source links information for Lotus Notes/Livelink/eRoom Migration.
    		•
    Growth Rate Depends on how many jobs have run and how much data is migrated. 10,000 items will consume about 15 MB disk space.
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)? N/A
    Comments If DocAve Migration Database is broken, it will not affect the migration job, but for Livelink/eRoom/Lotus Notes Migration, the links migrated from the source may be not accessible in the destination.

     

    Database Name DocAve Archiver Database
    Used by DocAve Archiver
    Functionality Stores the SharePoint object information that matched the Archiver rules and the archived status (approved/rejected/archived/failed, etc.)
    Growth Rate

    Depends on how many items are stored in the database.

    According to our test results, 200,000 records will consume 200 MB disk space, but this number will vary.
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)? Cannot be pruned. If the database becomes too large, we can provide a tool to prune the records in the database.
    Comments

    If the Archiver Database is broken, you can use a new one.

    However, this may affect Archiver if it is integrated with Governance Automation; the items that were approved to archive may become invalid.

     

    Database Name DocAve eDiscovery Database
    Used by DocAve eDiscovery
    Functionality
  • Stores the hold items.
  • Stores record of the content on hold.
  • Stores the relationship between the SharePoint hold item and the held data.
  • Stores the mapping of the Crawl Property and the Managed Property.
    		•
    Growth Rate
  • Depends on how many hold Items are there in environment.
  • Depends on how much data is held.
  • Depends on how many customized properties are mapped via Mapping Tool.
    		•
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)?
  • If the content on hold is released in DocAve, the record in the database will be deleted automatically.
  • If the content on hold is released in SharePoint, the record in the database will be deleted automatically after the hold item sync-up is finished.
    		•
    Comments If DocAve eDiscovery Database is corrupted, eDiscovery’s hold function will not work.

     

    Database Name Policy Enforcer Database
    Used by DocAve Administrator
    Functionality Stores the out-of-policy operation data for the Policy Enforcer function.
    Growth Rate

    Depends on how much out-of-policy operation data is generated.

    10,000 out-of-policy operation records – 30 MB
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)? In the Policy Enforcer profile, there is
    Retention Policy. The default retention period is 30 days.
    Comments If Policy Enforcer Database is corrupted, Policy Enforcer jobs will fail.

     

    Database Name Governance Automation Configuration Database
    Used by Governance Automation
    Functionality Stores site collection policies, approval processes, services, service requests, and settings information, etc.
    Growth Rate

    ​​Depends on how many site collection policies, approval processes, services, and service requests that Governance Automation contains.

  • 100 policies – 25.99 MB
  • 200 approval processes – 4.8 MB
  • 300 services – 35.39 MB
  • 20,000 service requests – 1.07 GB
    		•
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)?

    Workflow instance records of service requests will be automatically removed from the database when the related service requests are complete or cancelled.

    No pruning for other records.
    Comments If Governance Automation Configuration Database is corrupted, Governance Automation will not work.

     

    Database Name Governance Automation Audit Database
    Used by Governance Automation
    Functionality Stores user activity report, service request report, and approval process reports.
    Growth Rate

    Depends on the frequency of accessing Governance Automation, service request, and approval process entries in Governance Automation.

    20,000 audit records – 2.01 MB
    Recovery Model Simple
    Is there a feature to automatically prune the records in the database (like job/data pruning)? No pruning for Governance Automation Audit Database.
    Comments If Governance Automation Audit Database is corrupted, Governance Automation will not work.