Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Vault deployment template doesn't include separate storage drive for vault data. #355

Open
anton-fridrikh opened this issue Mar 2, 2023 · 0 comments

Comments

@anton-fridrikh
Copy link

anton-fridrikh commented Mar 2, 2023

Summary

The new feature is released with Vault v13: Until now, as part of the PAM on cloud deployment process, the Vault application, metadata and data have been installed on the C: drive. In this version, the Vault deployment process has been updated to deploy the Vault data and metadata on a different drive. This change improves the Vault storage capabilities that were, until now, limited to 2 terabytes due to the C: drive deployment.

This feature requires update of Vault and DR components deployment template(ARM template) - separate storage drive should be added to VM during deployment. Otherwise the deployment of VHD image will fail cause the second drive is not found.

See the support case 03267025

Steps to Reproduce

Run the deployment of vault server vhd image using existing ARM template.

Expected Results

Deployment should succeed.

Actual Results

Deployment fails with error: ITADB338S Missing or invalid Staging area directory in db parameter file ITADB369I utility terminated.

image003

Reproducible

  • [ X] Always
  • [ ] Sometimes
  • [ ] Non-Reproducible

Version/Tag number

Version 13.0

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

2 participants