Concepts
Prerequisites for adding hosts and installing Plug-ins Package for Linux or AIX
Suggest changes
PDFs
Before you add a host and install the plug-ins packages, you must complete all the requirements.
-
If you are using iSCSI, the iSCSI service must be running.
-
You must have enabled the password-based SSH connection for the root or non-root user.
SnapCenter Plug-in for Oracle Database can be installed by a non-root user. However, you should configure the sudo privileges for the non-root user to install and start the plug-in process. After installing the plug-in, the processes will be running as an effective root user.
-
If you are installing the SnapCenter Plug-ins Package for AIX on AIX host, you should have manually resolved the directory level symbolic links.
The SnapCenter Plug-ins Package for AIX automatically resolves the file level symbolic link but not the directory level symbolic links to obtain the JAVA_HOME absolute path.
-
Create credentials with authentication mode as Linux or AIX for the install user.
-
You must have installed Java 1.8.x, 64-bit, on your Linux or AIX host.
For information to download JAVA, see:
-
For Oracle databases that are running on a Linux or AIX host, you should install both SnapCenter Plug-in for Oracle Database and SnapCenter Plug-in for UNIX.
You can use the Plug-in for Oracle Database to manage Oracle databases for SAP as well. However, SAP BR*Tools integration is not supported. -
If you are using Oracle database 11.2.0.3 or later, you must install the 13366202 Oracle patch.
|
|
UUID mapping in the /etc/fstab file is not supported by SnapCenter. |
Linux Host requirements
You should ensure that the host meets the requirements before installing the SnapCenter Plug-ins Package for Linux.
| Item | Requirements | ||
|---|---|---|---|
Operating systems |
|
||
Minimum RAM for the SnapCenter plug-in on host |
1 GB |
||
Minimum install and log space for the SnapCenter plug-in on host |
2 GB
|
||
Required software packages |
Java 1.8.x (64-bit)Oracle Java and OpenJDK flavors If you have upgraded JAVA to the latest version, you must ensure that the JAVA_HOME option located at /var/opt/snapcenter/spl/etc/spl.properties is set to the correct JAVA version and the correct path. |
For the latest information about supported versions, see the NetApp Interoperability Matrix Tool.
Configure sudo privileges for non-root users for Linux host
SnapCenter 2.0 and later releases allow a non-root user to install the SnapCenter Plug-ins Package for Linux and to start the plug-in process. You should configure sudo privileges for the non-root user to provide access to several paths.
What you will need
-
Sudo version between 1.8.7 and 1.8.19P2.
-
Ensure that the non-root user is part of the Oracle installation group.
-
Edit the /etc/ssh/sshd_config file to configure the message authentication code algorithms: MACs hmac-sha2-256 and MACs hmac-sha2-512.
Restart the sshd service after updating the configuration file.
Example:
#Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: #Legacy changes #KexAlgorithms diffie-hellman-group1-sha1 #Ciphers aes128-cbc #The default requires explicit activation of protocol Protocol 2 HostKey/etc/ssh/ssh_host_rsa_key MACs hmac-sha2-256
About this task
You should configure sudo privileges for the non-root user to provide access to the following paths:
-
/home/SUDO_USER/.sc_netapp/snapcenter_linux_host_plugin.bin
-
/custom_location/NetApp/snapcenter/spl/installation/plugins/uninstall
-
/custom_location/NetApp/snapcenter/spl/bin/spl
|
|
If you are managing a RAC setup, the non-root user should be an Oracle user and it cannot be just any non-root OS user. |
Steps
-
Log in to the Linux host on which you want to install the SnapCenter Plug-ins Package for Linux.
-
Add the following lines to the /etc/sudoers file by using the visudo Linux utility.
Cmnd_Alias SCCMD = sha224:checksum_value== /home/SUDO_USER/.sc_netapp/snapcenter_linux_host_plugin.bin, /opt/NetApp/snapcenter/spl/installation/plugins/uninstall, /opt/NetApp/snapcenter/spl/bin/spl Cmnd_Alias PRECHECKCMD = sha224:checksum_value== /home/SUDO_USER/.sc_netapp/Linux_Prechecks.sh SUDO_USER ALL=(ALL) NOPASSWD:SETENV: SCCMD, PRECHECKCMD Defaults: SUDO_USER env_keep=JAVA_HOME Defaults: SUDO_USER !visiblepw Defaults: SUDO_USER !requiretty
SUDO_USER is the name of the non-root user that you created.
You can obtain the checksum value from the oracle_checksum.txt file, which is located at C:\ProgramData\NetApp\SnapCenter\Package Repository.
If you have specified a custom location, the location will be custom_path\NetApp\SnapCenter\Package Repository.
The example should be used only as a reference for creating your own data.
Best Practice: For security reasons, you should remove the sudo entry after completing every installation or upgrade. |
AIX Host requirements
You should ensure that the host meets the requirements before installing the SnapCenter Plug-ins Package for AIX.
|
|
SnapCenter Plug-in for UNIX which is part of the SnapCenter Plug-ins Package for AIX, does not support concurrent volume groups. |
| Item | Requirements | ||
|---|---|---|---|
Operating systems |
AIX 6.1 or later |
||
Minimum RAM for the SnapCenter plug-in on host |
4 GB |
||
Minimum install and log space for the SnapCenter plug-in on host |
1 GB
|
||
Required software packages |
Java 1.8.x (64-bit)IBM Java If you have upgraded JAVA to the latest version, you must ensure that the JAVA_HOME option located at /var/opt/snapcenter/spl/etc/spl.properties is set to the correct JAVA version and the correct path. |
For the latest information about supported versions, see the NetApp Interoperability Matrix Tool.
Configure sudo privileges for non-root users for AIX host
SnapCenter 4.4 and later allows a non-root user to install the SnapCenter Plug-ins Package for AIX and to start the plug-in process. You should configure sudo privileges for the non-root user to provide access to several paths.
What you will need
-
Sudo version between 1.8.7 and 1.8.19P2.
-
Ensure that the non-root user is part of the Oracle installation group.
-
Edit the /etc/ssh/sshd_config file to configure the message authentication code algorithms: MACs hmac-sha2-256 and MACs hmac-sha2-512.
Restart the sshd service after updating the configuration file.
Example:
#Port 22 #AddressFamily any #ListenAddress 0.0.0.0 #ListenAddress :: #Legacy changes #KexAlgorithms diffie-hellman-group1-sha1 #Ciphers aes128-cbc #The default requires explicit activation of protocol Protocol 2 HostKey/etc/ssh/ssh_host_rsa_key MACs hmac-sha2-256
About this task
You should configure sudo privileges for the non-root user to provide access to the following paths:
-
/home/AIX_USER/.sc_netapp/snapcenter_aix_host_plugin.bsx
-
/custom_location/NetApp/snapcenter/spl/installation/plugins/uninstall
-
/custom_location/NetApp/snapcenter/spl/bin/spl
|
|
If you are managing a RAC setup, the non-root user should be an Oracle user and it cannot be just any non-root OS user. |
Steps
-
Log in to the AIX host on which you want to install the SnapCenter Plug-ins Package for AIX.
-
Add the following lines to the /etc/sudoers file by using the visudo Linux utility.
Cmnd_Alias SCCMD = sha224:checksum_value== /home/AIX_USER/.sc_netapp/snapcenter_aix_host_plugin.bsx, /opt/NetApp/snapcenter/spl/installation/plugins/uninstall, /opt/NetApp/snapcenter/spl/bin/spl Cmnd_Alias PRECHECKCMD = sha224:checksum_value== /home/AIX_USER/.sc_netapp/AIX_Prechecks.sh AIX_USER ALL=(ALL) NOPASSWD:SETENV: SCCMD, PRECHECKCMD Defaults: AIX_USER !visiblepw Defaults: AIX_USER !requiretty
AIX_USER is the name of the non-root user that you created.
You can obtain the checksum value from the oracle_checksum.txt file, which is located at C:\ProgramData\NetApp\SnapCenter\Package Repository.
If you have specified a custom location, the location will be custom_path\NetApp\SnapCenter\Package Repository.
The example should be used only as a reference for creating your own data.
Best Practice: For security reasons, you should remove the sudo entry after completing every installation or upgrade. |
Set up credentials
SnapCenter uses credentials to authenticate users for SnapCenter operations. You should create credentials for installing the plug-in package on Linux or AIX hosts.
About this task
The credentials are created either for the root user or for a non-root user who has sudo privileges to install and start the plug-in process.
For information, see: Configure sudo privileges for non-root users for Linux host or Configure sudo privileges for non-root users for AIX host
Best Practice: Although you are allowed to create credentials after deploying hosts and installing plug-ins, the best practice is to create credentials after you add SVMs, before you deploy hosts and install plug-ins. |
Steps
-
In the left navigation pane, click Settings.
-
In the Settings page, click Credential.
-
Click New.
-
In the Credential page, enter the credential information:
For this field… Do this… Credential name
Enter a name for the credentials.
User name/Password
Enter the user name and password that are to be used for authentication.
-
Domain administrator
Specify the domain administrator on the system on which you are installing the SnapCenter plug-in. Valid formats for the Username field are:
-
NetBIOS\UserName
-
Domain FQDN\UserName
-
-
Local administrator (for workgroups only)
For systems that belong to a workgroup, specify the built-in local administrator on the system on which you are installing the SnapCenter plug-in. You can specify a local user account that belongs to the local administrators group if the user account has elevated privileges or the User Access control feature is disabled on the host system. The valid format for the Username field is: UserName
Authentication Mode
Select the authentication mode that you want to use.
Depending on the operating system of the plug-in host, select either Linux or AIX.
Use sudo privileges
Select the Use sudo privileges check box if you are creating credentials for a non-root user.
-
-
Click OK.
After you finish setting up the credentials, you might want to assign credential maintenance to a user or group of users on the User and Access page.
Configure credentials for an Oracle database
You must configure credentials that are used to perform data protection operations on Oracle databases.
About this task
You should review the different authentication methods supported for Oracle database. For information, see Authentication methods for your credentials.
If you set up credentials for individual resource groups and the user name does not have full admin privileges, the user name must at least have resource group and backup privileges.
If you have enabled Oracle database authentication, a red padlock icon is shown in the resources view. You must configure database credentials to be able to protect the database or add it to the resource group to perform data protection operations.
|
|
If you specify incorrect details while creating a credential, an error message is displayed. You must click Cancel, and then retry. |
Steps
-
In the left navigation pane, click Resources, and then select the appropriate plug-in from the list.
-
In the Resources page, select Database from the View list.
-
Click
, and then select the host name and the database type to filter the resources.You can then click
to close the filter pane. -
Select the database, and then click Database Settings > Configure Database.
-
In the Configure database settings section, from the Use existing Credential drop-down list, select the credential that should be used to perform data protection jobs on the Oracle database.
The Oracle user should have sysdba privileges. You can also create a credential by clicking
. -
In the Configure ASM settings section, from the Use existing Credential drop-down list, select the credential that should be used to perform data protection jobs on the ASM instance.
The ASM user should have sysasm privilege. You can also create a credential by clicking
. -
In the Configure RMAN catalog settings section, from the Use existing credential drop-down list, select the credential that should be used to perform data protection jobs on the Oracle Recovery Manager (RMAN) catalog database.
You can also create a credential by clicking
.In the TNSName field, enter the Transparent Network Substrate (TNS) file name that will be used by the SnapCenter Server to communicate with the database.
-
In the Preferred RAC Nodes field, specify the Real Application Cluster (RAC) nodes preferred for backup.
The preferred nodes might be one or all cluster nodes where the RAC database instances are present. The backup operation is triggered only on these preferred nodes in the order of preference.
In RAC One Node, only one node is listed in the preferred nodes, and this preferred node is the node where the database is currently hosted.
After failover or relocation of RAC One Node database, refreshing of resources in the SnapCenter Resources page will remove the host from the Preferred RAC Nodes list where the database was earlier hosted. The RAC node where the database is relocated will be listed in RAC Nodes and will need to be manually configured as the preferred RAC node.
For more information, see Preferred nodes in RAC setup.
-
Click OK.