Search the VMware Knowledge Base (KB)
View by Article ID

Configuring Upgraded vSphere Replication Appliances to Support up to 2000 Replications (2102463)

  • 0 Ratings

Details

This article applies to upgraded vSphere Replication appliances that use an embedded database. Use the table below to determine whether your vSphere Replication deployment requires additional configuration to enable the support of up to 2000 replications per vSphere Replication appliance.

NOTE: In addition to configuring the upgraded appliance, the maximum number of replications that a vSphere Replication Management Server can support depends on a number of factors in your environment, like bandwidth, change rate, compressibility, RPO, and others. See Requirements to the Environment for the Support of Up To 2000 Replications (KB 2107869).

Deployment Scenario 2000 Replications Support
vSphere Replication 5.5 upgrade to 6.0 with embedded database After additional configuration
vSphere Replication 5.8 upgrade to 6.0 with embedded database After additional configuration
vSphere Replication 5.8 upgrade to 6.1 with embedded database After additional configuration
vSphere Replication 5.5 upgrade to 6.0 with external database Yes
vSphere Replication 5.8 upgrade to 6.0 with external database Yes
vSphere Replication 5.8 upgrade to 6.1 with external database Yes
vSphere Replication 6.0 new deployment with embedded database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.
vSphere Replication 6.0 new deployment with external database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.
vSphere Replication 6.1 new deployment with embedded database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.
vSphere Replication 6.1 new deployment with external database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.
vSphere Replication 6.5 new deployment with embedded database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.
vSphere Replication 6.5 new deployment with external database Yes, but the value for event maximum age must be changed. See point IV in the Solution section.

 

The disk size of vSphere Replication appliances earlier than 6.0 cannot accommodate the database size that is required for the support of 2000 replications. Therefore, after you upgrade an earlier vSphere Replication appliance to version 6.0, you must modify the appliance to enable the support of 2000 replications.

The purpose of this article is to explain how to add a new disk to the vSphere Replication appliance, and reconfigure the internal database (DB) used by vSphere Replication to point to the new disk that you added. This procedure is not needed for upgraded vSphere Replication appliances that are configured to use an external database.

Solution

  1. Add a new virtual disk to the vSphere Replication appliance
    1. Power off the vSphere Replication appliance by using the vSphere Client or the vSphere Web Client.

    2. Add a new virtual disk to the virtual machine by using the Edit Settings dialog box.
      A 30 GB disk is sufficient in most cases.

    3. Power on the vSphere Replication appliance.

  2. Create an ext3 partition on the newly added disk
    You use a remote console session to complete this procedure. The required commands and the expected example output for each command are listed below.
    1. Open a remote console session to the vSphere Replication appliance (SuSE Linux based).

    2. Open the disk by using fdisk:

      # fdisk /dev/sdc
       The number of cylinders for this disk is set to 3916. The value is valid, but it is larger than 1024, and could, in certain setups, cause problems with:
      • software that runs at boot time, for example, old versions of LILO.
      • booting and partitioning software from other OSs, for example, DOS FDISK, OS/2 FDISK.  

    3. Create a new partition by pressing n
      Command action
         e   extended
         p   primary partition (1-4)


    4. In the new disk prompt, press p to create a primary partition 

    5. Select partition 1 and use the default values for first and last cylinders:

      Partition number (1-4): 1
      First cylinder (1-3916, default 1):
      Using default value 1
      Last cylinder, +cylinders or +size{K,M,G} (1-3916, default 3916):
      Using default value 3916

    6. Back in the main fdisk prompt, press p to print the partition details and confirm your changes:
      Command (m for help): p
       
      Disk /dev/sdc: 32.2 GB, 32212254720 bytes
      255 heads, 63 sectors/track, 3916 cylinders
      Units = cylinders of 16065 * 512 = 8225280 bytes
      Disk identifier: 0x555dbf7f
         Device Boot      Start         End      Blocks   Id  System
      /dev/sdc1               1        3916    31455238+  83  Linux


    7. Press w to write the changes to the disk.

      Command (m for help): w
      The partition table has been altered!
       
      Calling ioctl() to re-read partition table.
      Syncing disks.


    8. Create an ext3 file system on the disk by using this command:

      # mkfs.ext3 /dev/sdc1

      mke2fs 1.41.9 (22-Aug-2009)
      Filesystem label=
      OS type: Linux
      Block size=4096 (log=2)
      Fragment size=4096 (log=2)
      1966080 inodes, 7863809 blocks
      393190 blocks (5.00%) reserved for the super user
      First data block=0
      Maximum filesystem blocks=4294967296
      240 block groups
      32768 blocks per group, 32768 fragments per group
      8192 inodes per group
      Superblock backups stored on blocks:
              32768, 98304, 163840, 229376, 294912, 819200, 884736, 1605632, 2654208,4096000
       
      Writing inode tables: done
      Creating journal (32768 blocks): done
      Writing superblocks and filesystem accounting information: done

       
      This filesystem will be automatically checked every 27 mounts or 180 days, whichever

    9. Create a mount point for the new disk by using this command:
       
      # mkdir /postgres

    10. To activate the mount point, use a text editor to add the following line to /etc/fstab.

      /dev/sdc1 /postgres ext3 defaults 1 1​

    11. Run the following command:
      # mount –a
  3. Change the default data directory that the vSphere Replication appliance uses
    1. In the remote console session to the vSphere Replication appliance, verify that the new disk is correctly mounted by running this command:
      # mount

    2. Stop the vPostgres Database by using this command:
      # /etc/init.d/hms-vpostgres stop

    3. Stop the HMS service by using this command:
      # /etc/init.d/hms stop

    4. Copy the existing DB Files to the new location by using this command:
      # cp -rp /var/lib/vrmsdb /postgres

    5. Change the default data directory in the vSphere Replication embedded database config file.
      1. Open this file with a text editor: /opt/vmware/hms/conf/embedded_db.cfg
      2. Look for these lines and change the value of EMB_DB_STORAGE

        EMB_DB_INSTALL_DIR='/opt/vmware/vpostgres/9.3'
        #EMB_DB_TYPE='PostgreSQL'
        #EMB_DB_SERVER='127.0.0.1'
        #EMB_DB_PORT='5432'
        EMB_DB_INSTANCE='vrmsdb'
        EMB_DB_USER='vrmsdb'
        EMB_DB_PASSWORD='unused'
        EMB_DB_STORAGE=' /postgres/vrmsdb ' <--- Update this line


    6. Reboot the VR appliance.

    7. Verify that the hms-vpostgres service is running by using this command:
      # service hms-vpostgres status

    8. Verify that the hms service is running by using this command:
      # service hms status

    9. Remove the old vrmsdb files by running the following command:
      # rm -rvf /var/lib/vrmsdb

  4. Change the value for event maximum age to 3 hours.
    If you plan to replicate more than 500 virtual machines, you must change the default value for event maximum age at the vSphere Replication appliance.

    1. In the remote console session to the vSphere Replication appliance, open the /opt/vmware/hms/conf/hms-configuration.xml file for editing.

    2. Change the value for event maximum age to the following:
      <hms-eventlog-maxage>10800</hms-eventlog-maxage>

    3. Restart the HMS service by running the following command:
      # service hms restart

    4. Stop VCTA service by running following command:
      # service vmware-vcd stop
      NOTE: Stopping this service interrupts the replications to and from the cloud.

    NOTE: If a connectivity issue occurs in your environment or the vSphere Replication appliance encounters a problem, the offline or downtime period should not exceed the period set in the hms-eventlog-maxage tag. After the problem is resolved, there must be enough time for the events to be delivered within the maximum age period.

Request a Product Feature

To request a new product feature or to provide feedback on a VMware product, please visit the Request a Product Feature page.

Feedback

  • 0 Ratings

Did this article help you?
This article resolved my issue.
This article did not resolve my issue.
This article helped but additional information was required to resolve my issue.

What can we do to improve this information? (4000 or fewer characters)




Please enter the Captcha code before clicking Submit.
  • 0 Ratings
Actions
KB: