Migrating a Path Based Site Collection to a Host Named Site Collection where the content database is greater than 135 GB

Hi
I have a 136 GB content database which will not back up via Backup-SPSite ( Microsoft say you cannot backup more than 100GB).
So with out Backup / Restore how can I convert a Path Based Site Collection to a Host Named Site Collection  with my 136 GB content database which incidentally uses Remote Blob Storage ?
Thanks
Nigel 
Nigel Price NJPEnterprises

I see two options:
Make the Backup-SPSite work despite being over 100GB (that's going to be a supported limit rather than a hard boundary)
Externalise some of the content and then re-insert it after the move.

Similar Messages

  • Migration of SP2010 Foundation Path Based to SP 2013 Enterprise Host name site collections

    Greetz!
    Need some sanity checking here. We have an existing intranet that uses SP 2010 Foundation (all out of the box) using SQL Express. We are standing up a brand new 2013 Farm on new hardware in a new network which will use host name site collections.
    According to
    TechNet this is a supported upgrade path.
    My thought is to do a database attach method from the old farm to the new one to get the product edition upgraded. Then to convert path-based site collections to host-named site collections I would need to follow the method described
    here which is to backup and restore to the hnsc of my choice.
    Something seems off about this though. Can I just attach to the new SQL instance and run the Mount-SPContentDatabase  or is there something about the backup-spsite and restore-spsite commands that does a conversion??
    Thanks!
    Love them all...regardless. - Buddha

    You need to do the Mount-SPContentDatabase to upgrade the schema of the database from 2010 to 2013.  Then you'll need to do the backup and restore to change the sites over to Host Named Site Collections.  Both steps will be required to accomplish
    what you want since you can't backup a 2010 site and restore it to a 2013 farm.
    Paul Stork SharePoint Server MVP<br/> Principal Architect: Blue Chip Consulting Group <br/> Blog: <a href="http://dontpapanic.com/blog">http://dontpapanic.com/blog</a><br/> Twitter: Follow <a href="http://twitter.com/pstork">@pstork</a><br/>
    Please remember to mark your question as &quot;answered&quot; if this solves your problem.

  • Managed path for host named site collection is farm level or web application level?

    Hi,
    I would like to get advice.
    I created a webapplication for host named site collections.
    these are my host named site collections (except http://sp2013) under my webapplication
    Root Site Collection: http://sp2013
    Site Collection: portal1.sg
    Site Collection: portal1.sg/research
    Site Collection: portal1.sg/intranet
    research and intranet managed paths are farm level
    all my host named site collection will be accessed by http and https except "intranet" site collection will be only accessed by https
    so I changed the Intranet zone for site collection using Set-SPSiteUrl
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg") -Url "https://portal1.sg" -Zone Intranet
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg/research") -Url "https://portal1.sg" -Zone Intranet
    Set-SPSiteUrl (Get-SPSite "http://portal1.sg/intranet") -Url "https://portal1.sg/intranet" -Zone Intranet
    Now I need to create "search" site collection for "Enterprice Search Center"
    My question is that for the "search" managed path ... should i use farm level or web application level?
    "search" site collection will be will be accessed with both http and https also.
    Thanks a lot!

    managed path for HNSC is farm level and u can have 20 managed path
    while managed path for path based is 20 per web application in your case if you are going to have a a separate web application for search then u will use web app
    Kind Regards,
    John Naguib
    Technical Consultant/Architect
    MCITP, MCPD, MCTS, MCT, TOGAF 9 Foundation
    Please remember to mark your question as answered if this solves your problem

  • How-To: Migrate Classic Path-based SP2010 Site Collection with OOTB/SPD Workflows = To: Claims Different Path-based SP2013 Site Collection ?

    Hello,
    I want to move an entire site collection from an old SharePoint 2010 farm to a new SharePoint 2013 farm. But there are a few requirements:
    - The old SP2010 site collection contains multiple SPD Workflows and OOTB Workflows.
    - URLs must be changes as the example: 
    Source Site Collection URL: http://OldWebApp.SP2010.com/sites/OldSiteCollection 
    Destination Site Collection URL shall be: http://NewWebApp.SP2013.com/projects/NewSiteCollection
    - There are no custom solutions nor web parts.
    How to accomplis this successfully ?
    My steps would be:
    1) Copying the content database from SP2010 SQL to the SP2013 SQL via: Copy-only backup feature, or the traditional Backup & Restore.
    2) I have already the Web Application on the new SP2013 ready, So, I will just need to create the destination site collection in the SP2013 environment with the new desired URL: (http:\\NewWebApp.SP2013.com\projects\NewSiteCollection).
    3) Remove the newly created Content Database of the new site collection in the destination environment.
    4) Test-SPContentDatabase -name Old_Content_DB -webapplication http://NewWebApp.SP2013.com > C:\Issues.txt
    My worry is that the SP2010 Web Application is Classic-based and I cannot change the entire Web Application to Claims-based as it hosts other running site collections !
    Equally, My other worry is that the SP2013 Web Application is Claims-based and I cannot change the entire Web Application to Classic-based as it hosts other running site collections !
    First-Question=> I cannot run Convert-SPWebApplication as I don't want to impact the entire source nor destination web applications - How to resolve this?
    5) Mount-SPContentDatabase "Old_Content_DB" -DatabaseServer "DBServer" -WebApplication http://NewWebApp.SP2013.com
    Second-Question=> As I mentioned above that my requirement is to migrate this old SP2010 site collaction to a totally new URL in SP 2013. My concern is that after completing step-5, the site
    collection will overwrite the root new web application and it gets placed on: (http://NewWebApp.SP2013.com) !  I want it to be: (http://NewWebApp.SP2013.com/projects/NewSiteCollection) ? How to do this trick?
    Third-Question=> Will all the SPD Workflows & the OOTB Workflows work correctly after the entire site collection has been moved from SP2010 to SP2013? I am asking this because I seen this:
    (http://blogs.msdn.com/b/chandru/archive/2013/04/14/upgrading-spd-2010-workflows-to-spd-2013-workflows.aspx), and I got scared. What do you think ?
    Could you please help me out in my three questions ?

    Following are the steps:
    Take the backup of the content database in SP 2010.
    Create a classic based web application in SP 2013 using PowerShell.
    New-SPWebApplication -Name "TestApplication" -ApplicationPool "TestApplicationAppPool" -AuthenticationMethod "NTLM" -ApplicationPoolAc
    Create a content database in the web application created above.
    Mount the database 
    Mount-SPContentDatabase WSS_Content_100 -DatabaseServer SQL2012Demo -WebApplication http://sp2013demo:100
    Now convert the web application to use claims authentication:
    Convert-SPWebApplication -Identity "http://sp2013demo:100" -To Claims –RetainPermissions -Force
    Finally, migrate the users to use claims identity:
    $w = Get-SPWebApplication "http://sp2013demo:100"
    $w.MigrateUsers($True)
    See these links for more information:
    http://www.sharepointnadeem.com/2013/12/sharepoint-2013-upgrade-from-sharepoint.html
    http://www.sharepointnadeem.com/2014/01/upgrade-from-sharepoint-2010-classic.html
    Blog | SharePoint Learnings CodePlex Tools |
    Export Version History To Excel |
    Autocomplete Lookup Field

  • Migrating SP2010 host-named Site Collections

    Hi all, 
    I'm currently having an issue when upgrading Host-Named site collections from SP2010 to SP2013. Once upgraded into SP2013 (Database attach), It keeps on prompting me for credentials, even after adding my user as a Web Application user. 
    Is there any resources or considerations when upgrading Host-Named sites?
    Cheers

    Loopback check is the most common cause of this behaviour:
    http://www.harbar.net/archive/2009/07/02/disableloopbackcheck-amp-sharepoint-what-every-admin-and-developer-should-know.aspx
    To confirm, add a hosts file entry on a non SharePoint machine and then connect from there. It'll probably work.

  • Load balancing host named site collection

    I am jumping into the realm of host named site collection. While the learning experience has been good, still there are some questions unanswered. Please bare patience since my questions are long.
    - I have a non host header site on port 80 that has https certificate added to IIS for supporting app store in https mode.
    - I tried to created the host name site collection using https in this default port 80 non host header web application and was greeted with error. Then i extended the web app to different  zone with port 443 . Then created the host header site collection
    with https with web application name for extended 443 one. Creation went in fine.
    - I tired to use IPs on now extended IIS site and bind certificates on that one. The site does not load. I do the same again in the default zone iss site, bind ips on that one and site loads. Now question is even though host header site collection was created
    using extended web application url , why binding had to be done on default zone IIS site?
    - Second test, i changed the authentication mode for extended, no effect on host named site collection but as soon as i changed it in default zone it reflected in host named site collection. I am confused why it needs extended zone url to create the https
    site but every change done in default zone is getting reflected on this host named site collection.
    Now for load balancing , it works fine with IP? But how to load balance these host named site collection using url. I talked with f5 team and they said i need to send some reply query string from each site. Where do i do that? Or is it even needed? 
    Accoring to this link : https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm
    . If the site hosts an application, though, the monitor should request a dynamic page on each webserver which forces a transaction with the application to verify its health and returns a specific phrase upon success.
    For application monitoring, the recommended best practice is to create such a script specific to your application, configure the monitor Send string to call that script, and set the Receive string to match that phrase. 
    Has any one done this before? I tired to search for resource regarding this for iis or sharepoint but was not able to get anything.
    Thank you for your patience for reading such a long question. 
    Adit

    first part of question:
    Default Web Appliction in port 80: Creating https host named site collection fails.
    Extend default web application on port 443 : Https hostnamed site collection created when web application name is passed for extended web application on port 443. This means this site collection is associated with this extended web application correct? But
    all the changes made in IIS only reflect if it is made to port 80 web application. Also changing authentication scheme from Central Admin, only changes on default zone reflects on site collection not the one in extended web application? Why  if the site
    was only created on extended web application paremeter, changes on default are reflecting on it but not from extended.
    Second part of question:
    Each Hostnamed site collection when load balanced thorough f5 using IP for 3 WFE uses 3 IPs for each. This way we will run out of IPs pretty soon. I want to know if there is way to load balance these sites using Hostname or anyother paramenter through f5
    and if any body has done it? 
    https://devcentral.f5.com/articles/name-based-virtual-hosting-with-ltm link talks about sending reply string
    from application but i do not know where to set it up or how to do it? No resources in the net. Just asking if any one else has done it. 
    Adit

  • Best Practice for Host Named Site Collections and Web Apps

    Looking for advice on setting up the host named site collections.  If I am reading many of the technet articles and blogs correctly I should 1) have only 1 top level web app for host named site collections and 2) not have a host header for that web
    app.  If that's correct I am looking for advice.  We have 7 separate domains that we support in our farm.  Currently each of those domains is divided into web applications based on the domain,  *.contoso, *.trains.com, *.bakers.com, etc.
      Is the concept now that all of the host named site collections fall under that one web app?  How do we deal with the SSL for each of those separate domains which all have their own certificates? 
    Thanks in advance for your comments. 
    NLewis

    Yes, for creating host named site collections, first you create a host header less web app and then create host named site collections under that web app. However this is only for the cases where all the host named site collections ends in one domain. So
    you can create host named site collections as intranet.contoso.com, my.contoso.com, portal.contoso.com etc as they are all ending in *.contoso.com.
    As per your environment, if you have web apps which caters to different domains like *.contoso.com, *.trains.com, *.bakers.com, you need to create separate web apps as they are all ending in different domains. Then you can have a separate wildcard SSL certificate
    for each of those web apps.
    Hope this helps.
    Thanks
    Mohit

  • Having thousands of Host-Named Site Collections - which authentication type?

    So Microsoft seems to state the claims + Host-Named Site Collection (HNSC) approach is the way to go forward.
    Assuming we have thousands of site collections, and we don't want to go with good ol' NTLM authentication as our claim authentication type, then how should we authenticate?
    Both Kerberos and SAML would be a nightmare to manage, since for Kerberos we need to register a Service Principal Name (SPN) per HNSC. For SAML we would end up in a similar situation, since this would require us to configure a relying party
    + realm for every HNSC.

    Please see the documentation on using managed paths with host named site collections.
    http://technet.microsoft.com/en-us/library/cc288637(v=office.14).aspx#section5
    You would be very unlikely to have thousands of individual host names, I would never recommend such an architecture to a customer.  Instead, you are much more likely to use managed paths (/sites/, /personal/, etc) in combination with host names, significantly
    reducing the number of individual host names while still allowing you to easily scale to thousands of site collections.
    In Office 365, each tenant is provisioned with 3 top-level host names (<tenant>.sharepoint.com, <tenant>-public.sharepoint.com, and <tenant>-my.sharepoint.com), all subsequent site collections are provisioned using managed paths.
    Note that this is not really a question particular to HNSC.  If you decide to not use host-named site collections but want to use individual host names using web applications, you get far less.  According to our Software Boundaries and
    Limits document, you get maximum 20 web applications per farm with a maximum 5 AAMs per web application, yielding a maximum 100 individual host names. 
    http://technet.microsoft.com/en-us/library/cc262787.aspx
    While you can achieve more host names using HNSC, I would strongly discourage this design and instead seek to leverage managed paths. 
    Kirk Evans
    Architect, Azure Modern Apps Center of Excellence
    Microsoft Corporation
    Microsoft Certified Master, SharePoint 2010
    http://blogs.msdn.com/kaevans

  • Error Accessing Host Named Site Collections In SharePoint Foundation 2013

    We have a new SharePoint Foundation 2013 server that has one web application two host named site collections. We get the "This page can't be displayed" message when we try to navigate to either of the site collections. Adding the server's IP to
    the host file on the machine we are testing from doesn't help. We can ping the new sites from that machine. The web application does not have a host header.
    Web application URL = http://servername
    Site collection #1 URL = http://customer.company.com
    Site collection #2 URL = http://vendor.company.com

    Hi,
    I recommend to verify the things below:
    Check if site can be accessed with site collection administrator.
    Add the SharePoint sites to a trusted zone to see if the issue still occurs.
    As this issue can be caused by many reasons, you may check the ULS log for more detailed errors.
    For SharePoint 2013, by default, ULS log is at C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\LOGS.
    Best regards.
    Thanks
    Victoria Xia
    TechNet Community Support

  • Content Search Web Part over HTTPS for a Host Named Site Collection

    Hello
    I have a host named site collection http://media.contoso.com which is a media portal that stores videos and pictures. On my parent site collection http://site.contoso.com homepage I have a Content Search Web Part that displays videos from the media portal.
    Both sites work over https.
    When I edit the content search web part and enter the URL http://media.contoso.com in the 'Change Query' box, search returns the results as expected but when I enter the URL as
    https://media.contoso.com no results are returned.
    I have removed the binding in IIS to point to http://media.contoso.com.
    I need it to be https so that I don't see "HTTPS security is compromised by http://media.contoso.com" on my site collection homepage.
    Any idea why this is happening?
    Thanks
    Yoshi

    http://technet.microsoft.com/en-us/library/ee792873%28v=office.15%29.aspx
    In the Search SSL Settings dialog box, do one of the following:
    If you do not want the crawler to crawl a site when there is an SSL certificate warning, make sure that the
    Ignore SSL certificate name warnings check box is cleared. For security reasons, the check box is cleared by default.
    If you want the crawler to crawl a site even if there is an SSL certificate warning, make sure that the
    Ignore SSL certificate name warnings check box is selected.
    If this helped you resolve your issue, please mark it Answered. You can reach me through http://freeit-support.com/

  • Robots.txt and Host Named Site Collections (SEO)

    When attempting to exclude ALL SharePoint Sites from external indexing, when you have multiple web apps and multiple Host Named Site Collections, should I add the robots.txt file to the root of each web app, as well as each hnsc? I assume so, but, thought
    I would check with the gurus...
    - Rick

    I think, one for each site collection as each site collection has different name and treated as web site.
    "he location of robots.txt is very important  It must be in the main directory because otherwise user agents (search engines) will not be able to find it.  Search engines look first in the main directory (i.e.http://www.sitename.com/robots.txt)
    and if they don’t find it there, they simply assume that this site does not have a robots.txt file"
    http://www.slideshare.net/ahmedmadany/block-searchenginesfromindexingyourshare-pointsite
    Please remember to mark your question as answered &Vote helpful,if this solves/helps your problem. ****************************************************************************************** Thanks -WS MCITP(SharePoint 2010, 2013) Blog: http://wscheema.com/blog

  • Mismatch between the Content Database size and the total of each site collection' storage used.

    Hi All,
    Environment:  SharePoint 2010 with SP2.
    Issue: One of the Content databases size in our farm shows 200 GB as used. There are 25 site collections in the DB and we counted
    the total storage used of all site collections in that Content DB and is not more than 40 GB. (used "enumsites" command and counted the each sitecollections storage used).
    What actions/troubleshooting were done?
    Ran one script which will find the actual size of site collection and how much space used in the disk. But didn’t find major difference in the report.
    Checked “Deleted from end user recycle bin “in all the site collections and no major storage is noticed.
    Planning to Detach the problematic Content DB and attach ,will check whether any major effect is there
    Why the Content DB shows 200 GB as used when the total storage used of all site collections is just 40 GB.
    Appreciate suggestions from any one.
    Best Regards,
    Pavan Kumar Sapara.
    s p kumar

    Hi,
    Thanks for your reply.
    As there is only 20 MB of unallocated space for the above said DB, SQL DB team informed that they cannot perform the DB shrink at this moment.
    So we are thinking to Offload all the site collections to other new DB and then will Drop the problematic database. In this way we can overcome the
    issue.
    Answer for your queries.
    Are the mismatched sizes causing an issue? Are you short on diskspace for DB storage or SQL backups?
    No, there is no issue with the mismatched sizes. We are not on short on disk space. We just worried why it occupies that much size(200 GB) when
    the total storage used of all site collections in that DB is 40 GB.
    Best Regards,
    Pavan Kumar Sapara.
    s p kumar

  • Help needed on Host Named Site Collection creation --- please help

    Hi Friends,
    Question 1
    Can we create Host Named Site Collection following the pattern below?
    We will have three Department head Host Named Site Collections, names –
    HRHead.ourdomain.com
    MarkettingHead.ourdomain.com
    AdminHead.ourdomain.com
    Under each of these department head sites, there will be 3 or 4 Host Named Site Collections. The site structure will be like:
    HRHead.ourdomain.com
    n 
    HR1.ourdomain.com
    n 
    HR2.ourdomain.com
    n 
    HR3.ourdomain.com
    MarkettingHead.ourdomain.com
    n 
    MarkettingProduct1.ourdomain.com
    n 
    MarkettingProduct2.ourdomain.com
    AdminHead.ourdomain.com
    n 
    AdminCountry1.ourdomain.com
    n 
    AdminCountry2.ourdomain.com
    n 
    AdminCountry3.ourdomain.com
    Question 2
    If we want to use common template (like header, footer, company icons) for inner sites (e.g. AdminCountry1.ourdomain.com, AdminCountry2.ourdomain.com, AdminCountry3.ourdomain.com) how to create that template for Host Named Site Collection? If these were
    sub sites, we can take help of site templates. But these are Host Named Site Collections, how to use common design for Host Named Site Collection?
    Any hint from you will be really helpful. Thanks for your comments.

    Yes you should be able to create a site collection using a custom template.  Here's a BLOG on how to create a site collection with a custom template in 2010.  It should still work the same way.
    http://www.toddklindt.com/blog/Lists/Posts/Post.aspx?ID=218
    Paul Stork SharePoint Server MVP
    Principal Architect: Blue Chip Consulting Group
    Blog: http://dontpapanic.com/blog
    Twitter: Follow @pstork
    Please remember to mark your question as "answered" if this solves your problem.

  • AAM for Host named site collection

    I have non-host header web application at port 80:http://wwwserver 
    It is AAM to https://wwwserver in same zone.
    Now when i create host named site collection using http it works fine
    New-SPSite http://hostheader.site.com/ -OwnerAlias domain\username -HostHeaderWebApplication http://wwwserver -Template "STS#0"
    But when i do 
    New-SPSite https://hostheader.site.com/ -OwnerAlias domain\username -HostHeaderWebApplication https ://wwwserver -Template "STS#0" i get error Warning: The port specified for the new host header site does not match any known bindings in the specified
    web appplication . The new site will not be accessible if the web application is not extended to an IIS web site serving this port.
    Now when i try to extend web application on port 443 it says it is already used by sharepoint. I do not want to screw aam since all my app store urls are configured through https://wwwserver. Any way to achieve https in host named site collection?
    sachin
    sachin

    Hi Sachin,
    Powershell New-SPSite is specifically looking for a web application that responds to
    http://www, not http://www. I don't think AAM applies for web applications, only for the URLs that the web application responds too.
    Information on configuring HNSC and SSL in this blog as well:
    http://blogs.msdn.com/b/russmax/archive/2013/10/31/guide-to-sharepoint-2013-host-name-site-collections.aspx
    Regards,
    Gavin McKay

  • I am developing a site where the content is 1300 pixels in depth but the browser background is 2500 pixels in depth. I want the browser background to be just a little longer than the content, but cannot seem to make that happen. Does anyone have an idea

    I am developing an iWEB site where the content is 1300 pixels in depth but the browser background is 2500 pixels in depth. I want the browser background to be just a little longer than the content, say about 1340 pixels, but cannot seem to shorten the browser measurements. Does anyone have an idea how I can solve this problem?   I have tried to make height adjustments in the Page Layout section of the Inspector, but content height heading has no affect on anything.  I have built about 75 sites in iWEB and this is my first experience like this.

    That is a legitimate Mozilla newsletter. As it says in the email:
    You're receiving this email because you subscribed to receive email newsletters and information from Mozilla. If you do not wish to receive these newsletters, please click the Unsubscribe link below.
    Unsubscribe https://www.mozilla.org/en-US/newsletter/existing/ad9febcf-65ac-41fd-810b-798945f448f3/
    Modify your preferences https://www.mozilla.org/en-US/newsletter/existing/ad9febcf-65ac-41fd-810b-798945f448f3/ "

Maybe you are looking for