Make sure the network security group follows the firewall rules.
Select the network security group to be associated with SaaS Connectors. Using a secured public subnet is more cost-efficient than a private subnet. Select the subnet where you want the SaaS Connectors to be launched. To add (or remove) a SaaS Connector, see Manage Your SaaS Connections. TIP: For better performance and redundancy, we recommend that you deploy at least two SaaS Connectors for each SaaS Connection. Enter the number of SaaS Connectors you want to deploy in the region. Select the AWS region where you have EC2 instances to protect. In the Configure SaaS Connection for AWS dialog, provide: NOTE: To prepare your AWS account for Cohesity SaaS Connector deployment in a Public or Private subnet, see AWS SaaS Connector Deployment.Ĭlick the Actions menu ( ⋮) next to the AWS account and select Setup SaaS Connection. Each SaaS Connector is an m5.xlarge AWS EC2 instance. If you want Cohesity DataProtect to protect your AWS EC2 instances using Cohesity Snapshots, you need to set up a SaaS Connection for each AWS region where you have EC2 instances to protect. Next > Your new VMware SaaS Connection is available under Use Existing Connection to register your VMware sources. Once the SaaS Connector authenticates successfully, return to the Create New Connection dialog and click Verify Connection. NOTE: It can take another few minutes for the SaaS Connector to authenticate to the Cohesity DataProtect service. Enter the Connection Token and common configuration settings and click Save.
#How to download sas ova file password#
On initial login, change the default password and log in again with your new password. NOTE: After it boots, the services in the SaaS Connector VM (including the UI) can take 4-5 minutes to start.īrowse to the SaaS Connector VM IP address that you entered in the previous step and log in as admin/admin. Enter the Network IP Address, Network Netmask, and Default Gateway. Select a datastore with at least 20 GB disk space.Į. Select the SaaS Connection configuration.ĭ. Select a compute resource for the SaaS Connector VM and click Next.ī. Then configure more settings in the next few screens:Ī. ◦ In the Deploy OVF Template wizard, enter the OVA URL or specify the location of the OVA you downloaded. ◦ Right-click an inventory object and select Deploy OVF Template. To deploy the SaaS Connector OVA in your data center: ◦ Copy the OVA URL or Download the OVA file. Prepare to deploy the SaaS Connector in your data center: Under Deployment Platform, select VMware, then select a Connection Region for your data backups. In the form, click Create New Connection. Navigate to Sources and click Register Source. To add (or remove) a SaaS Connector, see Manage Your SaaS Connections.Īll the data that a SaaS Connection handles, from your sources to the cloud storage where your backups reside, is encrypted in flight and at rest. TIP: For better performance and redundancy, we recommend that you deploy at least two SaaS Connectors for each SaaS Connection in your data center.
Once deployed, each SaaS Connector is a virtual machine that runs on a vCenter or ESXi host in your data center.
#How to download sas ova file install#
You can install a VMware SaaS Connector using an installer OVA in your VMware environment, on a vCenter or ESXi host in your data center that has access to your data sources and meets the SaaS Connection system and firewall requirements.
0 kommentar(er)
