contentACCESS documentation version 3.1 with service pack

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. contentACCESS setup package
    1. Installation of contentACCESS
  3. contentACCESS components
    1. contentACCESS Central Administration
      1. Central administration login
      2. Automated single sign on
      3. Central Administration logout
      4. contentACCESS Central Administration user interface
    2. contentWEB
      1. Logging in to contentWEB
      2. Automated single sign on
    3. Virtual drive
    4. contentACCESS Web Services (Proxy)
    5. Central login page
  4. contentACCESS Tools
    1. Installing Outlook forms
    2. Legacy email archive connectors
    3. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    4. Legacy archive connector for Email Lifecycle Manager (ELM)
    5. Installing TECH-ARROW’s WinShortcutter
  5. Tenants in contentACCESS
    1. How to create a new tenant
    2. Tenant limitations
    3. How to provide access to a tenant (adding new tenant administrators)
    4. Tenant administrator invitation types
  6. General system configurations
    1. Connection
    2. User interface
    3. Users in contentACCESS
    4. Invitations
    5. Roles
      1. Creating roles
      2. Role details
      3. Role assignment
      4. Defining specific permissions of a role assignment
      5. Editing roles, editing role assignments
      6. General use cases of how to create/assign roles
      7. Managing access to contentACCESS objects
    6. Login providers
      1. Login providers’ context menu options
      2. External login provider configuration
      3. Associating an enabled provider with a user login
      4. contentACCESS users in third party systems
    7. System
    8. Licensing
      1. How to activate your license key
    9. Notifications
    10. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    11. Distributed environment in contentACCESS — Clusters
    12. Statistics
    13. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
      1. Exchange performance settings – turning off the Exchange throttling policies
      2. Hybrid Exchange environments in the Email Archive system
    6. Importing contentACCESS configurations from files
      1. Manual import of Exchange servers/groups/mailboxes to the contentACCESS Address book
      2. Importing File Archive root folders to be archived
  8. Creating new jobs in contentACCESS
  9. Jobs’ page, jobs’ context menu
  10. File Archive
    1. Introduction to File system archive
    2. File Archive settings
    3. Databases
    4. System settings
    5. Retentions
    6. Storages
    7. Root folders
    8. Aliases
    9. Schedules
    10. Provisioning settings and managing access to contentWEB
    11. Configuring aliases
    12. Configuration of jobs available in contentACCESS File Archive
    13. Configuration of File system archive job
    14. Configuration of a File system restore job
    15. Configuration of File system recovery job
    16. Configuration of Remote shortcutting job
    17. Active/inactive documents in File system archive
  11. Email Archive
    1. Important settings before creating an Email Archive job
    2. Database settings
    3. System settings
    4. Provisioning settings
    5. Retention settings
    6. Shortcuts in email archiving
    7. Storing of archived emails
    8. Creating email archive schedulers
    9. User experience
    10. Exchange 2013+: Mail app in OWA 2013+ or on MS Outlook 2013+ desktop version
    11. Exchange 2010: OWA 2010 integration
    12. Address book objects
    13. Granting access rights for mailbox users and explicit users to view the mailbox archive
    14. Creating contentWEB users (option 1)
    15. Manage access to a mailbox archive (option 2)
    16. Database and store assignment in email archiving
    17. How to assign database and storage to an Exchange group?
    18. How to assign database and storage to a mailbox?
    19. How to move data from source database/storage into a second (target) database/storage?
    20. Creating Email archive jobs: archive, restore, recovery, mailbox move, shortcut synchronizaion, shortcut repair
    21. Email archive job
      1. Email archive job configuration
    22. Email restore job
      1. Email restore job configuration
    23. Email recovery job
      1. Email recovery job configuration
    24. Mailbox move job
      1. Mailbox move job configration
    25. Shortcut synchronization job
      1. Shortcut synchronization job configuration
    26. Shortcut repair job
      1. Shortcut repair job configuration
    27. Public folder archiving
      1. How to configure a job to archive public folders
      2. Public folders in the contentWEB archive
      3. User permissions to public folders
      4. Public Folder archiving in hybrid Exchange environments
  12. SharePoint archive plugin
    1. SharePoint Archive settings
    2. SharePoint Archive job configuration
    3. SharePoint recovery job configuration
    4. SharePoint Publishing job
    5. SharePoint in the contentWEB archive
  13. Custom plugins
    1. Email management job configuration
    2. Storage replication plugin
    3. Sharing plugin
    4. Datengut plugin
    5. Email synchronizer plugin
  14. officeGATE
  15. accessGATE Mobile
  16. Virtual drive configurations
  17. Application settings
  18. Terms of use
  19. FAQ

10.7.Root folders

The root folder paths to be applied in a file archive job is specified in this section. The root folder defines the start point (start point = e.g. “c:”) of the archive process. A root folder set here is selected for an archive job on the given job’s configuration page. The relative path (e.g. folder “Test files” if directory “c:Test files” will be archived) can be set in the given job’s configuration section further on.
The root folders and their settings are written to the file system database defined in section System settings above (File Archive ⇒ Settings ⇒ System settings). A connection that already exists in the system database cannot be specified twice. E.g. if \tanewsTECH-ARROW files to archive is already set, then \tanewsTECH-ARROW files to archivecontracts cannot be added to the root folder’s list. This feature prevents the users from archiving the same folder into two different databases/storages. If the user wants to add a root which already exists in the system database, he will be prompted about this.

Hint: When the root folders are defined, be careful to NOT add the SAME PHYSICAL PATH TWICE.
Example: “D:Share” which is shared as “\serverShare” can be added to the list of root folder twice, like this:

  • D:Share
  • or as a shared path:

  • \serverShare
  • These paths are pointing to the same physical directory. contentACCESS can’t detect such collision.
    This configuration might result in a not deterministic behavior: if both root folders are assigned to a different database or they are processed by different jobs, it is not possible to predict in which archive the files will be stored.

    A root folder always must have an assigned database and a storage. The job which archives (restores/recovers) this root will use this database and storage.

    Hint: It is not recommended to change the database and storage connections already associated with a root folder. Changing the database will lead to problems when trying to retrieve the already archived items, because some of your data will be saved in the originally set database, and another part of data in the newly set database. The same retrieve problem might occur with changing the storage, too. The application warns the user about it:

    cACCESS 2.9 doc 136
    However, the database and storage assigned to a root can be changed using the “Edit” menu item in the root context menu. Do not use this option unless it is very necessary.

    The root folders may be either

    1. imported using the “import” button (refer to chapter Importing File Archive root folders to be archived) or
    2. added to the list using the “new” button.

    Click “new” to manually add a root folder that should be processed by a job.

    cACCESS 2.9 doc 137
    The File Path dialog opens. Enter the file path that should be applied and the applicable user credentials. The File Archive database and storage must be associated with this specific root folder directly in this dialog. It is NOT recommended to change the database and storage that is already used, because it will lead to file retrieve problems (as mentioned in the hint above). Use the “Change” option only in case if such change is really necessary (e.g. if you haven’t archived the root yet).

    cACCESS 2.9 doc 138

    Note: We recommend to specify the parent folder (the start point of the archive process) in the File Path dialog. The relative folder path can be specified further on when configuring the respective job.

    Deleting a root:
    Already configured root folders can be deleted from the list using the root’s context menu. A deleted root is only hidden, but it still exists in the database. If the user wishes to add an already deleted root again, he will be prompted that it already exists in the database, and he will be able to restore it with the old settings only (with the originally assigned database and storage).

    Yes No Suggest edit
    Help Guide Powered by Documentor
    Suggest Edit