Re: Restoring databases files on a brand new server

Tech-Archive recommends: Speed Up your PC by fixing your registry

From: Todd Klindt (usenet_at_klindt.org)
Date: 02/11/05


Date: Fri, 11 Feb 2005 15:26:20 -0600

When I've restored WSS to a different server I installed WSS and all the
patches on the new server, then restored ONLY the Content DBs. Add them in
Central Admin and the sites in them will be added to WSS. You'll have to
manually reproduce your settings. And remember to add your managed pathes.

tk
"AT Sys" <paklaw99@hotmail.com> wrote in message
news:ug197HHEFHA.1296@TK2MSFTNGP10.phx.gbl...
>I have a similar scenarios as the following:
>
> We are preparing a Disaster Recovery Procedures for our WSS.
>
> Quesiont:
>
> We set up a separated WSS server (named WSSNew)with SQL 2000 SP3
> installed.
> We want to restore the Content DB and Config DB to WSSNew server.
> However,
> after attached the Config and Content DB, they are still poining to the
> original WSS server.
>
> Is this possible to restore WSS DBs (Content and Config) into a separated
> server?
>
> Thanks
>
>
>
> "Alessandro Tiberti" <alessandro@remove.tiberti.it> wrote in message
> news:e3DbSiAEFHA.3348@TK2MSFTNGP10.phx.gbl...
>> thanks everyone. my situation was a little bit more complex and I was
>> able
>> to face it on the local microsoft.public.it.sharepoint NG with the help
>> of
>> an italian MVP.
>>
>> Just to le t you know, the bigger problem was with restoring permissions
> in
>> the database as the machine I was trying to restore to was a brand new.
>> So
> I
>> had to follow what was explained in this article
>> http://support.microsoft.com/kb/828815 and reboot the machine (after
>> doing
>> what is written in the article remove the causes but still return a
> "service
>> unavailable error unless the system or services are restarted).
>>
>> thank you everyone for your support!
>> Alessandro
>>
>> "Todd Klindt" <usenet@klindt.org> ha scritto nel messaggio
>> news:OO5nvEhDFHA.3840@tk2msftngp13.phx.gbl...
>> > I've done this a few times had pretty good luck. here's a _rough_
>> > breakdown of what I did.
>> >
>> > 1) Install WSS on destination server.
>> > 2) Put in managed pathes to match the managed pathes on the source
> server.
>> > 3) Restore CONTENT databases only. Using an method should work.
>> > 4) Add restored Content DBs to WSS from Central Admin. Sharepoint will
>> > grab the list of sites out of the content DB you are importing them and
>> > they should be good to go.
>> > 5) Reindex Full Text Catalogs.
>> >
>> > Hope that helps,
>> > tk
>> > "Jim Buyens" <news@interlacken.com> wrote in message
>> > news:09C9BB37-1BC0-4A45-9C8F-E685D2449790@microsoft.com...
>> >> Did you open the restored content database in SQL Enterprise Manager
> and
>> >> grant the Security Administrators and Database Creators roles to the
> new
>> >> application pool account?
>> >>
>> >> Jim Buyens
>> >> Microsoft MVP
>> >> http://www.interlacken.com
>> >> Author of:
>> >> *----------------------------------------------------
>> >> |\---------------------------------------------------
>> >> || Microsoft Windows SharePoint Services Inside Out
>> >> || Microsoft Office FrontPage 2003 Inside Out
>> >> ||---------------------------------------------------
>> >> || Web Database Development Step by Step .NET Edition
>> >> || Microsoft FrontPage Version 2002 Inside Out
>> >> || Faster Smarter Beginning Programming
>> >> || (All from Microsoft Press)
>> >> |/---------------------------------------------------
>> >> *----------------------------------------------------
>> >>
>> >>
>> >>
>> >> "Alessandro Tiberti" wrote:
>> >>
>> >>> dear all,
>> >>>
>> >>> I've got a problem I'm unable to get out from even after reading many
>> >>> docs... I backed up the two SQL 2000 databases of my WSS installation
> as
>> >>> I
>> >>> read that this was the best way to preserve everything. Now I'm
>> >>> unable
>> >>> to
>> >>> restore them. I was able, after some days of work, to understand how
> to
>> >>> connect the config db and the content db.
>> >>> the content db is correctly connect as I can see from the sharepoiont
>> >>> central administration interface but if I try to browse my
> pre-existing
>> >>> site
>> >>> I get a
>> >>>
>> >>> "Impossibile completare l'operazione.
>> >>>
>> >>> Riprovare."
>> >>>
>> >>> that means "Unable to complete the operation. Please Try again". no
>> >>> error
>> >>> codes, nothing I can look for... nothing in the event viewer. I'm in
> the
>> >>> urgency of accessing some files that were stored in this site, can
>> >>> someone
>> >>> please help?
>> >>>
>> >>> I can give you every missing information if you ask for ;)
>> >>>
>> >>> greetings and thanks a lot!
>> >>> Alessandro
>> >>>
>> >>> PS: I didn't find anything similar even searching with google, I hope
>> >>> not te
>> >>> come out with a FAQ ;)
>> >>>
>> >>>
>> >>>
>> >
>> >
>>
>>
>
>



Relevant Pages

  • 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)
  • Restore WSS sites after disaster
    ... I lost the system disk of a server with a couple of WSS ... The database files files were located on a different disk. ... It seems that in order to restore a WSS site (with stsadm -o restore etc. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: WSS v3 migration
    ... I blew away that restore and am doing it again to try and see ... is create a backup using stsadm, then delete the site and re-create it using ... Does NTBACKUP on SBS server back up WSS at this level or do you need to ...
    (microsoft.public.windows.server.sbs)
  • Re: Moving all DBs to new machine with same name
    ... These are 2 separate machines, but which have the same exact version of SQL ... I know what is involved with renaming a server. ... I won't be renaming the server with any of these DBs I am moving attached. ... > You don't need new databases, they will be created during restore. ...
    (microsoft.public.sqlserver.server)
  • Re: Copying WSS to another Server
    ... the data in sync I back the SQL databases up and restore them to the replica ... It already has WSS installed. ... > on one server and copy it to another for dev/test purposes, ...
    (microsoft.public.sharepoint.windowsservices)