BYO | How can I enable the Microsoft SQL Server instant access feature on BYO after storage is configured or upgraded without the nginx service installed? | Perform the steps in the following order: Install the required nginx service version. Ensure that the new BYO nginx configuration entry: /etc/nginx/conf.d/byo.conf is part of the HTTP section of the original: /etc/nginx/nginx.conf file. Run the command: /usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
|
BYO | How can I resolve the following issue in the vpfs-config.log file that is raised from:
Verifying that the MSDP REST API is available via https on port 10087 | Perform the steps in the following order: Install the policycoreutils and policycoreutils-python packages through the YUM tool. Add the following rules that SELinux for Nginx requires to bind on the 10087 port. Run the following command: /usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
|
BYO | Instant Access for BYO uses a self-signed certificate by default and only supports *.pem external certificate. How do I replace it with a certificate signed by external CA (*.pem certificate), if required? | To configure the external certificate, perform the following steps. If the new certificate is already generated (the certificate must contain long and short host names for the media server), go to step 4. Create the RSA public or private key pair. Create a certificate signing request (CSR). The certificate must contain long and short host names for the media server. The External Certificate Authority creates the certificate. Replace <PDDE Storage Path>/spws/var/keys/spws.cert with the certificate and replace <PDDE Storage Path>/spws/var/keys/spws.key with the private key. Run the following command to reload the certificate: /usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
|
BYO | How can I disable media automount for the instant access live mount share in gnome? If the automount is enabled, the source folder is mounted from the live mount share in gnome and smaller disks appear. In this scenario, the instant access feature does not work properly. The mounted disk content source is from the .../meta_bdev_dir/... folder under live mount share, while the mount target is in the /run/media/... folder. | Follow the guideline to disable the gnome automount: https://access.redhat.com/solutions/20107 |
BYO | How can I resolve the following issue in the /var/log/vpfs/vpfs-config.log file? **** Asking the NetBackup Webservice to trust the MSDP webserver (spws) ****
/usr/openv/netbackup/bin/nblibcurlcmd failed (1):
| Perform the steps in the following order: Ensure that your NetBackup primary server is up and there is no firewall blocking the connection between the NetBackup primary server and storage server. Run the following command on storage server to verify the connection status: /usr/openv/netbackup/bin/bpclntcmd -pn After the NetBackup primary server is up and connection between the NetBackup primary server and storage server is allowed, run the following command: /usr/openv/pdde/vpfs/bin/vpfs_config.sh --configure_byo
|
BYO and Flex Appliance | How can I enable host-based authentication and secure logon for Samba share so that the SQL Server instant access works on specific windows clients? | Perform the steps in the following order: In the storage server (one time operation) where the Samba share is exported from: For each Windows client, where the Samba share is accessed using the earlier credentials, save the credentials in the credential manager. To save the Samba credentials on a Windows client, open go to . In , enter the storage server domain name. Enter the Samba username and password. Ensure that the username is same as the user credentials that you created for Samba. Click and ensure that you can access <storage server domain name> without a logon prompt.
|
NetBackup Appliance | How can I enable host-based authentication and secure logon for Samba share so that the MSSQL instant access works on NetBackup Appliance and Windows clients? | Perform the steps in the following order: In the storage server (one time operation)
where the Samba share is exported from,
create new local user credentials for Samba
with the following Appliance CLISH path: In each Windows client, where the Samba
share is accessed using the earlier
credentials, save the new local user
credentials in the credential manager.
For Appliance, the smb.conf file configuration already contains map to guest = Never. The local users are added to Samba database automatically and the Samba password is the same as the logon password. The Windows clients can access the appliance's Samba share using credentials of the appliance's local users. Perform the steps in the following order: To manage appliance local users, go to the following CLISH path: To save the Samba credentials on a Windows client, open go to . In , enter the storage server domain name. Enter the Samba username and password. Click and ensure that you can access <storage server domain name> without a logon prompt.
|
