Foundations to a Good GRAX Deployment
While the GRAX webapp interface is the main interface to backing up, protecting, and retaining your data, it's all powered by a single-tenant backend service that depends on an array of infrastructure components to perform successfully.
For a recap of GRAX features, business cases, or deployment options, see our product documentation.
The basic architecture of GRAX is:
- Persistent Blob Storage
- Persistent Indexed Storage
- External Connectivity
- Network Security Management
The specific implementations of these simplistic labels can vary in both substance and complexity depending on implementation path chosen, platform of choice, and restrictions/regulations in place on all involved parties.
The guides in this section help explain the options you have in implementing GRAX, as well as enable your team to design, implement, and support the infrastructure yourself if so required.
Operating outside the scope of these limitations causes issues with data integrity, data loss, contractual agreements, and general service availability:
- Only one instance of GRAX may be running for a given license.
- Only one instance of GRAX may be talking to the storage bucket and the Database.
- Egress to
hq.grax.commust be available at all times.
- Storage bucket performance must be on par with documented S3 performance metrics.
GRAX is usually run inside a cloud provider account as part of an existing corporate cloud presence. You can either use the AWS Marketplace to quickly deploy GRAX, build your own infrastructure in any public cloud provider, or host privately yourself. For more information about setup and installation, see the following guides:
If you have any questions after reviewing this documentation, feel free to contact GRAX Support.
Updated about 2 months ago