Unfortunately, our Application nodes running on Azure VMSS ran into issues. The installation directory and local home are inaccessible but we have the MS Azure SQL Database and shared home intact. Are there any issues if we spin up a new multi-node VMSS and connect to the existing DB and shared home? Will it cause any issues with existing crowd integrations and installed plugins? What are the precautions we must consider before doing this production?
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.