Note: You must be a Windows Administrator to perform this solution.
Prerequisites: The original site must already be at DocuShare 7 Update 1 Patch 3 or higher.
Warning: DocuShare 7.5 and higher now uses SOLR as its search engine instead of IDOL. When moving to a new server running SOLR, you will be required to remove the old IDOL index queues and do a full dsindex of the new site. This process could take several hours or days depending on the size of your DocuShare site and its contents.
To migrate DocuShare 7 to a new DocuShare 8.0 Server:
1. Install DocuShare 8.0 on the new Windows server.
2. Do not start the new 8.0 Server, go to <dshhome>\config directory and remove the nebula file.
3. Start and license the new DocuShare 8.0 site.
Note: DocuShare Licensing can be reached at docushare.licenses@xerox.com. The licensing department will require the version of DocuShare installed on your server and the Host ID of the server. The DocuShare license key will need at least the same number of users as the server had that you will be restoring.
4. Once the new DocuShare 8.0 site is licensed, stop it.
5. Verify the Bucket Structures of the backed-up server and the new server match (If applicable)
Warning: This step is very important, please verify all the information below before proceeding with the backup and restore procedures.
A. To verify your bucket structure on the OLD DocuShare 7 server:
a. Open Windows Explorer
b. Navigate the folder structure into the <dshome>\config directory.
c. Open the ContentStore.xml file (in notepad or WordPad).
d. Look for an entry in the file called <NumberOfBuckets>512</NumberOfBuckets> it will have a value of 64 or 512, this is very important, make a note of this value.
B. To verify the newly installed DocuShare 8.0 server has the same bucket structure as the server that was backed up:
a. On the newly installed server, open Windows Explorer.
b. Navigate the folder structure into the <dshome>\config directory.
c. Open the ContentStore.properties file in a text editor such as Notepad.
d. Look for an entry in the file called NumberOfDirectories= edit this value to match the value found in step 4A. Then save the changes.
e. Open the ContentStore.xml in a text editor and look for the entry <NumberOfBuckets>512</NumberOfBuckets> edit this value to match the value that was on your old server. Then save the changes.
Warning: You must modify both the <dshome>\config\ContentStore.properties and the ContentStore.xml files to match the value that was on your old server.
6. Verify the Access Tracking Values on the Old and New Server match.
Warning: It is very important to check the data retention value matches the old server if you are moving to a new DocuShare server or install because if a customer changed the default value to a higher number of days or infinite days on the old server and does not make the appropriate changes on the new install, it will start purging the access data that is older than 365 days when DocuShare is first starting up on the new server. Also, in addition to deleting access tracking data (which may be critical for some customers), it may result in database transaction log to get full and bog down DocuShare.
A. To verify the access tracking value on the old server:
a. On the OLD DocuShare 7 Server, log into DocuShare as admin.
b. Click Admin Home | Site Management | Access Tracking. The Access Operation Tracking page displays.
c. Scroll to the bottom of the page, check the value in the field labeled Monitor Access Data and Access Data Retention.
Note: There is an internal timer that gets reset every time these values are changed. The data gets flushed from the Access_Table whenever those values are changed.
Note: The default value on a fresh install is 365 days.
Examples:
Changing the Access Data Rendition value to 180 days will flush the oldest data at the next check interval which is the value of the Monitor Access Data (default check time is every 1.6 minutes) leaving the desired 180 days’ worth of data.
B. To verify the newly installed DocuShare 8.0 server has the same access tracking value as the old server:
a. On the NEW DocuShare 8.0 Server, log into DocuShare as admin.
b. Click Admin Home | Site Management | Access Tracking. The Access Operation Tracking page displays.
c. Scroll to the bottom of the page, check the value in the field labeled Monitor Access Data and Access Data Retention.
d. Set the value to match the old server.
7. Restore a COPY of the OLD DocuShare 7 database to the NEW DocuShare 8.0 Server. This is the Database you connect to in DocuShare. For example, SQL Server.
Warning: Do not point your new server to the same database that your OLD DocuShare 7 Server is connected to. You should be pointing to a COPY of the database either on your existing Database Server or a New Database Server that is attached to a COPY of the old database.
8. From the Command Prompt in the <dshome>\bin directory, run dssetup on the new DocuShare 8.0 Server.
9. Change the database information to point to the restored COPY of the 7 database.
10. Download and install setupDB for DocuShare 8.0 on the new DocuShare 8.0 Server. (A readme file is included in the Collection with the installation instructions. You need to download the .bat or .sh then the .jar file). Available for download from https://docushare.xerox.com/doug/dsweb/View/Collection-19816
11. On the NEW DocuShare 8.0 Server, open a command prompt window (right-click and select Run as Administrator).
12. Change into the <dshome>\bin directory.
13. Type setupDB -v 08.00.00 and press Enter. This will upgrade the database to the DocuShare 8.0 version.
14. Once the command completes, restore the content store repository (documents directory).
Warning: When restoring the Content Store, do not overwrite or delete the guid.txt file.
15. Start DocuShare 8.0.
16. Remove the old IDOL queuenames not being used with SOLR:
Open a command prompt run as administrator in {dshome}\bin then run the commands
diagevent remove indexingQ
diagevent delete indexingQ
diagevent remove indexingQ2
diagevent delete indexingQ2
If any error is encountered when removing the queues from the commands above, then remove the queues in the database:
Stop DocuShare
Run the SQL query in the database:
DELETE FROM namedlisteners WHERE queuename='indexingQ' or queuename='indexingQ2';
DELETE FROM indexRecovery;
DELETE FROM eventTable;
DELETE FROM eventObjectTable;
Restart DocuShare
17. Index your site using the following command.
A. Open a Command Prompt window (make sure you right click and run as Administrator).
B. Change into the <dshome>\bin directory.
C. Type dsindextool index_all and press Enter.
Note: This process could take several hours or days depending on the size of your DocuShare site and its contents.