How to avoid exceeding the maximum number of mount points
What should be set as the maximum number of mount points (MAXNUMMP) for Data Protection for SAP HANA nodes on the Tivoli Storage Manager server ?
Backups fail with the error:
ANS0326E (RC41) This node has exceeded its maximum number of mount points.
SAP HANA behaves differently compared to SAP BR*Tools for Oracle and starts a dedicated backint process for each SAP HANA service to backup.
SAP HANA then sends the data to be backed up in one stream per service. Since SAP HANA does start a dedicated process for each stream/object to back up there will be never more than 1 session open by hdbbackint for database backups. In case of redo logs the data streamed by SAP HANA is sent to multiple destinations in parallel. Only in this case multiple sessions are utilized.
Therefore in the respective SERVER stanzas in the Data Protection for SAP HANA profile the SESSIONS options need be set so that the total of SESSIONS values add up to the chosen number of REDOLOG_COPIES (1-9).
The Data Protection for SAP HANA profile option MAX_SESSIONS then needs to be set to the sum of the SESSIONS values for all SERVER stanzas together.
In the node configuration on the Tivoli Storage Manager server(s) the MAXNUMMP option then needs to be set to at least the SESSIONS value in the respective SERVER stanza in the Data Protection for SAP HANA profile.
If in a scale-out environment the ASNODENAME client option is used to consolidate backups from several nodes under a single target nodename on the Tivoli Storage Manager server, then the MAXNUMMP option for the target node needs to be set to at least the number of mount points needed for all involved proxy nodes to work in parallel.
The following example shows the configuration for two SAP HANA partitions "A" (4 services) and "B" (1 service) where three backup copies of the redo logs should be stored:
... in the utl profile for SAP HANA :
BRARCHIVEMGTCLASS LOGMC1 LOGMC2 LOGMC3
... on the TSM server:
TSM target node: MAXNUMMP 15
TSM proxynodeA: MAXNUMMP 12
TSM proxynodeB: MAXNUMMP 3
It is advisable to choose MAXNUMMP to actually be up to two times larger than needed according to the calculation above, because a volume, which reached the EOV mark, still occupies one mount point as long as the volume is rewinding or dismounting.
|Storage Management||IBM Spectrum Protect for Enterprise Resource Planning||Data Protection for SAP HANA®||Linux||8.1.0|
More support for:
Tivoli Storage Manager for Enterprise Resource Planning
Data Protection for SAP HANA®
Software version: 6.4, 7.1.3
Operating system(s): Linux
Reference #: 1883533
Modified date: 29 March 2017
Translate this page: