locked
Moving content dbs between farms - site permissions RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I have setup a new Farm ready to house the data from the old farm.  It's a 2013 SP farm and it is just replacing the other 2013 SP farm due to DB upgrades and config changes we could do by just moving content.  However, after the Content DBs are moved, not the SP Config db, the Site permissions for all the sites are somewhat retained and somewhat not retained.  I cannot really see a pattern yet.  Has anyone else seen this and know why it is happening and better, how to make sure those permissions are retained when the content dbs come over?  Thank you!

    Wednesday, August 22, 2018 3:28 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote

    Let's try to work out the deltas so as to bound the problem scope:

    • Are both farms in the same domain?
    • Can you repeat the experience for a particular site collection?  For example, let's say, every time you migrate SITECOLLECTION-A from the old production farm to the new one, do you see the same permission changes occurring in this site collection?
    • Have you verified that someone didn't make permission changes to these sites shortly before you performed the backup?
    • Are both farms at the same build level?
    • Do the two farms have separate SQL Server instances?
    • Have you verified that when you mount the migrated content database, it's the correct one?

    Additionally,

    • What are the specific steps you are using to move content over?  Is it this: 1) Full content database backup on old production farm SQL Server instance; 2) copy over the backup file from the old SQL Server instance to the new one; 3) restore operation performed on the backup and on the new SQL Server instance; 4) Mount operation performed at the new farm of the restored content database?

    Friday, August 31, 2018 2:23 PM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    If the move was within the same domain, there shouldn't be any changes.  I move databases from production to development farms continuously and never experience any unexpected changes in permission.  Can you be more specific?  Maybe give some examples of what you mean?
    Wednesday, August 22, 2018 8:29 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I always do this when I move content databases to a new farm in the same domain

    If this is helpful please mark it so. Also if this solved your problem mark as answer.

    Thursday, August 23, 2018 7:14 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Yes, thank you for your response.  I took have done this and have not seen this permission issue.  For example, I have a Library with broken inheritance form the site and on the old site, I can access it and on the new site I can.  Then I thought I would look at the site's permissions and Check Permissions on myself.  The list on the current site is shorter than that of the new site and then the new site also has Limited Access either as another permissions group or added to an existing group that shows on both sites.  For instance the new site has "Full Control, Limited Access" whereas the current site has "Full Control".  Limited access is listed/in conjunction about 8 times on the new site and no where on the current site.  I'm going to keep digging see what other patterns I can pick up on.   Thank you again for your response.
    Thursday, August 23, 2018 5:52 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I suspect your site collection content database is not synchronized the "Config Database", it may be got disconnected while moving the dbs between farms.

    To put in same state as it were in old farm, use the Reset-SPSites Command to synchronize back to configuration database.

    Murugesa Pandian MCSA,MCSE,MCPD 

    Gear up for some solid action by doing.

    Thursday, August 23, 2018 6:26 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi satterc,

    Is there any update?

    If the post helps you, you can mark it as answer.

    Best regards,

    Grace Wang

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.


    Click here to learn more. Visit the dedicated forum to share, explore and talk to experts about Microsoft Teams.

    Friday, August 31, 2018 10:32 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Thank you for the answers however neither one has worked at this time.
    Friday, August 31, 2018 2:09 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Let's try to work out the deltas so as to bound the problem scope:

    • Are both farms in the same domain?
    • Can you repeat the experience for a particular site collection?  For example, let's say, every time you migrate SITECOLLECTION-A from the old production farm to the new one, do you see the same permission changes occurring in this site collection?
    • Have you verified that someone didn't make permission changes to these sites shortly before you performed the backup?
    • Are both farms at the same build level?
    • Do the two farms have separate SQL Server instances?
    • Have you verified that when you mount the migrated content database, it's the correct one?

    Additionally,

    • What are the specific steps you are using to move content over?  Is it this: 1) Full content database backup on old production farm SQL Server instance; 2) copy over the backup file from the old SQL Server instance to the new one; 3) restore operation performed on the backup and on the new SQL Server instance; 4) Mount operation performed at the new farm of the restored content database?

    Friday, August 31, 2018 2:23 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I was going through this list and is dawned on my about (are both farms at the same build level) that no they are not as we were SP1 on the old and June 2018 on the new.  So another search and that was it, April 2016 introduced this and I just missed it.  Thank you all for your responses.
    Friday, September 7, 2018 3:34 PM