Move WSS 2.0 to a new server
George Schneider
called server1:1080. I want to move this to a new server I just bought since
the old server is about t be taken offline and retired. How cna I best
accomplish this? The curren ws 2.0 runs on a sql 2000 server. The new
server I want to use the internalsql database since the plan is to after the
move to the newe server to upgrade to wss 3.0.
Mike Walsh
That way you have more options including only transferring some content
rather than the whole site.
Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no questions by e-mail please
Ada Pan [MSFT]
As Mike suggested, you may have several options to do the migration. I
would like to provide the following resources for your reference:
You can read up on this in the Admin Guide, under the Contents tab, at the
topic Backup and Migration --> Backing Up and Restoring Web Sites. To
obtain Microsoft Windows SharePoint Services Administrator's Guide, visit
the following Microsoft Web site:
Windows SharePoint Services Administrator's Guide
http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
A6A4-3E33FA13D230&displaylang=en
Upgrading to Windows SharePoint Services 3.0
http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40c
b-a32c-ff3395073dc91033.mspx
I hope this helps.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
George Schneider
upgrade. How could I accomplish that?
Ada Pan [MSFT]
Please see the article below:
Backing Up and Restoring Web Sites (Windows SharePoint Services 2.0)
http://technet2.microsoft.com/windowsserver/WSS/en/library/95deae2b-ecc4-4af
b-9acd-cf27ae0977fe1033.mspx?mfr=true
Or you can reference the topic Backup and Migration --> Backing Up and
Restoring Web Sites in Windows SharePoint Services Administrator's Guide:
Windows SharePoint Services Administrator's Guide
http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
A6A4-3E33FA13D230&displaylang=en
Please let me know if the information helps or you need further assistance.
George Schneider
when I restore to the new server the name will be http://server2 or
http://server2:1080.
"Ada Pan [MSFT]" wrote:
> Hi George,
>
> Please see the article below:
>
> Backing Up and Restoring Web Sites (Windows SharePoint Services 2.0)
> http://technet2.microsoft.com/windowsserver/WSS/en/library/95deae2b-ecc4-4af
> b-9acd-cf27ae0977fe1033.mspx?mfr=true
>
> Or you can reference the topic Backup and Migration --> Backing Up and
> Restoring Web Sites in Windows SharePoint Services Administrator's Guide:
>
> Windows SharePoint Services Administrator's Guide
> http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
> A6A4-3E33FA13D230&displaylang=en
Rich Raffenetti
make serverold an alias for server2.
If your users use dns to resolve names, the alias is called a CNAME.
If your users use NetBIOS, there is a capability to make NetBIOS aliases as
well. Search for keywords netbios and alias.
"George Schneider" <georgeds...@noemail.noemail> wrote in message
news:EDB1E322-F584-415D...@microsoft.com...
George Schneider
server since I have other applications running on it.
Ada Pan [MSFT]
The site name will be changed after you migrate the site to the new server.
But the name of http://server2 or http://server2:1080 depends on how you
store the site.
For your convenience, I would like to give an example below about how to
migrate a site from an old server to a new one. In this example, I assume
you have installed WSS 2.0 on the new server, want to migrate a site
http://server1:1080/ from the old server (Server1) to a new server
(Server2), and use an account with Domain Admin rights or appropriate
rights to perform the action.
#1. Build up the environment on the new server
==============================
1. Click Start - Administrative Tools - Internet Information Services (IIS)
Manager.
2. In IIS, right click on Web Sites and then select New | Web site.
3. In the wizard, click Next:
1) Type NewSite, and then click Next
2) Type 8888 in the TCP port text box, and then click Next
Note: You can also don't change the TCP port to 8888 and use the default
port 80 to host the sub-site that you want to migrate from the old server.
However, please make sure the 80 port is not occupied by another web site.
3) Locate the path C:\Inetpub\NewSite as the home directory, and then click
Next
4) Tick Read and Run scripts, and then click Next
5) Click Finish
4. Click Start - Administrative Tools - SharePoint Central Administration.
5. Under Virtual Server Configuration section, click Extend or upgrade
virtual server, click NewSite, click Extend and create a content database.
6. In the Extend and Create Content Database page:
1) Choose Create a new application pool, and type NewSite in the
application pool name text box.
2) Select Configurable option, and then type a domain user who must have
the appropriate permissions to access the related resources.
3) Type a domain user as the site administrator and email address:
domain\username, user...@abc.com.
4) Uncheck "Use default content database server", type a database name for
the site: NewSiteDB
5) Choose NTLM as the security configuration.
6) Click OK.
7) Wait until the backup process completes.
Note: Don't click the link <http://server2:8888> on the Virtual Server
Successfully Extended page.
#2. Back up one site on the old server
===========================
1. Click Start - Run, type CMD to open a command prompt.
2. Type the following command to back up the site:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN\SMIGRATE.EXE" -w http://server1:1080 -f c:\NewSitebk.fwp
#3. Create a new site on the new server
=========================
1. Move the file NewSitebk.fwp to the new server onto C:\.
2. On the new server, click Start - Run, type CMD to open a command prompt.
3. Type the following command to back up NewSite:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN\SMIGRATE.EXE" -r -w http://server2:8888/ -f
c:\NewSitebk.fwp
4. After the restore process completing, access http://server2:8888/ and
the sub-site will be been restored.
Hope this helps!
If anything is unclear or you need further assistance on this issue, please
feel free to let me know. I am glad to be of assistance.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
George Schneider
server using the WMDSE as the database. I the existing server I ran a backup
usign the SQL tools since this server runs full blown SQL 2000. On the new
server I restored the databses using OSQL. The problem I have is when I try
to connect to the configuration database I get a 4060 error that login
failed or something similar. I beleive this probably has to do with the
rights on the orignal databse that used SQL authentication and on this new
sharepoint server I'm usign Windows authentication. Is thee I can resolve
the rights issue and grant the appropiate permissions on the new server to
restore db's?
Ada Pan [MSFT]
It seems that you encounter a new issue which require individual attention.
To ensure we are productive in our support efforts, Please post this issue
separately so that our engineers and contributors within this newsgroup who
specialize in certain areas will be able to provide the 'value add' to
resolving these issues more efficiently.
It is important to us that we provide you with the best support possible
and by breaking down these issues separately we will be able to address
them in a timely manner.
Thank you for your patience and understanding.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
Ada Pan [MSFT]
How are you?
I am currently standing by for an update from you and would like to know if
you need further assistance on the original issue. Please let me know if
there is anything else I can do further assistance.
fink...@gmail.com
wrote:
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!
I have the exact same scenario as George, and tried every other way to
do this and failed every one. The main problem was renaming the
server to something else (as I was required) and having the old
database go along with the program. I have spent WAY too much time on
this and the SMIGRATE.EXE tool worked like a charm! I am wondering
why it took this long to find out that this tool existed with WSS 2.0
and why it is not plastered all over technet etc. (well I have not
done a direct search for the tool, but it was not mentioned in any of
the how-to's I came across).
So Thanks ADA PAN, for sharing that information, and thanks GEORGE for
asking the right questions.
Steve
Bryan L
on this -- it's exactly what I've been looking for.
I deviated from your instructions just a little bit - below are your
instructions with my specific deviations and notes included inline. I'm
taking the time to lay this out in the hope that it helps others.
*================================================*
OVERVIEW OF MY DEVIATIONS & GENERAL NOTES:
----------------------------------------------------------------
- I used stsadm.exe instead of smigrate.exe so that customizations and
security settings would be included
- My purpose in moving (actually, copying) the site collection was to have
an environment to test upgrade scenarios to WSS 3.0 without risking my
production WSS 2.0 site collection. I successfully moved a live WSS 2.0
site collection from one server (running SBS 2003 R2) to a Virtual Server
(running Server 2003 R2).
- The names of the server and the host headers (the website URLs) were all
changed from the source to the destination. (i.e. The source server was
called Main1 and the website was called http://source -- the destination
server was called Test-SP and the website was called http://swing). This
lets me run both sites live, side-by-side (tho on different servers) without
conflict.
- Both the source and destination servers use WMSDE as the database engine.
*================================================*
> For your convenience, I would like to give an example below about how to
> migrate a site from an old server to a new one. In this example, I assume
> you have installed WSS 2.0 on the new server, want to migrate a site
> http://server1:1080/ from the old server (Server1) to a new server
> (Server2), and use an account with Domain Admin rights or appropriate
> rights to perform the action.
*================================================*
A NOTE ABOUT PATCH LEVELS:
---------------------------------------
To ensure a successful migration, the version of WSS must be identical on
your source and destination servers. In my case, my source was running WSS
2.0 SP2 and Sharepoint Central Administration reported my version as
6.0.2.8117. I had installed SP2 on the destination server but SCA was
reporting that version as 6.0.2.6568. I discovered (thanks to some helpful
posts between Mike Walsh and Marty Penni) that a Sharepoint DST update
(KB924881) was needed to bring the version up to 6.0.2.8117.
Two things I noticed:
---------------------
- Update 924881 has been superceded by WSS 2.0 SP3. I chose not to install
SP3 on either server - to keep things simple I only applied update 924881 to
the destination server. (If you're already at SP3 on your source you should
install SP3 on the destination server also.)
- I'm running WSUS in my domain. For whatever reason WSUS did not flag
update 924881 as needed by my test destination server, so I had to install
the update manually. It went off without a hitch.
*================================================*
> #1. Build up the environment on the new server
> ==============================
>
> 1. Click Start - Administrative Tools - Internet Information Services
> (IIS)
> Manager.
>
> 2. In IIS, right click on Web Sites and then select New | Web site.
>
> 3. In the wizard, click Next:
>
> 1) Type NewSite, and then click Next
> 2) Type 8888 in the TCP port text box, and then click Next
>
> Note: You can also don't change the TCP port to 8888 and use the default
> port 80 to host the sub-site that you want to migrate from the old server.
> However, please make sure the 80 port is not occupied by another web site.
*================================================*
DEVIATION NOTE:
----------------------
I used port 80 for the new website because when I'm done with this project,
my end goal is to have my WSS 3.0 site collection running on another
server -- and that server already has sites using port 80. I needed to
verify they could coexist side by side. I'll show you more below.
*================================================*
> 3) Locate the path C:\Inetpub\NewSite as the home directory, and then
> click
> Next
> 4) Tick Read and Run scripts, and then click Next
> 5) Click Finish
>
> 4. Click Start - Administrative Tools - SharePoint Central Administration.
>
> 5. Under Virtual Server Configuration section, click Extend or upgrade
> virtual server, click NewSite, click Extend and create a content database.
>
> 6. In the Extend and Create Content Database page:
>
> 1) Choose Create a new application pool, and type NewSite in the
> application pool name text box.
> 2) Select Configurable option, and then type a domain user who must have
> the appropriate permissions to access the related resources.
> 3) Type a domain user as the site administrator and email address:
> domain\username, user...@abc.com.
> 4) Uncheck "Use default content database server", type a database name for
> the site: NewSiteDB
> 5) Choose NTLM as the security configuration.
> 6) Click OK.
> 7) Wait until the backup process completes.
> Note: Don't click the link <http://server2:8888> on the Virtual Server
> Successfully Extended page.
*================================================*
DEVIATION NOTE:
----------------------
I did not click the link, but I later wanted to verify the new site was
working properly before I tried to restore the site collection to it.
Therefore, I performed the following steps below -- ymmv.
WHAT I DID:
---------------
a.) In IIS, Expand Web Sites, right-click>Properties on the new web site
b.) On the Web Site tab, click Advanced...click Add...for TCP Port, enter
80; for Host Header value, enter the name (url) you want to use for the
website. Add additional Host Headers as desired, then click OK on all
properties boxes to return to IIS. (I created 2 host headers: "swing" and
"swing.domain.local").
c.) In your DNS configuration, be sure to add a new CNAME or A record that
matches the host header (I created a CNAME record called "swing" that
resolved to the A record for the destination server "Test-SP".
d.) Add the site name (w/ and/or w/o the domain suffix) to the Local
intranet zone in IE. (If you skip this step you may get a 401.2 Error when
trying to browse the site).
e). In IE on the destination server, browse to the new website (i.e.
http://swing) to verify the sharepoint installation is working. You'll be
prompted to choose a site template. Choose whatever -- it'll be overwritten
anyway when you restore your site collection.
Voila: I'm running the new sharepoint site on Port 80; thanks to the unique
host header, it doesn't get confused with other sites in IIS using the same
port because they also have unique host headers (also with corresponding
entries in DNS.)
*================================================*
> #2. Back up one site on the old server
> ===========================
>
> 1. Click Start - Run, type CMD to open a command prompt.
>
> 2. Type the following command to back up the site:
>
> "C:\Program Files\Common Files\Microsoft Shared\web server
> extensions\60\BIN\SMIGRATE.EXE" -w http://server1:1080 -f c:\NewSitebk.fwp
*================================================*
DEVIATION NOTE:
----------------------
I used stsadm.exe instead of smigrate.exe. If your Sharepoint installations
are indeed patched and updated to the same level you should have the correct
version of stsadm.exe, but I double-checked mine to be sure. (Both versions
were 11.0.8112.0.)
** For best results, lock your site collection before using stsadm.exe to
back it up. Read more about why to do this here:
http://technet.microsoft.com/en-us/library/cc288330.aspx
and read about how to do this here:
http://technet.microsoft.com/en-us/library/cc287673.aspx
HOW TO BACK UP USING STSADM.EXE:
------------------------------------------------
- On the source server, lock your site using the instructions linked above
- Open a command prompt and browse to C:\Program Files\Common
Files\Microsoft Shared\web server extensions\60\BIN
- Type the following command, modified as needed for your sitename and
desired filename/location, to back up the site:
C:\....\BIN>stsadm.exe -o backup -url http://source -filename
"S:\Backup\Main1\Source Web\backup.dat" -overwrite
- Wait for the message "Operation Completed Successfully". You will get no
progress indicator. If you like you can use Task Manager to watch
stsadm.exe and sqlservr.exe use CPU and memory resources to verify that it's
actually doing something. My site collection backed up to a file 1.1GB in
size in about 10 minutes, on 4 year old server hardware, to a network drive.
*================================================*
> #3. Create a new site on the new server
> =========================
>
> 1. Move the file NewSitebk.fwp to the new server onto C:\.
>
> 2. On the new server, click Start - Run, type CMD to open a command
> prompt.
>
> 3. Type the following command to back up NewSite:
>
> "C:\Program Files\Common Files\Microsoft Shared\web server
> extensions\60\BIN\SMIGRATE.EXE" -r -w http://server2:8888/ -f
> c:\NewSitebk.fwp
>
> 4. After the restore process completing, access http://server2:8888/ and
> the sub-site will be been restored.
*================================================*
DEVIATION NOTE - HOW TO RESTORE USING STSADM.EXE:
-------------------------------------------------------------------------
- On the destination server, open a command prompt and browse to C:\Program
Files\Common Files\Microsoft Shared\web server extensions\60\BIN
- Type the following command, modified as needed for your new sitename and
the backup file's name/location, to restore the site:
C:\....\BIN>stsadm.exe -o restore -url http://swing -filename
"S:\Backup\Main1\Source Web\backup.dat" -overwrite
- Wait for the message "Operation Completed Successfully". Again, you will
get no progress indicator. The restore took somewhat longer to run than the
backup. Get a cup of coffee.
Once the restore is complete, you should be able to browse your "new" site
collection using your new URL -- it should look and act just like the old
site collection from which you backed it up.
------------
Thanks again to Ada Pan for the terrific step-by-step instructions. Without
George Schneider's original post and Ada Pan's replies, I'd still be trying
to figure this out.
Regards and hope this helps others!
Bryan Linton
*================================================*
Andy
Bryan L wrote:
This is invaluable information!
09-May-08
This is invaluable information! Thanks for providing a clear step-by-step
on this -- it's exactly what I've been looking for.
I deviated from your instructions just a little bit - below are your
instructions with my specific deviations and notes included inline. I'm
taking the time to lay this out in the hope that it helps others.
*================================================*
OVERVIEW OF MY DEVIATIONS & GENERAL NOTES:
----------------------------------------------------------------
- I used stsadm.exe instead of smigrate.exe so that customizations and
security settings would be included
- My purpose in moving (actually, copying) the site collection was to have
an environment to test upgrade scenarios to WSS 3.0 without risking my
production WSS 2.0 site collection. I successfully moved a live WSS 2.0
site collection from one server (running SBS 2003 R2) to a Virtual Server
(running Server 2003 R2).
- The names of the server and the host headers (the website URLs) were all
changed from the source to the destination. (i.e. The source server was
called Main1 and the website was called http://source -- the destination
server was called Test-SP and the website was called http://swing). This
lets me run both sites live, side-by-side (tho on different servers) without
conflict.
- Both the source and destination servers use WMSDE as the database engine.
*================================================*
*================================================*
A NOTE ABOUT PATCH LEVELS:
---------------------------------------
To ensure a successful migration, the version of WSS must be identical on
your source and destination servers. In my case, my source was running WSS
2.0 SP2 and Sharepoint Central Administration reported my version as
6.0.2.8117. I had installed SP2 on the destination server but SCA was
reporting that version as 6.0.2.6568. I discovered (thanks to some helpful
posts between Mike Walsh and Marty Penni) that a Sharepoint DST update
(KB924881) was needed to bring the version up to 6.0.2.8117.
Two things I noticed:
---------------------
- Update 924881 has been superceded by WSS 2.0 SP3. I chose not to install
SP3 on either server - to keep things simple I only applied update 924881 to
the destination server. (If you're already at SP3 on your source you should
install SP3 on the destination server also.)
- I'm running WSUS in my domain. For whatever reason WSUS did not flag
update 924881 as needed by my test destination server, so I had to install
the update manually. It went off without a hitch.
*================================================*
*================================================*
DEVIATION NOTE:
----------------------
I used port 80 for the new website because when I'm done with this project,
my end goal is to have my WSS 3.0 site collection running on another
server -- and that server already has sites using port 80. I needed to
verify they could coexist side by side. I'll show you more below.
*================================================*
*================================================*
*================================================*
DEVIATION NOTE - HOW TO RESTORE USING STSADM.EXE:
-------------------------------------------------------------------------
- On the destination server, open a command prompt and browse to C:\Program
Files\Common Files\Microsoft Shared\web server extensions\60\BIN
- Type the following command, modified as needed for your new sitename and
the backup file's name/location, to restore the site:
C:\....\BIN>stsadm.exe -o restore -url http://swing -filename
"S:\Backup\Main1\Source Web\backup.dat" -overwrite
- Wait for the message "Operation Completed Successfully". Again, you will
get no progress indicator. The restore took somewhat longer to run than the
backup. Get a cup of coffee.
Once the restore is complete, you should be able to browse your "new" site
collection using your new URL -- it should look and act just like the old
site collection from which you backed it up.
------------
Thanks again to Ada Pan for the terrific step-by-step instructions. Without
George Schneider's original post and Ada Pan's replies, I'd still be trying
to figure this out.
Regards and hope this helps others!
Bryan Linton
*================================================*
Previous Posts In This Thread:
On Wednesday, April 02, 2008 3:59 PM
georgedschneide wrote:
Move WSS 2.0 to a new server
I have our current WSS 2.0 server on a sever name server1. Thes ite is
called server1:1080. I want to move this to a new server I just bought since
the old server is about t be taken offline and retired. How cna I best
accomplish this? The curren ws 2.0 runs on a sql 2000 server. The new
server I want to use the internalsql database since the plan is to after the
move to the newe server to upgrade to wss 3.0.
On Thursday, April 03, 2008 12:03 AM
Mike Walsh wrote:
I'd upgrade the old server to WSS 3.0 and then move it.
I'd upgrade the old server to WSS 3.0 and then move it.
That way you have more options including only transferring some content
rather than the whole site.
Mike Walsh
WSS FAQ http://www.wssfaq.com / http://wss.collutions.com
no questions by e-mail please
George Schneider wrote:
On Thursday, April 03, 2008 1:45 AM
v-adapa wrote:
Re: Move WSS 2.0 to a new server
------=_NextPart_0001_37A6619C
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hello George,
As Mike suggested, you may have several options to do the migration. I
would like to provide the following resources for your reference:
You can read up on this in the Admin Guide, under the Contents tab, at the
topic Backup and Migration --> Backing Up and Restoring Web Sites. To
obtain Microsoft Windows SharePoint Services Administrator's Guide, visit
the following Microsoft Web site:
Windows SharePoint Services Administrator's Guide
http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
A6A4-3E33FA13D230&displaylang=en
Upgrading to Windows SharePoint Services 3.0
http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40c
b-a32c-ff3395073dc91033.mspx
I hope this helps.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_37A6619C
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hello George,
\par
\par As Mike suggested, you may have several options to do the migration. I would like to provide the following resources for your reference:
\par
\par You can read up on this in the Admin Guide, under the Contents tab, at the topic Backup and Migration --> Backing Up and Restoring Web Sites. To obtain Microsoft Windows SharePoint Services Administrator's Guide, visit the following Microsoft Web site:
\par
\par Windows SharePoint Services Administrator's Guide
\par http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-A6A4-3E33FA13D230&displaylang=en
\par
\par Upgrading to Windows SharePoint Services 3.0
\par http://technet2.microsoft.com/windowsserver/WSS/en/library/91046a84-57a1-40cb-a32c-ff3395073dc91033.mspx
\par
\par I hope this helps.
\par
\par Regards,
\par
\par Ada Pan
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par }
------=_NextPart_0001_37A6619C--
On Thursday, April 03, 2008 2:53 PM
georgedschneide wrote:
The problem is I want to move the WSS 2.0 to tthe new server before I upgrade.
The problem is I want to move the WSS 2.0 to tthe new server before I
upgrade. How could I accomplish that?
"Mike Walsh" wrote:
On Friday, April 04, 2008 3:02 AM
v-adapa wrote:
Re: Move WSS 2.0 to a new server
------=_NextPart_0001_3D21298C
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hi George,
Please see the article below:
Backing Up and Restoring Web Sites (Windows SharePoint Services 2.0)
http://technet2.microsoft.com/windowsserver/WSS/en/library/95deae2b-ecc4-4af
b-9acd-cf27ae0977fe1033.mspx?mfr=true
Or you can reference the topic Backup and Migration --> Backing Up and
Restoring Web Sites in Windows SharePoint Services Administrator's Guide:
Windows SharePoint Services Administrator's Guide
http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-
A6A4-3E33FA13D230&displaylang=en
Please let me know if the information helps or you need further assistance.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_3D21298C
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hi George,
\par
\par Please see the article below:
\par
\par Backing Up and Restoring Web Sites (Windows SharePoint Services 2.0)
\par http://technet2.microsoft.com/windowsserver/WSS/en/library/95deae2b-ecc4-4afb-9acd-cf27ae0977fe1033.mspx?mfr=true
\par
\par Or you can reference the topic Backup and Migration --> Backing Up and Restoring Web Sites in Windows SharePoint Services Administrator's Guide:
\par
\par Windows SharePoint Services Administrator's Guide
\par http://www.microsoft.com/downloads/details.aspx?familyid=A637EFF6-8224-4B19-A6A4-3E33FA13D230&displaylang=en
\par
\par Please let me know if the information helps or you need further assistance.
\par
\par Regards,
\par
\par Ada Pan
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par }
------=_NextPart_0001_3D21298C--
On Friday, April 04, 2008 12:01 PM
georgedschneide wrote:
Re: Move WSS 2.0 to a new server
How do I contend with the issue that the website is http://serverold:1080 and
when I restore to the new server the name will be http://server2 or
http://server2:1080.
"Ada Pan [MSFT]" wrote:
On Saturday, April 05, 2008 9:54 AM
Rich Raffenetti wrote:
When you have server2 ready, rename serverold to something else and then make
When you have server2 ready, rename serverold to something else and then
make serverold an alias for server2.
If your users use dns to resolve names, the alias is called a CNAME.
If your users use NetBIOS, there is a capability to make NetBIOS aliases as
well. Search for keywords netbios and alias.
"George Schneider" <georgeds...@noemail.noemail> wrote in message
news:EDB1E322-F584-415D...@microsoft.com...
On Saturday, April 05, 2008 12:38 PM
georgedschneide wrote:
That would make the move easy but unfortuantly I can't rename the exisitng
That would make the move easy but unfortuantly I cannot rename the exisitng
server since I have other applications running on it.
"Rich Raffenetti" wrote:
On Thursday, April 10, 2008 1:10 AM
v-adapa wrote:
Re: Move WSS 2.0 to a new server
------=_NextPart_0001_2FCB47C0
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hello George,
The site name will be changed after you migrate the site to the new server.
But the name of http://server2 or http://server2:1080 depends on how you
store the site.
For your convenience, I would like to give an example below about how to
migrate a site from an old server to a new one. In this example, I assume
you have installed WSS 2.0 on the new server, want to migrate a site
http://server1:1080/ from the old server (Server1) to a new server
(Server2), and use an account with Domain Admin rights or appropriate
rights to perform the action.
==============================
1. Click Start - Administrative Tools - Internet Information Services (IIS)
Manager.
2. In IIS, right click on Web Sites and then select New | Web site.
3. In the wizard, click Next:
1) Type NewSite, and then click Next
2) Type 8888 in the TCP port text box, and then click Next
Note: You can also don't change the TCP port to 8888 and use the default
port 80 to host the sub-site that you want to migrate from the old server.
However, please make sure the 80 port is not occupied by another web site.
3) Locate the path C:\Inetpub\NewSite as the home directory, and then click
Next
4) Tick Read and Run scripts, and then click Next
5) Click Finish
4. Click Start - Administrative Tools - SharePoint Central Administration.
5. Under Virtual Server Configuration section, click Extend or upgrade
virtual server, click NewSite, click Extend and create a content database.
6. In the Extend and Create Content Database page:
1) Choose Create a new application pool, and type NewSite in the
application pool name text box.
2) Select Configurable option, and then type a domain user who must have
the appropriate permissions to access the related resources.
3) Type a domain user as the site administrator and email address:
domain\username, user...@abc.com.
4) Uncheck "Use default content database server", type a database name for
the site: NewSiteDB
5) Choose NTLM as the security configuration.
6) Click OK.
7) Wait until the backup process completes.
Note: Don't click the link <http://server2:8888> on the Virtual Server
Successfully Extended page.
===========================
1. Click Start - Run, type CMD to open a command prompt.
2. Type the following command to back up the site:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN\SMIGRATE.EXE" -w http://server1:1080 -f c:\NewSitebk.fwp
=========================
1. Move the file NewSitebk.fwp to the new server onto C:\.
2. On the new server, click Start - Run, type CMD to open a command prompt.
3. Type the following command to back up NewSite:
"C:\Program Files\Common Files\Microsoft Shared\web server
extensions\60\BIN\SMIGRATE.EXE" -r -w http://server2:8888/ -f
c:\NewSitebk.fwp
4. After the restore process completing, access http://server2:8888/ and
the sub-site will be been restored.
Hope this helps!
If anything is unclear or you need further assistance on this issue, please
feel free to let me know. I am glad to be of assistance.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_2FCB47C0
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hello George,
\par
\par The site name will be changed after you migrate the site to the new server. But the name of http://server2 or http://server2:1080 depends on how you store the site.
\par
\par For your convenience, I would like to give an example below about how to migrate a site from an old server to a new one. In this example, I assume you have installed WSS 2.0 on the new server, want to migrate a site http://server1:1080/ from the old server (Server1) to a new server (Server2), and use an account with Domain Admin rights or appropriate rights to perform the action.
\par
\par #1. Build up the environment on the new server
\par ==============================
\par
\par 1. Click Start - Administrative Tools - Internet Information Services (IIS) Manager.
\par
\par 2. In IIS, right click on Web Sites and then select New | Web site.
\par
\par 3. In the wizard, click Next:
\par
\par 1)\tab Type NewSite, and then click Next
\par 2)\tab Type 8888 in the TCP port text box, and then click Next
\par
\par Note: You can also don't change the TCP port to 8888 and use the default port 80 to host the sub-site that you want to migrate from the old server. However, please make sure the 80 port is not occupied by another web site.
\par
\par 3)\tab Locate the path C:\\Inetpub\\NewSite as the home directory, and then click Next
\par 4)\tab Tick Read and Run scripts, and then click Next
\par 5)\tab Click Finish
\par
\par 4. Click Start - Administrative Tools - SharePoint Central Administration.
\par
\par 5. Under Virtual Server Configuration section, click Extend or upgrade virtual server, click NewSite, click Extend and create a content database.
\par
\par 6. In the Extend and Create Content Database page:
\par
\par 1)\tab Choose Create a new application pool, and type NewSite in the application pool name text box.
\par 2)\tab Select Configurable option, and then type a domain user who must have the appropriate permissions to access the related resources.
\par 3)\tab Type a domain user as the site administrator and email address: domain\\username, user...@abc.com.
\par 4)\tab Uncheck "Use default content database server", type a database name for the site: NewSiteDB
\par 5)\tab Choose NTLM as the security configuration.
\par 6)\tab Click OK.
\par 7)\tab Wait until the backup process completes.
\par
\par Note: Don't click the link <http://server2:8888> on the Virtual Server Successfully Extended page.
\par
\par #2. Back up one site on the old server
\par ===========================
\par
\par 1. Click Start - Run, type CMD to open a command prompt.
\par
\par 2. Type the following command to back up the site:
\par
\par "C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\60\\BIN\\SMIGRATE.EXE" -w http://server1:1080 -f c:\\NewSitebk.fwp
\par
\par #3. Create a new site on the new server
\par =========================
\par
\par 1. Move the file NewSitebk.fwp to the new server onto C:\\.
\par
\par 2. On the new server, click Start - Run, type CMD to open a command prompt.
\par
\par 3. Type the following command to back up NewSite:
\par
\par "C:\\Program Files\\Common Files\\Microsoft Shared\\web server extensions\\60\\BIN\\SMIGRATE.EXE" -r -w http://server2:8888/ -f c:\\NewSitebk.fwp
\par
\par 4. After the restore process completing, access http://server2:8888/ and the sub-site will be been restored.
\par
\par Hope this helps!
\par
\par If anything is unclear or you need further assistance on this issue, please feel free to let me know. I am glad to be of assistance.
\par
\par Regards,
\par
\par Ada Pan
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par
\par
\par }
------=_NextPart_0001_2FCB47C0--
On Thursday, April 10, 2008 5:30 PM
georgedschneide wrote:
Here's what I've attempted. oN the new server I installed WSS 2.
Here's what I've attempted. oN the new server I installed WSS 2.0 on the new
server using the WMDSE as the database. I the existing server I ran a backup
usign the SQL tools since this server runs full blown SQL 2000. On the new
server I restored the databses using OSQL. The problem I have is when I try
to connect to the configuration database I get a 4060 error that login
failed or something similar. I beleive this probably has to do with the
rights on the orignal databse that used SQL authentication and on this new
sharepoint server I'm usign Windows authentication. Is thee I can resolve
the rights issue and grant the appropiate permissions on the new server to
restore db's?
"Ada Pan [MSFT]" wrote:
On Wednesday, April 16, 2008 12:58 AM
v-adapa wrote:
Re: Move WSS 2.0 to a new server
------=_NextPart_0001_7A6DEA27
Content-Type: text/plain
Content-Transfer-Encoding: 7bit
Hello George,
How are you?
I am currently standing by for an update from you and would like to know if
you need further assistance on the original issue. Please let me know if
there is anything else I can do further assistance.
Regards,
Ada Pan
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
====================================================
This posting is provided "AS IS" with no warranties, and confers no rights.
------=_NextPart_0001_7A6DEA27
Content-Type: text/x-rtf
Content-Transfer-Encoding: 7bit
{\rtf1\ansi\ansicpg1252\deff0\deflang1033{\fonttbl{\f0\fswiss\fprq2\fcharset0 Verdana;}}
\viewkind4\uc1\pard\f0\fs20 Hello George,
\par
\par How are you?
\par
\par I am currently standing by for an update from you and would like to know if you need further assistance on the original issue. Please let me know if there is anything else I can do further assistance.
\par
\par Regards,
\par
\par Ada Pan
\par
\par Microsoft Online Partner Support
\par Get Secure! - www.microsoft.com/security
\par ====================================================
\par When responding to posts, please "Reply to Group" via your newsreader so that others may learn and benefit from your issue.
\par ====================================================
\par This posting is provided "AS IS" with no warranties, and confers no rights.
\par
\par }
------=_NextPart_0001_7A6DEA27--
On Wednesday, April 30, 2008 5:12 AM
finkster wrote:
Re: Move WSS 2.0 to a new server
On Apr 15, 8:58=A0pm, v-ada...@online.microsoft.com (Ada Pan [MSFT])
wrote:
f
f
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=3D=
=3D=3D=3D
..
Thank you! Thank you! Thank you! Thank you! Thank you! Thank you!
I have the exact same scenario as George, and tried every other way to
do this and failed every one. The main problem was renaming the
server to something else (as I was required) and having the old
database go along with the program. I have spent WAY too much time on
this and the SMIGRATE.EXE tool worked like a charm! I am wondering
why it took this long to find out that this tool existed with WSS 2.0
and why it is not plastered all over technet etc. (well I have not
done a direct search for the tool, but it was not mentioned in any of
the how-to's I came across).
So Thanks ADA PAN, for sharing that information, and thanks GEORGE for
asking the right questions.
Steve
On Friday, May 09, 2008 1:34 PM
Bryan L wrote:
This is invaluable information!
This is invaluable information! Thanks for providing a clear step-by-step
on this -- it's exactly what I've been looking for.
I deviated from your instructions just a little bit - below are your
instructions with my specific deviations and notes included inline. I'm
taking the time to lay this out in the hope that it helps others.
*================================================*
OVERVIEW OF MY DEVIATIONS & GENERAL NOTES:
----------------------------------------------------------------
- I used stsadm.exe instead of smigrate.exe so that customizations and
security settings would be included
- My purpose in moving (actually, copying) the site collection was to have
an environment to test upgrade scenarios to WSS 3.0 without risking my
production WSS 2.0 site collection. I successfully moved a live WSS 2.0
site collection from one server (running SBS 2003 R2) to a Virtual Server
(running Server 2003 R2).
- The names of the server and the host headers (the website URLs) were all
changed from the source to the destination. (i.e. The source server was
called Main1 and the website was called http://source -- the destination
server was called Test-SP and the website was called http://swing). This
lets me run both sites live, side-by-side (tho on different servers) without
conflict.
- Both the source and destination servers use WMSDE as the database engine.
*================================================*
*================================================*
A NOTE ABOUT PATCH LEVELS:
---------------------------------------
To ensure a successful migration, the version of WSS must be identical on
your source and destination servers. In my case, my source was running WSS
2.0 SP2 and Sharepoint Central Administration reported my version as
6.0.2.8117. I had installed SP2 on the destination server but SCA was
reporting that version as 6.0.2.6568. I discovered (thanks to some helpful
posts between Mike Walsh and Marty Penni) that a Sharepoint DST update
(KB924881) was needed to bring the version up to 6.0.2.8117.
Two things I noticed:
---------------------
- Update 924881 has been superceded by WSS 2.0 SP3. I chose not to install
SP3 on either server - to keep things simple I only applied update 924881 to
the destination server. (If you're already at SP3 on your source you should
install SP3 on the destination server also.)
- I'm running WSUS in my domain. For whatever reason WSUS did not flag
update 924881 as needed by my test destination server, so I had to install
the update manually. It went off without a hitch.
*================================================*
*================================================*
DEVIATION NOTE:
----------------------
I used port 80 for the new website because when I'm done with this project,
my end goal is to have my WSS 3.0 site collection running on another
server -- and that server already has sites using port 80. I needed to
verify they could coexist side by side. I'll show you more below.
*================================================*
*================================================*
*================================================*
DEVIATION NOTE - HOW TO RESTORE USING STSADM.EXE:
-------------------------------------------------------------------------
- On the destination server, open a command prompt and browse to C:\Program
Files\Common Files\Microsoft Shared\web server extensions\60\BIN
- Type the following command, modified as needed for your new sitename and
the backup file's name/location, to restore the site:
C:\....\BIN>stsadm.exe -o restore -url http://swing -filename
"S:\Backup\Main1\Source Web\backup.dat" -overwrite
- Wait for the message "Operation Completed Successfully". Again, you will
get no progress indicator. The restore took somewhat longer to run than the
backup. Get a cup of coffee.
Once the restore is complete, you should be able to browse your "new" site
collection using your new URL -- it should look and act just like the old
site collection from which you backed it up.
------------
Thanks again to Ada Pan for the terrific step-by-step instructions. Without
George Schneider's original post and Ada Pan's replies, I'd still be trying
to figure this out.
Regards and hope this helps others!
Bryan Linton
*================================================*
Submitted via EggHeadCafe - Software Developer Portal of Choice
WPF Report Engine, Part 1
http://www.eggheadcafe.com/tutorials/aspnet/31ed1875-728d-4037-9074-4eba5c821311/wpf-report-engine-part-1.aspx