Table 8 on page 34 provides the checklist for SQL for NMM 2.3. Review the following checklist before installing NMM 2.3.
Verify that the device groups and associated snapshot devices for TimeFinder Mirror/Snap/Clone are configured properly.
Note: Configuring more than one snapshot technology with STD devices is not recommended.
If yes, pass. Otherwise, fail.
If TimeFinder/Mirror is configured, ensure that at least one BCV device is in Not Ready, Synchronized, or SyncInProg state, before taking backup. Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required.
If yes, pass. Otherwise, fail.
If TimeFinder/Clone is configured, ensure that at least one clone target device is in Not Ready, Created, or Recreated state, before taking backup.
Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required.
If yes, pass. Otherwise, fail.
If TimeFinder/Snaps is configured, ensure that at least one VDEV target device to be in Not Ready, Created, Recreated state before taking backup. Note: If the snapshot policy used deletes a snapshot at the time when the next backup is run, no action is required.
If yes, pass. Otherwise, fail. Table 7 Symmetrix checklist (page 3 of 3)
Check to see if: Details
Table 8 SQL checklist
Check to see if: Details
Check if SQL instance version for each instance installed: • SQL 2005 needs SP4
• SQL 2008 SP1 • SQL 2008 R2
If yes, pass. Otherwise, fail.
Check if SQL virtual server is online in case of clustered
instance. If yes, pass. Otherwise, fail.
Check if SQL services for each instance are up and running:
• SQL server • SQL browser
If yes, pass. Otherwise, fail.
Check if SQL server writer status is stable. If yes, pass. Otherwise, fail. Is SQL server running in single user mode? If yes, fail.
Preinstallation checklists 35
Microsoft SharePoint checklist
Table 9 on page 35 provides the checklist for SharePoint for NMM 2.3. Review the following checklist before installing NMM 2.3.
Table 9 SharePoint checklist
Check to see if: Details
• SharePoint server 2010 RTM.
• Microsoft Office SharePoint Server 2007 (for x86 and x64) Standard or Enterprise editions with SP2 or later and Windows SharePoint Services 3.0 with SP2.
• SharePoint server 2003 (for x86) Standard or Enterprise editions with SP2 and Windows SharePoint Services 2.0 with SP2.
If yes, pass. Otherwise, fail.
All essential SharePoint services are up and running:
• SQL server Writer (running and set to automatic) for SQL databases
• SharePoint Services Writer (running and set to automatic) for SharePoint 2007 and SharePoint 2010.
• SharePoint Search Writer for SharePoint 2007 or SharePoint 2010 Search — If not running, then it is a warning to check if role is enabled. Ensure that the services are started. Note: The service should be running only if the role is enabled.
• Microsoft Office Server Search Writer for Microsoft Office Server search — If not running, then it is a warning to check if role is enabled. Ensure that the services are started. Note: The service should be running only if the role is enabled.
If yes, pass. Otherwise, fail.
NMM client is installed on all machines participating in a farm for VSS backup. If yes, pass. Otherwise, fail. SharePoint VSS writer is registered on at least one web front-end within a farm. If yes, pass. If no, run stsadm -o
registerwsswriter. Else, it is a warning. Either SQL server writer or MSDE writer-SQL2000 is enabled for SharePoint server 2003. If yes, pass. Otherwise, fail.
The SharePoint environment is stable or not using the SharePoint server Administration tool. If yes, pass. Otherwise, fail. Staging area space requirements are fulfilled.
Note: More free space may be required if the staging is slow.
If requirements are fulfilled, pass.
For optimized backup — The number of processors on web front-end must be the size of largest site-collection.
SharePoint 2007 Shared Service Provider (SSP) is properly configured or not. If yes, pass. Otherwise, fail. For SharePoint 2007 and SharePoint 2010, the user should have administrator rights for
SharePoint, that is, the user should be the SharePoint administrator. If yes, pass. Otherwise, fail. If all components of Sharepoint are on the same machine, the machine might not be part of a
domain. If it is distributed than system should be part of domain. If a distributed farm is in domain, pass. Otherwise, fail. Check SharePoint, OSearch, SPSearch, SQL writers are in stable state. If yes, pass. Otherwise, fail.
Verify whether SharePoint VSS Writer is running under SharePoint farm administrator account. Otherwise, the writer will not be able to connect to the configuration database to obtain list of SharePoint components, and consequently SharePoint VSS backup will fail.
If SharePoint VSS writer is running under SharePoint farm administrator account, pass. Otherwise, fail.
In SharePoint 2010, if SPSearch is enabled in multiple servers of a farm, Sharepoint services and
search writers are not reported. If SPSearch is enabled only on a single server in the farm, pass. Otherwise, fail. In SharePoint 2010, check if SharePoint self privilege is enabled in configured database. If not