5.5
Table Of Contents
- VMware vSphere Replication Administration
- Contents
- vSphere Replication Administration
- Updated Information
- Overview of VMware vSphere Replication
- vSphere Replication Roles and Permissions
- vSphere Replication System Requirements
- Installing vSphere Replication
- Deploying Additional vSphere Replication Servers
- Upgrading vSphere Replication
- Reconfigure the vSphere Replication Appliance
- Reconfigure General vSphere Replication Settings
- Change the SSL Certificate of the vSphere Replication Appliance
- Change the Password of the vSphere Replication Appliance
- Change Keystore and Truststore Passwords of the vSphere Replication Appliance
- Configure vSphere Replication Network Settings
- Configure vSphere Replication System Settings
- Reconfigure vSphere Replication to Use an External Database
- Use the Embedded vSphere Replication Database
- Replicating Virtual Machines
- How the Recovery Point Objective Affects Replication Scheduling
- Replicating a Virtual Machine and Enabling Multiple Point in Time Instances
- Using vSphere Replication with Virtual SAN Storage
- Replicating Virtual Machines Using Replication Seeds
- Replicating a Virtual Machine in a Single vCenter Server Instance
- Configure Replication for a Single Virtual Machine
- Configure Replication for Multiple Virtual Machines
- Move a Virtual Machine to a New vSphere Replication Server
- Stop Replicating a Virtual Machine
- Reconfiguring Replications
- Performing a Recovery with vSphere Replication
- Monitoring and Managing Replications in vSphere Replication
- Troubleshooting vSphere Replication
- vSphere Replication Limitations
- Access the vSphere Replication Logs
- vSphere Replication Events and Alarms
- Solutions for Common vSphere Replication Problems
- Error at vService Bindings When Deploying the vSphere Replication Appliance
- OVF Package is Invalid and Cannot be Deployed
- Connection Errors Between vSphere Replication and SQL Server Cannot be Resolved
- Application Quiescing Changes to File System Quiescing During vMotion to an Older Host
- Configuring Replication Fails for Virtual Machines with Two Disks on Different Datastores
- vSphere Replication Service Fails with Unresolved Host Error
- Scalability Problems when Replicating Many Virtual Machines with a Short RPO to a Shared VMFS Datastore on ESXi Server 5.0
- vSphere Replication Sites Appear in the Disconnected State
- Error Recovering Virtual Machine in a Single vCenter Server Instance
- vSphere Replication RPO Violations
- vSphere Replication Appliance Extension Cannot Be Deleted
- vSphere Replication Does Not Start After Moving the Host
- Unexpected vSphere Replication Failure Results in a Generic Error
- Increase the Memory of the vSphere Replication Server for Large Deployments
- Reconnecting Sites Fails If One Of the vCenter Servers Has Changed Its IP Address
- Uploading a Valid Certificate to vSphere Replication Results in a Warning
- vSphere Replication Server Registration Takes Several Minutes
- Generating Support Bundles Disrupts vSphere Replication Recovery
- vSphere Replication Operations Take a Long Time to Complete
- vSphere Replication Does Not Display Incoming Replications When the Source Site is Inaccessible
- vSphere Replication is Inaccessible After Changing vCenter Server Certificate
- vSphere Replication Cannot Establish a Connection to the Hosts
- Anti-virus Agent in Firewall Terminates Virtual Machine Replication
- Initial Full Synchronization of Virtual Machine Files to VMware Virtual SAN Storage Is Slow
- vSphere Web Client 5.1.x Non-Functioning Option Binds vSphere Replication Traffic to a Specific vmknic
- Configuring Replication Fails After Rebuilding VRMS
- vSphere Replication Operations Run Slowly as the Number of Replications Increases
3 Enable TCP on the database instance.
4 Set a TCP port.
Option Action
Static TCP port Set the TCP port to the default of 1433.
Dynamic TCP port a Use a named instance of SQL Server. You can only use dynamic ports with a
named instance of SQL Server.
b Select the Show DB URL check box in the virtual appliance management
interface (VAMI) of the vSphere Replication appliance.
c Modify the DB URL value. Replace port=port_number with
instanceName=instance_name in the URL.
d Use the PortQuery command from a remote machine to check that the port
on which the SQL Server Browser service runs is not blocked by a firewall.
The SQL Server Browser runs on port 1434. Type the PortQuery command
in a terminal window.
PortQry.exe -n Machine_Name -p UDP -e 1434
5 Verify that the firewall on the database server permits inbound connections on the TCP port.
6 Create the vSphere Replication security login.
7 Create the vSphere Replication database and set the vSphere Replication security login as the
database owner.
8 Keep the dbo user and dbo schema settings.
Because the vSphere Replication security login is the database owner, it maps to the database user
dbo and uses the dbo schema.
Configure Oracle Server for vSphere Replication
You must configure an Oracle Server database correctly to support vSphere Replication.
You create and configure an Oracle Server database for vSphere Replication by using the tools that
Oracle Server provides.
This information provides the general steps that you must perform to configure an Oracle Server
database for vSphere Replication. For instructions about how to perform the relevant steps, see the
Oracle documentation.
Procedure
1 When creating the database instance, specify UTF-8 encoding.
2 Create the vSphere Replication database user account.
3 If they are not selected already, select the CONNECT and RESOURCE roles.
These roles provide the privileges that vSphere Replication requires.
VMware vSphere Replication Administration
VMware, Inc. 54