It kind of defeats the purpose of using a single install. The problem is my client has 100s of portals, and a small staff of developers. Also they want to keep licensing costs down, by having a single instance you reduce the amount of time to maintain the sites, and reduce the licensing costs, since most modules are licensed per instance.

SharePoint has the capability, maybe a way to schedule a template export with content would do what I need.

Hey, Patrick ... long time!

I agree that the inability to restore portals individually - or the possibility that one portal might negatively affect another - calls into question the benefit of putting multiple portals on the same install, when the portals are at all critical. Same codebase, same database for multiple portals is a selling point that doesn't have the value that it seems to on first blush.

I have an install with two portals that I need to split. Someday soon. Not entirely looking forward to that though I guess it is probably as simple as setting up two instances of the install, and dropping one portal from one and the other from the other ...

Hi,

PLEASE DO BACKUP EVERYTHING BEFORE YOU TRY THIS !

You can do next for this:

1) Export the portal to a template including the content. Modules not having IPortable will lose content/ data.

2) Create a new portal from this template and you have actually done a backup, but with a different portalid;

3) Change the portalid in portalalias to the new portal.

4) Check where data is missing and use own sql scripts! TAKE CARE! to copy data from old to new portal.

5) Remove the old portal

Good Luck.

J.