Subordinate Site collections dissapear when trying to change database
I want to create a backup farm with a webapplication webapp and three subordinate site collections each with there own database. 1. Add content DB ContDB1 to webapp 2. Create first site collection webapp/ which automatically gets ContDB1 3. Create second site collection webapp/sites/SC1 which also gets ContDB 4. Want to change DB for the second site collection to ContDB2 but the command stsadm -o deletecontentdb -url http://webapp/sites/SC1 -databasename ContDB -databaseserver servername removes both site collections and delete ContDB from webapp Is there any way to get around this ? Regards Rappe
March 24th, 2010 12:31pm

Hi, First, when you create a web application/first site collection, you need to have an existing content DB for it to save into, i.e. your contDB1. You can then force your next site collection to be saved into a different content DB by marking the exisiting one as full. If you go into 'Manage Content DB's' your notice you can set the site limit per DB. Set contDb1 to max sites = 1 and alert = 0. Now create a new content DB i.e. ContDB2 with a max site=1 and alert me =0. Now when you create a new site collection, the only place it can be saved is within your new contDB2. Your need to repeat these steps for each site collection you want in seperate DB's. If you have already created your site collections, and they are all contained within 1 DB, there is an stsadm command to move it. Or failing that, you can backup the site, create a new site collection and restore to that. RegardsAaron
Free Windows Admin Tool Kit Click here and download it now
March 24th, 2010 8:23pm

Thanks a lot it helped me ! Rappe
March 25th, 2010 4:25pm

Excellent, good to hear. RegardsAaron
Free Windows Admin Tool Kit Click here and download it now
March 25th, 2010 4:59pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics