Re: Copying WSS to another Server

We maintain a replica of our production environment for testing. To keep
the data in sync I back the SQL databases up and restore them to the replica
envvironment. It already has WSS installed. Once the SQL databases are
restored, and visible in SQL I add them to WSS from Central Admin. Go to
your virtual server settings and manage Content Databases. To get the data
in your restored DBs to show up in WSS, simply add the Content Databases to
WSS. After the DBS are finished being added you'll be able to browse the
sites you restored.

tk
"Richard" <anonymous@xxxxxxxxxxxxx> wrote in message
news:ec9339zRFHA.3288@xxxxxxxxxxxxxxxxxxxxxxx
> Hi,
>
> I have a client who wants to take a copy of an existing WSS configuration
> on one server and copy it to another for dev/test purposes, using SQL
> Server database backup/restore tools.
>
> I have previously been referred to two resources, one describing the use
> of FrontPage 2003 packages (which is not an option for my client), the
> other describes using SQL server. The link is
> http://www.microsoft.com/resources/documentation/wss/2/all/adminguide/en-us/stsf10.mspx
>
> When following the instructions for restoring WSS from a SQL backup, the
> procedure is written as if WSS does not
> already exist on the destination server. It takes you through the steps
> for extending the virtual server, creating a content database, etc. As I
> have said, my client already has an existing WSS configuration, but if new
> items are added on the production server, they need to take a copy for the
> dev/test server so that the two environments are always "in sync". But the
> minute I attach the restored configuration database from the production
> server to the dev server, WSS thinks it is part of a multi-server setup,
> and
> I cannot remove the production server from the web server list. This is in
> version 6.0.2.6411 (WSS + SP1 + security update)."
>
> Have I misunderstood the instructions, or is do I have to tell my client
> to completely remove WSS from the dev server before they attempt a restore
> of the database?
>
> Please clarify, or point me in the direction of some better instructions.
>
> Thanks,
>
> James
>
>


.

Relevant Pages

  • Re: Copying WSS to another Server
    ... I do not restore the Config databases, ... It already has WSS installed. ... Go to your virtual server settings and manage Content Databases. ...
    (microsoft.public.sharepoint.windowsservices)
  • Database restore, both from same and different server
    ... Production WSS is working, but a web part has a memory leak. ... production to a development server. ... I've had all kinds of problems trying to restore this ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: AS2005 ... what is wrong with it?
    ... What I have seen is that the dev server is *faster* than the prod server ... And does your dev server also have all 6 databases with all these roles? ... When I restore the "PROV" i got approx 20 sec. ... Starting from an empty data folder should show if this theory is true ...
    (microsoft.public.sqlserver.olap)
  • Re: AS2005 ... what is wrong with it?
    ... I have 6 OLAP databases on the server. ... When I restore the "PROV" i got approx 20 sec. ...
    (microsoft.public.sqlserver.olap)
  • Re: Restoring databases files on a brand new server
    ... When I've restored WSS to a different server I installed WSS and all the ... then restored ONLY the Content DBs. ... > We want to restore the Content DB and Config DB to WSSNew server. ...
    (microsoft.public.sharepoint.windowsservices)
Loading