Prev: One last check with the experts before migration begins
Next: Time out of sync on domain computers
From: Robert on 7 May 2010 08:52
You can do what you want 3 ways:

1. Use the command line stsadm -o backup to backup full companyweb on old server (SBS2008) and then stsadm -o restore on the new SBS 2008 server. This option overwrites the existing SharePoint site on the new SBS 2008 Server.

2. Use the command line ststadm -o export to backup full companyweb on old server (SBS2008) and then stsadm -o import to restore on the new SBS 2008 server. This option merges the backed up sharepoint site with the new SBS 2008 Server.

3. Deatch, copy and reattach content databases from old to new server. A couple of command line steps required here but nothing too onerous. This replaces the existing Sharepoint databases on new SBS 2008 server with those from old server.

Let me know if you need more specifics

@directorcia
www.ciaops.com



lwoody7110 wrote:

Import Sharepoint (companyweb) database from old SBS2008 to new server SBS2008
25-Apr-10

Hi all

Googling has not found me a guide for SBS2008 (only SBS2003). I am
hoping the knowledge in this group can help me.

I am moving my SBS2008 to a better host server (more CPU and RAM).
The rebuild has gone very well. I have taken my time to ensure the
server starts up with out error. The only remaining item is to move
the old companyweb Sharepoint DB across to the new server.

The server name and domain name are identical. The old server is
still working for me to access the previous sharepoint database. The
new sharepoint is virtually blank. There is nothing on the new
companyweb that I wish to keep.

Does anyone know the correct steps to export the entire companyweb
from the old server, and import it to the replacement server?

This is a home/hobby server for context. No business is going to
suffer from this.

Many thanks

Previous Posts In This Thread:


Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Customized Find Control for FlowDocuments
http://www.eggheadcafe.com/tutorials/aspnet/233d3397-0388-473c-8473-721a40cf910c/wpf-customized-find-contr.aspx
From: lwoody7110 on 9 May 2010 12:02
Thanks for the links. I've been away from the newsgroup for a while.
I'll give this a go within a couple of days and report back here.
From: lwoody7110 on 10 May 2010 03:30
On May 9, 5:02 pm, lwoody7110 <lwo...(a)nildram.co.uk> wrote:
> Thanks for the links.  I've been away from the newsgroup for a while.
> I'll give this a go within a couple of days and report back here.

Successfully exported using the following command on the old server

stsadm -o -export -url http://companyweb -nofilecompression -filename
c:\companyweb.bak

Copied c:\companyweb.bak to a portable drive.

Mounted the portable drive as H:\ on the replacement server.

I had a problem with the command "stsadm -o -import -url http://companyweb
-filename h:\companyweb.bak". Kept saying "File does not exist". I
gave up and repeated the export on the original server excluding "-
nofilecompression". This time the import command worked and
successfully merged the old companyweb on top of the new server's
companyweb.

However, it did not keep the original file creation dates, and some
announcements are missing, despite no errors in the export log.

I will have another go tonight using the "restore" command in the hope
it retains all the dates and announcements.

For anyone using copy and paste to export/import their companyweb, it
will not work (for some reason), you have to type the commands
manually.
From: Chris Puckett [MSFT] on 10 May 2010 11:15
That usually happens because of the dashes getting translated differently.
You can confirm this by just retyping the dashes.

--
Chris Puckett

This posting is provided "AS IS" with no warranties, and confers no rights.



"lwoody7110" <lwoody(a)nildram.co.uk> wrote in message
news:b2d27721-9fca-41e9-a79f-390391fc0016(a)o8g2000yqo.googlegroups.com...
> On May 9, 5:02 pm, lwoody7110 <lwo...(a)nildram.co.uk> wrote:
>> Thanks for the links. I've been away from the newsgroup for a while.
>> I'll give this a go within a couple of days and report back here.
>
> Successfully exported using the following command on the old server
>
> stsadm -o -export -url http://companyweb -nofilecompression -filename
> c:\companyweb.bak
>
> Copied c:\companyweb.bak to a portable drive.
>
> Mounted the portable drive as H:\ on the replacement server.
>
> I had a problem with the command "stsadm -o -import -url http://companyweb
> -filename h:\companyweb.bak". Kept saying "File does not exist". I
> gave up and repeated the export on the original server excluding "-
> nofilecompression". This time the import command worked and
> successfully merged the old companyweb on top of the new server's
> companyweb.
>
> However, it did not keep the original file creation dates, and some
> announcements are missing, despite no errors in the export log.
>
> I will have another go tonight using the "restore" command in the hope
> it retains all the dates and announcements.
>
> For anyone using copy and paste to export/import their companyweb, it
> will not work (for some reason), you have to type the commands
> manually.

From: lwoody7110 on 11 May 2010 13:06
It hasn't gone well. Two odd things

1. "Announcements" are only showing the default view. If I click on
a annoucenment URL to view the entire contents, I see nothing more.
2. A restore failed with an error message...

stsadm -o restore -url http://companyweb -filename h:\companyweb.bak -
overwrite
gets me the following error
Your backup is from a different version of Windows SharePoint Services
and cannot be restored to a server running the current version. The
backup file should be restored to a server with version
'1178817357.0.26156915.0' or later.

This "killed" the running http://companyweb.

Imediately after the error above, I tried stsadm -o import -url
http://companyweb -filename h:\companyweb.bak -updateversions 2
....which resulted in a new error message:

The site http://companyweb could not be found in the Web application
SPWebApplication Name=SBS SharePoint Parent=SPWebService.

Now restoring the server from backup to state prior to trying the
stsadm -o restore attempt.

Any ideas about the DB message from the "...with version
'1178817357.0.26156915.0' or later".
 |  Next  |  Last
Pages: 1 2 3
Prev: One last check with the experts before migration begins
Next: Time out of sync on domain computers