jj_in_atlanta
Tue Apr 24 15:46:01 CDT 2007
Thanks for the advice. I was able to move my sites in dev, although it was a
lot harder than I though it should be.
You can't restore the Site configuration database, so I lose data like any
quota's I've defined, AntiVirus settings, mail, Usage analysis settings. Not
a big dea, but worth noting.
Doing the site restores was also a bit of a pain and took lots of attempts
before I figured out a method. Many times I got an error "
http://test1 is
already routed to the Default zone of another application. Remove that
mapping or use a different URL."
so I had to delete the mapping and try again.
I was also unable to restore more than one web application. the second
restore would fail with an error:
"The IIS Web Site you have selected is in use by SharePoint. You must
select another port or hostname."
I read a mskb article about this, but their workaround didn't work for me.
I wound up manually creating the 2nd top-level web application, then doing a
SharePoint restore of only the content database for that web app. Then I had
to add that database to the web application and delete the original content
database.
Of course, doing a db-only restore through the sharepoint admin interface
always ended with an error
"Cannot attach database to Web application. Use the command line tool or
Central Administration pages to attach the database manually to the proper
Web Application."
Even though the database was properly restored, and that was all I asked to
be restored. So then I had to delete the timer job definition.
Far too much work, but I've got a procedure now that I can apply in
production for when we move those databases.
"vincentw56" wrote:
> I tried to do that originally and it would not work for me. I had to do it
> the other way which was much faster that doing it through the back up. The
> restore would go to the end and then fail. So everytime I tried, it would
> take 45 minutes to restore and then just fail. It should work both ways, but
> if the backup/restore method doesn't work, you can do it the way I did it.
> --
> Vincent Wright
>
>
> "Etienne Legendre" wrote:
>
> > Hello
> >
> > do a backup with stsadm -o backup ..... command line.
> > Install from scratch you new WSS (will recreate the Central Admin web and
> > databases, that's the problem) on your new SQL Server 2005
> > Create a site collections (choose the template you want, it will be
> > destroyed)
> > restore with stsadm - o restore .... -overwrite
> >
> > And it is done
> >
> > EtienneL
> >
> >
> > "jj_in_atlanta" <jj_in_atlanta@community.nospam> a écrit dans le message de
> > news:29DE08DA-6B55-47CB-BF3A-D11B8E03D0C1@microsoft.com...
> > >I need to know the same thing.
> > > We have setup our WSS 3.0 farm on one SQL2005 server, but we will have to
> > > move it to another SQL2005 server in the near future.
> > >
> > > I'd like to move all the databases: configuration, search, and content and
> > > then point the farm to the new SQL server but I can't find any any info on
> > > doing that.
> > > I can get our DBAs to move the databases - but then how to tell WSS where
> > > to
> > > find them?
> > >
> > > Will I have to backup the individual sites, destroy the existing farm,
> > > then
> > > create a new farm on the new db server and restore the individual sites?
> > >
> > > Thanks
> > >
> >
> >