Moving SOS Collab to another machine

A collection of information about Collab, including solutions to common problems.

Moderator: SourceGear


Posts: 9736
Joined: Tue Dec 16, 2003 1:25 pm
Location: SourceGear
PostPosted: Thu Feb 26, 2004 1:34 pm
Moving an SOS Collab 1.1 installation to another machine requires an exact set of steps be followed. Let’s say you currently have a SOS Collab server on machine A, and you want to have an SOS Collab server on machine B.

1. Make sure Microsoft SQL and VSS are already installed on machine B.

2. Install SOS Collab 1.1 on machine B. When prompted to enter a path for attachments, enter a path that exactly matches the path to attachments on machine A. (This path can be seen by launching the SOS Collab server manager).

3. On machine A, Backup the ggdata database from with SQL Enterprise Manager. Exact steps to do this are listed below. These steps must be followed so that SourceOffSite Collab attachments will be backed up as well.

4. Remove the “ggdata” database from machine B. This can be done by launching osql from the command prompt, and typing “DROP DATABASE ggdata;” This can also be done from the SQL Enterprise manager. Please note: make sure you are doing this on the machine B, the machine you are moving data to, not machine A, the machine you are moving data from.

5. On Machine B, stop the SOS Collab Primary server and SOS Collab Web servers. This can be done from within the services control panel.

6. On Machine B, restore the ggdata database backed up in step 3. Please follow the directions included with the document so that the attachments are restored as well.

7. From within the Enterprise manager, choose "Console Root -> SQL Servers -> SQL Server Group -> [Machine B] -> Databases -> ggdata -> Users", right-click on gguser and delete.

8. From within the Enterprise manager, choose "Console Root -> SQL Servers -> SQL Server Group -> [Machine B] -> Security -> Logins", right-click on gguser and delete. Then recreate the gguser login, using the password you selected for the SOS Collab Admin when you installed SOS Collab on machine B. Then select "Properties". Go to the "Database Access" Tab. In the top area, check the checkbox next to "ggdata". Now in the bottom area, check the checkbox next for "db_owner".

9. From the control panel, start the SOS Collab Primary and SOS Collab Web services.

At that point, all data should be moved accordingly. Let me know if you encounter any difficulties.


Backing up SOS Collab Data
The Microsoft Data Engine (MSDE) and MS SQL Server have a command tool that can be used to back up and restore the SOS Collab database.

(Please note: The SOS Collab Servers directory does not contain any project data. All information is stored in the SQL database, which is in your SQL installation folder.)

The SOS Collab database consists of the 'ggdata' database and file attachments.
· Backing up the 'ggdata' database to a location to disk
· Backing up the file attachments
· Restoring SourceOffsite Collab Data and File Attachments
· Additional Information

(Please Note: This procedure does not back up the Visual SourceSafe database.)

Backing up the 'ggdata' database to a location to disk
The SQL database can be backed up using the osql utility that ships with MSDE and MS SQL Server. The username and password used with the osql utility should be the username 'sa' and the 'sa' password. Note that osql commands are case sensitive.

1. From a command prompt, launch the osql.exe using the following command:
osql -Usa -P<sa_password>

2. Type the following commands at the prompts. Note that the path to the backup location should be surrounded by single quotes.

1> BACKUP DATABASE ggdata TO DISK = '<file_path>'
(enter)
2> GO
(enter)

The file_path should be the full path to an existing folder. The path to the backup location on disk should include the name of the backup file with a '.dat' extension. An example backup file path would be 'c:\backups\ggdata.dat'.

Backing up the file attachments
Copy the 'attach' folder to a backup location. The 'attach' folder is located in the SourceOffSite Collab Servers directory (SourceOffSite Collab Servers\Data\Attach). The default location for this folder is:
c:\Program Files\Sourceoffsite Collab Servers\Data\Attach.


Restoring SourceOffsite Collab Data and File Attachments

To restore the SourceOffSite Collab installation, you must restore the 'ggdata' database, and the file attachments.
Restoring the 'ggdata' database to a location from disk

1. From a command prompt, launch the osql.exe using the following command:
osql -Usa -P<sa_password>
2. Type the following commands at the prompts. Note that the path to the backup location should be surrounded by single quotes.

1> RESTORE DATABASE ggdata FROM DISK = '<file_path>'
(enter)
2> GO
(enter)

The file_path should be the full path to the backup folder. The path to the backup location should include the name of the backup file which will have a '.dat' extension.

Note: If restoring the SQL database to a different machine, the steps above are correct if the two SQL installations exist in the same path on both machines. If one is in a different path, use this alternate command to restore the database:

RESTORE DATABASE ggdata FROM DISK='<file_path>' WITH MOVE 'ggdata' TO '<data_path>\ggdata.mdf', MOVE 'ggdata_log' TO '<data_path>\ggdata_log.LDF'

Where <data_path> is the path to a folder called "data" that should exist somewhere within the SQL installation folder.

Restoring the file attachments
Copy the 'attach' folder from the backup location to the SourceOffSite Collab Servers\Data (SourceOffSite Collab Servers\Data\Attach) directory.

Additional Information
Additional information on using the osql.exe utility to back up and restore a Microsoft Data Engine Database including backing up and restoring the database to and from TAPE can be found at the following URL:
http://msdn.microsoft.com/library/defau ... 75t2_6.asp
Linda Bauer
SourceGear
Technical Support Manager

Return to Knowledge Base (Collab)

Who is online

Users browsing this forum: No registered users and 2 guests

cron