This article describes how to move required files to new repository which resides to a different Site and make the files not available between these Sites.  

Background

XXXXXXX(If applicable, provide any other information the user needs before starting the steps; otherwise, delete this section.)XXXXXXX

Steps to Accomplish

Option 1

1. In “eB System Management Console” (SMC), under your community create new Repository Group with a new repository located in it.
2. Now connect to eB WEB or Director and do a search on documents, you would like files to be copied to new repository and add these documents to basket (before doing this please clear all documents from basket and don’t add large amount of files as Basket might come up with Time out error when opening it)

3. Go to Basket, select all Documents and using “Bulk Update” action move files to new repository group (in this example REP). By doing this all files will be copied to new location and they will be in new repository group.

   Note: Delete content of the basket only after step 10.

4.  On your App server create new Site.

5. Add your Community in Storage Server and add this server in to a New site. In this example community is “TESTREP” and new server is DUBEBDEV3, and in New repository group  point/link Client (using fast connection) to DUBEBDEV3 server.

6. Create new repository in your Storage Server. This repository must
   belong to new Repository Group and should be located on new Site. (If you have
   added Storage server to new site before creating repository you won’t get Site
   Select Module)

7. Replicate files between repositories which are allocated to new repository group (REP). As shown in screenshot below, files from REP repository will be copied to DEV3 repository (which is located on Storage Server)

8. After files being replicated from your App server to your Storage server, you can delete repository which is located on App server  (in example case it’s REP repository) and delete it from devices.
   
   8.1.After taking all these steps you can delete connections between Client and opposite Sites. At this point you will have two sites with different repositories (containing different files) on each site. The problem is that these repositories will belong to different Repositories groups, that means that you will have to use Document templates configured to upload files to New Site. Otherwise system will upload files to Repository Group which is set as default one. Example: if default is set to MAIN then connected to NEW repository you won’t be able to upload file without using Template set to use New repository group. You can fix this “issue” joining these communities.
   
   

   Please follow steps below how to combine Repository Groups.

9. In Storage Server create Repository which would be in New Site and would belong to your Original/Old (in example case it’s MAIN) Repository group.

10. Same as in step 3 go to Basket, select all Documents and using Bulk Update action move files to Old repository group (in this example MAIN) (WARNING – links between sites should be deleted  or set in slow mode - step 8.1). By doing this all files will be copied to new repository located on New Site but belongs to
    old Repository Group.  By doing this you won’t have to use Document templates with default repository set in i - files will be uploaded depending on Site you connect to.

11. Delete Repository Group created in STEP 1  (Rep Group) and repository created in STEP 6 (Repository which is on new site but belongs to new Repository Group)