locked
Move-SPSite with no IIS reset? RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Does anyone know the definite or potential side-effects of not performing an IIS reset immediately after performing a Move-SPSite command to move a site collection from one content database to another is?

    We have been tasked with splitting some our larger content databases up to make them more manageable and are using Move-SPSite to do so.  However, we are operating in a 24/hour no-break environment and have to submit an outage report in order to request and perform an IIS reset.  To move a site collection on the other hand, we only have get approval from the site collection owner.

    So our plan is to move all the site collections throughout the week when possible and then submit one outage report to perform the IIS reset once they are all moved.  But in the meantime, what are the negative consequences of moving a site and then not performing an IIS reset for a few days?

    Wednesday, January 8, 2014 3:11 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Are you able to verify this in your Test environment first? If you read the below thread it reads that no downtime is required. Read Trevor's reply.

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/0cb7f0b6-01cf-42f7-bdb1-3f896bf4156e/no-downtime-required-with-movespsite?forum=sharepointadminprevious

    Amit

    • Proposed as answer by JasonGuo Tuesday, January 21, 2014 2:14 AM
    • Marked as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    Wednesday, January 8, 2014 3:36 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I would not assume anything by lack of response, other than folks may not know.

    IISReset in this case is likely used to clear up any cached pointers to the old database for this site collection.  The move-spsite command locks the database so that it cannot be modified during the move, so as far as "Safety" goes, it covers the aspect while the database is moving.  The risk you are assuming is that some piece of cache is not holding on to the old database name and trying to insert rows into tables with reference to the site ID of the site you moved, or other subsites that might be contained there-in.  Not even sure that it would try to write without reading first to find the site in that database, but  I would say for Risk Mitigation purposes, best to not let it hang out too long before you IIS Reset.

    • Proposed as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    • Marked as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    Friday, January 10, 2014 3:58 PM

All replies

  • Question
    Sign in to vote
    1
    Sign in to vote

    Are you able to verify this in your Test environment first? If you read the below thread it reads that no downtime is required. Read Trevor's reply.

    http://social.technet.microsoft.com/Forums/sharepoint/en-US/0cb7f0b6-01cf-42f7-bdb1-3f896bf4156e/no-downtime-required-with-movespsite?forum=sharepointadminprevious

    Amit

    • Proposed as answer by JasonGuo Tuesday, January 21, 2014 2:14 AM
    • Marked as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    Wednesday, January 8, 2014 3:36 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    It's true that the Move-SPSite command doesn't require downtime.  But after the process completes, it displays the message "WARNING: IIS must be restarted before this change will take effect. To restart IIS, open a command prompt window and type iisreset."

    The iisrest command does affect app pools, and this is the reason we have to submit an outage request before we can perform one.  In reality, the impact of an iisreset is small and the duration is short, but the powers that be deemed it outage request worthy.

    We have tested this in test and couldn't find any issues.  But we're still nervous because just because we couldn't find an issue doesn't mean one doesn't exist.

    Wednesday, January 8, 2014 3:59 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is it safe to assume by the lack of responses that not performing an iisreset immediately will have no negative outcome?  Is this just a general maintenance routine to perform clean up?
    Friday, January 10, 2014 3:16 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    I would not assume anything by lack of response, other than folks may not know.

    IISReset in this case is likely used to clear up any cached pointers to the old database for this site collection.  The move-spsite command locks the database so that it cannot be modified during the move, so as far as "Safety" goes, it covers the aspect while the database is moving.  The risk you are assuming is that some piece of cache is not holding on to the old database name and trying to insert rows into tables with reference to the site ID of the site you moved, or other subsites that might be contained there-in.  Not even sure that it would try to write without reading first to find the site in that database, but  I would say for Risk Mitigation purposes, best to not let it hang out too long before you IIS Reset.

    • Proposed as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    • Marked as answer by JasonGuo Tuesday, January 21, 2014 2:15 AM
    Friday, January 10, 2014 3:58 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Do you have a load balanced environment?

    If so you could have taken a web front out of your load balancer one at a time while you perform the reset and users wouldn't ever notice.

    Monday, December 7, 2015 3:31 AM