1

I have two web applications that can be accessed by the following urls:

  1. http://servername/

  2. http://servername:8090/

Now I want to swap the web applications urls. So I am thinking of the following approach:

  1. Take a backup of all the site collections on the first and second web application.
  2. Permanently delete all the site collections.
  3. Restore the backup files of the site collection to the new locations.

Can anyone advise if my above approach is considered valid?

Thanks

  • 1
    actually, moving content databases method could be much easier! – Vamsi K K Sep 15 '15 at 11:52
  • @VamsiKK what about the site collections them-selfs ? will they get moved by moving the content DB ? – john Gu Sep 15 '15 at 11:56
  • 1
    Yes, Content DB includes those site collections. – Vamsi K K Sep 15 '15 at 12:31
4

Two easy options i am thinking about.

Method # 1

  • Make the changes on the AAM and Update the IIS bindings.
  • Yo may need to IIS reset at then end.

Method # 2

  • Detach the Content Database from web App A & web App B

  • Now attach Content DB from Web app A to Web App B & From web B to Web App A.

  • but i tried my approach on a test server , where i took a backup for all the site collections. then i delete the site collections from the web applications. now i got 2 web applications without any site collections. then i restore the site collection to the desired web application.. and seems it is working well,, so is this a valid approach ? although it might require more effort compare to what u are suggesting ,, but i am more comfortable with it, but not sure if this will cause behind the scene problems ? – john Gu Sep 15 '15 at 14:43
  • 1
    I would say, this approach is doing a simple work in hard way....yesterday in one of my HR session...instructor asked me do you want smarter or hard? so no offense but your method is hard....i would personally go with db detached and attached...5 min total. – Waqas Sarwar MVP Sep 15 '15 at 14:47
  • Yes, content DB is much easier. Also, don't forget that you have to install solutions on the new web application. not all solutions are globally deployed! You also need to worry about any web config changes that need to be moved. – Vamsi K K Sep 16 '15 at 20:44

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.