pdf_icon Download contentACCESS Manual as PDF

  1. Introduction to contentACCESS
    1. Services provided by contentACCESS
    2. Software requirements
  2. Installation of contentACCESS
  3. contentACCESS Tools
    1. Installing Virtual drive
    2. Installing the Proxy server (contentACCESSWS)
    3. Installing the Proxy web services
    4. Installing Outlook forms
    5. Legacy email archive connectors
    6. Legacy archive connector for Metalogix Archive Manager Exchange Edition (MAM EE)
    7. Legacy archive connector for Email Lifecycle Manager (ELM)
    8. Installing TECH-ARROW’s WinShortcutter
  4. contentACCESS Central Administration
    1. Central administration login
    2. contentACCESS Central Administration user interface
  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 — role types, creating new users, adding user logins
    4. How to activate your license key
    5. How to create user logins to an already existing user?
    6. System administrators
    7. Login providers
    8. System
    9. Licensing
    10. Notifications
    11. Monitoring — how to find out possible misconfigurations / reasons of potential system/job failures
    12. Distributed environment in contentACCESS — Clusters
    13. Statistics
    14. How to create/configure databases — All databases
  7. Common features
    1. Databases
    2. Schedules
    3. Retentions
    4. Storages
    5. Exchange connections
    6. Importing contentACCESS configurations from files
  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. File archive Databases
    4. File archive System settings
    5. File archive Retentions
    6. File archive Storages
    7. Root folders
    8. Aliases
    9. File archive 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. Email archive 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. How the end user should log in to contentWEB (archive) over Internet?
    17. Database and store assignment in email archiving
    18. How to assign database and storage to an Exchange group?
    19. How to assign database and storage to a mailbox?
    20. How to move data from source database/storage into a second (target) database/storage?
    21. Creating Email archive jobs: archive, restore, recovery, mailbox move
    22. Email archive job
    23. Email restore job
    24. Email recovery job
    25. Mailbox move job
  12. Custom plugins
  13. Email management job configuration
  14. SharePoint archive plugin
  15. Storage replication plugin
  16. Sharing plugin
  17. Datengut plugin
  18. Email synchronizer plugin
  19. contentWEB
  20. officeGATE
  21. accessGATE Mobile
  22. Virtual drive
  23. Terms of use
  24. FAQ

10.17.Active/inactive documents in File system archive

Definition of terms: file = file on the file system; item = archived file in the archive



To avoid displaying duplicate items in the archive the user has got the choice to filter between active and inactive items in the contentACCESS archive (contentWEB). A duplicated item is created, when a file is processed multiple times and is saved into the archive multiple times. A typical use case might be, when a user copies a file from one source folder to a target folder in his file system, then deletes the file from the source folder. Let’s assume, that the archive job meanwhile caught and processed both files (created duplicates in the archive). In such cases, the files processed in the source and target folder need to be differentiated from each other in the archive. The file archived from the source location will be inactive in the archive (the file in the source location is not available on the user’s side, the user deleted it); the file archived from the target location will be active in the archive (the file in the target location is available for the user). The contentWEB active/inactive filter makes it easy to display the actual (last touched) files in the archive.

When is an item/folder inactive in the archive? An item/folder gets an inactive status in the archive, if the file/folder no longer exists in the file system (neither the original, nor the shortcut to it). Once the item is touched (e.g. versions were created, it was restored by a job, or recovered), its status will turn to active.

When an archive job is running, it is synchronizing the current state of the archive with the state of the file system. The following tables will give an overview to a user, when an item is active/inactive in the archive. The light blue cells contain the files/folders that are found by an archive/restore/recovery job in the file system (on the user’s side), the grey cells inform the reader about the action that the job performs when it finds this particular file/folder.


Archive with shortcutting method

File system (user’s side)
Is item in archive in the same location?
A) Shortcut was found by the archive job YES: the job does not touch the shortcut. The item will be ACTIVE. NO: the job will duplicate the item to the new location. The shortcut will be updated with a new ID. The new item will be ACTIVE (the old item is not touched).
B) File was found by the archive job
Is item in the archive?
YES: If the file was changed, a new version will be created in the archive, and the file will be converted to shortcut. The item will be ACTIVE in the archive. NO: The file will be archived and the file will be converted to shortcut; the item will be ACTIVE in the archive.
C) No shortcut, no file was found by the archive job YES: the item will be INACTIVE in the archive. NO: no action will be performed by the job
D) Folder no longer exists
Is folder in the archive?
YES: folders will be INACTIVE (recursively); items will be INACTIVE
E) Folder exists
Is folder in the archive?
YES: permissions will be actualizes and the folder will be set to ACTIVE NO: it will be archived and will be set to ACTIVE



Archive with the “Keep original” method

File system (user’s side)
Is item in archive in the same location?
A) Shortcut was found by the archive job YES: the job does not touch the shortcut. The item will be ACTIVE. NO: the job will duplicate the item to the new location. The shortcut will be updated with a new ID. The new item will be ACTIVE (the old item is not touched).
B) File was found by the archive job
Is item in the archive?
YES: If the file was changed, a new version will be created in the archive, and the file will be kept in the file system. The item will be ACTIVE in the archive. NO: The file will be archived and the original will be kept; the item will be ACTIVE in the archive.
C) No shortcut, no file was found by the archive job YES: the item will be INACTIVE in the archive. NO: no action will be performed by the job.
D) Folder no longer exists
Is folder in the archive?
YES: folders will be set to INACTIVE(recursively); items will be set to INACTIVE.
E) Folder exists
Is folder in the archive?
YES: permissions will be actualized and the folder will be set to ACTIVE, NO: it will be archived and will be set to ACTIVE.



Archive with the “Delete original” method

File system (user’s side)
Is item in archive in the same location?
A) Shortcut was found by the archive job YES: the job does not touch the shortcut. The item will be ACTIVE NO: the job will duplicate the item to the new location. The shortcut will be updated with a new ID. The new item will be ACTIVE (the old item is not touched).
B) File was found by the archive job
Is item in the archive?
YES: If the file was changed, a new version will be created in the archive, and the file will be deleted from the file system. The item will be INACTIVE in the archive. NO: The file will be archived and the original will be deleted; the item will be INACTIVE in the archive.
C) No shortcut, no file was found by the archive job YES: the item will be INACTIVE in the archive. NO: no action will be performed by the job.
D) Folder no longer exists
Is folder in the archive?
YES: folders will be set to INACTIVE(recursively); items will be set to INACTIVE.
E) Folder exists
Is folder in the archive?
YES: permissions will be actualized and the folder will be set to ACTIVE. NO: it will be archived and will be set to ACTIVE.


Note: The user may browse for his archived items either in contentWEB, or on Virtual drive. By default, Virtual drive displays the active items only, but this is configurable from the Virtual drive’s configuration page (System ⇒ Client applications ⇒ Virtual drive configuration).



Automatic restore from shortcut

File system (user’s side) Action performed by the restore job
A) Shortcut found The job restores the original into the file system location; the item in the archive will be set to ACTIVE.
B) No shortcut found No action.



Automatic recovery

File system (user’s side) Action performed by the recovery job
A) File found No action, file will be skipped.
B) Shortcut found No action, shortcut will be skipped.
C) Nothing found C/1) If the job configuration requires to recover original: the original will be created in the file system; the item will be ACTIVE in the archive.
C/2) If the job configuration requires to recover shortcut; the shortcut will be created in the file system; the item will be ACTIVE in the archive.



Manual recovery from contentWEB

File system (user’s side) Action performed by the manual recovery
D) File found No action, file will not touched, it will be skipped. The item will be ACTIVE in the archive.
E) Shortcut found Shortcut will be replaced by the original file in the file system; it will be ACTIVE in the archive.
F) Nothing found New file will be created in the file system; the item in the archive will be ACTIVE.



Other use cases:
 The shortcut is deleted from file system: during the archive process nothing happens in the archive, the items change to INACTIVE if they were active before.

 The shortcut is moved: the item is duplicated to the new location. The new item is ACTIVE. The old item will be INACTIVE if there is no file or shortcut at the old location.

Yes No Suggest edit
Help Guide Powered by Documentor
Suggest Edit