Note: This information only applies to Surround SCM 2008.1 and earlier.
You can move a Surround SCM database using a network connection, a Zip drive, or an FTP connection. If you are upgrading Surround SCM, you can update your database in the existing location or in the new location. You should wait to move the database until you are sure the upgrade is successful.
General Tips
As a precaution, make a backup copy of the database. Using the copy and paste method to move the database from one location to another should not impact your original database. See
Backing Up Surround SCM.
Before you begin moving the files, make sure the Surround SCM Server is not running. This ensures you get a clean copy of the database because it is not being written to when it is moved.
Surround SCM database files and license server database files can be difficult to find if they are not stored in the default location. Search for the SCMServDb and LicenseServDb directories to find the files. You can also search for the individual table file extensions (.SDB).
Moving All Databases
- Install Surround SCM and the Seapine License Server in the new location.
- In both locations, stop the Surround SCM server and the Seapine License Server.
- In the old location, copy the LicenseServDB directory and all sub-directories and paste them in the install directory in the new location. Following are the default install locations:
Windows: C:\Program Files\Seapine\License Server\LicenseServDb
Mac OS X: /Applications/Seapine License Server/LicenseServDb
Linux: /var/lib/splicsvr/LicenseServDb
Solaris: /opt/splicsvr/LicenseServDb
- In the old location, copy the SCMServDB directory and all sub-directories and paste them in the install directory in the new location. Following are the default install locations:
Windows: C:\Program Files\Seapine\SurroundSCM\SCMServDb
Mac OS X: /Applications/SurroundSCM/SCMServDb
Linux: /var/lib/SurroundSCM/SCMServDb
Solaris: /opt/SurroundSCM/SCMServDb
- Start the Seapine License Server in the new location.
- Start the Surround SCM Server in the new location.
Changing Operating Systems
The database file structure is the same on each operating system supported by Surround SCM. The Surround SCM server recognizes data from a Windows-based operating system the same as if it was on a Unix-based operating system. No special conversion is necessary.
Caveats
All the data files in the /var/lib/SurroundSCM (or otherwise specified) directory and all subdirectories must be owned by the root user. These data files have a .SDB extension. The Surround SCM data file naming convention is case sensitive and requires all upper case letters, for example SCMOPTNS.SDB. These files need read-write permissions in order to save data.
If your database files are being copied in lowercase, you may want to download the mix2caps.pl script, which is attached to this article. This script automatically changes the data file names and the file extensions to all uppercase. This Perl script was donated to us by M.S. Praveen of ControlNet, (I) Inc. and does not come with a warranty. It can be changed and modified to meet your needs.
Troubleshooting
|
|
|
|
Q.
|
After moving the Surround SCM server, I can no longer connect and I get an incompatible version error.
|
|
|
|
|
A.
|
The Surround SCM server is most likely running a different version than the Surround SCM client. You need to upgrade your client to the same version.
|
|
|
|
|
Q.
|
The Surround SCM Server is installed on a computer with a Unix-based operating system. I run the script to start the Surround SCM server and I get an [OK]. I cannot see the server running and I also cannot connect to it using any client.
|
|
|
|
|
A.
|
The Surround SCM script, surroundscm, that starts the service should be located in /etc/rc.d/init.d/surroundscm.
There are a few different ways to verify that the Unix Surround SCM server is running:
ps -ef |grep scmserver - Lists the Surround SCM process if it is running
ipcs |grep surroundscm - Indicates if a Surround SCM semaphore has been taken out
netstat -pan |grep 4900 - Indicates the server is listening for connections when the server is running. 4900 is the default Surround SCM Server port.
The surroundscm script may run and create a /var/lock/scmserver but not actually start the server. This is usually related to permissions. The surroundscm script must be owned and executed by root.
All of the following files and directories must be owned by the Surround SCM user. The following file and directory locations are the default locations. Your file and directory locations may be different depending on the options chosen during installation.
/var/lib/surroundscm/ - The directory and all its contents
/usr/bin/scmserver - Surround SCM Server binary
/var/log/SCMStartup.log - Server log where server messages and errors are stored
/etc/spscm.conf - Surround SCM Server file that contains configuration settings
Use the following command to run the surroundscm script in debug mode:
/etc/rc.d/init.d/surroundscm foreground
|
Search the Knowledgebase
Browse by Category
Print this page
Email this page
Post a comment
Subscribe me
Add to favorites
Remove Highlighting
Edit this Article
