Hi, I'm new at SnapCenter and after finally I got SC installed and working as well. I added a linux based HANA host and succeed to provide the HANA plugin as well. Now I have problems running the hana plugin based snapshot. As I understod, hdbuserstore key has to be (and so it has been) generated as root at the hana host and so the user within the SC Resource configuration (hana plugin settings) has to be root as well. Now if I start the hana snapshot I receive the following error: SCC-00164: Application quiesce for plug-in [hana] failed with exit code [1] and with error : Verification of HDBSQL_CMD [hdbsql] failed with error: [/bin/sh: hdbsql: command not found]. Set valid HDBSQL_CMD for the SAP HANA plug-in on this host using "Set-SmConfigSettings -Plugin -HostName hostname -PluginCode hana configSettings @{"HANA_HDBSQL_CMD"="path_to_HDBSQL_CMD"} " PowerShell cmdlet from SnapCenter Server. SCC-00161: Application unquiesce for plug-in [hana] failed with exit code [-1] and error : Verification of HDBSQL_CMD [hdbsql] failed with error: [/bin/sh: hdbsql: command not found]. Set valid HDBSQL_CMD for the SAP HANA plug-in on this host using "Set-SmConfigSettings -Plugin -HostName hostname -PluginCode hana configSettings @{"HANA_HDBSQL_CMD"="path_to_HDBSQL_CMD"} " PowerShell cmdlet from SnapCenter Server. I do not now how to start a SC Console session on my sc-host, I do not know how to initiate a cmdlet command and don't know either what this cmdlet is doing, and where. And I wonder how -in case I have a second HANA instance running on that host- I can separately configure two independant hdbsql path's for user root. actually Question 3 is not so important, may be this is clear to me, once I have the solution for 1 and 2 I hope someone can help...
... View more
On mid of June, I find the backup jobs was showing failed and warring on dashboard. After view the log, the log were showing the SnapVault relationship for source volume were failed. Also checked destination volumes didn't have the daily snapshot were replicated. May I know how can I do and which way I can solve the problem. Thanks!! ------------------------------------------------------- SnapCenter log: ErrorCode (-1), ErrorMessage (SnapVault update failed for 2 relationships: Relationship [SB0SVMN01 : NETAPP_SBSAN02_vol ==> SB1SVMN01 : NETAPP_SBSAN02_vol_sv] failed with error: SnapVault relationship for source volume [SB0SVMN01 : NETAPP_SBSAN02_vol] and destination volume [SB1SVMN01 : NETAPP_SBSAN02_vol_sv] is not healthy. Relationship [SB0SVMN01 : NETAPP_SBSAN01_vol ==> SB1SVMN01 : NETAPP_SBSAN01_vol_sv] failed with error: SnapVault relationship for source volume [SB0SVMN01 : NETAPP_SBSAN01_vol] and destination volume [SB1SVMN01 : NETAPP_SBSAN01_vol_sv] is not healthy.) ----------------------------------------------------------
... View more
we have a need to take snapshots on SQL host which have cluster configured with three nodes. it worked fine with replication. After we added a fourth node to the cluster, the snapshots failed to take on schedule with errors "No SQL resource is discovered on the host", "An error occurred while retrieving the cluster resources of type 'Network Name' The RPC server is unavailable. ". does anyone else ever had same issue? Please share your experience. 1). we only configured plugin on one host, do we have to add all four SQL hosts to the SnapCenter? 2). we configured to backup SQL instance from one host.
... View more
Has anyone had experience competing against Nexsan in general, or their Assureon product specifically? They are claiming to have a lot of the same capabilities we have and we are losing on price: * Security features comply with corporate and governmental regulatory requirements including HIPAA, CJIS, GDPR, PCI-DSS, SOX, SEC-17 and WORM * Assureon software can be implemented in a public cloud or on-premise * Data stored in the Assureon is immutable and cannot be corrupted by malicious malware https://www.nexsan.com/secure-data-vault/
... View more
When I visually checked the ACL of the file on the GUI of Windows, there was no difference between the migration source and the migration destination. However, the DACL was "Changed" in the verification of XCP. What is the cause of this happening as a verify specification?
... View more
