Block IO refers to storage presented to servers that is not using NAS protocols such as CIFS or NFS. Block IO will utilize protocols such as FCP, iSCSI and FcoE. This section will cover the standard procedure and responsibilities of the various teams when presenting storage via Block IO protocols.
When connecting servers to Storage Network (SAN Switch) Wintel and/or Unix Platform support team must follow the following conventions:
1. Prior to connecting Servers to SAN & Storage use the NetApp IMT to verify the configuration is supported by NetApp. If the configuration is unsupported the storage team reserve the right to refuse to perform presentation as such configurations can effect storage performance and stability
2. The correct software must be installed for example FC storage presentation to Windows will require the use of DSM, Host Utilities etc.... Use the appropriate software for your platform
3. When connecting devices to the storage network you must use the same physical ports on each SAN switch
4. Prior to requesting storage you should request for the storage team zone your device at the earliest opportunity as performing zoning is an out of hours activity and therefore could impact an urgent request for storage provisioning. You must provide the storage team with the following pieces of information in order for zoning to be performed:
Note: HBA number and port number cannot be simply made up. They must follow convention of PCI address. For HBA's with only a single port, Port Number will always be Port1
iSCSI protocols
When presenting storage from Servers to Storage via iSCSI Wintel and/or Unix Platform support team must follow the following conventions:
Prior to connecting Servers to SAN & Storage use the NetApp IMT to verify the configuration is supported by NetApp. If the configuration is unsupported the storage team reserve the right to refuse to perform presentation as such configurations can effect storage performance and stability
NetApp IMT: http://now.netapp.com/matrix/
Storage Presentation using Block IO, Disk Storage
Support team responsibilities:
Manage the NetApp Storage devices themselves
Perform zoning as per QBE specifications
Communicate to Wintel team when zoning is
complete so redundancy can be tested
Enable iSCSI on storage IP interface – more
than one VLAN for MPIO purposes
Manage iGroups – where SnapDrive for Windows
is not available/suitable for iGroup management
Create volumes as per Wintel team
specification, when LUN's need to be created advise Wintel team LUN names for
them to create using SnapDrive.
NetApp Volume names are the responsibility of
the Storage team, however invite input from respective client teams.
If requested by Wintel admin, assist them with raising NetApp support incident
(provide contacts, guidance etc).
<-----------------------------
SMVI Focus
VMware Admin team
responsibilities:
SMVI initial Installation: This is a collaborative effort led by VMWare Admin
Team, calling on platform support team and Storage team for certain topics.
Details:
NOTE: Follow best practics when connecting to storage systems i.e. use storage networks for communication with SAN infrastructure, use Server Network when communicating with vCenter.
Enable the SMVI service to run with the appropriate rights / authentication
NOTE: AD Credenials
for SMVI do not require vCenter Admininstrator rights, please consult TR's
to only assign required vCenter privilages to perform necessary operations
i.e. create/destroy datastore ec...
Determine if custom user accounts are required, then inform Storage team
appropriately.
NOTE: Root credentials
should not be used when connecting to storage. Raise a request with storage
team asking them to create the SMVI specific backup account with the
appropriate API access, these API's must be determined by SMVI Team. Storage
team will only create the account as per your specification.
When a storage system administrator's user credentials change, update the
information in SMVI
Add a vCenter Server in SnapManager for Virtual Infrastructure (Since the
SnapManager for Virtual Infrastructure server communicates directly with a
vCenter Server via HTTPS to discover the data centers and datastores within
your virtual environment)
Configure vCenter Server as necessary ( so that SnapManager for Virtual
Infrastructure can connect to the virtual machine and provide access to its
contents).
Add the physical storage systems on which the active images of the
datastores and virtual machines that are managed by that vCenter Server
reside.
NOTE: Set snapshot policy as appropriate for volume size. i.e. if you want to keep 30 days backup, ensure the volume is sized for this level of retention based on daily change rate. If you require more space raise a request with storage team asking which volumes you require increasing in size and by how much.
Manage the NetApp Storage devices themselves
Enable Snapshot protection in the volumes where those datastore and virtual
machine images reside - on the direction of VMware admin. Vmware Admin then
control the snapshots of those volumes
Enable Snapmirror protection in the
volumes where those datastore and virtual machine images reside - eg activate
the snapmirror license, configure the volumes as snapmirror source volumes etc.
Vmware Admin then control the snapmirroring (and snapshot schedule) of those
volumes
If requested by Vmware admin, create custom user accounts for SMVI. A nonroot or
nonadministrator account might be required for SnapManager for Virtual
Infrastructure to access a specific storage system. in this case, you must
create a custom storage system account with a new storage system role, group,
and user
If requested by Vmware admin, assist them with raising netApp support incident
(provide contacts, guidance etc)
----------------
SnapDrive for Windows Focus
VMware Admin team responsibilities:
What SnapDrive does
SnapDrive software integrates with Windows
Volume Manager so that storage systems can serve as virtual storage devices for
application data in Windows Server 2003 and Windows Server 2008 environments.
SnapDrive manages LUNs on a storage system, making these LUNs available as local
disks on Windows hosts. This allows Windows hosts to interact with the LUNs just
as if they belonged to a directly attached redundant array of independent disks
(RAID).
SnapDrive provides the following additional features:
• It enables online storage configuration, LUN expansion, and streamlined management.
• It enables connection of up to 168 LUNs.
• It integrates Data ONTAP Snapshot technology, which creates point-in-time images of data stored on LUNs.
• It works in conjunction with SnapMirror software to facilitate disaster recovery from either asynchronously or synchronously mirrored destination volumes.
• It enables SnapVault updates of qtrees to a SnapVault destination.
Deploy SnapDrive for Windows on any Windows server, Virtual or Physical that
requires access to a NetApp LUN via iSCSI or FC protocols.
Use NetApp IMT to verify your configuration is supported checking components
such as OS, HBA, Drivers, HBA Firmware, NetApp software are all supported prior
to deployment.
http://now.netapp.com/matrix/
Determine what pre-requisite software is required i.e. Windows Hotfixes
Wintel team should use SnapDrive to perform the
following functions:
NOTE: Observe best practices with mixing hardware and software initiators particularly in relation to iSCSI setups.
When LUN's are to be presented to hosts via FC protocol in particular, Wintel team should ensure that they have the correct DSM and Host utilities kit installed in order to avoid LUN Path Misconfiguration problems.
Volume sizing for LUNs where Snapshots are
taking place must be done by the Wintel team, it is the Wintel team's
responsibility to tell the storage team the size of the volume the require. For
example a LUN of 10gb has a daily change rate of 20% and you wish to keep 5 days
of backups, therefore the Volume size for the 10GB LUN should be at least 20g
(Fractional Reserve 0%).
Schedule automated backup executions using sdcli etc...
Specify a retention policy for stored backups using sdcli etc...
Specify criteria for backup-related alert notification using sdcli etc...
Work with VMware teams to enable vCenter integration
in order to perform VMDK snapshots of VM's.
Problem determination and prevention:
Own problem determination relating the use of SnapDrive software, backup or
restore failures
If required, raise support incident with NetApp (provider of the SnapDrive
software)
Maintain a functioning Microsoft VSS
environment on the host as many problems can be due to improper VSS
configurations.
Maintain / upgrade / patch the versions of SnapDrive software as required, and
as recommended by the NetApp online guidance.
Use NetApp tools such as OntapWinDC or
Windows Event viewer to diagnose issues
Understand issues raised in the SnapDrive® 6.3 for Windows®
Installation and Administration Guide.
SnapDrive for Windows Focus, Disk Storage Support
team responsibilities:
Manage the NetApp Storage devices themselves
Create volumes for LUN's to reside in as per
Wintel team's specification. Where snapshotting is required on LUN's it is the
responsibility of the Wintel team to size the volume and notify the storage team
how large the volumes should be.
Enable Snapshot protection in the volumes
where those datastore and virtual machine images reside - on the direction of
Wintel admin. Wintel Admin then control the snapshots of those volumes
Enable Snapmirror protection in the volumes
where those datastore and virtual machine images reside - eg activate the
snapmirror license, configure the volumes as snapmirror source volumes etc.
Wintel Admin then control the snapmirroring (and snapshot schedule) of those
volumes.
Assist Wintel team with regards to iGroup
management, either pre-creating initiators for WWN's/IQN's as specified by the
Wintel team or allowing the Wintel team to create iGroups themselves via
SnapDrive.
If requested by Wintel admin, create custom user accounts for SnapDrive.
NOTE: It is NetApp best practice for a
dedicated AD account to be used for SnapDrive, naming convention should follow
clear defined standards and should be used only for SnapDrive authentication
with Software services and NetApp filers i.e. QBEEO\svc_SDW
If requested by Wintel admin, assist them with raising NetApp support incident
(provide contacts, guidance etc)
SnapManager for Exchange Focus
Wintel Admin team responsibilities:
What is SnapManager for Exchange?
SnapManager provides you an integrated data management solution for Microsoft Exchange that enhances the availability, scalability, and reliability of Exchange databases. SnapManager provides rapid online backup and restoration of databases, along with local or remote backup set mirroring for disaster recovery. SnapManager uses online Snapshot technology that is part of Data ONTAP and integrates Exchange backup and restore APIs and Volume Shadow Copy Service (VSS). SnapManager uses SnapMirror to support disaster recovery. SnapManager provides the following data management capabilities:
• Migrating Exchange databases and transaction logs to LUNs on storage systems
• Backing up Exchange databases and transaction logs from LUNs on storage systems
• Verifying the backed-up Exchange databases and transaction logs
• Managing backup sets
• Archiving backup sets
• Restoring Exchange databases and transaction logs from previously created backup sets
How SnapManager and SnapDrive work together
SnapDrive provides the underlying layer of support for SnapManager by working with the NTFS Windows file system, Windows Volume Manager, and LUNs to help you to manage resources on the storage system in the Windows environment.
NOTE: Use SnapManager for all backup-related operations. Use SnapDrive only to create and manage the LUNs and storage system volumes that contain your Exchange data.
Use NetApp IMT to verify your configuration is supported checking components such as OS, HBA, Drivers, HBA Firmware, NetApp software are all supported prior to deployment.
http://now.netapp.com/matrix/
Wintel team should use SnapManager for Exchange to
perform the following functions:
Determine volume sizing and liaise with Storage Team to provision required storage, Storage Team will only allocate volumes as per defined specification, LUN's will be created by Wintel team.
Determine what pre-requisite software is required i.e. Windows Hotfixes
Use AD accounts with appropriate privileges to perform backups on Exchange and the necessary storage functions.
NOTE: It is NetApp best practice for a dedicated AD account to be used for SnapManager for Exchange, naming convention should follow clear defined standards and should be used only for SnapDrive authentication with Software services and NetApp filers i.e. QBEEO\svc_sme
Work with VMware team to provision storage appropriately when working with Exchange servers in a virtualised environment.
NOTE: Use appropriate decision making when
provisioning disks via FC or iSCSI i.e. am I using RDM's?
Problem determination and prevention:
Own problem determination relating the use of SnapManager software, backup or
restore failures.
If required, raise support incident with NetApp (provider of the SnapManager
software)
Maintain a functioning Microsoft VSS
environment on the host as many problems can be due to improper VSS
configurations.
Maintain / upgrade / patch the versions of SnapManager software as required, and
as recommended by the NetApp online guidance.
Use NetApp tools such as OntapWinDC or
Windows Event viewer to diagnose issues
Understand issues raised in the SnapManager® 6.0 for Microsoft® Exchange
Installation and Administration Guide.
SnapManager for Exchange Focus, Disk Storage
Support team responsibilities:
Manage the NetApp Storage devices themselves
Create volumes for LUN's to reside in as per
Wintel team's specification. Where snapshotting is required on LUN's it is the
responsibility of the Wintel team to size the volume and notify the storage team
how large the volumes should be.
Enable Snapshot protection in the volumes
where those datastore and virtual machine images reside - on the direction of
Wintel admin. Wintel Admin then control the snapshots of those volumes
Enable Snapmirror protection in the volumes
where those datastore and virtual machine images reside - eg activate the
snapmirror license, configure the volumes as snapmirror source volumes etc.
Wintel Admin then control the snapmirroring (and snapshot schedule) of those
volumes.
If requested by Wintel admin, assist them with raising NetApp support incident
(provide contacts, guidance etc).
<-----------------------------
SnapManager for SQL Focus
Wintel Admin team responsibilities:
Overview
SnapManager is an SQL Server aware application that provides backup and restore functionality in an SQL Server environment. Relationship with other components of an SQL Server installation backed by a storage system: The following illustration shows the relationship between storage systems, SnapDrive, and SnapManager for Microsoft SQL Server.
How SnapManager and SnapDrive work together
SnapDrive integrates with the NTFS Windows file system and the Windows
Volume Manager to enable the management of the LUNs and VMDKs on a
storage system in a Windows environment. SnapDrive provides the underlying
layer of support for SnapManager by making these LUNs and VMDKs available
as local disks on the Windows host system. When to use SnapDrive: You can use SnapDrive only to create, connect, expand, and manage LUNs and VMDKs.
SnapDrive manages LUNs and VMDKs on a storage system, making these disks
appear as available and as ordinary local disks on the Windows host server. This
enables the server to interact with the LUNs and VMDKs as if they were directly
attached, physical disks. Having SnapDrive installed on the SQL Server is a requirement for using SnapManager.
NOTE: Use SnapManager for all backup-related operations. Use SnapDrive only to create and manage the LUNs and storage system volumes that contain your SQL data.
Use NetApp IMT to verify your configuration is supported checking components such as OS, HBA, Drivers, HBA Firmware, NetApp software are all supported prior to deployment.
http://now.netapp.com/matrix/
Wintel team should use SnapManager for SQL to
perform the following functions:
Manage and specify backup retention and develop a policy i.e. CRM database 30 days retention and vCenter database14 days retention.
Determine volume sizing and liaise with Storage Team to provision required storage, Storage Team will only allocate volumes as per defined specification, LUN's will be created by Wintel team.
Determine what pre-requisite software is required i.e. Windows Hotfixes
Use AD accounts with appropriate privileges to perform backups on SQL and the necessary storage functions.
NOTE: It is NetApp best practice for a dedicated AD account to be used for SnapManager for SQL, naming convention should follow clear defined standards and should be used only for SnapDrive authentication with Software services and NetApp filers i.e. QBEEO\svc_sql
Determine backup type based on database characteristic i.e. Simple Recovery, Full or Bulk Logged.
Work with VMware team to facilitate SMVI/SMSQL combined backups when using databases stored on VMDK's for simplified SQL deployments.
NOTE: The key differences in backup/restore
functionality available when backing up data stored on VMDK's instead of LUN's
Problem determination and prevention:
Own problem determination relating the use of SnapManager software, backup or
restore failures.
If required, raise support incident with NetApp (provider of the SnapManager
software)
Maintain a functioning Microsoft VSS
environment on the host as many problems can be due to improper VSS
configurations.
Maintain / upgrade / patch the versions of SnapManager software as required, and
as recommended by the NetApp online guidance.
Use NetApp tools such as OntapWinDC or
Windows Event viewer to diagnose issues
Understand issues raised in the SnapManager® 5.1 for Microsoft® SQL Server®
Installation and Administration Guide
SnapManager for SQL Focus, Disk Storage Support
team responsibilities:
Manage the NetApp Storage devices themselves
Create volumes for LUN's/VMDK's to reside in
as per Wintel team's specification. Where snapshotting is required on LUN's it
is the responsibility of the Wintel team to size the volume and notify the
storage team how large the volumes should be.
Enable Snapshot protection in the volumes
where those datastore and virtual machine images reside - on the direction of
Wintel admin. Wintel Admin then control the snapshots of those volumes
Enable Snapmirror protection in the volumes
where those datastore and virtual machine images reside - eg activate the
snapmirror license, configure the volumes as snapmirror source volumes etc.
Wintel Admin then control the snapmirroring (and snapshot schedule) of those
volumes.
If requested by Wintel admin, assist them with raising NetApp support incident
(provide contacts, guidance etc).
<-----------------------------
Virtual Storage Console Focus
Wintel Admin team responsibilities:
Overview
The Virtual Storage Console software provides storage configuration and monitoring using Virtual Storage Console capability, datastore provisioning and virtual machine cloning using the Provisioning and Cloning capability, and backup and recovery of virtual machines and datastores using Backup and Recovery capability. The Rapid Cloning Utility and the SnapManager for Virtual Infrastructure applications have been renamed and integrated into Virtual Storage Console as the Provisioning and Cloning and Backup
and Recovery capabilities in order to provide a single vSphere Client plug-in that provides end-toend virtual machine lifecycle management for VMware environments running NetApp storage. Because Virtual Storage Console is a vCenter Server plug-in, it is available to all vSphere Clients that connect to the vCenter Server. This is different than a client-side plug-in that must be installed on every vSphere Client. You can install the Virtual Storage Console software on either the vCenter Server or on another Windows server in your data center; do not install it on a client computer. The Virtual Storage Console software adds a NetApp icon to the Solutions and Applications panel of
the vSphere Client home page. When you select the About panel, Virtual Storage Console displays version information for each of the installed capabilities and Virtual Storage Console version information.
NOTE: Use NetApp IMT to verify your configuration is supported checking components such as OS, HBA, Drivers, HBA Firmware, NetApp software are all supported prior to deployment.
http://now.netapp.com/matrix/
Wintel team should use VSC to perform the following
functions:
Launch the FilerView GUI to create LUNs and manage storage controllers
Collect diagnostic information from the ESX hosts, storage controllers, and Fibre Channel
switches
Access tools to set guest operating system timeouts and to identify and correct misaligned disk partitions
NOTE: Although VSC offers functionality that will allow the Wintel team to be Quasi-Storage Administrators, Storage functions such as resizing datastores/volumes, enabling/performing deduplication are tasks strictly for the Storage team.
Although the scope of the VSC is vast, for our purposes it is only intended to be used as a tool to give the Wintel team a greater level of visibility of the storage rather than surrendering control.
Determine what pre-requisite software is required i.e. Windows Hotfixes
Use AD accounts with appropriate privileges to perform various functions on the vCenter servers I.e. QBEEO\svc_sql
Specifiy RBAC as appropriate to perform only the
base core VSC functions as above. Storage team will create the appropriate
accounts based on the API functionality specified by the Wintel team.
Problem determination and prevention:
Own problem determination relating the use of VSC software, backup or restore
failures.
If required, raise support incident with NetApp (provider of the VSC software)
Maintain a functioning Microsoft VSS
environment on the host as many problems can be due to improper VSS
configurations.
Maintain / upgrade / patch the versions of VSC software as required, and as
recommended by the NetApp online guidance.
Understand issues raised in the NetApp® Virtual
Storage Console 2.0.1 for VMware® vSphere™ Installation and Administration Guide
Virtual Storage Console Focus, Disk Storage
Support team responsibilities:
Manage the NetApp Storage devices themselves
Create user accounts on the system for VSC to
authenticate against based on specification to be provided by Wintel/VMware
teams. Root credentials cannot be used.
If requested by Wintel admin, assist them with raising NetApp support incident
(provide contacts, guidance etc).
<-----------------------------
------------------------------
Wintel / VMware Platform support team
Support and own and use the tools used by the
platform to integrate and schedule snapshots (Snap Manager, SMVI etc)
Support and own and use the tools used by the platform to manage LUNs (eg
SnapDrive, also Snapdrive Space reclamation)
Perform problem determination on those tools
Regularly Ensure that host platform components meet minimum supported versions
as per NetApp / n Series documentation (applies Host Bus Adapters, Multipath
Drivers, Operating system versions and so on
Manage Cifs shares permission
maintain the ACL's on the NTFS File system on the CIFS.
Note: Root permissions on NTFS when volumes are created are done by Storage;
Storage team creates volume and root cifs then wintel build structure below it
Run and manage the Antivirus configuration that serves the NSeries / NetApp device
Montior diskusage on LUNS ( stuart Driver )
Perform CIFS snapshots restores from local and SV volumes ( Stuart Driver )
Unix Platform Support team
Support and own and use the tools used by the platform to integrate and schedule
snapshots (Snap Manager, SMVI etc)
Support and own and use the tools used by the platform to manage LUNs (eg
SnapDrive)
Perform problem determination on those tools
Regularly Ensure that host platform components meet minimum supported versions
as per NetApp / n Series documentation (applies to Host Bus Adapters, Multipath
Drivers, Operating system versions and so on
Montior diskusage on LUNS ( stuart Driver )
Messaging support team (Exchange, Enterprise Vault)
Support and own and use the tools used by the platform to integrate and schedule
snapshots (Snap Manager, SME etc)
Support and own and use the tools used by the platform to manage LUNs (eg
SnapDrive)
Perform problem determination on those tools
Regularly Ensure that host platform components meet minimum supported versions
as per NetApp / n Series documentation (applies to Host Bus Adapters, Multipath
Drivers, Operating system versions and so on
Manage SME responsible for montioring snapshots,snapmirror via SME ( Stuart Driver )
Database (Polyserve, DB2 etc) team
Regularly Ensure that host platform components meet minimum supported versions
as per NetApp / n Series documentation (database Operating system versions and
so on)
Maintain the mapping documentation of High-level database "containers" or
databases down through to which N Series / netApp LUNs are used
TSM Backup/Recovery support team
TSM Backups:
Monitor and manage the backups: When a backup fails or overruns, clarify what
actions are taken place to investigate the root cause/fix the problem.
NDMP backups are run via commands issued on the TSM server. Atkins have some scripting around this which is monitored by the IDC TSM team. (Andy Wharton)
Backups using TSM BA Client (eg incremental or
Snapdiff incremental) should be monitored via Bocada and/or TSM TEC/ITM6
alerting. It depends on whether individual servers or a centralized approach for
all volumes (Atkins) is being used as to who would deal with failures. (Andy
Wharton).
TSM Restores:
Helpdesk perform TSM-based restores. They log onto the Web Client, currently on
a Domain server but eventually on the Proxy Servers. Backup & Recover team
should only need to get involved if the helpdesk had a problem?
Disagree with Restore Statement ( stuart Driver)
Above statement is accurate for Atkins. Helpdesk perform restores of individual files which need to be pulled back from TSM. End users can perform their own restores of data from snapshots BUT this can depend on how much data they need to restore. Atkins seem to prefer IBM to do this from TSM, perhaps more than they should. (Andy Wharton)
TSM Restores for NDMP Netapp volume backups are performed by the TSM Backup/Recovery Team ( Stuart Driver)
Any restores should always be to a temporary area and then the data copied back to the primary area. This avoids accidental overwrite of data (particularly as NDMP restore seem to perform pre-restore activities). (Andy Wharton)
Service / Help Desk team
perform TSM-based restores
Disagree TSM based restores performed by client teams or Backup and rcovery team ( Stuart Driver)
This is correct for Atkins. (Andy Wharton).
Operations, Monitoring team
Receive Operations Manager alert definitions from storage team, including any
exceptions
Implement alerting based on those definitions
Enterprise Capacity and Performance Management
team
Capacity management:
Track and report on the overall usable Disk
capacity and freespace remaining for growth. Estimate when current capacity will
be exceeded
Track and report on the savings achieved through use of deduplication
Receive new storage capacity demands and early notifications and estimates from
requestors (RFS managers, architects and solutioners)
Receive and approve Storage Request forms from requestors
Maintain Demand Tracker spreadsheet and Capacity Model spreadsheet to assist
capacity management
Work with Storage team to agree where new storage requests should be provisioned
(which aggregates etc)
Hold meetings with Storage team and Service Management to review the request
pipeline to pre-empt any potential shortfalls at a component and NetApp level.
This will also review organic growth and other factors that could lead to
additional requirements or changes.
Performance management
Use Performance data gathered by Operations
Manager and Server-based SRM to help diagnose performance problems
Identify storage performance issues below and
work with Storage/Client teams to resolve:
Hardware & Facilities Management team
Perform power connections for new disk shelves
Other existing documents to review:
A draft that I need to finalise, covering IBM vs NetApp vs Customer responsibilities. Attached here:
QBE NetApp Storage R&Rs V5.doc
>>>>>>>>>>>>> From a BeNeLux Backup and Recovery document: Notes://D06DBL002/
SSO BeNeLux Backup & Recovery Roles & Responsibilities v1.xls
Columns were impossible to paste.. they are supposed
to show:
- Account & Service Management
- SSO Storage team
- Platform Teams (pSeries/xSeries/iSeries/
- Database/Application support teams
- Other Team specified in Comment field
and Letters mean:
RASCI model
R (Responsible) Executing the work. Give account to the Person/ Team who is
accountable.
A (Accountable) Person / Team who is accountable, Empowered to make the final
judgement. Accountable includes Responsible (if not seperately defined).
S (Supportive) Person / Team who give support
C (Consulted) Person/ Team beforehand consulted, two way communication and
mandatory.
I (Informed) Person / Team informed on results/status, one way communication and
mandatory.
Setup/Configure Snapmirror Relations A
Setup/Configure Snapvault relations A
Setup/Configure Snapshot backups on Filer (Online Snapshots) A
Install/Configure Snapdrive C A
Create Storage Volumes/Qtrees for use with Snapdrive A C
Create LUNs via Snapdrive A S
Create Snapshots (Snapdrive) A S
Install/Configure Snapmanager by Platform Team C A
Install/Configure Snapmanager by Database/ Application support Team C A
Create Backups via Snapmanager by Platform Team C A
Create Backups via Snapmanager by Database/ Application support Team C A
Setup/Configure Syncmirror A C C
Monitor Snapmirror Scheduled Updates A
Monitor Snapvault schedules updates A
Monitor Snapshot backups on Filer (Online Snapshots) A
Monitor Snapshots (Snapdrive) by Platform Team A S
Monitor Snapshots (Snapdrive)by Database/ Application support Team A S
Monitor Syncmirror A
Restore Volume from snapmirror A R C C
Perform Restore from Snapvault A S R
Perform Restore from Snapshot backups (Online Snapshots) A S I
Perform Restore via Snapmanager by Platform Team A S I
Perform Restore via Snapmanager by Database/ Application support Team A S I
Perform Restores via Snapdrive by Platform Team A S I
Perform Restores via Snapdrive by Database/ Application support Team A S S I
---------------
Also:
Americas SRM for Disk and Filesystem Server DRAFT_4142009.doc from Patrick Grob. Attached here:
Nseries BPG Americas SRM for Disk and Filesystem Server DRAFT_4142009.doc
Also - even older:
SMD vs Storage v-EMEA.PPT from Patrick Grob. Attached here:
nseries BPG SMD vs Storage v-EMEA.ppt
Triage Template - How to troubleshoot issues accessing the Filer over CIFS
Use the questions in this Technical Triage Template to narrow down your issue. This will improve case resolution times.
If RSA (Remote Support Agent) is not enabled, then request an AutoSupport.
If the issue persists, use the Support Report feature and sent HTML file generated to IBM
Were there any changes?
Check the messages logs at the time of the issue's start for errors.
Is LDAP configured in the options?
If not, consider running the CIFS setup.
What corresponding errors are seen on the filer?
What errors are seen in the /etc/messages logs?
What is the qtree security style set to?
Are the users and the filer in the same domain?
If the issue is affecting all users:
Is the filer's domain
membership okay?
filer> cifs domaininfo
Is the share set up
properly?
filer> cifs shares
Can the users ping the filer by hostname and IP address?
Can the hosts be pinged from the filer by hostname and IP address?
If any pings fail, use the nslookup command. Perform nslookup on hostnames and IP Addresses. Ifnslookup fails, go to the DNS template.
Can the hosts ping the filer by name and IP address?
Can the filer ping the hosts by hostname and IP address?
What error is the user seeing on the client?
What error is seen on the filer?
Are all affected users in a common Active Directory Group?
Does this group have the proper share level and file system level permissions?
Can the filer ping the host by hostname and IP address?
Is the user logged into the host with a valid domain account?
What errors is the user seeing on the client?
What errors are seen on the filer?
Does the user have the correct share level and file system level permissions?
Can the user connect to the filer using different credentials?
Enable options
cifs.trace_login (remember to disable when troubleshooting to keep
excessive logging to a minimum)
Enable options cifs.trace_dc_connection (
Have the client attempt access before gathering ASUP in order to collect cifs trace logging.
Generate a new AutoSupport.
If RSA is not enabled, then from the filer, use filer> options autosupport.doit now
If the user cannot retrieve
the adtlog.evt file due to the CIFS issue, they can turn on FTP to get
the file (if they are not using FTP already)
options ftpd.enable on
options ftpd.dir.override /vol/etc/log
advanced datacollection at L2 request only for advanced troubleshooting:
Attempt to connect to the filer from the client:
Stop the packet trace:
filer> pktt stop all
Troubleshooting
Vscan/Fpolicy
PBLK Exhaustion
Oplocks
Widelinks
Multi-Protocol Permissions
2. When did the issue start?
3. Were there any changes?
4. Is the issue affecting all users, a group of users or one user?
5. Are the users and the filer in the same domain?
6. What is the exact error they are reporting (get a screen shot of of the error by pressing Ctrl+Print Screen)?
If 'ping by IP' fails, the issue is likely to be related to network connectivity between the client and filer. Check for issues like Firewall, WAN Accelerators, NAT Devices, and other components associated with the network.
If 'ping by IP' is successful but ping by Name fails, have the customer check the DNS configuration of the client
If pinging the filer by both name and IP Address are successful, move on to test authentication.
1011076: How to perform Windows authentication and Windows-to-UNIX usermapping
1012304: How to troubleshoot Microsoft Client permission issues
Triage Template - How to troubleshoot OnCommand Core Package issues
General Information:
The OnCommand product is divided into two components:
OnCommand Host Package (VMware plug-in integrates with OnCommand Core to allow for policy-based backup and restore). See the OnCommand Host Package triage template if the problem is suspected to be with that component.
System requirements for the OnCommand Core Package are described in the IBM Interoperability Matrix .
Always refer the product Release Notes and other product documents on the IBMSupport site for product details, best practices and additional system requirements.
Did this configuration ever work? If yes, when did it stop working?
What is the frequency of the failure? (How often, is it intermittent?)
Does it work in another setup/ configuration? (For example, a lab reproduction).
What changed since it worked previously?
When did the issue occur? Be as specific as possible, with the date and time; this will help NetApp when examining the log files.
What other errors, if any, are observed?
Does the issue affect every storage controller, some storage controllers, or only one storage controller? Identify which ones, by name, serial number and IP address.
Does the issue affect all the OnCommand Host Package clients, some OnCommand Host Package clients, or only one OnCommand Host Package client? Identify the specific client(s) by name and function.
Has isolation of the issue been attempted, such as suspending other services or operations to simplify the environment? Be as detailed as possible to establish timelines for the activity.
3. Are you running OnCommand Standard or the Express edition? Are you running previous release of Operations Manager (if so, what is the release)?
4. Which release of Data ONTAP is the affected storage controller running?
5. Are you running a supported configuration as specified in the OnCommand Core and Host Package Installation and Setup Guide and/ or the IBM Interoperability Matrix ?
6. Does the OnCommand server meet the minimum requirements as specified within the OnCommand Core and Host Package Installation and Setup Guide and/or NetApp Interoperability Matrix Tool?
7.
Is the DataFabric Manager
server deployed on a system that is running no other applications?
Note: Best practices and product documentation indicate that the
DataFabric Manager server be the only application running on the server.
8. If OnCommand worked properly before the reported behavior, were any changes made to the storage system or the OnCommand server, such as patches to the host OS, product reconfiguration, network, or other maintenance?
9. Is there a firewall installed on the network that could be affecting communication between the storage system and the DataFabric Manager server?
10.
Could this be a browser
issue? Are you using one of the supported browsers? Have you tried
clearing the browser cache?
Note: OnCommand Core Package supports a reduced set of browser and
versions as compared to the existing DFM product. Check the IBM Interoperability
Matrix for
a list of supported browsers and versions.
11. Does the environment include OSSV?
Which is the version of the NetApp Host Agent that is installed on the OSSV server(s)?
If the reported behavior is specific to OSSV only, switch to the OSSV template.
2. Download and extract the DataFabric Manager Data Collector (dfmdc) from the Utility Toolchest in the Downloads link in the NetApp Support site, to the DataFabric Manager server, and run it per instructions on the download page. If the host is Windows, dfmdc must be run as Administrator from the CLI and not be impacted by UAC. Right-click the command prompt shortcut, and select Run as Administrator. Navigate to the directory where the dfmdc data files were extracted and begin the data collection. The dfmdc tool creates a single file archive as the output.
3. Collect the Host Services information from the DataFabric Manager server. Archive/ ZIP the following into a single file named hostserviceinfo, and add the appropriate extension.
dfm hs diag <hostserviceID> (column one from dfm hs list is the ID)
dfm hs controller list
dfm hs plugin list
dfm vmdatastore list –a
dfm vcenter list –a
dfm hypervisor list –a
dfm datacenter list –a
dfm vdisk list -a
6. Download and run the Data Collection Tool for Windows (ONTAPWinDC) from the Utility Toolchest in the Downloads link in the NetApp Support site, to each host involved in the issue (each host would be where the OnCommand Host Package was installed for integration with this DataFabric Manager server).
7. Collect the following logs from the same hosts where ONTAPWinDC was executed. Archive/ ZIP the following into a single file named hostpkglogs, and add the appropriate extension.
C:\Program Files NetApp\OnCommand Host Package\VMware UI Plugin\log\*
C:\Program Files
NetApp\OnCommand Host Package\SnapDrive\snpdrvdbg.
C:\Program
Files\NetApp\DataFabric\Agent\
/opt/NTAPagent/ on Solaris and Linux
Linux/ Solaris: ntap_agent query and ntap_agent version
Collect ntap_agent.log, ntap_
Combine all files/ output into a folder named 'nha' and upload the archive per Section - 3: Sending Data to NetApp, below.
C:\Program Files\NetApp\DataFabric\
<dir_where_the_downloaded_
If present, all hs_err_*****.log files