Another aspect of the recent discussion about backups is the ability to cleanup the database and purge "orphaned" assets.
If you look closely at an OpenSim database that has been in use for a while the assets portion is huge, even if all regions and inventory has been deleted. I first ran across this after loading several huge OAR and IAR files multiple times - each time the files were loaded it created an entire asset tree in the database. The database grew to 10Gb with only 4 active regions! It seems that when an object/wearable/texture/whatever is deleted then all that is actually removed is th epointer entry that refers to the underlying data, if all references to that data have been deleted then it is left as an orphan. There are very good reasons not to delete these orphans from within OpenSim, but at present there is no mechanism to do this even offline. About the best that can be done at present is to dump everything to OAR/IAR files and reload then periodically. This is a reasonable workaround, but not really a long term solution. Back when 0.6.8/9 (different database setup) was in use there was an effort to create an SQL macro set to do this, but it was shelved as 0.7.x came closer. Is there some other solution out there that I don't know about? Maybe this would be a worthwhile support project. I have very little SQL experience, but a lifetime as a C/C++ programmer and would be willing to contribute what I can. Karen _______________________________________________ Opensim-users mailing list [email protected] https://lists.berlios.de/mailman/listinfo/opensim-users
