You have a SharePoint Server 2010 Service Pack 1 (SP1) server farm. You need to back up the contents of a custom list every day. The solution must minimize the size of the backup. What should you do?

Question

Options

• AFrom Central Administration, click Performa site collection backup.
• BFrom Central Administration, click Perform a backup.
• CCreate a scheduled task that runs the backup-spsite cmdlet.
• DCreate a scheduled task that runs the export-spweb cmdlet.

• A
  3% (1)
• B
  3% (1)
• C
  10% (3)
• D
  84% (26)

Explanation

The Export-SPWeb cmdlet exports a site, list, or library. The capability to export from a library is a new feature in SharePoint 2010 Products. Granular backup operations Backing up a Site Collection You can backup a specific site collection using either Central Administrator or Powershell. Using Central Administrator Select Backup and Restore From the UI select Perform a site collection backup Select the appropriate site collection from the pull down menu Include proper UNC path including backup file named like: filename.bak Selecting Start backup redirects to _admin/sitebackuporexportstatus.aspx page. Using Powershell backup-spsite -identity Exporting a Site/sub-site Export a specific site using Central Administrator: 1. Select Backup and Restore 2. From the UI select Export a site or list 3. Select Site Collection\Site "leave list drop down clear" 4. Optional categories is to export full security or export versioning history 5. Selecting Start export redirects to _admin/sitebackuporexportstatus.aspx page. Using specific list or library: 1. Select Backup and Restore 2. From the UI select Export a site or list 3. Select Site Collection\Site 4. Select a list 5. Optional categories "export full security or export versioning history" 6. Selecting Start export redirects to _admin/sitebackuporexportstatus.aspx page. Using Note: This example demonstrates exporting a document library named cake from Contosoweb Backup & Restore Sites in SharePoint 2010 Let's take a closer look at backup and sestore. When working with sites, we can use the Export- SPWeb cmdlet to export a site: This example exports an entire site to a backup file. It is also possible to export specific content from a subsite, such as lists, document libraries, and list items. You use the ItemUrl parameter to export lists or list items from a subsite. Here is an example of exporting a list called Calendar from C:\Backup\spWebCalendar.bak The Export-SPWeb cmdlet also supports the IncludeUserSecurity switch parameter, which allows you to include access control lists for all items. By default, Export-SPWeb exports the last major version of a list item, but you can change this by setting the IncludeVersions parameter to include the current version, last major and minor version, or all versions of each item. After you have an export file, you can use the Import-SPWeb cmdlet to import it into a subsite. Importing a subsite works as long as you specify a site collection that contains a matching template; otherwise, an Import-SPWeb cmdlet also supports the UpdateVersions parameter, which allows you to specify how to handle items that already exist in a list. The possible values are Append, Overwrite, and Remove Sites in SharePoint 2010 Finally, let's take a look at how to remove an existing site. The Remove-SPWeb cmdlet removes a specific site from SharePoint 2010. If the top-level site is deleted, the site collection is also Here is an example of running this cmdlet: settings for better backup or restore performance You can configure settings in both Central Administration and Windows PowerShell to increase backup or restore efficiency and If you are using the Export-SPWeb Windows PowerShell cmdlet, you can use the NoFileCompression parameter. By default, SharePoint Server 2010 uses file compression while exporting Web applications, site collection, lists, or document libraries. You can use this parameter to suppress file compression while exporting and importing. File compression can use up to 30% more resources, but the exported file will use approximately 25% less disk space. If you use the NoFileCompression parameter when exporting, you must also use it when you import the same content. You can also use the NoLogFile parameter. By default, SharePoint Server 2010 always creates a log file when you export content. You can use this parameter to suppress log file creation to save resources. However, we recommend that you always create logs. This is because logs can be used in troubleshooting. Moreover, log creation does not use many backup-restore- part-1.aspx

No community discussion yet for this question.