http://blogs.msdn.com/subhajitc/archive/tags/Backup+And+Restore/default.aspxTags: Backup And Restoreen-USCommunityServer 2.1 SP1 (Build: 61025.2)http://blogs.msdn.com/subhajitc/archive/2008/08/09/sharepoint-backup-and-restore-same-amount-of-free-space-required-for-initiating-full-or-incremental-backups.aspxSat, 09 Aug 2008 11:11:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8844815Subhajit.Chatterjee0http://blogs.msdn.com/subhajitc/comments/8844815.aspxhttp://blogs.msdn.com/subhajitc/commentrss.aspx?PostID=8844815<P>Just observed that during initiation of&nbsp;SharePoint Disater Recovery Backups (via STSADM or Central Admin), it&nbsp;expects the same amount of free space to be available on the UNC path irrespective of whether you are taking a full or incremental backups. This turns out to be an issue for large farm scenarios ( data &gt; 500 GB) as after having taken a "full" backup, the free space available on the share&nbsp;might not be greater than 50%. The operation will not start if the UNC path doesn't have enough free space which it computes in the very beginning.</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8844815" width="1" height="1">Backup And Restorehttp://blogs.msdn.com/subhajitc/archive/2008/05/19/sharepoint-backup-and-restore-moving-content-across-environments.aspxMon, 19 May 2008 08:37:00 GMT91d46819-8472-40ad-a661-2c78acb4018c:8518714Subhajit.Chatterjee0http://blogs.msdn.com/subhajitc/comments/8518714.aspxhttp://blogs.msdn.com/subhajitc/commentrss.aspx?PostID=8518714<P>If you thought that moving content from one environment to the other using SharePoint backup and restore was as simple as the click of a button, then read this blog to understand why it is not.</P> <P>Due to the differences in the "environmental factors' , additional steps might be necessary to ensure that the restore process succeeds.There is a nice <A class="" title=article href="http://technet.microsoft.com/en-us/library/cc263025.aspx" target=_blank mce_href="http://technet.microsoft.com/en-us/library/cc263025.aspx">article</A>&nbsp;in MSDN that talks about how to troubleshoot backup and restore issues. Typically you would need to investigate the log files to figure out why any particular operation failed.</P> <P><U>Known issue:</U>&nbsp;S<STRONG>earch indexes</STRONG> cannot be restored using this approach.&nbsp;A full crawl is required after the entire restore process to rebuild them again.</P> <P>Keep the following points in mind while&nbsp;planning for&nbsp;a backup and restore activity,-</P> <OL> <LI>SharePoint&nbsp;restore&nbsp;always creates a fresh new&nbsp;database. Hence delete the old content databases before moving ahead with the restore operation.</LI> <LI>Delete the SSP before restoring the same.</LI> <LI>Ensure that the various service accounts have necessary permissions on the UNC path &amp; SQL Server</LI> <LI>Ensure that there is sufficient disk space on the database drives. </LI></OL> <P style="COLOR: green; BACKGROUND-COLOR: yellow" mce_keep="true"><STRONG><U>Update - 8/8/2008</U></STRONG><BR>I just came across another blog by Stefan Gobner where he mentions about additional known issues with this operation. Read <A class="" title=here style="COLOR: blue; FONT-BOLD: true" href="http://blogs.technet.com/stefan_gossner/archive/2008/03/12/common-error-situation-with-when-using-backup-restore-to-transfer-a-database-to-a-new-farm-on-moss-2007.aspx" target=_blank mce_href="http://blogs.technet.com/stefan_gossner/archive/2008/03/12/common-error-situation-with-when-using-backup-restore-to-transfer-a-database-to-a-new-farm-on-moss-2007.aspx">here</A>&nbsp;for more details.&nbsp;</P><img src="http://blogs.msdn.com/aggbug.aspx?PostID=8518714" width="1" height="1">Backup And Restore