Suggested Cloud Cluster Security Group Rules | |||
Direction | Source / Destination | Service | Purpose |
Inbound | <SG ID of this SG> | All | Intra-cluster communication |
Inbound | Management SG or CIDR | TCP 22 | Cluster Admin CLI |
Inbound | Management SG or CIDR | TCP 443 | Cluster Admin UI |
Outbound | HotAdd Proxy CIDR | TCP 58000 | Proxy Control |
Outbound | vCenter IP | TCP 7444 | vCenter SSO |
Outbound | vCenter IP | TCP 443 | vCenter API |
Outbound | ESXi CIDR | TCP 443 | vSphere API |
Outbound | Protected vSphere VM CIDR | TCP 12800-12801 | Rubrik Backup Service |
Suggested Compute Gateway Rules | ||||
Source | Destination | Service | Applied To | Purpose |
Connected VPC | Proxy Network Segment | TCP 58000 | VPC Interface | Proxy Control |
Connected VPC | Protected VM Segment(s) | TCP 12800-12801 | VPC Interface | RBS File Restore |
Suggested Management Gateway Rules | |||
Source | Destination | Services | Purpose |
Connected VPC | vCenter | TCP 7444 | vCenter SSO |
Connected VPC | vCenter | TCP 443 | vCenter API |
Connected VPC | ESXi | TCP 443 | vSphere API |
Proxy Network Segment | vCenter | TCP 7444 | vCenter SSO |
Proxy Network Segment | vCenter | TCP 443 | vCenter API |
Proxy Network Segment | ESXi | TCP 902 | vSphere API |
Questions | Choose from the list (all that apply) Provide free text when there is no list |
What backup repositories are supported? | AWS S3, AWS EC2, AWS cross-region, on-premises object or NAS, Azure Blob, Google Cloud Storage, S3 Compliant Object |
How is backup data transmitted to the repository? | ENI |
Describe the implementation of the Datamover component | Multi Proxy |
Datamover Scale | One per SDDC to Multiple per cluster |
In large SDDCs (>500 VMs, >nTBs), your solution may scale data movers. How do you scale? | Data mover scale is determined but the number of VMs and SLA domain policy |
How are additional data movers provisioned? | Automatic |
Describe additional functionalities of image-based backups | File-based recovery App consistency via VSS App consistency via pre/postscript |
Describe if in-guest backup options are available | API |
Describe security features | Encryption at rest Encryption in transit Immutable Filesystem |
Describe network bandwidth/utilization control features | Configurable bandwidth |
Describe the design of deduplication/compression features | Source Side (VMC) |
Describe added-value services/features not listed above | Ransomware detection and rollback via Polaris Radar Data classification via Polaris Sonar |
Hybrid centralized management: Describe how on-premises and VMC backups can be managed. Do you support single management console? | Unified management for VMC, on-prem vSphere, databases, filesystems, and public cloud workloads via Rubrik’s Polaris platform |
Hybrid restore/migration mode: Describe how a VM can be restored from on-premises backup to VMC or from VMC to on-premises | |
For example, let’s say that you have a hybrid configuration. On-premise with local backup, in VMC with cloud backup. What happens if an on-premise VM is migrated to VMC? Will the backup solution automatically update the location of the repository or will the VM still be backed up on premise? | Yes. vSphere VMs can be protected, replicated, and restored between Rubrik clusters protecting VMware Cloud on AWS SDDCs and those protecting traditional VMware environments. Upon restoration to the target site, Rubrik will automatically discover the newly protected VM and apply the appropriate policy locally. |