Re: WSS and Hosting

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

From: Ian Morrish (Ian_Morrish_at_HotMail_dot_com)
Date: 04/26/04 

Date: Mon, 26 Apr 2004 13:59:28 +1200

Yes

Only if using SQL backup/restore which is why you only use this option for
full server DR, yes;-)

SMIGRATE is a command line utility so you can run it as a scheduled task for
each site.
Regards,
Ian
http://www.wssdemo.com

"RJ" <jr@testout.com> wrote in message
news:uWakfEzKEHA.2244@tk2msftngp13.phx.gbl...
> Thanks Ian.
>
> So what you are saying is that using SMIGRATE, you are able to restore the
> individual sites (if required) - onto another server with another (not
> original) CONFIG database.
>
> I just have this perception (maybe wronggg) that sites must have their own
> original CONFIG database to work. If I can get a WSS site transferred or
> restored using SMIGRATE as you say then yeah, I probably am worrying too
> much.
>
>
>
>
> "Ian Morrish" <Ian_Morrish@HotMail_dot_com> wrote in message
> news:OwpaqzyKEHA.2260@TK2MSFTNGP09.phx.gbl...
>> To give the best advice we would really need to know the number of users
> and
>> size of documents to be stored in WSS.
>> WSS was designed for hosting many sites (thousands) that share the one
>> config database. I think there are far more important things to worry
> about.
>> If you want individual site backups that can be restored independently of
>> other sites (and even to other servers) then the smigrate utility might
>> be
> a
>> better approach.
>> I use smigrate all the time now as I can (and do) easily restore a site
>> to
> a
>> new server where as a SQL only backup would probably not work.
>>
>> Regards,
>> Ian
>> "RJ" <jr@testout.com> wrote in message
>> news:O5vlxYyKEHA.1388@TK2MSFTNGP09.phx.gbl...
>> > Our company wants to host numerous WSS sites for numerous business
>> > units/groups. Our plan is to have each business unit to have its WSS
>> > site -
>> > ALL on ONE server.
>> >
>> > I just need to clarify my understanding...with you alls assistance.
>> >
>> > (1) Per server, I can only have one config database - therefore, if I
>> > have
>> > 5-10 WSS sites (each with their own content database in SQL 2000) -
>> > then
>> > they will share that ONE configuration database. IS this TRUE?
>> >
>> > (2) For disaster recovery purposes, I will save the CONTENT database
> for
>> > each WSS site (each business unit) from within SQL (SQL backup) - What
> is
>> > the best method for this?
>> >
>> > I ask the best solution for disaster recovery using SQL because since
> the
>> > ONE configuration database exists for ALL the WSS sites on this one
>> > server,
>> > then it IS possible that the restore can mess up another WSS site.
>> >
>> > Example, WSS site A required to be restored from 2 weeks back;
> therefore,
>> > I
>> > will also have to restore the ONE config database that serves the other
>> > WSS
>> > sites - this will mess up the OTHER WSS sites config - ALL in ONE
>> > config
>> > database -
>> >
>> > Hope you guys understand me and can provide some guidance...thank you
>> > kindly.
>> >
>> >
>>
>>
>
>

Relevant Pages

  • Re: Size limit on smigrate ?
    ... The server is off line with only me logged in as ... I'll emial you the log file from the backup tha t produced ... these files I an trying to restore. ... the smigrate tool will not skip larger sub site. ...
    (microsoft.public.windows.server.sbs)
  • Re: changing from RAID-0 backup/restore problem
    ... Backup/Restore on different machines. ... Today or tomorrow I shall receive the new disks to mount ... >> restored on that server and now up and running. ... >> Directory and restore on a test environement ...
    (microsoft.public.windows.server.sbs)
  • Re: WSS and Hosting
    ... So what you are saying is that using SMIGRATE, you are able to restore the ... > new server where as a SQL only backup would probably not work. ... >> then it IS possible that the restore can mess up another WSS site. ...
    (microsoft.public.sharepoint.windowsservices)
  • Re: copy existing wss v2
    ... I think that "site already in use" means that you have already created a site in that name in the new server. ... Firstly that you can't smigrate to top-site level and secondly you can only use smigrate when you have not specified a template for the site level you are "restoring" to. ... The two are connected because in WSS 2.0 the top-level site is given a template when WSS 2.0 is installed. ... I haven't used stsadm for this but there are some similarities in what it won't accept when being used to restore. ...
    (microsoft.public.sharepoint.windowsservices)
  • Restoring SPS 2003 Portal + sites to alternate server using only a SQL Backup
    ... At our organisation we are looking at the usual backup/restore options - i.e. disaster recovery and/or document level restore capability. ... What we actually do at the moment is use Veritas BackupExec Agents to back up the files and system state on the SPS 2003 server, and use the SQL Agent on the backend SQL 2000 Server where all the content is stored. ...
    (microsoft.public.sharepoint.portalserver)