no more smigrate :-(

Hi all

Struggling without the WSS3 administrators guide. Has it been released?

We have a relatively large WSS site with many subwebs - around 20gig SQL DB
all up. With WSS2, I used to use smigrate is an easy means to restore
individual files from a backed up library. I had a script that listed all
site collections for a given virtual server, and then recursively run stsadm
-enumsubwebs for each site collection. For each subweb, I would then run
smigrate with the -e option to then do subwebs individually.

I did this so we ended up with lots of smaller, more managable FWP files and
not a monster one. This was not for true DR, but more for the common
situation of a developer stuffing up a subweb or files in a document library
being clobbered. This method allowed for quick restores of common types of
data.

So now with WSS3 you lose smigrate and have to use STSADM export/import. I
also see that we have lost the use of the -e parameter? Can anybody confirm
this?

Now as another question - as I'm struggling to find out an answer, does
stsadm -o backup allow a restore to a completely separate sharepoint box or
is this still the realm of stsadm -export/import

Engelbert
Tue Jul 04 08:10:00 CDT 2006

Please put WSSv3 in the subject line when posting here. This newsgroup
assumes WSSv2 ...

1. I look every day at what's new and I haven't seen it (I haven't looked
today yet ...)

2. Do you mean stsadm to move from WSSv2 to WSSv3 or within WSSv3 ?

3. You might consider posting WSSv3 questions only to (one of) the new
newsgroups - in this case .setup_and_administration. You'll still have to
say WSSv3 in the subject but most posts to them do tend to be for the beta
products (thus maybe people with v3 knowledge read them and not this ng) and
theoretically this WSSv2 newsgroup will disappear at some stage.

Engelbert

"Paul" <Paul@discussions.microsoft.com> wrote in message
news:84AA447D-BB7C-4BAA-B32E-86AE8A63F0B8@microsoft.com...
> Hi all
>
> Struggling without the WSS3 administrators guide. Has it been released?
>
> We have a relatively large WSS site with many subwebs - around 20gig SQL
> DB
> all up. With WSS2, I used to use smigrate is an easy means to restore
> individual files from a backed up library. I had a script that listed all
> site collections for a given virtual server, and then recursively run
> stsadm
> -enumsubwebs for each site collection. For each subweb, I would then run
> smigrate with the -e option to then do subwebs individually.
>
> I did this so we ended up with lots of smaller, more managable FWP files
> and
> not a monster one. This was not for true DR, but more for the common
> situation of a developer stuffing up a subweb or files in a document
> library
> being clobbered. This method allowed for quick restores of common types of
> data.
>
> So now with WSS3 you lose smigrate and have to use STSADM export/import. I
> also see that we have lost the use of the -e parameter? Can anybody
> confirm
> this?
>
> Now as another question - as I'm struggling to find out an answer, does
> stsadm -o backup allow a restore to a completely separate sharepoint box
> or
> is this still the realm of stsadm -export/import
>
>

Paul
Tue Jul 04 08:58:01 CDT 2006

> 2. Do you mean stsadm to move from WSSv2 to WSSv3 or within WSSv3 ?

no, this purely within WSSv3. I want to do a similar thing to what I did
with v2 and smigrate -e

> 3. You might consider posting WSSv3 questions only to (one of) the new
> newsgroups - in this case .setup_and_administration. You'll still have to
> say WSSv3 in the subject but most posts to them do tend to be for the beta
> products (thus maybe people with v3 knowledge read them and not this ng) and
> theoretically this WSSv2 newsgroup will disappear at some stage.
>
thx i'll give it a shot

Todd
Wed Jul 05 09:14:33 CDT 2006

At TechEd they were saying that STSADM would back up webs as well as site
collections in V3. Have you tried it?

tk
"Paul" <Paul@discussions.microsoft.com> wrote in message
news:F2418AC7-3218-453A-95AB-72AEF227CF60@microsoft.com...
>> 2. Do you mean stsadm to move from WSSv2 to WSSv3 or within WSSv3 ?
>
> no, this purely within WSSv3. I want to do a similar thing to what I did
> with v2 and smigrate -e
>
>> 3. You might consider posting WSSv3 questions only to (one of) the new
>> newsgroups - in this case .setup_and_administration. You'll still have to
>> say WSSv3 in the subject but most posts to them do tend to be for the
>> beta
>> products (thus maybe people with v3 knowledge read them and not this ng)
>> and
>> theoretically this WSSv2 newsgroup will disappear at some stage.
>>
> thx i'll give it a shot

Patrick
Wed Jul 05 09:52:29 CDT 2006

stsadm will now perform two new operations at the web level.
stsadm export
stsadm import

Hope this helps!
Patrick

Engelbert
Wed Jul 05 10:03:05 CDT 2006

How about from WSSv2 to v3 ?

Is that possible with stsadm (or even with these two statements) ?

Engelbert

"Patrick Feltz" <usenet@unruly1.com> wrote in message
news:O95UkKEoGHA.4332@TK2MSFTNGP03.phx.gbl...
> stsadm will now perform two new operations at the web level.
> stsadm export
> stsadm import
>
> Hope this helps!
> Patrick
>

Patrick
Wed Jul 05 10:47:42 CDT 2006

I have not tested this however, In the past I have attempted to perform an
stsadm -o restore from one WSSv2 deployment to another WSSv2 deployment and
was not able to restore the site because the versions of WSS were different
so I highly doubt stsadm would work for this.

My recommendation would be to backup the WSSv2 site collection and restore
the WSSv2 site collection to a new content database. Adding that content
database to the WSSv3 environment will upgrade that content database and the
site collection(s) within it.

Hope that helps!
Patrick