Infoscale DR Manual Configuration
Infoscale DR Manual Configuration
Contents
About this document ......................................................................................................................................... 3
Changing the application service group and the replication service group configurations ................... 7
Page 2 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
Page 3 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
2. On the New Dynamic Disk Group panel, provide the following input:
a. In the Group name text box, specify a name for the disk group.
b. Select Create cluster group.
c. Select the required disks from the Available disks box and click Select.
d. Click Next.
3. Follow the wizard prompts through the Finish page to complete the workflow.
Creating volumes
1. In the VEA tree view, right-click the disk group you just created and click New Volume.
Page 4 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
2. On the Assign Disks for Volume panel, provide the following input:
a. Select the disk group from the Group name drop-down list.
b. Select the appropriate Site Preference option.
c. Select the required disks from the Available disks box and click Select.
d. Click Next.
Page 5 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
a. In the Volume name text box, specify a name for the volume.
b. Specify the size of the volume.
c. Select the layout of the volume.
d. In the Mirror Info section, select Mirrored and use the Total Mirrors field to specify the
number of disks on which you want to mirror the volume data.
e. Click Next.
4. On the Add Drive Letter and Path panel, select the drive letter and click Next.
5. Follow the wizard prompts through the Finish page to complete the workflow.
Page 6 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
Configuring replication
To configure data replication, you must first configure the VxSAS service and then configure the
replicated data set (RDS) on all the cluster nodes at both sites.
For details about these configuration tasks, refer to the Volume Replicator Administrator’s Guide
applicable to your InfoScale version, for example: Volume Replicator 7.4 Administrator's Guide –
Windows.
1. For the Lanman resource in the application service group, set the DNSOptions attribute to
PurgeDuplicate.
A sample Lanman resource in the main.cf (cluster configuration) file should look like:
Lanman SG-LanmanRes (
VirtualName = LANMANPRI
IPResName = SG-IP
DNSUpdateRequired = 1
ADUpdateRequired = 1
DNSCriticalForOnline = 1
ADCriticalForOnline = 1
DNSOptions = { PurgeDuplicate }
)
Page 7 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
2. Create a replication service group with the same SystemList attribute value as that of the
application service group.
Adding resources
1. Copy the VMDg resource from the application service group to the replication service group
and then delete it from the application service group.
2. On the replication service group, perform the following tasks:
a. Add the IP resource and update the Address, SubNetMask, and MACAddress attributes.
Add a MACAddress value for each system.
b. Add the NIC resource and update the MACAddress attribute for each system.
Page 8 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
3. On the application service group, add the RVGPrimary resource and update the
RvgResourceName attribute with the value of the VvrRvg resource name created in the
replication service group.
4. Bring both the service groups online.
1. Set the application service group to have an online local hard dependency on the replication
service group.
Page 9 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
2. Set the MountV resource in the application service group to depend on the RVGPrimary
resource.
Page 10 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
4. Save the configuration for these changes to reflect in the main.cf file.
1. At the DR site, stop Cluster Server (VCS) by running the hastop -all -force command.
2. Copy the application service group details from main.cf at the primary site and add them to
main.cf at the DR site.
Make sure that you also copy over the lines related to the service group dependencies.
Then, make the following changes:
3. Copy the replication service group details from main.cf at the primary site and add them to
main.cf at the DR site.
Make sure that you also copy over the lines related to the service group dependencies.
Then, make the following changes:
a. Update the IP resource attributes to include the MACAddress and the IP address details of
each of the DR cluster nodes.
b. Similarly, update the NIC resource attributes to include the MACAddress details of the
each of the DR cluster nodes.
c. Update the DGGuid attribute of the VMDg resource with the DiskGroup ID, which you can
identify by running the vxdg list command.
4. Run the hacf -verify <location_of_main.cf> command to ensure that the main.cf file does not
have any syntax errors.
5. Start VCS by running the hastart -all command.
6. At both sites, configure the application service group as global.
Page 11 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
In the Java GUI, right-click the application service group and click Configure As Global.
Alternatively, you can run the following commands sequentially to make the application service
groups global:
Page 12 of 14
Manual Configuration of InfoScale Disaster Recovery Setups for Applications
7. From VEA, use the File > User Manager > New User option to add the Group Operator privilege
on the service groups for the cluster nodes at both sites.
Note: The replication service group remains online at both sites and the application service group
remains online only at the primary site.
3. On the Change Replication Settings dialog box, use the Primary side IP and the Secondary side
IP drop-down lists to select the appropriate IP addresses. These addresses are configured while
adding the IP resource to the replication service group.
Page 13 of 14
This page is intentionally left blank.
Arctera helps organizations around the world thrive by ensuring they can trust, access, and illuminate their data from creation to retirement.
Created in 2024 from Veritas Technologies, an industry leader in secure multi-cloud data resilience, Arctera comprises three business units: Data
Compliance, Data Protection and Data Resilience. Arctera provides tens of thousands of customers worldwide, including 70% of the Fortune
100, with market-leading solutions that help them to manage one of their most valuable assets: data.
Learn more at www.arctera.io. Follow us on X @arcteraio. For global contact information visit arctera.io/contact.
Copyright © 2025 Arctera. All rights reserved. Arctera and the Arctera Logo are trademarks or registered trademarks of Arctera or its affiliates in
the U.S. Other names may be trademarks of their respective owners.