http://www.invirtus.com/content/view/824/425/

Libra abstracts “delta” configurations from original base images then compacts, optimizes and catalogs configurations as “packages.” Libra Packages are portable and can be used later by the same user or distributed to any number of users so work can be leveraged. Furthermore, with Libra it is not necessary for the identical, binary replica of a virtual machine to be used downstream by another user.

As for the fixes to SPSIteManager, I looked back, and in fact the only “Bug” fix was the one I mentioned in my last comment. Everything else was new functionality.

First off, thanks for the quick reply!

Before I had known about your response, I went ahead and just tried to restore the .bak file to the right site and new content database since that part of the repartition apparently worked. However, before I was able to restore the site, I had to clear out the orphan data(using the stsadm -databaserepair) that was possibly floating out there due to the incomplete delete. After deleting all the corruption, I tried to restore the site and it still would not let me. I soon figured out that there was still a site entry in the config db site table and once that was removed, I was able to begin the restore process.

But I guess my question is: How do I know whether the site prior to running the repartition command in SPSiteManager is either orphaned or has documents check out? Deleting the site would not possible because eventually I will have to perform this in a production environment (during a scheduled outage of course).

As for the fixes for the SPSiteManager that are no longer available. Is it possible to still get the last copy before you decommissioned since I still would like to use it?

Thanks again for all your help!

Eric Chiang

You’re not doing ANYTHING wrong , and you don’t need to change anything in your environment.
Also, this is a proper way to pose these questions

The problem is not with SPSiteManager, but with that site in question.

I have a theory that it’s one of two things
1) an Orphaned Site
2) Possibly checked out documents that cause that error message to manifest itself, if the site is > 2GB (Like yours) and there are checked out documents. (Something I discovered a couple of months ago)

The easiest way to prove it’s simply a problem with that site, is to use STSADM to try to delete the site.

i.e. STSADM -o deletesite -url http://blahblah.

You’ll get the same error, and shows that the problem is with the site.

As for correcting it,
1) Let’s make sure the URL is valid (It should be, because it’s the same URL we used to back it up)

2) If that’s correct, and it’s still causing a problem, check out the following Orphaned Site articles if you have not already, and let’s make sure it’s not an orphaned site (See the hotfix location referenced here: http://blogs.msdn.com/krichie/archive/2006/06/30/652453.aspx)

3) If it’s the checked out documents issue I’m thinking it might also be, you’ll need to contact Microsoft and report the problem. I’m not sure what the status of that one was before I left.

Lastly, thanks for the “Rocks” comment on SPSiteManager
I removed it from the CodePlex site (For reasons I’ll note in a minute) but the version that was in the Utility Suite package (And the whole utility suite package itself) is still on the web components download site at Microsoft (I can’t controll that one), but the reason I’m noting it is, there were a couple of bug fixes I put into SPSiteManager that are not in the utility suite package, and were only in the updated version of it at the CodePlex site.
(For one of them, see http://blogs.msdn.com/krichie/archive/2006/09/11/749393.aspx)

The whole reason the utility suite is dead, is documented here:
http://blog.krichie.com/2007/01/18/the-sharepoint-utility-suite-is-dead/

Therefore, I won’t be putting any real effort into updating them, because I don’t own them The names, etc are the property of Microsoft, even though they are completely unsupported by Microsoft.

Mind you, I will be providing some cool stuff eventually as either part of DeliverPoint, or something else

HTH!!!
– Keith

I am sorry, but I am not sure where to pose this question since you have retired your blog.msdn.com account, but this question is about the SP Utility, specifically the repartition aspect of it. In test scenario, I tried to move a 72 GB site (part of a 276 GB content db) to its own content database using this tool (which by the way rocks!). However, I’ve noticed that at times I get errors during the process and am not sure how to resolve them since I will need to run it via an SDD. In this case, I started the repartition using the insdd parameter, and the back up ran to completion, but during the “deleting site…” phase a warning came on and mentioned that “There is no Web named ‘/sites/test1′” Can you shed any light on this and what environmental settings need to be optimal for this utility to function properly? I did read an article from SharePoint advisor written by Chris Fields that gave me some insight regarding some of his personal best practices, but even doing so, I obviously am still doing something wrong. Any advice would be greatly appreciated. And again, I apologize for this question not being in the right forum.