WSSv2 restore fail

Hi All - STSv2 (installed actually for Project Server)

created a sub site called test http://servername/test

stsadm.exe -o backup -url http://ilsproject/test -overwrite -filename c:
\stsbackup\testsite.dat

then try stsadmin -o restore url http://ilsproject/test -filename c:
\stsbackup\testsite.dat

but just get You cannot create the root Web "http://server/test" unless
an explicit inclusion or a proper wildcard inclusion is defined.

only docs say to ensure managed paths set up correctly - so - what is
correctly ??

I tried adding /test in the managed paths - same thing ??

what am I missing ???

Dave
Mon Nov 27 10:52:54 CST 2006

Did you delete the site collection you backed up? You can overwrite an
existing site collection, you either have to delete the
http://ilsproject/test site collection or restore it to a new managed
path. "test" has to exist in the manged paths as an explicit inclusion
for the http://ilsproject/test to be rendered properly. try creating
either a new explicit manged path or a wild card managed path.

Create a "Test2" explicit manged path and use the following command:
stsadm -o restore -url http://ilsproject/test2 -filename c:\...

or create a "projects" wild card path and use the following command
stsadm -o restore -url http://ilsproject/projects/test -filename
c:\....

also if you are using as a project server you might want to create a
wildcard inclusion manged path so that all your projects sites can be
created under that managed path. By using an explicit inclusion path,
you only have the ability to create a site collection on that path
only. So any other project sites will fail when they go to be created
on that path if a site already exists there.

ERoss
Mon Nov 27 15:42:11 CST 2006

In article <1164646374.276970.251400@n67g2000cwd.googlegroups.com>,
dave.wollerman@gmail.com says...

Thanks for the response -

'test' is in managed paths

Path Type
(root) Explicit inclusion
sites Wildcard inclusion
test Wildcard inclusion

And I did delete test site before trying restore -

(just through site settings / delete this site)



> Did you delete the site collection you backed up? You can overwrite an
> existing site collection, you either have to delete the
> http://ilsproject/test site collection or restore it to a new managed
> path. "test" has to exist in the manged paths as an explicit inclusion
> for the http://ilsproject/test to be rendered properly. try creating
> either a new explicit manged path or a wild card managed path.
>
> Create a "Test2" explicit manged path and use the following command:
> stsadm -o restore -url http://ilsproject/test2 -filename c:\...
>
> or create a "projects" wild card path and use the following command
> stsadm -o restore -url http://ilsproject/projects/test -filename
> c:\....
>
> also if you are using as a project server you might want to create a
> wildcard inclusion manged path so that all your projects sites can be
> created under that managed path. By using an explicit inclusion path,
> you only have the ability to create a site collection on that path
> only. So any other project sites will fail when they go to be created
> on that path if a site already exists there.
>
>

ERoss
Mon Nov 27 16:03:42 CST 2006

In article <1164646374.276970.251400@n67g2000cwd.googlegroups.com>,
dave.wollerman@gmail.com says...

Thanks - it does not work -

followed the bellow & just received the error again -

Yes I deleted -

I now have deleted test & test1 sites - still no closer to being able to
restore

which means that I have a project server that cannot be restored in
event of emergency

this effing sucks



> Did you delete the site collection you backed up? You can overwrite an
> existing site collection, you either have to delete the
> http://ilsproject/test site collection or restore it to a new managed
> path. "test" has to exist in the manged paths as an explicit inclusion
> for the http://ilsproject/test to be rendered properly. try creating
> either a new explicit manged path or a wild card managed path.
>
> Create a "Test2" explicit manged path and use the following command:
> stsadm -o restore -url http://ilsproject/test2 -filename c:\...
>
> or create a "projects" wild card path and use the following command
> stsadm -o restore -url http://ilsproject/projects/test -filename
> c:\....
>
> also if you are using as a project server you might want to create a
> wildcard inclusion manged path so that all your projects sites can be
> created under that managed path. By using an explicit inclusion path,
> you only have the ability to create a site collection on that path
> only. So any other project sites will fail when they go to be created
> on that path if a site already exists there.
>
>

Dave
Tue Nov 28 08:21:22 CST 2006

if "test" is a wildcard inclusion then the site http://ilsproject/test
cannot be a site. your site would have to be
http://ilsproject/test/site.

after re-reading your first post. i realized you said that "test" was a
sub site. I assume this is a web under the root level site of
http://ilsproject/. Webs cannot be backed up using stsadm. Webs will
need to be backed up and restored with smigrate. If you want to turn
the web into it's own site collection then you would need to backup
using smigrate, create a new top-level site (do not apply a template),
then restore the backed up web using smigrate. Here is a sample script
that I used to do this.

(Backup the web)
smigrate -w http://ilsproject/test -f testbackup.fwp

(Create a top level site collection)
stsadm -o createsite -url http://ilsproject/test/site -ownerlogin
domain\id -owneremail id@domain.com

(Restore the web to the site collection)
smigrate -r -w http://ilsproject/test/site -f testbackup.fwp

you should be able to run this in a BAT file. Also the new site
collection url is http://ilsproject/test/site (which means)
http://virtualserver/wildcard-managed-path/site-name. Smigrate will not
pull over the permissions.

As far as a disaster recovery plan. I wouldn't use the above solution.
I would make sure the SQL databases are backed up using the sql backups
(content and config db's) and make sure the IIS metabase is backed up
as well on the WFE servers. If there is a complete diaster then you can
rebuild the environment with this information. If you want to do site
backups then use STSADM -O BACKUP to backup the entire site
collections, not the webs inside the site collections.

If you need more information or specific help, send me an email. I have
done alot with moving sites around and recovering data from backups
with WSS v2.