AvePoint Knowledge Base Limitations for DocAve 6 Products If DocAve Agent Account has the SharePoint_Shell_Access Role

Limitations for DocAve 6 Products If DocAve Agent Account has the SharePoint_Shell_Access Role

Search and filter

KB Article ID: 13282

Product: DocAve 6 Suite
Product Version: 6.8.0.0
SharePoint Version: 2013,2013 SP1

Details:

The DocAve 6 Agent account must have the database role of SharePoint_Shell_Access for SharePoint 2013 Content Databases.

*Note: The SharePoint_Shell_Access role can only be assigned via SharePoint 2013 Management Shell. For instructions on how to assign this role to a user, refer to the following Microsoft technical article: https://technet.microsoft.com/en-us/library/ff607596.aspx.

When the DocAve Agent account has this role for Content Databases, some DocAve 6 modules have several limitations. The following table details those limitations. 

AvePoint recommends that you assign the db_owner role of Content Databases to the DocAve Agent account. When using the db_owner role, DocAve 6 does not experience these limitations.​

 

​Module​ ​​Limitations

Granular Backup and Restore

Content Manager

Deployment Manager

Replicator

Archiver

SharePoint Migration

​ ​ ​ ​ ​ ​ ​

 ​Cannot keep the following properties of lists or libraries:

  • Created By
  • Modified By
  • Created Time
  • Modified Time
    		•
    ​Cannot keep workflow instances and the related column values.
    ​Cannot keep the following properties of workflow association:

  • Name
  • Author
  • Configuration
  • Created Time
  • Modified Time
  • The name of the column that displays workflow status
    		•
    ​Cannot keep the comment for checking in a checked-out version.
    ​If a library has the
    Require documents to be checked out before they can be edited option enabled, the user who performed actions on the first document version will be restored as the DocAve Agent account user.

    When​ DocAve performs a backup, the Web part source content is backed up after the backup of ​all pages has finished; therefore, the history versions of the page do not contain the Web part.

    ​Circumstance:

  • A page contains a Web part.
  • The Web part content is retrieved from another object within the same scope, for example, a document library within the same site collection.
  • The page has multiple versions.
    		•

    ​When DocAve performs the backup, the source data of the Lookup column is backed up after the backup of all pages is finished. Therefore, in the history versions of the page, the Lookup column values are empty.

    Circums​tance:

  • A page contains a column with the type of Lookup.
  • The Lookup column values are retrieved from another object within the same scope, for example, the column of a library within the same site.
  • ​The page has multiple versions.
    		•
    Granular Backup and Restore ​Do not support restoring history versions only.
    ​Do not support site collection level restore job.

    Content Manager

    Deployment Manager

    Replicator

    		 ​Cannot keep the TP_GUID of ghosted page and survey.
    ​Do not support site collection level rollback job.
    ​Cannot keep the following properties of hidden files and hidden folders:

  • Created By
  • Modified By
  • Create​d Time
  • Modified Time
    		•
    Administrator ​Do not support moving a site collection to a different content database.
    ​Do not support deleting orphan sites.
    Deployment Manager ​Do not support Managed Metadata Service rollback job.
    All Modules that Need to Back up and Restore SharePoint Content ​If SharePoint content databases have RBS configured, you must manually assign the
    db_rbs_admin database role to the DocAve Agent account.

    When you assign the
    SharePoint_Shell_Access role to the DocAve Agent account via SharePoint 2013 Management Shell, the
    db_rbs_admin role cannot be assigned to the DocAve Agent account automatically.

    Without the
    db_rbs_admin role, there will be errors during the backup and restore processes.