SBS 2003 - Move companyweb from one server to another

Hi

I could really do with some help on this one...

We currently have our companies intranet running in Sharepoint on our SBS
2003 server (companyweb)

I need to backup the whole of companyweb and move/restore it to a new SBS
2003 installation located on a different server in a new domain..

I've looked around the web for info, but I'm getting very lost in the
suggested ways of doing it...., especially if you are restoring it to a new
server with a different name/domain....

I don't know a lot about Sharepoint so we need to keep this simple.... I was
wondering if there are any tools etc to do the job....?, or a dead simple
"bullet proof" way of doing it...?

Any help is very much appreciated

Merv
Sun Jun 29 08:36:05 PDT 2008

Should be some help here Colin...

Swinging Your Companyweb
http://msmvps.com/blogs/cgross/archive/2006/06/06/99955.aspx

--
Merv Porter [SBS-MVP]
============================

"Colin A" <noreply@thisaddress.com> wrote in message
news:OgSBHyf2IHA.4672@TK2MSFTNGP04.phx.gbl...
> Hi
>
> I could really do with some help on this one...
>
> We currently have our companies intranet running in Sharepoint on our SBS
> 2003 server (companyweb)
>
> I need to backup the whole of companyweb and move/restore it to a new SBS
> 2003 installation located on a different server in a new domain..
>
> I've looked around the web for info, but I'm getting very lost in the
> suggested ways of doing it...., especially if you are restoring it to a
> new
> server with a different name/domain....
>
> I don't know a lot about Sharepoint so we need to keep this simple.... I
> was
> wondering if there are any tools etc to do the job....?, or a dead simple
> "bullet proof" way of doing it...?
>
> Any help is very much appreciated
>

Colin
Sun Jun 29 10:10:26 PDT 2008

Hi thanks for your help....

I found that article today just after I put up the post...

I've done it to the letter, and it has caused me a heep of problems...

1. I followed the steps listed prior to a restore with smigrate to the
letter and I lost the companyweb complteley... My only option was to
re-install Sharepoint..., all I can think is I must have done something
wrong... (empty, brand new server, never been used, just built it...)

2. I've now got Sharepoint back to it's default state (add and remove
programes, KB829114), it's on a brand new, un-used server, and working...

3. Using smigrate to restore the compayweb, I ran into more problems....

It's says
"manifest xml is invalid: premature end of file"
Error: 589913

I've no idea what this means and I can't seem to find any thing about
it.....?

Any help would be appreciated....

Merv
Sun Jun 29 10:58:17 PDT 2008

Is this a WSS 3.0 site that you're moving to the new server?

Moving a WSS 3.0 site to a new farm
http://msmvps.com/blogs/cgross/archive/2007/05/09/moving-a-wss-3-0-site-to-a-new-farm.aspx

--
Merv Porter [SBS-MVP]
============================

"Colin A" <noreply@thisaddress.com> wrote in message
news:el22Gsg2IHA.2188@TK2MSFTNGP04.phx.gbl...
> Hi thanks for your help....
>
> I found that article today just after I put up the post...
>
> I've done it to the letter, and it has caused me a heep of problems...
>
> 1. I followed the steps listed prior to a restore with smigrate to the
> letter and I lost the companyweb complteley... My only option was to
> re-install Sharepoint..., all I can think is I must have done something
> wrong... (empty, brand new server, never been used, just built it...)
>
> 2. I've now got Sharepoint back to it's default state (add and remove
> programes, KB829114), it's on a brand new, un-used server, and working...
>
> 3. Using smigrate to restore the compayweb, I ran into more problems....
>
> It's says
> "manifest xml is invalid: premature end of file"
> Error: 589913
>
> I've no idea what this means and I can't seem to find any thing about
> it.....?
>
> Any help would be appreciated....
>

Colin
Sun Jun 29 11:07:08 PDT 2008

Hi Merv

No, it was a WSS 2.0 to a WSS 2.0...., patched to SP3 on both... :-?

Col

Colin
Sun Jun 29 12:57:10 PDT 2008

Don't suppose you know where I could find out what the smigrate error
message means...?

Col

Merv
Sun Jun 29 13:56:04 PDT 2008

I've been looking but I can't find anything. I'll keep trying.

--
Merv Porter [SBS-MVP]
============================

"Colin A" <noreply@thisaddress.com> wrote in message
news:unXZRJi2IHA.1772@TK2MSFTNGP03.phx.gbl...
> Don't suppose you know where I could find out what the smigrate error
> message means...?
>
> Col
>

Merv
Sun Jun 29 14:20:49 PDT 2008

Not sure if it's related, but...

Error when you use the SharePoint Migration Tool to try to restore a Windows
SharePoint Services Web site: "Error getting manifest for http://localhost
(fatal)"
http://support.microsoft.com/kb/926409

--
Merv Porter [SBS-MVP]
============================

"Colin A" <noreply@thisaddress.com> wrote in message
news:unXZRJi2IHA.1772@TK2MSFTNGP03.phx.gbl...
> Don't suppose you know where I could find out what the smigrate error
> message means...?
>
> Col
>

Costas
Sun Jun 29 15:17:46 PDT 2008

Colin,

Another way you might want to try, is to backup the current companyweb by
going to the command prompt, change to the
c:\program files\common files\Microsoft Shared\Web Server Extensions\60\Bin
directory and execute the following command:

stsadm.exe -o backup -url http://companyweb -filename
c:\backup.dat -overwrite

After that take the 'backup.dat' file from the C:\ directory and copy it on
the new server. On the new server, follow steps 1 to 16 from the link that
Merv posted, but instead of using smigrate, use the following command from
the command prompt (same directory as the one I posted above)

stsadm.exe -o restore -url http://companyweb -filename
c:\backup.dat -overwrite

See if that works

--
Costas


"Colin A" <noreply@thisaddress.com> wrote in message
news:unXZRJi2IHA.1772@TK2MSFTNGP03.phx.gbl...
> Don't suppose you know where I could find out what the smigrate error
> message means...?
>
> Col
>

Colin
Sun Jun 29 23:12:40 PDT 2008

Thanks Merv

I think we may be on to something here....

I've tried to open the manifest.xml file (after extracting it...) with the
XML Editor just to see what is physically at the bottom of the file.... The
"premature end of file" message was my reason....

The XML Editor runs out of memory opening the file...??, so the idea of
making the manifest.xml smaller seems to be on the right track...

I'll have a look and report back...

Many thanks for all your help.....

Colin
Sun Jun 29 23:14:05 PDT 2008

Thanks for this Costas....

Will this be okay for moving it from one server/domain to another one with a
completely differnet name etc....?

Thanks
Col

Costas
Mon Jun 30 04:43:51 PDT 2008

Yes, because you backup only the site contents.

--
Costas


"Colin A" <noreply@thisaddress.com> wrote in message
news:enUJAin2IHA.4004@TK2MSFTNGP03.phx.gbl...
> Thanks for this Costas....
>
> Will this be okay for moving it from one server/domain to another one with
> a completely differnet name etc....?
>
> Thanks
> Col
>

AllenM
Mon Jun 30 11:34:07 PDT 2008

If you have already restored companyweb back to the default state according
to KB829114 then all you really need to do is copy over the datafiles.

Restore only the configuration and the content databases to \Program
Files\Microsoft SQL Server\MSSQL$SharePoint\Data. Specifically, restore the
following configuration files and databases: . STS_Config.mdf
. STS_Config_log.ldf
. STS_Servername_1.mdf
. STS_Servername_1_log.ldf
Note Do not restore any other default files such as the Master.mdf file or
the Model.mdf file.


"Colin A" <noreply@thisaddress.com> wrote in message
news:enUJAin2IHA.4004@TK2MSFTNGP03.phx.gbl...
> Thanks for this Costas....
>
> Will this be okay for moving it from one server/domain to another one with
> a completely differnet name etc....?
>
> Thanks
> Col
>