Q1: What is SnapManager for SharePoint?
A1: SnapManager for Microsoft SharePoint Server helps you reduce storage costs and manage your growing SharePoint environment more efficiently. You can greatly simplify SharePoint data management and easily monitor the status and growth of your SharePoint Server farms across your entire enterprise.
SnapManager provides the ability to easily migrate and store SharePoint files on Server Message Block (SMB or CIFS) shares outside of Microsoft SQL Server® to improve scalability of large SharePoint 2007 or 2010 deployments.
With its browser-based user interface, SnapManager enables you to automate your data backup processes and other administrative functions. You can back up SharePoint Server data in seconds. With SnapManager, you can also recover any size database in minutes rather than hours from local or remote backups.
With SnapManager, you can also plan and implement a highly reliable disaster recovery strategy. Together with SnapMirror®, you can simplify remote replication of SharePoint Server data so it can be recovered rapidly in the event of a disaster.
Q2: Does SnapManager for SharePoint support Microsoft SharePoint Server 2010 Service Pack 1 (SP1)?
A2: Yes, SMSP 6.0 P1 and SMSP 6.1 both support Microsoft SharePoint Server 2010 SP1.
Q3: What is the latest version of SnapManager for SharePoint?
A3: Version 6.1, previous versions were 6.0 Patch 1(P1), and also SnapManager 5.0 for Microsoft Office SharePoint Server (SMMOSS).
Q4: Are there SMSP customer examples?
Q5: In SMSP 6.1 the BLOB stores can now be included in the backup plan by a checkbox “Backup archived data for this farm”. Does that now mean that you can SnapVault the BLOB stores via the advanced tab as well in Backup Builder?
A5: No, the SnapVault for the BLOB store is not available in SMSP 6.1.
Q6: Do we support the 4TB database limit?
A6: SharePoint supports the 4TB limit both w/ and w/o RBS enabled, this content db size has not been tested with SMSP 6.0 but is a test target for SMSP 6.1 which is currently active. From an implementation standpoint a customer should not use 4TB content dbs just because they can, there should be thought put into the type of data that is stored (low Write/high-Read, high/lo collaboration, etc.).
Q7: Can extender encrypt the blobs or encryption only occurs if the items are left in the DB.
A7: SnapManager for SharePoint Extender (Storage Optimization) does not provide encryption it does provide compression either on Media Server or Sharepoint Agents which means either of these two can perform compression. As this is extended content the BLOB is outside the SQL Servers and the stubs / pointers are in the SharePoint Content database.
SQL Server offers Transparent Data Encryption (TDE) that will encrypt the database at the disc level. This should address the “data at rest” part of the issue on encryption. In order to address the transaction level security, use SSL between SharePoint & SQL Server. However RBS with TDE is not supported.
Q8: What Service Accounts and permissions are needed for SMSP to work.
A8: SharePoint Admin needs Farm Admin rights and the user needs to be added to all the Application Pools. SQL Server would have the account of Processadmin, sysadmin, SQL server state permission. There are other permissions that need to be created/added in SnapManager for SharePoint and SnapManager for SQL Server. These are discussed in detail in Microsoft SharePoint 2010 and NetApp SnapManager 6.0 Best Practices Guide. Please refer to the following KB article.
Q9: Does our backup catalog look at names only or does it also catalog data inside the documents?
A9: We offer the Snapinfo LUN which holds all the information about the NetApp Snapshots. If the need is to have a backup catalog to tape then SnapProtect would fit best in that situation.
Q10: What SMSP Manager user interface commands use the different Executables (EXEs) that are provided in the \VaultClient\bin directory?
A10: The individual Feature Module, Tool (EXE) and descriptions are below:
Feature Module: Service Managing
Feature Module: Storage Optimization-Archiver
Feature Module: Platform Backup & Platform Restore
Q11: Is there a place that has SharePoint resources to leverage and learn from?A12: Check \\10.58.88.61\SharePointDownloads for training materials, conference materials related to SharePoint, SMSP binaries, and more.
Q11: What are the different Ports that SnapManager for SharePoint used by default?A13: The following Ports are the defaults;Manager Ports
Q12: Is there an easy way to identify versions of assemblies in the Global Assembly Cache (GAC) for the restore controller?
Figure 1. SnapManager for SharePoint Restore Controller view of the files backed up in the GAC.
Figure 2. Microsoft Windows Server 2008 view of files in the GAC that are reflected in SMSP's backup.
Q13: Can SMSP handle backup/restore of SharePoint Farms that are in different Active Directory domains from a single SMSP Manager?
A13: Yes, the SMSP Agent in the different domain requires the correct user credentials in order to run backup/restore operations, and the SMSP Manager can communicate with the SMSP Agents cross the Active Directory domains correctly, then SMSP can backup/restore farms in different domains.
Q14: Can we use SQL aliasing with SnapManager for SharePoint 6.1?
A14: Yes, SMSP supports SQL aliasing.
Q15: Do I need to install SMSP RBS provider on the FAST servers to index the RBS content?
A15: The FAST Crawl the data from SharePoint farm using the index connector, which access the data through SharePoint WFE, so you don't need to install SMSP RBS provider on FAST server.
Q16: Can SMSP and Avepoint co-exist in an environment?
A16: Yes it can up through SMSP version 6.1 and DocAve 6. Please make sure the ports for SMSP and AvePoint are not the same.
Q17: What are the prerequisites NetApp software required for SMSP install?
A17: The following prerequisites are required:
This NetApp Community is public and open website that is indexed by search engines such as Google. Participation in the NetApp Community is voluntary. All content posted on the NetApp Community is publicly viewable and available. This includes the rich text editor which is not encrypted for https.