Restoring backup from standalone to Server farm mode....

This is a discussion on Restoring backup from standalone to Server farm mode.... within the Sharepoint forums in Microsoft Tools category; Here is the scenario of WSS 3.0: WSS 3.0 is presently running on Windows 2003 R2 (MIDC-ISA) in standalone mode. Windows Internal Database (express) is in use. The same server is having ISA 2006 installed & running. WSS 3 contains many more subsites and user data (content) in it. Now, WSS 3.0 is installed as a fresh on Windows 2008 x64 (Application Server- MIDC-AS01) in server farm mode. SQL 2005 installed on Windows 2008 x64 (Database Server- MIDC-SQL01) is being configured for WSS 3.0 successfully. Now, data/ content/ sites/ subsites need to be migrated from MIDC-ISA to new systems. For ...

Go Back   Application Development Forum > Microsoft Tools > Sharepoint

Object Mix

Register FAQ Calendar Search Today's Posts Mark Forums Read
  #1  
Old 09-08-2008, 02:34 AM
Vinod Jadhav
Guest
 
Default Restoring backup from standalone to Server farm mode....

Here is the scenario of WSS 3.0:

WSS 3.0 is presently running on Windows 2003 R2 (MIDC-ISA) in standalone
mode. Windows Internal Database (express) is in use. The same server is
having ISA 2006 installed & running.
WSS 3 contains many more subsites and user data (content) in it.
Now, WSS 3.0 is installed as a fresh on Windows 2008 x64 (Application
Server- MIDC-AS01) in server farm mode.
SQL 2005 installed on Windows 2008 x64 (Database Server- MIDC-SQL01) is
being configured for WSS 3.0 successfully.
Now, data/ content/ sites/ subsites need to be migrated from MIDC-ISA to new
systems.

For this, I’ve backed up WSS 3 from central admin of MIDC-ISA. I tried to
restore the backup to MIDC-AS01 through ‘Central Administration’. The
settings done are as follows: (Settings before change are shown in (bracket)).
===================
Restore from Backup – Step 4 of 4: Select Restore Options:

Farm\Windows SharePoint Services Web Application\SharePoint - 80
1. New web application URL: http://midc-as01/wss (http://midc-isa)
2. New web application name: SharePoint - 80

Farm\Windows SharePoint Services Web Application\SharePoint - 80\WSS_Content
3. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
4. New directory name: D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
5. New database name: WSS_Content

Farm\Windows SharePoint Services Search\Search
instance\WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7
6. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
7. New directory name: D:\Program Files\Microsoft SQL
Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
8. New database name: WSS_Search_MIDC-SQL01
(WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7)

========================
Error:
The backup/restore job failed. In order to rerun the backup/restore the
timer job must be deleted from the Timer Job Definitions page. Failure
Message: Access to the path 'D:\WSS_ISA_Backup\spbrtoc.xml' is denied.

Where am I going wrong? Please guide. I searched for the same, but could not
resolve the issue.

Whether is it possible to migrate data from standalone to server farm?

Thanks in advance.

Reply With Quote
  #2  
Old 09-12-2008, 09:17 AM
Mike HAGGAG
Guest
 
Default Re: Restoring backup from standalone to Server farm mode....

Vinod,
How's this coming along? Did you figure-out a solution?
I have the impression you're doing it the hard way and it won't work. The
backup you did also backed-up the configuration and the Central
Administration databases which are different (new) on the new farm server.
All you really need to do is backup the CONTENT database on the old server
using SQL Express Management Studio, and restore them into the new SQL
server (MIDC-SQL01).
Then Create a new Web Application and a Blank Site Collection (using Central
Administration) on the new farm and add the content database to it.
--
Hope this helps!
Only my 2 cents! Not authoritative and comes with no warranty or guarantee
of useability, correctness or accuracy!
"Vinod Jadhav" <Vinod Jadhav@discussions.microsoft.com> wrote in message
news:BEF984EB-FF62-4CD8-93BD-9EDD9A27A3B0@microsoft.com...
> Here is the scenario of WSS 3.0:
>
> WSS 3.0 is presently running on Windows 2003 R2 (MIDC-ISA) in standalone
> mode. Windows Internal Database (express) is in use. The same server is
> having ISA 2006 installed & running.
> WSS 3 contains many more subsites and user data (content) in it.
> Now, WSS 3.0 is installed as a fresh on Windows 2008 x64 (Application
> Server- MIDC-AS01) in server farm mode.
> SQL 2005 installed on Windows 2008 x64 (Database Server- MIDC-SQL01) is
> being configured for WSS 3.0 successfully.
> Now, data/ content/ sites/ subsites need to be migrated from MIDC-ISA to
> new
> systems.
>
> For this, I've backed up WSS 3 from central admin of MIDC-ISA. I tried to
> restore the backup to MIDC-AS01 through 'Central Administration'. The
> settings done are as follows: (Settings before change are shown in
> (bracket)).
> ===================
> Restore from Backup - Step 4 of 4: Select Restore Options:
>
> Farm\Windows SharePoint Services Web Application\SharePoint - 80
> 1. New web application URL: http://midc-as01/wss (http://midc-isa)
> 2. New web application name: SharePoint - 80
>
> Farm\Windows SharePoint Services Web Application\SharePoint -
> 80\WSS_Content
> 3. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
> 4. New directory name: D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
> 5. New database name: WSS_Content
>
> Farm\Windows SharePoint Services Search\Search
> instance\WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7
> 6. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
> 7. New directory name: D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
> 8. New database name: WSS_Search_MIDC-SQL01
> (WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7)
>
> ========================
> Error:
> The backup/restore job failed. In order to rerun the backup/restore the
> timer job must be deleted from the Timer Job Definitions page. Failure
> Message: Access to the path 'D:\WSS_ISA_Backup\spbrtoc.xml' is denied.
>
> Where am I going wrong? Please guide. I searched for the same, but could
> not
> resolve the issue.
>
> Whether is it possible to migrate data from standalone to server farm?
>
> Thanks in advance.
>



Reply With Quote
  #3  
Old 09-12-2008, 10:18 AM
flo
Guest
 
Default Re: Restoring backup from standalone to Server farm mode....

Hi,
No I don't think it is possible to restore a backup made from the GUI of a
Sharepoint standalone server to a farm of Moss servers. What works though
is to do a backup of the content database in SQL Server Management Studio by
detaching/attaching the database, create a new web application and apply
this content database to it.

If you want to perform a backup using the GUI and you have access denied on
the target file share, the following accounts need to have change and read
permissions on it :
- The account authenticated to Central Admin when using the UI
- Central Admin application pool account
- SQL Server account
- SPTimer service account

Hope it helps,

Flo.


"Vinod Jadhav" <Vinod Jadhav@discussions.microsoft.com> wrote in message
news:BEF984EB-FF62-4CD8-93BD-9EDD9A27A3B0@microsoft.com...
> Here is the scenario of WSS 3.0:
>
> WSS 3.0 is presently running on Windows 2003 R2 (MIDC-ISA) in standalone
> mode. Windows Internal Database (express) is in use. The same server is
> having ISA 2006 installed & running.
> WSS 3 contains many more subsites and user data (content) in it.
> Now, WSS 3.0 is installed as a fresh on Windows 2008 x64 (Application
> Server- MIDC-AS01) in server farm mode.
> SQL 2005 installed on Windows 2008 x64 (Database Server- MIDC-SQL01) is
> being configured for WSS 3.0 successfully.
> Now, data/ content/ sites/ subsites need to be migrated from MIDC-ISA to
> new
> systems.
>
> For this, I've backed up WSS 3 from central admin of MIDC-ISA. I tried to
> restore the backup to MIDC-AS01 through 'Central Administration'. The
> settings done are as follows: (Settings before change are shown in
> (bracket)).
> ===================
> Restore from Backup - Step 4 of 4: Select Restore Options:
>
> Farm\Windows SharePoint Services Web Application\SharePoint - 80
> 1. New web application URL: http://midc-as01/wss (http://midc-isa)
> 2. New web application name: SharePoint - 80
>
> Farm\Windows SharePoint Services Web Application\SharePoint -
> 80\WSS_Content
> 3. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
> 4. New directory name: D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
> 5. New database name: WSS_Content
>
> Farm\Windows SharePoint Services Search\Search
> instance\WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7
> 6. New database server name: MIDC-SQL01 (MIDC-ISA\Microsoft##SSEE)
> 7. New directory name: D:\Program Files\Microsoft SQL
> Server\MSSQL.1\MSSQL\Data (C:\WINDOWS\SYSMSI\SSEE\MSSQL.2005\MSSQL\DATA\)
> 8. New database name: WSS_Search_MIDC-SQL01
> (WSS_Search_MIDC-ISA_4f43f04327144f62a6c0177e44f8ddd7)
>
> ========================
> Error:
> The backup/restore job failed. In order to rerun the backup/restore the
> timer job must be deleted from the Timer Job Definitions page. Failure
> Message: Access to the path 'D:\WSS_ISA_Backup\spbrtoc.xml' is denied.
>
> Where am I going wrong? Please guide. I searched for the same, but could
> not
> resolve the issue.
>
> Whether is it possible to migrate data from standalone to server farm?
>
> Thanks in advance.
>



Reply With Quote
Reply


Thread Tools
Display Modes


All times are GMT -5. The time now is 10:10 PM.


Powered by vBulletin® Version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Optimization by vBSEO 3.2.0
vB Ad Management by =RedTyger=

In an effort to better serve ads to our visitors, cookies are used on objectmix.com. For more information, check out our Privacy Policy.