I am trying to backup SAP HANA database which is in Azure VM by using Recovery Vault service. While running "msawb-plugin-config-com-sap-hana.sh" script file I am getting the error
Failed to determine SYSTEM_KEY_NAME: Please specify with the '--system-key' option.
Need a valid system key to create the backup key.
Please help me to resolve this error.
According to the prerequisites https://learn.microsoft.com/en-us/azure/backup/tutorial-backup-sap-hana-db#prerequisites, you have to create a key in the default hdbuserstore.
You can create it by login as ndbadm:
su - ndbadm
and add the key:
/hana/shared/NDB/hdbclient/hdbuserstore set BACKUP YOUR_HOSTNAME:30013 SYSTEM YOUR_PASSWORD
Then as a root, run the script.
After running the script, you can check again as the ndbadm user if the key AZUREWLBACKUPHANAUSER is there:
/hana/shared/NDB/hdbclient/hdbuserstore list
and delete your previously created key:
/hana/shared/NDB/hdbclient/hdbuserstore delete BACKUP
The script uses the command "runuser" (in my case ndbadm). When hdbuserstore is executed under the profile ndadm no keys is returned. You can copy the files SSFS_HDB.DAT and SSFS_HDB.KEY in the path returned by hdbuserstore LIST from a profile with valid files.
Refer to SAP Note 2853601 - Why is Nameserver Port Used in HDBUSERSTORE for SAP Application Installation.
In an MDC - nameserver port (e.g. 30013) is used in hdbuserstore instead of indexserver port (e.g. 30015) for a tenant DB.
Screenshot
Related
I am using Azure Storage Explorer to read data from my Azure storage emulator.
I can create Containers just fine and even use them, until I turn off my machine. When I turn mt machine on and start using the explorer again, I keep getting this error:
If I try and create a container with the same name as the ones I cant see, I get an error saying container already exists so the container still exists somewhere, just that my explorer can't retrieve it. And the container names are all in lowercase so not sure whats happening!
Please check and make sure to have container name and blob names are
between 3 and 63 characters .
If you are usingt proxy settings in storage explorer to connect to your account, please
verify that proxy settings are properly formatted by checking as they can be
case sensitive.
If set to Use environment variablesmake sure to set HTTPS_PROXY or
HTTP_PROXY environment variables are set as given. If these are not
correct , then it may not connect to the server properly.
After that restart the explorer .
Also check the similar issue: Unable to retrieve child resources - "The specifed resource name contains invalid characters" ยท GitHub
I made a file on Azure using "File Service" and then tried to mount it using "connect". It has given me the username: localhost\xyz.
Two questions:
why username starting from "localhost" and not with "Azure"?
why I am unable to mount as windows security not giving any error, instead keep on turning back to credentials page?
p.s. TCP port 445 working properly..
Here are a few workarounds that worked for us.
WAY-1
You can directly go to your PowerShell of your machine and paste the script that you have provided in your storage account
WAY-2
You can click on More options and select for different account and then use the storage account name prepended with AZURE\ as the username and a storage account key as the password.
WAY-3
You can create a file share directly by unchecking the connect using different credentials.
OUTPUT:
For all the above ways here is the screenshot of fileshares that got mounted.
REFERENCES:
Mount SMB Azure file share on Windows
I installed Azure cosmos db Emulator in my office laptop. First it is shows 8081 already running. I changed the port issue resolved.
But it showing Unable to add firewall rule settings. Please restart the Azure Cosmos Emulator with/NOFirewall Option.
I try with below 2 commands in CMD
Microsoft.Azure.Cosmos.Emulator.exe /NoFirewall Microsoft.Azure.Cosmos.Emulator.exe /port=1729/NOFirewall Microsoft.Azure.Cosmos.Emulator.exe [/NOFirewall] [/port=1729]
But I the issue not resolved. Please help me to solve this issue.
[1]: https://i.stack.imgur.com/sgw2G.png
Generate a new authorization key and save to the specified file. The generated key can be used with the /Key or /KeyFile options.
Microsoft.Azure.Cosmos.Emulator.exe /GenKeyFile=<path to key file
If the emulator is already running, shut it off.
Next, remove the emulator's data directory from the following path:
(C:\Users\user name\AppData\Local\CosmosDBEmulator)
Run the following command to restart the emulator:
/AllowNetworkAccess /KeyFile=generatedKey /NoFirewall /Port=#####
Please refer for the command-line parameters or to Troubleshoot issues when using the Azure Cosmos DB Emulator
Note: You can use any port you like, but make sure it isn't currently in use. For the data explorer to continue operating, you must replace your created key with the default key.
I had the same issue. Kindly check if your system has admin rights. If not you will be needing to get it by adding your id local admin list.
Open CMD
Type lusrmgr. It will redirect you to Local Users and Groups.
Enter Groups.
Open Administrator.
Select Add.
Under Enter the object names to select provide your primary email Id.
Restart.
And voila you are now the admin of your system.
I used the Azure Backup client (MARS) to back up a server he had. The server no longer exists. In the Azure portal I am unable to delete the vault because the resource group contains backup items.
I tried using Powershell but Az.RecoveryServices is not meant to be used for MARS BackupManagementType. You can Get-AzureRmRecoveryServicesBackupContainer but then Get-AzureRmRecoveryServicesBackupItem fails because there is no WorkLoadType for MARS
So I cant delete the backup items from the Portal. I cant delete backup Items using powershell and the server no longer exists so I can use the MARS agent to delete items.
You can't delete a Recovery Services vault that has servers registered in it, or that holds backup data.
To gracefully delete a vault, unregister servers it contains, remove vault data, and then delete the vault.
If you try to delete a vault that still has dependencies, an error message is issued, and you will need to manually remove the vault dependencies, including:
Backed up items
Protected servers
Backup management servers (Azure Backup Server, DPM)
Refer to this article for detailed info:https://learn.microsoft.com/en-us/azure/backup/backup-azure-delete-vault
Note: You can use Cloud Shell available in portal to achieve this. Please select PowerShell after you launch Cloud Shell.
Kindly let us know if the above helps or you need further assistance on this issue.
I am the admin of this particular azure subscription. I had to add my ssh key to a ubuntu server. But when I try to add the ssh key through "Reset Password", After sometime I'll get the following error message.
VM agent on VM 'Server' has not reported latest status for extension 'enablevmaccess'. Please verify the VM has a running VM agent and can establish outbound connections to Azure storage.
What might be the issue? How to resolve this?
Failed to reset ssh key
vmaccess is enabled
Two simple thing you might try;
Uninstall the VMAccess extension and try reset again.
Use the 'Run Command' to set/reset password.
Hope this helps.
your first error tells you exactly why this happens. vm extension needs to talk to azure storage to report extension status. if it cant - portal operations might fail (this doesnt mean the extension failed; its just unable to report actual extension status).