none
Backup-SPSite Max File Size

    Question

  • Hi all,

    Does anyone know the max size of a backup file the backup-spsite PowerShell command will support. I don't want my files to split, and I believe Microsoft recommends using PowerShell for site collections under 15GB... but a recommendation and the actual supported size of the backup file could be two different things.

    Thanks,

    K.


    Personal Blog: http://thebitsthatbyte.com

    Thursday, April 05, 2012 2:53 PM

Answers

  • To my knowledge there is no limit on the size of the file except for whatever limits exist in the file system (e.g. FAT32: 4 GB, NTFS: many terabytes). The recommendation you've seen of 15 GB (this was for MOSS I believe, SP2010 is 100 GB, see below) is due to the length of time needed to do a site collection backup of that size.

    The site collection size is limited (and supported) to the size of the content database. Site collection backups are supported to a size of 100 GB, at which point you must use database backups:

    SharePoint site collection backup and restore is only supported for a maximum site collection size of 100 GB. For larger site collections, the entire content database must be backed up. If multiple site collections larger than 100 GB are contained in a single content database, backup and restore operations can take a long time and are at risk of failure.



    Jason Warren
    Infrastructure Specialist
    Habañero Consulting Group
    www.habaneros.com/blog

    Thursday, April 05, 2012 7:07 PM
  • Hi Kelly.

    In addition to what Jason answered, I seem to remember that there is some sort of hidden limitation in the siza of the manifest file generated. If the manifest file grows bigger than 2GB then the backup/restore will fail. That was due to an old limitation with a single textfile or similar, filesystem related or something.
    I think that this is still a valid limit but I do not know if you will ever hit that size...

    It would probably have to be a sitecollection bigger than the supported 100GB...but...I had a customer from when I was at Microsoft who had problems with the manifest size. That since the size of the manifest is related to the sheer number of objects, files and items.

    Not really sure if that helps...or just confuses things...

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download the SharePoint Branding Project here

    Thursday, April 05, 2012 7:19 PM

All replies

  • To my knowledge there is no limit on the size of the file except for whatever limits exist in the file system (e.g. FAT32: 4 GB, NTFS: many terabytes). The recommendation you've seen of 15 GB (this was for MOSS I believe, SP2010 is 100 GB, see below) is due to the length of time needed to do a site collection backup of that size.

    The site collection size is limited (and supported) to the size of the content database. Site collection backups are supported to a size of 100 GB, at which point you must use database backups:

    SharePoint site collection backup and restore is only supported for a maximum site collection size of 100 GB. For larger site collections, the entire content database must be backed up. If multiple site collections larger than 100 GB are contained in a single content database, backup and restore operations can take a long time and are at risk of failure.



    Jason Warren
    Infrastructure Specialist
    Habañero Consulting Group
    www.habaneros.com/blog

    Thursday, April 05, 2012 7:07 PM
  • Hi Kelly.

    In addition to what Jason answered, I seem to remember that there is some sort of hidden limitation in the siza of the manifest file generated. If the manifest file grows bigger than 2GB then the backup/restore will fail. That was due to an old limitation with a single textfile or similar, filesystem related or something.
    I think that this is still a valid limit but I do not know if you will ever hit that size...

    It would probably have to be a sitecollection bigger than the supported 100GB...but...I had a customer from when I was at Microsoft who had problems with the manifest size. That since the size of the manifest is related to the sheer number of objects, files and items.

    Not really sure if that helps...or just confuses things...

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download the SharePoint Branding Project here

    Thursday, April 05, 2012 7:19 PM
  • Thanks all, this was helpful


    Personal Blog: http://thebitsthatbyte.com

    Thursday, April 05, 2012 9:02 PM
  • Kelly, thank you. You pushed me over the edge to 6000 points :-)

    In addition to my answer before, if you have large or several large site collections, I would recommend using SQL backup instead. SQL's backup is much more robust and performance is so much better. Also, if you do SQL backup of the entire DB, you can use 'unattached restore' item level and up.

    Recover content from an unattached content database (SharePoint Server 2010)
    http://technet.microsoft.com/en-us/library/hh269602.aspx

    If you have many site collections in the same DB, split them up, one large Site Coll in one DB...

    Regards


    Thomas Balkeståhl - Technical Specialist - SharePoint - http://blog.blksthl.com
    Download the SharePoint Branding Project here

    Thursday, April 05, 2012 9:10 PM