| Author |
Messages |
|
SuperUser
 
Posts:26
 |
| 03/22/2003 11:15 PM |
|
| I am attempting to replicate / backup and restore our production UMP to a test and development server with little success. Most content is coping over fine as long as I make a few SQL level changes in the Portal DB. But for some reason I lose the BPV and SLMO funtionality. Has anyone successfully restored the UMP to a different server? |
|
|
|
SuperUser
Posts:26
|
| 04/29/2003 9:45 AM |
|
We opened an issue with CA and the solution is a bit cumbersome to me... I think there should be an easier way to move from a test environment to a production environment without deleting the entire production database. This is the proposed solution:
Shutdown the Portal on the source server
Backup the PortalDB database on the source server
Backup the content directory of the source portal (i.e. x:\tnd\portal\content\repository)
Install the portal on the destination machine.
Import the PortalDB database on the destination database server
Copy the content directory from the source installation to the destination installation
Restore the repository into the destination database server
Update the destination repository to reflect the destination machine. The following SQL should be performed where name is the host name of the destination machine:
update portaldba.por_server set name = ''
At this time all your UMP documents will still have links to the old server. The easiest way is to run this SQL command
ISQL -Udatabase_user -Pdatabase_password
1> use DATABASE
2> update POR_DOCUMENT set FILENAME=replace(FILENAME,"http://OLDNAME:", "http://NEWNAME: ")
3> go
such as
ISQL -Usa -Pxxx
1> use PortalDB
2> update POR_DOCUMENT set FILENAME=replace(FILENAME,"http://LOCALHOST:8080 ", "http://MYHOST: 8080")
3> go
Now you need to teach Portal how to connect to the BPV repositories. Make sure that you point to the same global catalog as the original machine, so you have access to the same WV repositories. Go to BPV Publishing wizards and publish some information from each repository that you need access to. This will force Portal to ask for password and remember it.
As you can see, it's a little destructive to the production environment. Anybody have a better suggestion?
|
|
|
|
|