Assure MIMIX for AIX®

Assure MIMIX for AIX User Guide

Version 5.2
 Notices

Assure MIMIX for AIX User Guide

December 2023
Version: 5.2.04.00
Copyright 2003, 2023 Precisely.
Precisely
1700 District Ave Ste 300
Burlington MA 01803-5231
USA
Precisely provides no expressed or implied warranty with this manual.

Trademarks
See www.precisely.com for information about our valuable trademarks.
The following are trademarks or registered trademarks of their respective organizations or companies:
• AIX, AIX 5L, AS/400, DB2, eServer, FlashCopy, IBM, Informix, i5/OS, iSeries, MQSeries, OS/400, Power,
PowerHA, System i, System i5, System p, System x, System z, and WebSphere—International Business
Machines Corporation.
• Adobe and Acrobat Reader—Adobe Systems, Inc.
• HP-UX—Hewlett-Packard Company.
• Teradata—Teradata Corporation.
• Intel—Intel Corporation.
• Linux—Linus Torvalds.
• Excel, Internet Explorer, Microsoft, Windows, and Windows Server—Microsoft Corporation.
• Mozilla and Firefox—Mozilla Foundation.
• Java, Solaris, Oracle—Oracle Corporation.
• Red Hat—Red Hat, Inc.
• Sybase—Sybase, Inc.
• UNIX and UNIXWare—the Open Group.
All other brands and product names are trademarks or registered trademarks of their respective owners.
Support
Getting technical support: Customers with a valid maintenance contract can get technical assistance via
Support. There you will find product downloads and documentation for the products to which you are entitled,
as well as an extensive knowledge base.

Note: Some screenshots in this User Guide may not reflect the most recent product names.
Contents
Chapter 1 Overview of Data Replication Concepts 15
Introduction............................................................................................................... 15
Roles in the system architecture .............................................................................. 16
Assure MIMIX for AIX replication groups .............................................................. 16
Assure MIMIX for AIX clusters .............................................................................. 16
Assure MIMIX for AIX file container ...................................................................... 16
Assure MIMIX for AIX datatap............................................................................... 17
Assure MIMIX for AIX journal ................................................................................ 18
Support for non-root user ownership and permissions for protected Logical Volumes
19
Support for data encryption in Assure MIMIX DR for AIX ..................................... 19
Assure MIMIX for AIX agents ................................................................................... 20
LCA agent ............................................................................................................. 20
Super transaction and RWB in the LCA log file.................................................. 20
ABA agent ............................................................................................................. 20
AA agent................................................................................................................ 21
RA agent ............................................................................................................... 21
Replication................................................................................................................ 22
Journal configuration ................................................................................................ 22
Production journal ................................................................................................. 23
Recovery journal ................................................................................................... 23
Recovery log sizing ............................................................................................ 23
Log file configuration ................................................................................................ 24
Log size estimate .................................................................................................. 24
Number of logs ...................................................................................................... 24
Assure MIMIX for AIX snapshots ............................................................................. 25
Recovery .................................................................................................................. 26
Assure Unified Interface ........................................................................................... 26
Assure MIMIX for AIX with the Assure UI portal....................................................... 27
Assure MIMIX for AIX with the command line interface ........................................... 27
Chapter 2 Planning your Environment 29
Allocating space for Assure MIMIX for AIX logs and journals .................................. 29
Guidelines for production journal size ...................................................................... 30
Production journal size estimate 1 ........................................................................ 31
Production journal size estimate 2 ........................................................................ 31
Production journal size estimate 3 ........................................................................ 31
Production journal size best estimate.................................................................... 31
Guidelines for recovery journal size ......................................................................... 32
Recovery journal size estimate 1 .......................................................................... 32
Recovery journal size estimate 2 .......................................................................... 32
Recovery journal size estimate 3 .......................................................................... 32
Guidelines for volume groups................................................................................... 33
Guidelines for selecting volumes to be protected..................................................... 33
Guidelines for snapshot journal size ........................................................................ 34
Guidelines for log size .............................................................................................. 34
Determining storage requirements ........................................................................... 35
Application information checklist .............................................................................. 37
Database information checklist ................................................................................ 37
Domain name server checklist ................................................................................. 38

3 Assure MIMIX for AIX User Guide v5.2.04.00

 Network information checklist................................................................................... 38
Storage information checklist ................................................................................... 38
General information checklist ................................................................................... 39
Chapter 3 Using the Sizing Tool to Calculate LFC Size 41
Overview of LFC sizing ............................................................................................ 41
System requirements for the sizing tool ................................................................ 41
Installing the sizing tool ......................................................................................... 41
Running the sizing tool from the Assure MIMIX for AIX Sizing Tool GUI .............. 42
Introduction tab................................................................................................... 42
Config and Run tab ............................................................................................ 44
View and Analyze Log tab.................................................................................. 46
View Chart tab.................................................................................................... 48
Running the sizing tool script from the command line........................................... 49
sztool script command options ........................................................................... 52
Chapter 4 Supported Configurations 53
Replication using 4096 byte or 512 byte disk block sizes ........................................ 53
Local CDP Solution configuration............................................................................. 54
WAN replication with no local CDP configuration..................................................... 54
Broadcast replication configuration .......................................................................... 55
Local bi-directional replication configuration ............................................................ 55
Supported Assure MIMIX for AIX configurations...................................................... 56
Production server and recovery server configuration............................................ 56
Production to recovery configuration..................................................................... 56
Assure MIMIX HA for AIX configuration and resources not supported .................... 57
Upgrading from GeoCluster v3.6 to Assure MIMIX HA for AIX ................................ 57
Chapter 5 Installation Procedures 59
Overview .................................................................................................................. 59
System requirements for Assure MIMIX for AIX....................................................... 60
Operating system requirements ............................................................................ 60
Time synchronization (xntpd) requirement ............................................................ 61
Disk space and memory requirements.................................................................. 61
Network requirements ........................................................................................... 62
Archiving products supported................................................................................ 62
Assure UI portal and portal application system requirements .................................. 62
Assure MIMIX for AIX installation components ........................................................ 63
Assure MIMIX for AIX installation wizard prerequisites......................................... 63
Before you install...................................................................................................... 64
Important licensing information ................................................................................ 64
Request license keys from AIX or Windows.......................................................... 64
License file considerations .................................................................................... 66
Licensing notes: ................................................................................................. 66
Installing Assure MIMIX for AIX using the installation wizard................................... 66
Install a new instance of Assure MIMIX for AIX .................................................... 67
Define user groups ............................................................................................. 69
Install MIMIX for AIX portal application only.......................................................... 69
User roles ........................................................................................................... 70
Reinstall Assure MIMIX for AIX ............................................................................. 71
Upgrade Assure MIMIX for AIX ............................................................................. 73

Assure MIMIX for AIX User Guide v5.2.04.00 4

 Using smit to install Assure MIMIX for AIX, the Assure UI server, and the portal appli-
cation..................................................................................................................... 75
Step 1. Request a License ................................................................................. 76
Step 2: Install Assure MIMIX for AIX, the Assure UI server, and the portal applica-
tion................................................................................................................... 76
Installing using native interface commands.............................................................. 77
Installing Assure MIMIX for AIX, Assure UI server, and the portal application on the
same node.......................................................................................................... 77
Installing Assure MIMIX for AIX.......................................................................... 77
Installing Assure Unified Interface ...................................................................... 78
Installing the Assure MIMIX for AIX portal application ....................................... 78
Installing the Assure UI server and the portal application on a separate node ..... 78
Installing Vision Common ................................................................................... 78
Installing Assure Unified Interface ...................................................................... 78
Installing the Assure MIMIX for AIX portal application ....................................... 79
Define user groups ............................................................................................. 79
User roles ........................................................................................................... 79
Log files ................................................................................................................. 79
Run the validate_license command ...................................................................... 79
License expiration ................................................................................................. 80
Uninstall Assure MIMIX for AIX ............................................................................... 81
Using smit to uninstall Assure MIMIX for AIX........................................................... 83
Installing the Assure UI server and the portal application on Windows.................... 83
Uninstalling the Assure UI server and the portal application from Windows ............ 84
Post-installation tasks............................................................................................... 85
Logging in to the Assure UI portal ......................................................................... 85
Enable automatic startup....................................................................................... 86
Maintaining the node_config.properties file........................................................... 87
Additional options for the node_config.properties file......................................... 88
Chapter 6 Configuring Replication Groups 89
Using the Assure UI portal to configure replication groups ...................................... 90
Create and configure a new replication group....................................................... 90
Configuration initialization progress (new configuration) .................................. 110
Change a replication group’s configuration ......................................................... 112
Dynamically changing configuration of a replication group .............................. 115
Manually changing configuration of a replication group ................................... 116
Configuration initialization progress (Change Configuration) ........................... 128
Rename a replication group ................................................................................ 131
Delete a replication group ................................................................................... 133
Using earlier versions of Assure MIMIX for AIX to configure replication groups .....
133
Configuration window for Replication Groups ..................................................... 134
Using the command line to perform configuration tasks ........................................ 134
Initialize a context................................................................................................ 135
Send partially filled containers automatically....................................................... 135
Verify your configuration using the sccfgchk command ...................................... 135
Support for LVM commands when the Assure MIMIX for AIX drivers are loaded.. 135
es_swmaj ............................................................................................................ 137
Usage ............................................................................................................... 137

5 Assure MIMIX for AIX User Guide v5.2.04.00

 Syntax .............................................................................................................. 137
Assure MIMIX for AIX default ports ........................................................................ 138
Editing the /etc/services file to add specific port assignments ............................ 138
Activating syslog debug.......................................................................................... 141
Chapter 7 Configuring Clusters 143
Using the Assure UI portal to configure clusters .................................................... 144
Create and configure a cluster ............................................................................ 144
Configuration window for Clusters.......................................................................... 153
Change Application wizard..................................................................................... 154
Add replication group to Cluster ............................................................................. 161
Chapter 8 Starting and Stopping 169
Using the Assure UI portal to start and stop Assure MIMIX for AIX ....................... 169
Using the Assure UI portal to start Assure MIMIX for AIX................................... 169
Using the Assure UI portal to stop Assure MIMIX for AIX ................................... 170
Using the command line to start and stop Assure MIMIX for AIX .......................... 171
Using the command line to start Assure MIMIX for AIX ...................................... 171
non-Disruptive Startup Mode............................................................................ 172
Monitoring the log files ........................................................................................ 173
Using the command line to stop Assure MIMIX for AIX ...................................... 173
Chapter 9 Creating Snapshots 175
Overview ................................................................................................................ 175
Using snapshots to protect your data..................................................................... 175
Using the Assure UI portal to create a snapshot.................................................... 176
Using the Assure UI portal to increase the snapshot buffer size......................... 178
Using the command line to create a snapshot ....................................................... 179
Creating snapshots based on the current redo log ............................................. 180
Creating snapshots based on a specific date and time....................................... 181
Verify that the DATEMSK environment variable is defined .............................. 181
Establish the date format for the DATEMSK environment variable.................. 181
Create snapshots based on a specific date and time....................................... 182
Creating a snapshot based on a specific event mark.......................................... 184
Creating a snapshot based on a specific LFCID ................................................. 185
Chapter 10 Administrative Tasks 187
Verify the configuration using the sccfgchk command ........................................... 188
Updating the Assure MIMIX for AIX configuration.................................................. 188
Verifying available free space ................................................................................ 188
Using the Assure UI portal to configure events and subscriptions ......................... 188
Using the Assure UI portal to extend logical volumes and file systems ................. 193
Using the Extend Logical Volume Size wizard .................................................... 193
Steps run to extend a logical volume ............................................................... 197
Using the Extend File System Size wizard.......................................................... 200
Steps run to extend a file system ..................................................................... 204
Using the command line to extend an Assure MIMIX for AIX-protected file system .....
204
Extending a protected file system beyond the limit of the region (block) size ..... 206
Increasing the snapshot journal space on the recovery server .............................. 207
Removed Logical Volume corrective action ........................................................... 208

Assure MIMIX for AIX User Guide v5.2.04.00 6

 Setting up JFS log isolation.................................................................................... 213
Removing a File system from an Assure MIMIX for AIX protected jfslog............... 214
Setting up error notification .................................................................................... 214
ODM commands ................................................................................................. 215
Error Notify Messages......................................................................................... 216
Sync While Active - full synchronization................................................................. 218
Sync While Active - checksum-based synchronization .......................................... 219
Verify that replica logical volumes are synchronized with logical volumes on the pro-
duction server...................................................................................................... 221
Alternative method for performing initial synchronization....................................... 222
Using IBM Power Systems Live Partition Mobility with Assure MIMIX for AIX....... 223
Overview ............................................................................................................. 223
Automatically registering the es_migrate script................................................... 223
Manually registering the es_migrate script.......................................................... 224
Before you migrate a partition ............................................................................. 225
Migrating a partition .......................................................................................... 225
Using the rn_shutdown script ................................................................................. 226
Steps performed by the rn_shutdown script........................................................ 226
Using the gc_shutdown.sh script to gracefully shutdown all configured applications in
an Assure MIMIX HA for AIX clustered environment .......................................... 227
Steps performed by the gc_shutdown.sh script .................................................. 227
IOCTL call handling................................................................................................ 228
Chapter 11 Working with Assure MIMIX for AIX Applications 229
Overview ................................................................................................................ 229
Database recovery operations scenarios ............................................................... 229
Database resurrection concept ........................................................................... 230
Database repair concept ..................................................................................... 230
Performing a volume restore .................................................................................. 231
Step 1: Stop Assure MIMIX for AIX on the production server .......................... 232
Step 2: Create new volumes to replace failed volumes ................................... 232
Step 3: Create a snapshot on the recovery server........................................... 233
Step 4: Validate the information provided by the snapshot .............................. 234
Step 5: Destroy the snapshot ........................................................................... 234
Step 6: Recreate the snapshot on the recovery server .................................... 235
Step 7: Copy volumes on recovery server to replacement volumes on production
server............................................................................................................. 235
Step 8: Restart Assure MIMIX for AIX on the production server ...................... 235
Step 9: Rollback the appropriate context on the production server.................. 235
Step 10: Mount the volumes for the context ..................................................... 237
Step 11: Destroy the snapshot ......................................................................... 237
Performing a production restore............................................................................. 237
Using theAssure UI portal for a production restore ............................................. 238
Using the command line to perform a production restore ................................... 241
Chapter 12 Working with Archived Data 245
Overview of working with archived data ................................................................. 245
Performing a snapshot-based backup to archive media ........................................ 245
Performing a production restore from archived logs .............................................. 246

7 Assure MIMIX for AIX User Guide v5.2.04.00

Chapter 13 Introduction to Disaster Recovery 249
Introduction............................................................................................................. 249
Assure MIMIX for AIX Disaster Recovery .............................................................. 250
Assure MIMIX for AIX recovery process ............................................................. 250
How Assure MIMIX for AIX Disaster Recovery works......................................... 250
Assure MIMIX for AIX Disaster Recovery management ..................................... 251
Failover context overview.................................................................................... 251
Failover context specifications ............................................................................ 251
Failover context and primary context relationship ............................................ 252
Set up a Failover context.................................................................................. 252
Failover context naming conventions ............................................................... 252
How the Failover context works .......................................................................... 252
rtdr Failover command ........................................................................................ 253
Syntax .............................................................................................................. 253
Assure MIMIX for AIX Disaster Recovery operations............................................. 254
Failover process overview................................................................................... 254
Preparing before a Failover................................................................................. 255
Setting up a Failover context............................................................................... 255
Before performing Failover operations ................................................................ 255
Validating data integrity .................................................................................... 255
Verify restore point ........................................................................................... 256
Create a virtual restore snapshot ..................................................................... 256
Chapter 14 Disaster Recovery Operations 257
Using the Assure UI portal to perform failover and failback ................................... 257
Run a procedure..................................................................................................... 257
About procedure and step processes............................................................... 258
Failover and failback for 2-node non-clustered replication groups......................... 258
Planned Failover for 2-node non-clustered replication groups............................ 258
Run Planned Failover Procedure dialog for 2-node non-clustered replication
groups: Unmount file systems on current production server ......................... 260
Resume Planned Failover Procedure dialog for 2-node non-clustered replication
groups: Stop replication on current production server................................... 260
Resume Planned Failover Procedure dialog for 2-node non-clustered replication
groups: Failover replication group: Server roles change ............................... 260
Resume Planned Failover Procedure dialog for 2-node non-clustered replication
groups: Start replication on the new recovery server .................................... 260
Resume Planned Failover Procedure dialog for 2-node non-clustered replication
groups: Start replication on new production server ....................................... 260
Unplanned Failover for 2-node non-clustered replication groups........................ 261
Run Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Create snapshot on failover server................................................... 262
Resume Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Delete snapshot on failover server ................................................... 263
Resume Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Rollback failover server .................................................................... 263
Resume Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Failover replication group: Server roles change ............................... 263
Resume Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Start replication on the recovery server............................................ 263

Assure MIMIX for AIX User Guide v5.2.04.00 8

 Resume Unplanned Failover Procedure dialog for 2-node non-clustered replication
groups: Start replication on the new production server ................................. 263
Failback for 2-node non-clustered replication groups ......................................... 264
Run Failback Procedure dialog for 2-node non-clustered replication groups: Un-
mount file systems on current production server........................................... 265
Resume Failback Procedure dialog for 2-node non-clustered replication groups:
Stop replication on current production server................................................ 265
Resume Failback Procedure dialog for 2-node non-clustered replication groups:
Failback configured production server........................................................... 265
Resume Failback Procedure dialog for 2-node non-clustered replication groups:
Failback configured recovery server.............................................................. 265
Failover and failback for 2-node clustered replication groups ................................ 265
Planned failover for 2-node clustered replication groups .................................... 266
Unplanned Failover for 2-node clustered replication groups............................... 267
Run Unplanned Failover Procedure dialog for 2-node clustered replication groups:
Create snapshot on failover server................................................................ 269
Resume Unplanned Failover Procedure dialog for 2-node clustered replication
groups: Delete snapshot on failover server ................................................... 269
Resume Unplanned Failover Procedure dialog for 2-node clustered replication
groups: Rollback failover server .................................................................... 270
Resume Unplanned Failover Procedure dialog for 2-node clustered replication
groups: Failover replication group: Server roles change ............................... 270
Resume Unplanned Failover Procedure dialog for 2-node clustered replication
groups: Start replication on the new production server ................................. 270
Failback for 2-node clustered replication groups................................................. 270
Failover and failback for 3-node non-clustered broadcast replication groups ........ 272
Planned Failover for 3-node non-clustered broadcast replication groups ........... 272
Run Planned Failover Procedure dialog for 3-node non-clustered broadcast repli-
cation groups: Unmount file systems on current production server............... 274
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Stop replication on current production server ................. 274
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Prepare current recovery server for failover.................... 275
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Prepare current production server for failover................. 275
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Failover replication group: Server roles change.............. 275
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new recovery server 2...................... 275
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new recovery server 1...................... 275
Resume Planned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new production server...................... 275
Unplanned Failover for 3-node non-clustered broadcast replication groups....... 275
Run Unplanned Failover Procedure dialog for 3-node non-clustered broadcast rep-
lication groups: Create snapshot on failover server ...................................... 278
Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Delete snapshot on failover server.................................. 278
Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Rollback failover server................................................... 278

9 Assure MIMIX for AIX User Guide v5.2.04.00

 Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Failover replication group. Server roles change.............. 278
Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new recovery server 2...................... 279
Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new recovery server 1...................... 279
Resume Unplanned Failover Procedure dialog for 3-node non-clustered broadcast
replication groups: Start replication on new production server...................... 279
Failback for 3-node non-clustered broadcast replication groups......................... 279
Run Failback Procedure dialog for 3-node non-clustered broadcast replication
groups: Unmount file systems on current production server ......................... 280
Resume Failback Procedure dialog for 3-node non-clustered broadcast replication
groups: Stop replication on current production server................................... 280
Resume Failback Procedure dialog for 3-node non-clustered broadcast replication
groups: Failback configured production server.............................................. 281
Resume Failback Procedure dialog for 3-node non-clustered broadcast replication
groups: Failback configured recovery server 1.............................................. 281
Resume Failback Procedure dialog for 3-node non-clustered broadcast replication
groups: Failback configured recovery server 2.............................................. 281
Using the command line to perform failover and failback for 2-node non-clustered rep-
lication groups ..................................................................................................... 281
Failover process overview................................................................................... 282
Preparing before a Failover................................................................................. 282
Setting up a Failover context............................................................................... 282
Before performing Failover operations ................................................................ 283
Validating data integrity .................................................................................... 283
Verify restore point ........................................................................................... 283
Create a virtual restore snapshot ..................................................................... 283
Failover operations.............................................................................................. 284
Performing a Failover restore ........................................................................... 284
Start the application.......................................................................................... 285
Performing resync ............................................................................................... 285
Resync with region recovery ............................................................................ 286
Performing failback........................................................................................... 286
Manual resynchronization process if production server data is lost ................. 287
Using the command line to perform failover and failback for 2-node clustered replica-
tion groups........................................................................................................... 289
Chapter 15 CLI Assure MIMIX DR for AIX Commands 291
esmon..................................................................................................................... 292
Usage .................................................................................................................. 292
Syntax ................................................................................................................. 292
extend_replica_lv ................................................................................................... 293
Usage .................................................................................................................. 293
es_swmaj ............................................................................................................... 293
Usage .................................................................................................................. 293
Syntax ................................................................................................................. 293
rn_temp_journal ..................................................................................................... 294
Usage .................................................................................................................. 294
Syntax ................................................................................................................. 294

Assure MIMIX for AIX User Guide v5.2.04.00 10

 rtattr ........................................................................................................................ 295
Usage .................................................................................................................. 295
Syntax ................................................................................................................. 295
Example 1 ........................................................................................................... 295
Example 2 ........................................................................................................... 296
rtdr .......................................................................................................................... 297
Usage .................................................................................................................. 297
Syntax ................................................................................................................. 299
rtmark (and Event Marks)....................................................................................... 301
Usage .................................................................................................................. 301
Syntax ................................................................................................................. 301
Event Marker File and the rtmark command ....................................................... 301
Print available event marks for rollback............................................................ 302
rtmnt ....................................................................................................................... 304
Usage .................................................................................................................. 304
Syntax ................................................................................................................. 304
Parameters.......................................................................................................... 304
rtstart ...................................................................................................................... 305
Usage .................................................................................................................. 305
Syntax ................................................................................................................. 305
Parameters.......................................................................................................... 305
rtstop ...................................................................................................................... 306
Syntax ................................................................................................................. 306
Parameters.......................................................................................................... 306
rtumnt ..................................................................................................................... 307
Usage .................................................................................................................. 307
Syntax ................................................................................................................. 307
Parameters.......................................................................................................... 307
sclist ....................................................................................................................... 308
Usage .................................................................................................................. 308
Syntax ................................................................................................................. 308
scconfig .................................................................................................................. 311
Usage .................................................................................................................. 311
Syntax ................................................................................................................. 311
Parameters.......................................................................................................... 311
Send partial containers automatically using the Replication Group Configuration
wizard ............................................................................................................ 313
scsetup ................................................................................................................... 313
Usage .................................................................................................................. 313
Syntax ................................................................................................................. 313
Parameters.......................................................................................................... 314
scrt_ra .................................................................................................................... 315
Usage .................................................................................................................. 315
Syntax to display the Available rollback windows ............................................... 315
Syntax to create snapshots ................................................................................. 316
Parameters.......................................................................................................... 316
scrt_rc..................................................................................................................... 318
Usage .................................................................................................................. 318
Syntax ................................................................................................................. 318
Session restore targets ....................................................................................... 318

11 Assure MIMIX for AIX User Guide v5.2.04.00

 Session termination............................................................................................. 318
Process overview ................................................................................................ 319
General procedure ........................................................................................... 319
Procedure notes .................................................................................................. 320
scrt_vfb................................................................................................................... 321
Usage .................................................................................................................. 321
Syntax ................................................................................................................. 321
Parameters.......................................................................................................... 321
sccfgd_cron_schedule............................................................................................ 322
Usage .................................................................................................................. 322
Syntax ................................................................................................................. 322
Examples............................................................................................................. 322
sccfgd_putcfg ......................................................................................................... 323
Usage .................................................................................................................. 323
Syntax ................................................................................................................. 323
Parameters.......................................................................................................... 323
sccfgchk ................................................................................................................. 324
Usage .................................................................................................................. 324
Syntax ................................................................................................................. 324
Parameters.......................................................................................................... 324
sztool ...................................................................................................................... 325
Usage .................................................................................................................. 325
Syntax ................................................................................................................. 325
Parameters.......................................................................................................... 325
Chapter 16 CLI Assure MIMIX HA for AIX Commands 327
Command syntax ................................................................................................... 327
General options ................................................................................................... 327
Node commands .................................................................................................... 328
deployConfig ....................................................................................................... 328
Syntax .............................................................................................................. 328
Example ........................................................................................................... 328
deconfigure.......................................................................................................... 328
Syntax .............................................................................................................. 328
Example ........................................................................................................... 328
validateLicense.................................................................................................... 328
Syntax .............................................................................................................. 328
Example ........................................................................................................... 328
startCluster .......................................................................................................... 329
Syntax .............................................................................................................. 329
Example ........................................................................................................... 329
showCluster......................................................................................................... 329
Syntax .............................................................................................................. 329
Example ........................................................................................................... 329
stopCluster .......................................................................................................... 329
Syntax .............................................................................................................. 329
Example ........................................................................................................... 329
supportSnapshot ................................................................................................. 329
Syntax .............................................................................................................. 330
Example ........................................................................................................... 330

Assure MIMIX for AIX User Guide v5.2.04.00 12

 Application commands ........................................................................................... 331
startApplication.................................................................................................... 331
Syntax .............................................................................................................. 331
Example ........................................................................................................... 331
clearApplication ................................................................................................... 331
Syntax .............................................................................................................. 331
Example ........................................................................................................... 331
setApplicationPolicy ............................................................................................ 331
Syntax .............................................................................................................. 332
Example ........................................................................................................... 332
Example ........................................................................................................... 332
moveApplication .................................................................................................. 332
Syntax .............................................................................................................. 332
Example ........................................................................................................... 333
stopApplication .................................................................................................... 333
Syntax .............................................................................................................. 333
Example ........................................................................................................... 333
stopAllLocalApplications...................................................................................... 333
Syntax .............................................................................................................. 333
Example ........................................................................................................... 333
showApplication .................................................................................................. 333
Syntax .............................................................................................................. 333
Example ........................................................................................................... 334
Resource commands ............................................................................................. 335
startResource ...................................................................................................... 335
Syntax .............................................................................................................. 335
Examples.......................................................................................................... 335
clearResource ..................................................................................................... 335
Syntax .............................................................................................................. 335
Example ........................................................................................................... 335
showResource..................................................................................................... 336
Syntax .............................................................................................................. 336
Example ........................................................................................................... 336
stopResource ...................................................................................................... 336
Syntax .............................................................................................................. 336
Example ........................................................................................................... 336
showEvents ......................................................................................................... 336
Syntax .............................................................................................................. 336
Example ........................................................................................................... 337
setLogLevel ......................................................................................................... 337
Syntax .............................................................................................................. 337
Example ........................................................................................................... 338
performNetDiscovery........................................................................................... 338
Syntax .............................................................................................................. 338
Example ........................................................................................................... 338
performDiscovery ................................................................................................ 338
Syntax .............................................................................................................. 339
Example ........................................................................................................... 339
exit....................................................................................................................... 339
Syntax .............................................................................................................. 339

13 Assure MIMIX for AIX User Guide v5.2.04.00

 Example ........................................................................................................... 339
Appendix A Integration of PowerHA (HACMP) with Assure MIMIX for AIX 341
Configuring a highly available Assure MIMIX for AIX/PowerHA production server envi-
ronment (option 1) ............................................................................................... 341
Assure MIMIX for AIX configuration requirements .............................................. 342
Configuring highly available production servers - Option 1 ................................. 343
Assure MIMIX for AIX/PowerHA integration requirements.................................. 347
Sample Assure MIMIX for AIX start script ........................................................ 349
Sample Assure MIMIX for AIX shutdown script................................................ 350
Managing Assure MIMIX for AIX in a HA production server environment........... 351
Changing the Assure MIMIX for AIX configuration ........................................... 351
Changing the Assure MIMIX for AIX configuration after extending a filesystem in a
PowerHA highly available production server environment ............................ 352
Updating the Assure MIMIX for AIX configuration on the secondary production
server............................................................................................................. 353
Managing Failover to the recovery server ........................................................... 357
Unplanned Failover .......................................................................................... 357
Planned Failover .............................................................................................. 363
Configuring a highly available Assure MIMIX for AIX production server in a PowerHA
environment (option 2) ........................................................................................ 367
Assure MIMIX for AIX configuration requirements .............................................. 367
Configuring highly available production servers - Option 2 ................................. 368
Sample Assure MIMIX for AIX start script ........................................................ 375
Sample Assure MIMIX for AIX stop script ........................................................ 376
Managing Assure MIMIX for AIX in a HA production server environment........... 377
Changing the Assure MIMIX for AIX configuration ........................................... 377
Changing the Assure MIMIX for AIX Configuration after extending a filesystem in a
PowerHA highly available production server environment ............................ 378
Other topics to consider before making configuration changes ....................... 379
Managing Failover to the recovery server ........................................................... 380
Unplanned failover ........................................................................................... 380
Planned Failover .............................................................................................. 386
Configuring an Assure MIMIX for AIX/PowerHA production to recovery server environ-
ment (option 3) .................................................................................................... 390
Prerequisites ....................................................................................................... 390
Overview of the failover process ......................................................................... 390
Sequence to manually bring the resource groups online .................................... 391
Sequence to manually bring the resource groups offline .................................... 391
Planned Failover procedure ................................................................................ 391
Unplanned Failover procedure ............................................................................ 391
Failback procedure.............................................................................................. 392
PowerHA for AIX configuration............................................................................ 392
Appendix B Installing X11 for the Sizing Tool 399

Assure MIMIX for AIX User Guide v5.2.04.00 14

Overview of Data Replication
Concepts 1

Introduction
The Assure MIMIX for AIX User Guide describes how to install, configure,
maintain and administer data replication software.
A combination of High Availability clustering and data replication ensures an
effective and efficient disaster recovery solution. Assure MIMIX HA for AIX is
the clustering component that automates the detection and recovery of
applications and their dependent resources from various system and human
failures. Assure MIMIX DR for AIX, is the replication component that provides
Continuous Data Protection (CDP) and a high level of data protection from both
disasters and data corruption. Assure MIMIX HA for AIX and Assure MIMIX
DR for AIX, working together, comprise the Assure MIMIX for AIX solution.

The Assure MIMIX for AIX data replication solution:

• Provides “Support for non-root user ownership and permissions for protected
Logical Volumes” on page 19.

• Provides “Support for data encryption in Assure MIMIX DR for AIX” on

page 19.

• Provides asynchronous data replication

• Includes rapid data rollback with Any Point-in-Time virtualization

• Provides Read/Write data snapshots for off-host processing

• Provides functionality with little or no production application impact

• Minimizes application Recovery Time Objective (RTO) and Recovery Point

Objective (RPO) within an Optimized Recovery Window (ORW)

• Is resilient to network, storage, and system failures and outages

• Optimizes for rapid recovery to Any Point-in-Time

• Allows for administrative double-check before change of production data

• Supports both block and file based applications

• Maintains application write-order fidelity

Assure MIMIX for AIX User Guide version 5.2.04.00 15

 • Has no proprietary hardware dependencies

• Always looks to supplement, not replace, existing enterprise processes for

logical storage management, backup, and high availability

Roles in the system architecture

A standard Assure MIMIX for AIX system configuration consists of at least two
similar servers: a production server and a recovery server. A production server is
where the production application resides, and the recovery server is where a data
replica is maintained, rapid recoveries of the production data can be initialized, any
point-in-time may be virtualized, and enterprise processes may be off-loaded from
the production server. The production server’s data is restored from the recovery
server.

Assure MIMIX for AIX replication groups

You can use the Configuration Wizard to configure replication groups. Once you
define replication groups you can add them to a cluster.

An Assure MIMIX for AIX replication group includes:

• The applications and associated files and volumes that you want to protect.

• The production and recovery servers.

• Archiving systems.

Refer to “Using the Assure UI portal to configure replication groups” on page 108.

Assure MIMIX for AIX clusters

A high-availability cluster consists of two nodes that share at least one, and
preferably several, communication links, and typically one or more sets of storage
devices. The cluster component services, manage generic applications and their
dependent resources providing continuous availability of the application, Internet
Protocol (IP) connectivity to the application, and the application's access to its data.
Refer to “Configuring Clusters” on page 161.

Assure MIMIX for AIX file container

An Assure MIMIX for AIX File Container is a generic term used to describe the
storage object that the Assure MIMIX for AIX Context needs to function correctly.
While there are different specialized types of File Containers, the most commonly
discussed and most necessary to understand is the Log File Container (LFC). A LFC
is the logical unit of data movement around the system. When an LFC is filled with
data writes on the production server it is fully transferred to the recovery server.
Once transferred, it is processed and applied to the data replica. You can also send
partially filled containers. The Send partially filled containers automatically

16 Assure MIMIX for AIX User Guide v5.2.04.00

 option enables you to control the frequency of shipping containers (LFCs) to the
recovery server during low I/O periods. The Send partially filled containers
automatically option can be managed in two ways:

• Use the Replication Group Configuration Wizard. Refer to the New Replication
Group Container Options panel, and the field, “Send partially filled containers
automatically” on page 153.

• Use the command line using the scconfig command. Refer to “scconfig” on
page 329.

Assure MIMIX for AIX datatap

The AIX Logical Volume Manager (LVM) maintains the hierarchy of logical
structures that manage disk storage. Assure MIMIX for AIX kernel extensions, or
datataps, reside logically above the LVM layer inside the operating system kernel.
Furthermore, these datataps are logically below the file system level and handle
block level transfers. The datatap receives a buffer structure from the file system
layer in the case of a file system write operation or from the application in the case
of a raw Logical Volume write. Data is then processed and sent onto the LVM
(Logical Volume Manager) layer. For read operations from storage, data passes
through untouched.

Assure MIMIX for AIX User Guide v5.2.04.00 17

 The datatap is loaded on both the production server and the recovery server. On the
production server, the datatap is responsible for splitting data write operations. Each
write results in a write to the intended protected volume as well as to a redo log.

Assure MIMIX for AIX journal

Two specific structures are used to contain the redo and undo logs in the Assure
MIMIX for AIX architecture. The After Image Log File Container (AILFC) and
Before Image Log File Container (BILFC) are used to hold these logs. The entire set
of logs is known as a journal to Assure MIMIX for AIX, and on the recovery server,
associated redo logs together with undo logs form the journal. The journal is often
illustrated as a single pool, and these logs are block storage devices that do not
interact with resident file systems or their cache buffers.

18 Assure MIMIX for AIX User Guide v5.2.04.00

 Support for non-root user ownership and permissions for
protected Logical Volumes
When you create a new replication group configuration or change a replication
group configuration to add Logical Volumes to a replication group, Logical Volume
ownership and permissions information (UGM or User Group Mode Info) is
collected from the production server and added to the Assure MIMIX DR for AIX
ODM, to retain the production server's ownership and permissions on the
production server and recovery server.

If Logical Volume ownership or permission information is changed on the

production server for any Logical Volume configured in a replication group, you
must change the replication group configuration using the Configuration Wizard so
that the changes can be made to the Assure MIMIX DR for AIX ODM and applied
to the recovery server

To update the Assure MIMIX DR for AIX ODM and the recovery server, two
completely separate configuration changes are required and must be executed in the
following order:

• The first configuration change is to remove the affected Logical Volumes from
the configuration. Refer to “Change a replication group’s configuration” on
page 130.
• The second configuration change is to add the removed Logical Volumes to the
configuration. Refer to “Change a replication group’s configuration” on
page 130.

Support for data encryption in Assure MIMIX DR for AIX

Assure MIMIX for AIX uses Log File Containers (LFCs) to transfer data from the
production server to the recovery servers. OpenSSL is used to encrypt the data that
is protected by Assure MIMIX DR for AIX.

NOTE
Assure MIMIX DR for AIX uses TLS 1.2 as the protocol for encryption
and self-signed certificates for authentication.

LFCs are created unencrypted on the production server and placed into the LFC
pool. Before the LFCs are transferred to the recovery server, they are first encrypted
and then transferred to the recovery server. Once transferred to the recovery server,
the Assured Backup Agent (ABA) unencrypts the LFCs and stores them in the
received LFC pool before applying the LFC.

Assure MIMIX for AIX User Guide v5.2.04.00 19

 NOTE
This activity requires additional CPU bandwidth to encrypt and unencrypt
the LFC on each server.

You can enable or disable encryption in the Configuration Wizard with the Use
encryption during replication option, which is on the New Replication Group
Container Options panel. See page 120 and page 121 for details on the New
Replication Group Container Options panel. You can also use this option on the
Change Replication Group Container Options panel. See page 143.

Assure MIMIX for AIX agents

Assure MIMIX for AIX uses the following agents:

• Log Creation Agent (LCA)—The primary agent that runs on the production
server, called the Log Creation Agent (LCA).

• Assured Backup Agent (ABA)—A primary agent that runs on the recovery
server

• Archive Agent (AA)—A primary agent that runs on the recovery server

• Restore Agent (RA)—A primary agent that runs on the recovery server

LCA agent
Shipping logs from the production server to the recovery server is the responsibility
of the LCA. The LCA reads from the journal any redo log information that has been
closed, or sealed, and this information is then shipped over one or more IP networks
to an agent that runs on the recovery server. Both agents bind and communicate over
the same socket. Socket port addresses can either be default addresses or they can be
programmatically selected.

Super transaction and RWB in the LCA log file

The super transaction replicates data by reading dirty regions (the default is 4 MB)
as marked in the state map. Each PVS (Production Volume Set) LV (Logical
Volume) has a state map. These dirty regions are read from the associated PVS LV
and written to a LFC (Log File Container). This operation is referred to as RWB
(Read Write Back).

ABA agent
On the other side of the socket and running on the recovery server, the ABA is
collecting log information. The ABA receives the redo log information in the time
order it was created on the production server, and then stores this information in
recovery logs. Remember, these are block storage devices that do not interact with
resident file systems. As the ABA receives the data, it dynamically creates

20 Assure MIMIX for AIX User Guide v5.2.04.00

 optimized State Map Transactions (SMTX). The blocks identified are then sorted in
ascending device/block order. Block ordering is a more efficient organization for
applying modifications to the data, or replica, on the recovery server.

Before the modifications are applied to the replica, yet another block storage device
is written to with information that would allow the replica to step backward in time.
This storage device is called the undo log and appears to be nothing more than a
logical volume to the volume manager. Once the undo log information is saved on
disk, the redo log can be applied to the replica to bring it up to date with the data on
the production server.

AA agent
The AA, or Archive Agent, also runs on the recovery server. It is used to extend
Assure MIMIX for AIX’s rollback capabilities by recording redo and undo logs to
media. The AA currently works with Tivoli Storage Manager (TSM). The AA uses
the TSM API to send archive requests to TSM. When the logs are archived, they are
always spooled in pairs. Depending on the TSM configuration the data is stored on
media. A redo and an undo log are always together when the AA stores on media.
This gives Assure MIMIX for AIX the ability to restore the data to any point in
time. By unwinding the data with a course grained undo log, then applying fine
grained redo log information to the log, the state of the data can be restored to any
point in time.

RA agent
Restoration is handled by the RA and runs on the recovery server. It does not,
however, run continuously like the other agents. It can programmatically be
executed from the command line or through the GUI. The RA deals with the
following types of restore operations:

• Virtual restores to a specific date and time

• Production restores to a specific date and time

• Virtual restores to a virtual full backup (VFB)

• Production restores to a virtual full backup (VFB)

• Restoring individual protected volumes

Virtual restores occur on the backup server. Production restores are restores in
which all volumes defined in a context are rolled back together on the production
server.

Assure MIMIX for AIX User Guide v5.2.04.00 21

Replication
Assure MIMIX for AIX runs automatically on a production server, creating a
mirrored copy of protected data on the recovery server. For increased availability, it
is recommended that the recovery server be a remote machine. The following
illustration shows storage data flow during Assure MIMIX for AIX replication:

On the production server, write operations to storage are split by the datatap. One
copy of the data is delivered to the protected volume. The other copy of data is
combined with metadata and stored in the redo log. The LCA sweeps through the
production journal and reads any log that has been filled, or sealed, then transmits
the log file over TCP/IP to the ABA which stores the log file to disk on the recovery
server.

NOTE
Data does not pass through the datatap on the recovery server.

The ABA sweeps through the log files in time order and uses the metadata reads
from the replica to calculate the amount of change required to apply the working log
file and stores this information in the undo log. The ABA then reads from the redo
log and applies the modification in block order to the replica.

Journal configuration
Assure MIMIX for AIX uses the following journals:

• “Production journal” on page 23

22 Assure MIMIX for AIX User Guide v5.2.04.00

 • “Recovery journal” on page 23

Production journal
The production journal holds redo log buffers until the logs are transferred to the
recovery server. Then the logs are available to receive new application write data.
Sizing the journal properly prevents the recovery server from falling so far behind
the production server that dynamic recovery must occur for the recovery server to
catch up. If the journal is too small, then transfers between the production server and
the recovery server are performed more frequently than is efficient. If the journal is
too big, then the recovery server may fall so far behind the production server that
dynamic recovery must occur.

The appropriate size of the production journal is proportional to the length of

network or recovery server downtime that Assure MIMIX for AIX can sustain
without falling into dynamic recovery, or the amount of data in write throughput
spikes that exceed system bandwidth that Assure MIMIX for AIX can sustain
without falling into dynamic recovery.

Recovery journal
The recovery journal is on the recovery server, and holds redo and undo logs, that
act as Assure MIMIX for AIX’s internal rollback window. If you are using external
archive media such as tape, then the size of the journal on the recovery server is not
critical to the ability to restore data. The larger the recovery journal, the larger the
internal rollback window, which implies faster access to redo and undo logs during
production restores in that window.

Recovery log sizing

If you are not using external archive media, then the size of the recovery journal is
critical for data protection. Rollbacks cannot extend beyond the logs that exist on
the recovery server. You must estimate average throughput and calculate journal
area based on the length of the desired average restore window.

The size of the recovery journal is proportional to write throughput and the required
internal rollback window.

The journal on the recovery server should be at least 256MB. Note that this is twice
the space recommended for the minimum on the production server, because the
recovery server contains both redo logs and undo logs.

Refer to Chapter 2 “Planning your Environment” on page 29 for information and

formulas to help you size the journals for your system. Refer to Chapter 3 “Using
the Sizing Tool to Calculate LFC Size” on page 41 to automated the process of
sizing the journals for your system.

Assure MIMIX for AIX User Guide v5.2.04.00 23

Log file configuration
All logs are the same size on the production server and the recovery server. The log
size affects the amount of data that Assure MIMIX for AIX processes for each
transaction.

By increasing the size of the logs, processing is reduced and the elimination of
common blocks in the undo logs is more efficient. Decreasing log size results in a
more up-to-date replica on the recovery server, because log transfers occur more
frequently.

When you determine the best log size, keep these conditions in mind:

• The journal should contain at least eight logs

• Minimum log size is 2MB

• Maximum log size is one-half of the available RAM but not greater than 512
MB

• Typical log size is 16MB

To calculate log size, you need an estimate of average write throughput, and the
required processing rate. For the required processing rate, if Assure MIMIX for AIX
processes one log every 60 seconds, the replica will be one minute behind the
production system.

Log size estimate

log size = (average write throughput) / (processing rate)

Number of logs
number of logs = (journal size) / (log size)

Even though the calculation for the number of log files appears trivial, keep in mind
that the number of log files can affect performance. If enough log files are available
on the production server, Assure MIMIX for AIX does not have to rely on state
maps during an outage, because it has not run out of log files to take in data. A state
map contains information about data changes for each storage device protected by
Assure MIMIX for AIX. It can be used to reconstruct data changes if the underlying
data is corrupted or lost. During peak usage, when an application is writing data
faster than the network can transmit, extra log files enable the system to buffer
during these peak periods without having to rely on state maps, eliminating the risk
of a restore blackout window. On the recovery server, a sufficient number of log
files allows activity to be buffered in the event that the tape drive or library is taken
offline.

The Chapter 2 “Planning your Environment” on page 29 contains information and

formulas to help you size the logs for your system.

24 Assure MIMIX for AIX User Guide v5.2.04.00

Assure MIMIX for AIX snapshots
Snapshots use significantly less space and are more efficient than data mirrors. A
mirror is an up-to-date copy of data for a logical volume. Two or more complete
copies can exist at the same time, although only one copy is seen or used by an
application, so mirrors require double or more the amount of disk space than the
original data.

A snapshot is a view of data at a specific point in time, much like a photographic

image is a snapshot of physical images at a particular point in time. You can use
snapshots to validate data before you save it to permanent storage, data mine and
generate reports, and retrieve specific data items.

Snapshots are stored in a different location than the replica so that the replica can
continue to march along in time. The snapshot, however, is frozen with respect to
the replica. Again, using the analogy of a photograph, you can now draw on the
photograph and it does not effect the original subject of the photograph. The ability
to modify the snapshot is accomplished by using a copy-on-write log file.

Notice from the above figure that data is passing through the datatap on the recovery
server in the case of reads and writes to snapshot data. Assure MIMIX DR for AIX
uses a different set of device minor numbers when dealing with snapshots, so that
the datatap knows which log files to access in a specific order. For example, when a
write operation is directed at the snapshot it is actually written to the copy-on-write
(COW) log instead. If the data has not been modified, then a read operation would
come from the snapshot. If the data has been modified, then the read would come
from the copy-on-write log. Keep in mind that the snapshot is the representation of
the application data at a specific point in time.

Related Topics:

Assure MIMIX for AIX User Guide v5.2.04.00 25

 • “Using the Assure UI portal to create a snapshot” on page 194.

• “Using the command line to create a snapshot” on page 197.

Recovery
Generally, there are two types of recovery restorations. A production restore is a
rollback in time which takes place in the protected volumes on the production
server. The other type of restore, a virtual restore, is a rollback in time which is
executed over a read-writable virtual image of the protected volumes which reside
on the recovery server.

For a production restore, Assure MIMIX DR for AIX must have exclusive I/O
access to the protected volumes. The application must be stopped, and the file
systems must be unmounted. Assure MIMIX DR for AIX is the only process that
should be allowed to write into the protected volumes during a production restore.
The control over the protected volumes and the information stored by the Assure
MIMIX DR for AIX process allow an undo of data corruption faster than the
corruption occurred.

Production restores are useful for a database “crash” where the database will not
come up. By recovering an image of the actual production database to some point in
the past directly on the production disk itself, Assure MIMIX DR for AIX can
rollback a crashed database in minutes rather than hours or days for the most
disastrous operational situation a database can encounter.

In contrast, a virtual restore is useful for database repair. In this case, an image of the
database is rolled back to some point in the past on the snapshot which resides on
the recovery server. Select pieces of the data can then be extracted and copied into
the production database.

Related Topics:

• “Using the Assure UI portal to perform failover and failback” on page 275.

• “Using the command line to perform failover and failback for 2-node
non-clustered replication groups” on page 299.

Assure Unified Interface

The Assure Unified Interface (Assure UI portal) is a server that runs portal
applications for Precisely products. The Assure UI Portal enables multiple products
and instances to be easily monitored and managed from a browser-based graphical
interface in a single, unified view. The Assure UI Portal also provides services and
portlets for performing activities common to products.

Any Precisely product that provides a portal application at a compatible version to

the Assure UI portal can be used. A portal application includes the graphical

26 Assure MIMIX for AIX User Guide v5.2.04.00

 interface and supporting functionality for the product’s use within the Assure UI
portal.

The Assure UI portal is quick to configure and easy to customize. Portal

connections define how the portal connects to nodes in your enterprise. When
configuring an instance of a product, you identify the portal connections the
instance will use to connect to, retrieve data from, and perform actions for the
product.

Assure MIMIX for AIX with the Assure UI portal

You use the Assure MIMIX for AIX installation wizard to install Assure MIMIX for
AIX, the portal application and the Assure UI server. Refer to the section in Chapter
5, “Installation Procedures” on page 59.

To log into the Assure UI portal, refer to “Logging in to the Assure UI portal” on
page 88.

NOTE
If you have a problem logging into the Assure UI portal, refer to the Assure
Unified Interface User’s Guide packaged with Assure MIMIX for AIX.

Assure MIMIX for AIX with the command line interface

You can also use the command line interface to work with Assure MIMIX for AIX.
For a list of commands and their usage, refer to Chapter 16 “CLI Assure MIMIX
DR for AIX Commands” on page 309 and Chapter 17 “CLI Assure MIMIX HA for
AIX Commands” on page 345.

Assure MIMIX for AIX User Guide v5.2.04.00 27

28 Assure MIMIX for AIX User Guide v5.2.04.00
Planning your Environment
2

Use this chapter to prepare Assure MIMIX for AIX for its initial configuration.

This chapter contains:

• “Allocating space for Assure MIMIX for AIX logs and journals” on page 29

• “Guidelines for production journal size” on page 30

• “Guidelines for recovery journal size” on page 32

• “Guidelines for selecting volumes to be protected” on page 33

• “Guidelines for snapshot journal size” on page 34

• “Guidelines for log size” on page 34

• “Determining storage requirements” on page 35

• “Application information checklist” on page 37

• “Database information checklist” on page 37

• “Network information checklist” on page 38

• “Storage information checklist” on page 38

• “General information checklist” on page 39

Allocating space for Assure MIMIX for AIX logs and journals
Assure MIMIX for AIX records write information into log files. Logs are block
storage devices of the same size. Typically, multiple logs are contained in a
Logical Volume. The pool of disk storage that contains the logs is called a journal.
A production journal exists on the production server and a recovery journal exists
on the recovery server.

The production journal is the storage that contains all of the logs. A single log is
transferred to the recovery server when that log is filled. For example, if each LFC
is 64MB and there are 100 production LFCs, then the production journal is
6400MB. When the current LFC is filled with approximately 64MB of write I/O
data (there is some additional metadata), it will be transferred to the recovery
server.

Assure MIMIX for AIX User Guide v5.2.04.00 29

 All logs in the production journal are redo logs. They contain information that
moves the disk image of the application forward through time when the information
is applied. This is called rolling forward.

Half of the logs in the recovery journal are redo logs, and half are undo logs. Undo
logs contain information that moves a disk image of the application back through
time when they are applied. This is called rolling back.

The recovery server also contains the snapshot journal. The snapshot journal is the
space on the recovery server where Assure MIMIX for AIX stores copy-on-write
information and write-cache data for snapshots.

The following table shows the variables that are used for estimating journal sizes
and log sizes. You need these estimates in order to configure Assure MIMIX for
AIX:

Concept Meaning

Throughput Disk write rate of the application over a business cycle,

typically 24 hours.

Average Average write rate of the application during a business cycle

throughput

Peak Maximum write rate of the application during a business

throughput cycle.

Peak duration Average length of time that peak throughput occurs.

Bandwidth Maximum throughput supported by Assure MIMIX for AIX.

It is typically limited by the network that connects the
production and recovery servers.

NOTE
Use a tool such as iostat to estimate throughput. You can also use the
Sizing tool to estimate throughput. For more information, refer to “Using
the Sizing Tool to Calculate LFC Size” on page 41.

Guidelines for production journal size

The production journal holds redo log buffers until the logs are transferred to the
recovery server. Then, the logs are available to receive new application write data.

The goal of sizing the production journal properly is to prevent the recovery server
from falling so far behind the production server that dynamic recovery must occur
for the recovery server to catch up. If the production journal is too small, then
transfers between the production server and the recovery server are performed more
frequently than is efficient.

30 Assure MIMIX for AIX User Guide v5.2.04.00

 The appropriate size of the production journal is proportional to one of the
following:

• No-impact downtime: The length of network or recovery server downtime that

Assure MIMIX for AIX can sustain without falling into dynamic recovery.

• The amount of data in throughput spikes that exceed system bandwidth that
Assure MIMIX for AIX can sustain without falling into dynamic recovery

Production journal size estimate 1

If you are unable to use a tool such as iostat to estimate write throughput, then allow
at least 128 MB for the production journal. You can also use the Sizing tool to
estimate write throughput. For more information, refer to “Using the Sizing Tool to
Calculate LFC Size” on page 41.

Production journal size estimate 2

This estimate uses the following information:

• An estimate for average write throughput

• The length of no-impact downtime that is required

Calculate production journal size as follows:

production journal size = (average write throughput) x (no-impact downtime)

Production journal size estimate 3

This estimate assumes the following:

• Estimates for peak throughput, peak duration, and bandwidth exist.

• Peak throughput must be greater than bandwidth.

• Assure MIMIX for AIX must not fall into dynamic recovery when write spikes
exceed bandwidth.

Calculate production journal size as follows:

production journal size=[(peak write throughput)- bandwidth]x(peak duration)

Production journal size best estimate

The best estimate for the size of the production journal is the maximum of the above
estimates 1, 2, and 3.

Assure MIMIX for AIX User Guide v5.2.04.00 31

Guidelines for recovery journal size
The recovery journal holds redo and undo log buffers, which act as Assure MIMIX
for AIX’s internal rollback window. If you are using external archive media such as
tape, the size of the recovery journal is not critical to the ability to restore data.
However, the larger the recovery journal, the larger the internal rollback window,
which implies faster access to redo and undo logs during production restores in that
window.

If you are not using external archive media, then the size of the recovery journal is
critical for data protection. Rollbacks cannot extend beyond the logs that exist on
the recovery server. You must estimate average throughput and calculate recovery
journal area based on the length of the desired average restore window.

The size of the recovery journal is proportional to:

• Throughput

• Required internal rollback window

Recovery journal size estimate 1

The recovery journal should be at least 256 MB. Note that this is twice the space
recommended for the minimum size of the production journal, because the recovery
server contains both redo logs and undo logs.

Recovery journal size estimate 2

This estimate uses the following information:

• Estimate for average throughput

• The internal rollback window is longer than the business cycle.

Calculate recovery journal size as follows:

recovery journal size = 2 x (average write throughput) x (rollback window)

Recovery journal size estimate 3

This estimate uses the following information:

• Estimates for peak throughput and peak duration

• The internal rollback window is shorter than the business cycle.

Calculate recovery journal size as follows:

recovery journal size = 2 x (peak write throughput) x (rollback window)

32 Assure MIMIX for AIX User Guide v5.2.04.00

Guidelines for volume groups
The volume group types of the production and recovery servers must be compatible.
Servers with big or scalable volume group types may be combined, but a production
server with a small volume group may only be combined with a recovery server
with a small volume group.

The following table summarizes the supported combinations of production and

recovery volume group types:

Production

Small Big Scalable

Small OK No No
Recovery
Big No OK OK

Scalable No OK OK

NOTE
AIX may refer to the Small volume group type as Normal or Original
volume group type.

Guidelines for selecting volumes to be protected

The filesystems configured in the following replication groups should not be
automatically mounted at system restart or manually mounted when the system is
up:

• Assure MIMIX for AIX non-clustered Replication Group

• Assure MIMIX for AIX Replication Group managed by an Assure MIMIX for
AIX cluster

• Assure MIMIX for AIX Replication Group managed by a Power HA cluster

The mounting and unmounting of the protected filesystems will be performed by

Assure MIMIX for AIX, unless you plan to start replication in non-Disruptive
Startup Mode. If so, refer to “non-Disruptive Startup Mode” on page 190.

The mount attribute in /etc/filesystems, for all filesystems configured in an Assure

MIMIX for AIX Replication Group, needs to be set to mount = false. Use chfs to
change the mount attribute.

Example: chfs -a mount=false /<protected filesystem name>

Assure MIMIX for AIX User Guide v5.2.04.00 33

 NOTE
If a file system is protected by Assure MIMIX for AIX and uses a jfslog or
jfs2log, then that corresponding jfslog and jfs2log must also be protected.

Guidelines for snapshot journal size

The snapshot journal should typically be between 10 and 30 percent of the total size
of the protected volumes. Smaller snapshot journals are appropriate when snapshots
are not kept for a long time and when production I/O is light. Larger snapshot
journals are necessary when you want to keep snapshots for an extended period of
time and when heavy production I/O activities are required.

IMPORTANT
You can also use the Sizing tool to calculate write journal pool size. For
more information, refer to “Using the Sizing Tool to Calculate LFC Size”
on page 41.

Guidelines for log size

All logs are the same size on the production server and the recovery server. The log
size affects the amount of data that Assure MIMIX for AIX processes for each
transaction.

Increasing log size has the following benefits:

• Assure MIMIX for AIX processing is reduced.

• Elimination of common blocks in the undo logs is more efficient.

Decreasing log size results in a more up-to-date replica on the recovery server
because log transfers occur more frequently.

When you determine the best log size, keep these conditions in mind:

• The production journal should contain at least 8 logs.

• Minimum log size is 2 MB.

34 Assure MIMIX for AIX User Guide v5.2.04.00

 NOTE
Use the following equation to ensure that the space you allocate for LFCs
coincides with the physical partition size of the VG where the LFC LVs
are allocated. This enables you to utilize all the space in a LV. This is not a
requirement, you can elect to not utilize all the available space in a LV.

y = (number of LFCs / number of LFC LVs) * LFC size

Where y

should be evenly divisible by the physical partition size of the VG where

the LFC LVs are allocated.

• Maximum log size is one-half of the available RAM on the recovery server.

To calculate log size, you need the following information:

• Estimate of average write throughput

• Required processing rate. For example, if Assure MIMIX for AIX processes
one log every 60 seconds, the recovery server will be one minute behind the
production server.

Calculate log size as follows:

log size = (average write throughput)/(processing rate)

Calculate the number of logs as follows:

number of logs = (journal size)/(log size)

Determining storage requirements

Consider the following guidelines to determine storage requirements:
1. Use the following assumptions to decide on the appropriate storage
requirements.

Recovery Window goal = 1 day

Average Aggregate Write I/O per day = 1 GB

Network outage protection = 12 hours

Amount of data and metadata that will fit in an LFC:

– amount of data = .95 of LFC size

– amount of metadata = .05 of LFC size

Therefore, a 16MB LFC will hold 15.2 MB of data.

Assure MIMIX for AIX User Guide v5.2.04.00 35

 2. Using these assumptions, determine the LFC space.

Production LFC space __1GB x .5 = 500MB_________

Recovery LFC space __2 x (1GB) x 1 = 2 GB_________

3. Using this space, calculate the LFC size and the number of production and
recovery LFCs.

LFC size _16 MB___________________________

Production LFCs __500 /(16 * .95)= 33________________

Recovery LFCs ___2000/(16 * .95) = 132_______________

4. If there is space available to create a separate volume group, create a volume

group that is large enough to hold the LFCs.

36 Assure MIMIX for AIX User Guide v5.2.04.00

Application information checklist

Application Data Information

(to be protected by Assure MIMIX Customer Information
for AIX)

What is the location of the data

associated with the application?
Specifically, what bus, spindle, HBA,
or LUN contains the data?

What are the characteristics of the

data?

Are there licensing issues related to

running the application on the
recovery server?

Which applications or services need

to be highly available?

Will the application be running

during Assure MIMIX for AIX
installation?

Host name dependency?

IP address dependency?

Database information checklist

Database Customer Information

Database product and release

Supported in the high availability

(cluster) environment?

Supported for the operating system

release?

Which volume groups contain the

database or table to be protected?

What is the process for keeping the

data consistent?

Assure MIMIX for AIX User Guide v5.2.04.00 37

Domain name server checklist

Domain Name Server Customer Information

Is DNS enabled?

Is Network Information Services

(NIS) mounted?

Is NIS exported?

Network information checklist

Network Information Needed Customer Information

What kind of network connects the

production server and the recovery
server?

Are there firewall restrictions such as

port limitations between any of the
machines?

Which network connections are

shared and which are dedicated?

What are the IP addresses of the

following:
Administrative Server
production server
recovery server

What routers, bridges, and hubs are

part of the system?

Is the network currently established,

or will it be established during
Assure MIMIX for AIX installation?

Storage information checklist

Storage Information Needed Customer Information

Is storage direct-attached or SAN?

If SAN, what are the HBA and

firmware levels?

Disk IDs (hdisk) and associated

volumes (including the JFS log) and
file systems

38 Assure MIMIX for AIX User Guide v5.2.04.00

 Storage Information Needed Customer Information

Space required for the file systems,

including potential growth (number
and size)

Is there logical volume manager

mirroring?

What volumes are to be protected?

Which volumes store the

application?

Are the application volumes

logically shared?

Are the volumes physically shared?

Is the disk subsystem already

established, or will it be established
during Assure MIMIX for AIX
installation?

Tivoli Storage Manager

Information Needed Customer Information

Release:
• Policy domain
• Policy set
• Management class
• Backup copy
• Archive copy

Storage pools:
• Disk
• Tape

Policy domain:
• Type
• Number
• Shared?

General information checklist

Additional Information Needed Customer Information

Is FTP available on all servers?

If FTP is not available, are

CD-ROM drives available?

Assure MIMIX for AIX User Guide v5.2.04.00 39

 Additional Information Needed Customer Information

Does the application need specific

volume or file system names?

Logical volumes to be assigned to

Assure MIMIX for AIX
File system names and mount points

Number, size, and location of

Assure MIMIX for AIX redo logs.
Refer to “Allocating space for
Assure MIMIX for AIX logs and
journals” on page 29

How much time does the restore

window encompass?

40 Assure MIMIX for AIX User Guide v5.2.04.00

Using the Sizing Tool to Calculate
LFC Size 3

Overview of LFC sizing

Assure MIMIX for AIX uses Log File Containers (LFC) to transfer data from the
production Server to recovery server. Before you install Assure MIMIX for AIX,
you need to define the number of LFCs for the production and recovery servers.
On the recovery server, you must also define the Write Journal (WJ) disk space
percentage.

You can use the Sizing Tool to calculate configuration values before Assure
MIMIX for AIX is installed. It is also useful to run the tool after Assure MIMIX
for AIX is installed to determine if the number of LFCs or WJ percentage needs to
be adjusted.
This chapter describes:

• “System requirements for the sizing tool” on page 41

• “Installing the sizing tool” on page 41

• “Running the sizing tool from the Assure MIMIX for AIX Sizing Tool GUI”
on page 42

• “Running the sizing tool script from the command line” on page 49

System requirements for the sizing tool

Keep in mind the following system requirements before you run the Sizing tool:

• Can only be run on AIX.

• The sztool_gui requires Java 1.5 or greater.

• The sztool_gui requires Xwindows.

Installing the sizing tool

To install the Sizing tool refer to the following sections in Chapter 5 “Installation
Procedures” on page 59:

• “Installing Assure MIMIX for AIX using the installation wizard” on page 69

Assure MIMIX for AIX User Guide v5.2.04.00 41

 • “Using smit to install Assure MIMIX for AIX, the Assure UI server, and the
portal application” on page 78

NOTE
The Assure MIMIX for AIX Installation Wizard and the smit installation
program provide the sztool command for the command line Sizing Tool
and the sztool_gui command you can use to access the Assure MIMIX for
AIX Sizing Tool GUI.

Running the sizing tool from the Assure MIMIX for AIX
Sizing Tool GUI
You will need to install and enable XWindows on your workstation. You will need
to set up a DISPLAY environment variable on the AIX node so that it can launch the
Sizing Tool GUI on the workstation.

See “Installing X11 for the Sizing Tool” on page 417 for more information.

To access the Assure MIMIX for AIX Sizing Tool GUI, type
/usr/scrt/sztool/sztool_gui from the command line.

The Assure MIMIX for AIX Sizing Tool GUI window displays. The first tab,
Introduction displays, by default.

There are four Assure MIMIX for AIX Sizing Tool GUI tabs:

• “Introduction tab” on page 42

• “Config and Run tab” on page 44

• “View and Analyze Log tab” on page 46

• “View Chart tab” on page 48

Introduction tab
The Introduction page describes how you use the sizing tool. For detailed
information, click Help. This button displays the URL to access the Precisely
Support web site. From this site you can download documentation that describes
how you use the sizing tool. In addition, you are provided with Support email and
phone numbers. Click Exit to exit the Assure MIMIX for AIX Sizing Tool GUI.

42 Assure MIMIX for AIX User Guide v5.2.04.00

Assure MIMIX for AIX User Guide v5.2.04.00 43
 Config and Run tab
You use the Config and Run page to configure LVs. Perform the following activities
to configure LVs:

• To select individual LVs, use the check box next to the LV, to select the LVs that
will be protected by Assure MIMIX for AIX.

• Click the Select all LVs button to select all LVs.

• Click the Run Disk Discovery Again button to re-discover the LVs.

The table below describes the parameters that you can modify:

Parameter Description

Collection Interval Specifies how many times you want to collect data. The
Count default value is 24 hours.
Collection Interval Specifies how many minutes to wait between each data
Minutes collection interval. The default value is 60 minutes.

44 Assure MIMIX for AIX User Guide v5.2.04.00

 Parameter Description

Lfc Size (MB) Specifies the size for the Assure MIMIX for AIX LFC. The
default value is 16 MB.

Replication Outage Specifies the hours that the production server can not send LFCs
Hours to the recovery server. When this occurs, the LFCs will begin to
backup on the production sever, until there are no more LFCs
available. Once Assure MIMIX for AIX runs out of LFCs, it
marks the regions which require synchronization in the state
map as dirty. These dirty regions will automatically be
synchronized when the LFCs become available. CDP
functionality will resume as soon as the resynchronization
completes. More LFCs are required as outage time increases.
The default value is 8 hours.

CDP Window Specifies how many hours the data can go back in time to
Hours restore data from the recovery server to the production server.
The window size determines the number of LFCs on the
recovery server. The default value is 8 hours.

Snapshot Duration Specifies the number of hours you want to keep a snapshot
Hours valid. As the snapshot duration hours increase you need to
increase the Write Journals disk space. The default value is 8
hours.

• The Run button becomes active, when you select an LV(s) and specify values
for the LV parameters.

NOTE
Before you click the RUN button, start your application on the selected
LVs, and ensure that your application has a heavy load, so the tool collects
enough data to reflect the activity for a worst case scenario.

• Click the RUN button to:

– Save the configured data into /tmp/sztool/sztool.cfg file

– Invoke the backend sztool script
– Display the Job Progress Window. This window shows the sztool job status,
and enables you to:
• Close the window and re-display it by clicking the Get Job Status button.
• Halt the current running background job
• Exit from sztool and check results

Assure MIMIX for AIX User Guide v5.2.04.00 45

 NOTE
You can view /tmp/sztool/sztool.log on the production server, once the
back end sztool job (scripts) is running.

Click the Exit Sztool button to exit from sztool. The backend data
collection job will not be interrupted. You can come back later to check
the results via the View and Analyze Log tab.

View and Analyze Log tab

You use the View and Analyze Log page to view the log file output from the sztool
script sizing tool.

46 Assure MIMIX for AIX User Guide v5.2.04.00

 This page contains three sections:

• Results—This section shows general information for the sztool script sizing log
file. Click the Display Log button to display the results derived from the
original log file. You can view:

– Production server Number of LFCs and the production server disk space
requirements
– Recovery server Number of LFCs and the recovery server disk space
requirements
– Minimum Write Journal Percentage

• Detailed logs from latest run—This section shows a scrollable text area
containing detailed statistics for the sztool script sizing log file. The log file
name is /tmp/sztool/sztool.log Click the Display Log button to display the
results derived from the original log file. The columns show:

– Logical Volume
– IO Count
– Kb read

Assure MIMIX for AIX User Guide v5.2.04.00 47

 – Kb written
– Kbps (kilobit per second)

• Try different parameters to get results from the already collected data. You can
edit the parameters shown below to see different log file results.

– Lfc Size (MB) Low. Refer to “Lfc Size (MB)” on page 45.
– CDP Window Hours. Refer to “CDP Window Hours” on page 45.
– Replication Outage Hours. Refer to “Replication Outage Hours” on
page 45.
– Snapshot Duration Hours. Refer to “Snapshot Duration Hours” on page 45.

To see different log file results:

1. Change the LFC size and CDP Window Hours.

2. Click the Show results with above parameters button.

The sztool script executes against the collected data to display log file
information in the Results section and the Detailed logs from last run
section.

NOTE
This output will not overwrite the /tmp/sztool/sztool.log file contents.

3. Click the Display Log button if you wish to re-display the results derived
from the original log file.

View Chart tab

The Chart data represents the time with respect to total disk writes over time, on all
selected LVs. You can view data for individual LVs in the sztool.log. The unit of
writes is in MB.

NOTE
A pdf version of the Chart is automatically saved in
/tmp/sztool/DiskWriteChart.pdf.

48 Assure MIMIX for AIX User Guide v5.2.04.00

 The Help button displays the Sizing Tool GUI version and information to contact
Support.

Running the sizing tool script from the command line

Perform the following steps to run the sztool script from the command line.

NOTE
Before you run the Sizing tool you must have performed the installation
steps described in “Installing the sizing tool” on page 41.

1. To start the Assure MIMIX for AIX Sizing Tool, type

/usr/scrt/sztool/sztool from the command line. The tool automatically
creates a working directory /tmp/sztool, a config file /tmp/sztool/sztool.cfg
and a diskinfo file /tmp/sztool/diskinfo. The diskinfo file contains a list
of all LVs on the system. The user selects which LVs should be protected by
Assure MIMIX for AIX. The working directory is for storing the config file, log
file and tmp files. The configuration file is for user to specify LV names and
other run time parameters.

2. Review the diskinfo file and determine which LVs Assure MIMIX for AIX
should protect.

Assure MIMIX for AIX User Guide v5.2.04.00 49

 3. Modify the parameters in the sztool.cfg configuration file shown below:
LVs_1=testloglv testlv
LVs_2=
LVs_3=
LVs_4=
LVs_5=
LVs_6=
LVs_7=
LVs_8=
LVs_9=
LVs_10=
Collection_Interval_Count=24
Collection_Interval_Minutes=60
Lfc_Size_MB=16
Replication_Outage_Hours=8
CDP_Window_Hours=8
Snapshot_Duration_Hours=8

The table below describes the configuration file parameters that you can
modify:

Parameter Description

LVs_1= For example, you can enter LVs_1=LV1 LV2

LVs_2= LV2 LV4, with a space between each LV.
Typically, you place three or five LV names per
..... line as appropriate. You can add more LV
LVs_10= names for any additional lines. If there are not
any additional LV names, leave the remaining
LVs lines blank.

Collection_Interval_Count Specifies how many times you want to collect

data. The default value is 24 hours.

Collection_Interval_Minutes Specifies how many minutes to wait between

each data collection interval. The default value
is 60 minutes. Set the
Collection_Interval_Count to 24 hours and the
Collection_Interval_Minutes to 60 minutes.
This is referred to as the 24*60 setting. This is
the recommended configuration to use when
you execute the sztool script.

Lfc_Size_MB Specifies the size for the Assure MIMIX for

AIX LFC.

50 Assure MIMIX for AIX User Guide v5.2.04.00

 Parameter Description

Replication_Outage_Hours Specifies the hours that the production server

can not send LFCs to the recovery server. When
this occurs, the LFCs will begin to backup on
the Production Sever, until there are no more
LFCs available. Once Assure MIMIX for AIX
runs out of LFCs, it marks the regions which
require synchronization in the state map as
dirty. These dirty regions will automatically be
synchronized when the LFCs become available.
CDP functionality will resume as soon as the
resynchronization completes. More LFCs are
required as outage time increases.

CDP_Window_Hours Specifies how many hours the data can go back

in time to restore data from the recovery server
to the production server. The window size
determines the number of LFCs on the recovery
server.

Snapshot_Duration_Hours Specifies the number of hours you want to keep

a snapshot valid. As the snapshot duration
hours increase you need to increase the Write
Journals disk space.

4. Start your business application on the selected LVs. The load of the businesses
application should be as close to the worst case scenario to ensure a meaningful
result.

5. Type /usr/scrt/sztool/sztool from the command line to restart the

sztool. The sztool runs in background and you can check the results in the
/tmp/sztool/sztool.log. Check the /tmp/sztool/sztool.log file to
be sure the tool is running, one collection interval is required before LV I/O data
is written to the /tmp/sztool/sztool.log. Check the
/tmp/sztool/sztool.log after the last collection interval count for the final
result. It is safe to log out from the terminal because “sztool” uses “nohup”. The
process will take 24 hours with the default collection interval count of 24 and
collection interval of 60 minutes.

6. When the tool completes, check the log file or the AIX window. At the bottom
of the log file or AIX window, the “<<---------<" lines indicate the
production and recovery server number of LFCs, and the percentage of Write
Journal (WJ). The log file also contains detailed information for each LV IO
statistics for each data collection interval. The standard log file is called
sztool.log. An additional copy of the log file is also created,
sztool.log-MM_DD_YYYY-HH:MM:SS. For example:
sztool.log-02_19_2010-14_22_19, where HH is the 24 hour interval.

Assure MIMIX for AIX User Guide v5.2.04.00 51

 sztool script command options
The table below describes the sztool script command options.

sztool
script
Command Description
Options

sztool If issued for the very first time, the working directory, diskinfo
file and sztool.cfg file are generated. You should review the
diskinfo file and then modify sztool.cfg, accordingly. You can
then re-run sztool.

sztool -c Assigns CDP_Window_Hours a value and run against existing

data log file. Only screen output. Example: sztool -c24.

sztool -d Generates the /tmp/sztool/diskinfo file. Performed automatically

when you run sztool for the first time.

sztool -g Generates the sztool.cfg file in /tmp/sztool. Performed

automatically when you run sztool for the first time.

sztool -h Prints out a help message.

sztool -l When the log file is created, this command prints out the
calculation results for different LFC sizes based on the existing
log file. For example, sztool -l32 prints out the results when the
LFC size is at 32M. sztool -l16 -l512, prints out all the
calculation results from 32MB to 512MB. You cannot have
spaces between -l and the LFC size number. Only screen output,
there is not any delay or sleep.

sztool -r Assigns Replication_Out_Hours a value and runs against the

existing data log file. Only screen output. For example: sztool
-r24, or sztool -r24 -l2 -l32.

sztool -s Assigns Snapshot_Duration_Hours a value and runs against the

existing data log file. Only screen output. Example: sztool -s12.

sztool -x Executes the sztool and prints the file name and line number of
the statement for debugging purposes. For debugging, use
sztool_main -x to view screen output.

sztool -v Prints out the sztool version number.

52 Assure MIMIX for AIX User Guide v5.2.04.00

Supported Configurations
4

Assure MIMIX for AIX supported configurations are determined by the number
of datataps (kernel level software that intercepts application writes) and recovery
servers. Some of the configurations supported by Assure MIMIX for AIX are
presented in this chapter.

This chapter contains:

• “Replication using 4096 byte or 512 byte disk block sizes” on page 53

• “Local CDP Solution configuration” on page 54

• “WAN replication with no local CDP configuration” on page 54

• “Broadcast replication configuration” on page 55

• “Local bi-directional replication configuration” on page 55

• “Supported Assure MIMIX for AIX configurations” on page 56

• “Assure MIMIX HA for AIX configuration and resources not supported” on

page 57

• “Upgrading from GeoCluster v3.6 to Assure MIMIX HA for AIX” on

page 57

Replication using 4096 byte or 512 byte disk block sizes

IBM AIX introduced support for DISK BLOCK SIZE of 4096 bytes in AIX 7.1
TL3 and AIX 6.1 TL9.

You can replicate your source data, as long as the source and target disks have the
same DISK BLOCK SIZE. For example, you can replicate your source data that
resides on disks with a DISK BLOCK SIZE of 512 bytes to target disks with a
DISK BLOCK SIZE of 512 bytes. Additionally, Assure MIMIX DR for AIX
Containers must reside on disks with a DISK BLOCK SIZE of 512 bytes.

You can replicate your source data that resides on disks with a DISK BLOCK
SIZE of 4096 bytes to target disks with a DISK BLOCK SIZE of 4096 bytes.
Additionally, Assure MIMIX DR for AIX Containers must reside on disks with a
DISK BLOCK SIZE of 4096 bytes.

Assure MIMIX for AIX User Guide v5.2.04.00 53

 Use the AIX command lsvg <vgname> to determine the DISK BLOCK SIZE of a
volume group.

IMPORTANT
A replication group cannot contain a mix of 4096 byte and 512 byte disk
block size types.

Local CDP Solution configuration

This configuration involves one or more datataps, one recovery server, as well as
one LAN-based (100Mb Ethernet, GigE) network connection between the
production and the recovery servers.

LAN
Production
Recovery
Server
Server

Datatap

WAN replication with no local CDP configuration

This configuration involves one or more datataps and one recovery server.

When developing Assure MIMIX for AIX solution, the WAN bandwidth as well as
application peak throughput write I/O rates need to be considered.

Production WAN
Server Remote Recovery
Server

54 Assure MIMIX for AIX User Guide v5.2.04.00

Broadcast replication configuration
In this configuration there is one production server and two recovery servers
(Recovery 1 and Recovery 2) for data replication, snapshot creation, data recovery
and failover operations. If you want to move the production server due to an
unplanned outage or for maintenance, you must select Yes for the Failover option
on the Servers panel when you run the Configuration wizard, see page 109. With
multiple recovery servers, you can select the recovery server that you wish to
failover to at failover time in the first step of the Planned or Unplanned Failover
Procedures. See Chapter 15 “Disaster Recovery Operations” on page 275.

Local bi-directional replication configuration

This configuration involves one or more datataps and two recovery servers that are
associated through a LAN connection. Two interrelated contexts are created.
The LCA/ABA agents are used in a bi-directional manner. These agents need to be
configured before the failover and failback operations are used. For more
information about Assure MIMIX for AIX failover and failback operations, refer to
Chapter 14 “Introduction to Disaster Recovery” on page 267.

NOTE
The recovery server becomes the failover production server in the
bi-directional configurations. For more information about Assure MIMIX
for AIX failover operations, refer to Chapter 14 “Introduction to Disaster
Recovery” on page 267.

LAN
Production
Recovery
Server
Server

Assure MIMIX for AIX User Guide v5.2.04.00 55

Supported Assure MIMIX for AIX configurations

Production server and recovery server configuration

This configuration comprises a single cluster consisting of a production server node
and a recovery server node.

A production and recovery server configuration is supported when you use Assure
MIMIX HA for AIX with Assure MIMIX DR for AIX. The production server is
where the production applications reside. The recovery server, maintains data,
initializes rapid recoveries of production data, virtualizes Any Point-In-Time
recovery, and maintains enterprise processes off-loaded from the production server.

Production to recovery configuration

The figure above shows what happens during normal operation of a production to
recovery server configuration, the Primary Context is active on the production and
recovery servers. In this mode:

• The application started by Assure MIMIX HA for AIX and Assure MIMIX DR
for AIXon the production Server writes data to the local storage.

• An Assure MIMIX DR for AIX “Data Tap” intercepts these writes as they are
written to the logical volume and additionally sends them to the recovery server.

The recovery server writes the same, ordered data to another, independent storage
set. These servers may be connected via a LAN or WAN.

56 Assure MIMIX for AIX User Guide v5.2.04.00

Assure MIMIX HA for AIX configuration and resources not
supported
In prior versions of Assure MIMIX HA for AIX, the following configurations and
resources were supported; these configurations and resources are not supported in
version 5.2:

• Cascade replication

• Highly Available Production Server Environment

• Applications with no replication groups defined

• Disk Networks

• Shared Volume Groups

Upgrading from GeoCluster v3.6 to Assure MIMIX HA for AIX

The migrate_config.sh command automatically runs when you upgrade from
GeoCluster version 3.6 to Assure MIMIX HA for AIX.

The following sample output shows what the migration report will look like:

################################################################################
EchoCluster 3.6.0.2 -> Assure MIMIX for AIX 5.1 Migration Report:
Volume groups removed from p520-71: ID100, ID298, ID37, ID435, ID502, ID65, ID72
Disk NetworkInterfaces removed from p520-71: ID463
Volume groups removed from p520-72: ID100, ID298, ID37, ID435, ID469, ID65, ID72
Disk NetworkInterfaces removed from p520-72: ID464
Applications (no Assure MIMIX DR for AIX contexts defined) removed: ID268, ID451
Applications (highly available production server configuration) removed: ID320
AppGroups removed: ID271, ID323, ID454
Disk networks removed: ID462
Highly available production server contexts removed: ID539

Upgraded.\data\ID4ccd0527-c558-4c0c-8c35-af20bb975994\104.xml

The migration completed successfully at Tue Mar 10 11:31:15 EDT 2015

################################################################################

Assure MIMIX for AIX User Guide v5.2.04.00 57

58 Assure MIMIX for AIX User Guide v5.2.04.00
Installation Procedures
5

Overview
This chapter describes Assure MIMIX for AIX, the Assure MIMIX for AIX portal
application and the Assure UI server installation procedures.
Before you begin, ensure that you review support information, system
requirements, and decide on your preferred configuration. Once you have
installed the Assure MIMIX for AIX components you can work with the Assure
UI portal. Refer to “Logging in to the Assure UI portal” on page 88.

• “System requirements for Assure MIMIX for AIX” on page 60

• “Assure UI portal and portal application system requirements” on page 62

• “Assure MIMIX for AIX installation wizard prerequisites” on page 63

• “Important licensing information” on page 64

• “Installing Assure MIMIX for AIX from the command line” on page 66

• “Install a new instance of Assure MIMIX for AIX” on page 70

• “Reinstall Assure MIMIX for AIX” on page 74

• “Upgrade Assure MIMIX for AIX” on page 76

• “Using smit to install Assure MIMIX for AIX, the Assure UI server, and the
portal application” on page 78

• “Installing using native interface commands” on page 80

• “Uninstall Assure MIMIX for AIX” on page 84

• “Using smit to uninstall Assure MIMIX for AIX” on page 86

• “Installing the Assure UI server and the portal application on Windows” on

page 86

• “Uninstalling the Assure UI server and the portal application from Windows”
on page 87

Assure MIMIX for AIX User Guide v5.2.04.00 59

System requirements for Assure MIMIX for AIX
Assure MIMIX for AIX requires an IBM System p™ with the IBM AIX operating
systems.

NOTE
Assure MIMIX for AIX supports Internet Protocol version 6 (IPv6).

Operating system requirements

Assure MIMIX for AIX runs on the IBM AIX operating system. Supported versions
include:

• AIX version 7.3

• AIX version 7.2

• AIX version 7.1

• requires 7100 TL3 SP3 or higher

• requires 7100 TL2 SP5 or higher
• requires 7100 TL1 SP10 or higher

• If you are using Open SSH 7.x, you must:

– Before you use the Assure MIMIX for AIX Installation Wizard, you must
add these lines to the /etc/ssh/sshd_config file on each AIX server, and then
restart sshd:
• PermitRootLogin yes
• KexAlgorithms +diffie-hellman-group1-sha1
• Ciphers +blowfish-cbc
– When using the wizard, you must log in as the root user.

• If you are using Open SSH 8.x, you must:

– Before you use the Assure MIMIX for AIX Installation Wizard on AIX 7.3,
you must add these lines to the /etc/ssh/sshd_config file on each AIX server,
then restart sshd:
• PermitRootLogin yes
• KexAlgorithms +diffie-hellman-group1-sha1
• Ciphers +3des-cbc
– When using the wizard, you must log in as the root user.

60 Assure MIMIX for AIX User Guide v5.2.04.00

 Time synchronization (xntpd) requirement
The use of time synchronization is required to keep the time between the nodes in a
replication group in sync for both application and Assure MIMIX for AIX
functionality and log issues.

Disk space and memory requirements

Review the Assure MIMIX for AIX disk space and memory requirements:

• Assure MIMIX for AIX requires 2 MB in root and 125 MB in /usr. The 125 MB
in /usr is for the /usr/scrt directory which contains binaries, libraries,
configuration, and logs.

IMPORTANT
The /home/usr/scrt/ directory is created when the scrt user is created in
AIX. Do not copy any files to this directory because Assure MIMIX for
AIX deletes this directory during the de-installation process.

• The amount of RAM required for the Assure MIMIX for AIX application
depends on the size of the protected data (StateMap size) and log size. The
maximum log size is one half of RAM.

• The disk space requirement for Assure MIMIX for AIX file containers is
approximately 500 MB for a small configuration.

• For each Replication Group, allow approximately 200 MB in /var for log
files.

• The disk space requirement is approximately 70 MB for a small configuration

and diagnostic logs.

• Assure MIMIX for AIX requires at least 128 MB for logs on the production
server, and at least 256 MB for logs on the recovery server for LFCs. The LFCs
on the recovery server contain the undo and redo logs.

• The calculation for the undo and redo logs is based on the required recovery
window and the network outage protection size. Refer to “Determining storage
requirements” on page 35. If you use the snapshot journal, ensure that you take
into account its size. Refer to “Guidelines for snapshot journal size” on
page 34.

• The operating system and maintenance level must be correctly installed on all
nodes. Each node should be at the same operating system version, and within
two release levels of each other.

• You should have at least 110MB of temporary disk space in /usr/sys for
installation. The Cluster services will need an additional 86MB free space in
/usr.

Assure MIMIX for AIX User Guide v5.2.04.00 61

 Network requirements
To ensure that you can replicate data, issue the ping command, which uses Internet
Control Message Protocol (ICMP), to verify that the IP addresses configured for
Assure MIMIX DR for AIX are active. You must verify that you can ping the IP
addresses configured for the recovery server from the production server and vice
versa. This means that the ICMP packets are not blocked or discarded at the router
level.

The ping command uses the following ICMP types:

• ICMP, type 8 (echo-request)

• ICMP, type 0 (echo-reply)

These ICMP types should not be blocked on the intermediate routers.

NOTE
ICMP traffic should be allowed on both the host IP address
(HostIPAddress) and all replication IP addresses (IPAddress,
IPAddressAlt1-IPAddressAlt8).

Example
You have an active, reachable IP address 10.10.1.2 (production server), and you
want to ping 192.168.1.2 (recovery server).

To reach the destination, 192.168.1.2, network traffic flows through the 10.10.1.1
router, which will forward the ICMP packets to the 192.168.1.* network.
If you specify,
# ping 192.168.1.2

and there is no response, this indicates that the ICMP packets sent by the ping
command are possibly dropped by the router for the network between the two
systems.

Archiving products supported

Assure MIMIX for AIX supports archiving LFCs and making backups of Replica
LVs using the Tivoli® Storage Manager on AIX.

Assure UI portal and portal application system requirements

The Assure UI portal and the Assure MIMIX for AIX portal application (PA) have
the following system requirements.

• The required disk space to install and run the Assure UI portal and the Assure
MIMIX for AIX portal application is approximately 1 GB in /opt, of which 375

62 Assure MIMIX for AIX User Guide v5.2.04.00

 MB is required for the software and the rest is needed to preserve the last 10
rotating log files for different components of the Assure UI portal.

• The required physical RAM is 2 GB for the Assure UI portal.

• Internet Explorer 9 or above, or Firefox.

• The wizard includes Java 8 JRE, which is used during installation processes and
is removed when installation completes. The Java Runtime Environment (JRE)
included in the wizard has a .dll with dependencies on
C:\Windows\System32\vcruntime140.dll. The vcruntime140.dll must be present
on the PC where the wizard will be used to allow the wizard to properly open
and run. The file is part of the Microsoft Visual C++ software runtime library. If
the file is missing, you can install or reinstall the Microsoft Visual C++
Redistributable Package from Microsoft's website. A web search can identify
other means of obtaining the vcruntime140.dll.

NOTE
The Assure UI portal supports Internet Protocol version 6 (IPv6).

Assure MIMIX for AIX installation components

You can designate the Assure MIMIX for AIX components you wish to install
during the installation process:

• Assure MIMIX DR for AIX

• The Assure MIMIX HA for AIX (the clustering component) is automatically

installed but can only be used if licensed.

• The Assure UI portal and the Assure MIMIX for AIX portal application

• Documentation

Note: The Sizing tool is automatically installed when you install the Assure
MIMIX DR for AIX component.

Assure MIMIX for AIX installation wizard prerequisites

If you use the Assure MIMIX for AIX installation wizard, the following
prerequisites are required on the AIX target system:

• The wizard includes Java 8 JRE, which is used during installation processes.
The Java Runtime Environment (JRE) included in the wizard has a .dll with
dependencies on C:\Windows\System32\vcruntime140.dll. The
vcruntime140.dll must be present on the PC where the wizard will be used to
allow the wizard to properly open and run. The file is part of the Microsoft
Visual C++ software runtime library. If the file is missing, you can install or
reinstall the Microsoft Visual C++ Redistributable Package from Microsoft's

Assure MIMIX for AIX User Guide v5.2.04.00 63

 website. A web search can identify other means of obtaining the
vcruntime140.dll.

• Either ssh and scp or rexec and rcp must be allowed. If ssh fails then rexec and
rcp is used.

• If rexec will be used rexecd must be configured in /etc/inetd.conf.

• To use rcp the ~root/.rhosts file must have the local host and user name.

• Check /etc/services to find the ports used by exec and shell and check that those
ports are not blocked.

• There is the option available to send a ping to the AIX system to determine if it
is reachable.

• This requires that the “echo” port is not blocked. This is usually defined as port
7 in /etc/services

Before you install

Review the following before you install:

1. Request a license for each node as described in Request license keys from AIX
or Windows.

2. Reviewing “Important licensing information” on page 64.

3. Ensure each target node is connected by the network to the production and
recovery server(s). Make sure that host names and IP addresses of Assure
MIMIX for AIX servers are accessible from the workstation.

Important licensing information

The following sections describe license key considerations:

• “Request license keys from AIX or Windows” on page 64

• “License file considerations” on page 66

Request license keys from AIX or Windows

Follow the steps shown below to request license keys for Assure MIMIX for AIX
from an AIX machine or a Windows machine:

• Precisely Support at https://support.precisely.com/. Proceed to step 1.

• Assure MIMIX for AIX installation CD. Proceed to step 2.

1. From https://support.precisely.com/

a. If necessary, select the link to access Syncsort products.

64 Assure MIMIX for AIX User Guide v5.2.04.00

 b. Sign in with your email address and password.
c. Under MyProducts, select Assure MIMIX for AIX.
d. Select the version number from the Version dropdown.
e. Click the License Keys tab.
f. Click License Key Request. Fill out the License Key Request form and then
click Submit. This sends a request to Precisely and your license keys will be
emailed to you.
2. To request license keys from the Assure MIMIX for AIX installation CD:

a. If the installation CD is copied to an AIX machine, click install.bin.

b. If the installation CD is copied to a Windows machine, click install.exe.
The Assure MIMIX for AIX Welcome screen displays.

3. On the Welcome screen, click Next and navigate to the License Key Locations
screen.

4. On the License Key Locations screen, click Continue Without License Keys.

5. On the Continue Without License Keys screen, select Contact Precisely to get
new license keys, and click Next.

The Contact Precisely screen displays.

6. Use one of the following methods to procure license keys.

• On the Internet—Sign in to your account at:

https://support.precisely.com/
• Email—Copy and paste the information on the Contact Precisely screen into
your email message. You can find the email address for your geographical
location in the Contact Us information displayed when you have signed into
the Support website. When you contact Precisely Customer Accounting
supply the Node name, Unique ID, System Model, and Online Virtual CPUs.
Email your information to Precisely Customer Accounting and request a
license key. A license file will be generated and emailed to you.

Assure MIMIX for AIX User Guide v5.2.04.00 65

 License file considerations
Table 1, “License Information for Customer Accounting,” on page 66 summarizes
the information you must provide Customer Accounting when requesting a new
license key.

Table 1 License Information for Customer Accounting

Provide 5.2 licensing information for
Customer Accounting AIX Command Example

LPAR (partition ID) uname -f “03CC409102B99203”

Hardware Tier uname -M “IBM,7778-23X”
(System Model)
Number of CPU’s lparstat -i Use the “Online Virtual CPUs”
value
Product Major.Minor number 5.2
Maintenance expiration Optional

Licensing notes:
• If you upgrade your system and the system model changes, it is required that
you obtain and apply a new license file. There is a 30-day grace period to obtain
the new license file.

• Replication is suspended in the following situations:

– When an Assure MIMIX for AIX license key expires replication will be
suspended until a new license key file is applied on the server(s) that has
the expired license key files. Use the Update License Keys wizard to
update license keys for Assure MIMIX for AIX software already
installed on a server. To access the wizard, run Setup.exe. The Assure
MIMIX for AIX Splash screen displays. You can then select the License
Keys wizard.
– If the processor resources are increased to a value that is greater than the
value specified in the license key file, the license key will become Not
valid. Replication will be suspended until the processor resources value is
decreased to the value specified in the license key file or you obtain and
apply a new license key file with a greater number of CPUs.

Installing Assure MIMIX for AIX from the command line

1. Create a directory on the file system with minimum 1.4G of free space.

For example

# mkdir -p /usr/sys/inst.images/5.2.4

66 Assure MIMIX for AIX User Guide v5.2.04.00

 # cd /usr/sys/inst.images/5.2.4

2. Download MX_5240.zip into the newly created directory.

NOTE
If your AIX node cannot be unzipped, then download MX_5240.tgz.

3. Unzip MX_5240.zip file by running “# unzip MX_5240.zip”

Additionally, uncompress the zip file by running:

# gzip -d MX_5240.tgz
# tar xvf MX_5240.tar

4. Change the permission of the install_mx.sh install script to make it

executable by running “# chmod +x install_mx.sh”
5. Start the install by running “# install_mx.sh –options”.
The following are the available options when you run the command:

Usage: install_mx.sh [-i|-u] [-c] [-e] [-p] [-a] [-h]

• -i : If this is a new install

• -u : If this is a reinstall of same version or an upgrade
• -e : Install (Assure MIMIX for AIX - includes Common Java and
MXWS)
• -c : Install Assure MIMIX HA for AIX
• -p : Assure Unified Interface including MIMIX for AIX Portal
Application
• -a : Install all (Assure MIMIX for AIX including Common Java and
MXWS) and Assure Unified Interface including MIMIX for AIX Portal
Application and Assure MIMIX HA for AIX
• -h : Help message on install_mx.sh

Examples:

• Install Assure MIMIX for AIX

install_mx.sh -i -e

• Install Assure MIMIX HA for AIX

install_mx.sh -i -c

• Install Assure MIMIX HA for AIX & Assure MIMIX for AIX

install_mx.sh -i -c -e

• Upgrade Assure Unified Interface

Assure MIMIX for AIX User Guide v5.2.04.00 67

 install_mx.sh -u -p

• Upgrades/reinstall Assure MIMIX for AIX and Assure Unified Interface

install_mx.sh -u -e -p

6. After initiating the installation procedure, you must accept the End User License
Agreement (EULA). You can navigate through it by pressing "Enter" or skip it
by pressing "q". When you reach the end of the EULA, the following message
appears:

Please type 'yes' to confirm that you accept

Precisely Inc. End User License Agreement

You can accept the message typing 'yes', and the installation will proceed. If no
valid response is received after ten attempts, the installation process will fail.
7. Request license keys from AIX

Follow the below steps to request license keys for Assure MIMIX for AIX
from an AIX system:

From https://support.precisely.com/

a. Select the link to access Precisely products, if required.

b. Sign in with your email address and password.
c. Under MyProducts, select Assure MIMIX for AIX.
d. Select the version number from the Version dropdown.
e. Click the License Keys tab.
f. Select Request License Key. Complete the License Key Request form
and click Submit. This sends a request to Precisely, and you will receive
your license keys through an email.
g. The license file received from Support should be copied to the below
location on the AIX node:
/usr/scrt/run/node_license.properties
8. License file considerations

The following table summarizes the information you must provide Customer
Accounting when requesting a new license key:

68 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 2: License Information for Customer Accounting

Provide 5.2
licensing
information for
Customer
Accounting AIX Command Example
LPAR (partition uname -f “03CC409102B99
ID) 203”

Hardware Tier uname -M “IBM,7778-23X”

(System Model)
Number of CPUs lparstat -i Use the “Online
Virtual CPUs”
value

Product 5.2
Major.Minor
number

Maintenance Optional
expiration

Licensing notes:

• When you upgrade your system and the system model changes, you must
obtain and install a new license file. There is a 30-day grace period to obtain
the updated license file.
• When an Assure MIMIX for AIX license key expires, replication stops until
a new license key file is applied to the server(s) containing the expired
license key files.

9. Run the validate_license command

After you apply the license, run the validate license command:
/usr/scrt/bin/validate_license

A message about license validation shows, such as License validated or License

validation failed.

Installing Assure MIMIX for AIX using the installation wizard

This section describes:

• “Install a new instance of Assure MIMIX for AIX” on page 70

• “Install MIMIX for AIX portal application only” on page 73

• “Reinstall Assure MIMIX for AIX” on page 74

Assure MIMIX for AIX User Guide v5.2.04.00 69

 • “Upgrade Assure MIMIX for AIX” on page 76

IMPORTANT
Although the installation wizard is still available, it is no longer included
with the software. Please contact help if you require the Installation
Wizard.

Install a new instance of Assure MIMIX for AIX

When you use the installation wizard to install a new instance of Assure MIMIX DR
for AIX or Assure MIMIX HA for AIX, the wizard also installs the Assure MIMIX
for AIX portal application and the Assure Unified Interface.

1. Download the Assure MIMIX for AIX installation program from the:

• Precisely Support at https://support.precisely.com/.

• Assure MIMIX for AIX installation CD. Proceed to step 2.

To download, do the following:

a. Under My Products, select Assure MIMIX for AIX.

b. Click the Downloads tab.
c. Select and download the Assure MIMIX for AIX product zip file.
2. Do one of the following:

• Click Setup.exe, to display the Assure MIMIX for AIX Installation splash
screen. Then, click Install Assure MIMIX for AIX.
• Execute install.bin, to run the Assure MIMIX for AIX Installation Wizard.

The Assure MIMIX for AIX Welcome screen displays.

• Run install.exe to install onto a remote AIX machine.

The Assure MIMIX for AIX Welcome screen displays.

The Assure MIMIX for AIX Installation Wizard runs and displays the
Assure MIMIX for AIX Welcome screen.

Click Next.

3. The Terms And Conditions screen displays. Read and accept the terms of the
License Agreement. Click Next.

4. The Select Product screen displays. Select Assure MIMIX for AIX. Click Next.

5. The Installation Options screen displays.

Select Create a new installation—Create a new Assure MIMIX for AIX

installation. Click Next.

70 Assure MIMIX for AIX User Guide v5.2.04.00

 IMPORTANT
The following steps detail how to create a new installation.

6. The Node Login screen displays.

NOTE
You must log into the node as root.

a. Enter User and root password.

b. Click Log In to log in to the node.
c. Click Next.
7. The Specify Nodes screen displays.
a. Enter the node name or IP address and click Add. This points the installer to
the target node where you want to install Assure MIMIX for AIX. The
Specify Nodes screen displays with the additional node.
b. Click Next.
The Node Login screen displays. Specify the Password and click Log In.Then
Click Next.

The Retrieving Installation Information screen briefly displays. When the

Product Options screen display appears, click Next.

The Documentation Options screen displays. Select the node for which the
documentation will be installed and click Next.

8. The License Key Location screen displays. Do one of the following:

• If you have license key files from Precisely, click Next. Proceed to step 11
on page 72.
• Click Continue Without License Keys.

9. The Continue Without License Keys screen displays. Select one of the
following and click Next.

• Select Complete the installation without license keys to install Assure

MIMIX for AIX without license keys. You can install Assure MIMIX for
AIX without license keys but cannot use it until valid license keys are
applied. Proceed to step 11 on page 72.
• Select Contact Precisely to get new license keys.

10. If you selected to contact Precisely to get new keys, the Contact Precisely screen
displays. Use one of the following methods to procure license keys.

– On the Internet—Log in to your account at:

https://support.precisely.com/.

Assure MIMIX for AIX User Guide v5.2.04.00 71

 – Email—Copy and paste the information on the Contact Precisely
screen into your email message. Email your information to Precisely
Customer Accounting and request a license key. You can find the
email address for your geographical location in the Contact Us
information displayed when you have signed into the Support website.
A license file will be generated and emailed to you.

NOTE
Once you procure the license keys from Precisely, click Next on the
License Key Location (see page 71) to continue the installation. Proceed to
step 11 on page 72.

11. The License Key Check screen briefly displays to validate your license keys,
then the Installing Assure MIMIX for AIX screen displays showing the results
of the installation process for the Assure MIMIX for AIX software.

12. When the Assure MIMIX for AIX installation completes the Install Assure
Unified Interface screen displays. Select the nodes where you want to install
Assure Unified Interface.

Click Next.

13. The Installing Assure Unified Interface screen briefly displays.

When the installation completes, the Installation Complete screen displays.

NOTE
To enable HTTPS (SSL) refer to the Assure Unified Interface User’s Guide
packaged with Assure MIMIX for AIX.

14. After you have installed Assure MIMIX for AIX, the Assure MIMIX for AIX
portal application, and the Assure UI server, you can log into the Assure UI
portal. You must have a valid user ID and password for the node on which the
Assure UI server is installed. See “Logging in to the Assure UI portal” on
page 88.

15. Click Done to exit the installation wizard.

Define user groups

The installation process creates the ECadm and ECops groups in /etc/group. If you
are working with Assure MIMIX HA for AIX you must be a member of one of these
groups. Once the installation has added the groups, a system administrator must add
individual system users to those groups.

72 Assure MIMIX for AIX User Guide v5.2.04.00

 Install MIMIX for AIX portal application only
When you use the installation wizard and select the option to install the MIMIX for
AIX portal application only, the Assure UI server and the Assure MIMIX for AIX
portal application are installed. The

1. Click Next on the Welcome and Terms and Conditions screens.

2. The Select Product screen displays.

a. Select Assure Unified Interface.

b. Click Next.
3. The Node Login screen displays.

a. Enter the Node and root password.

NOTE
You must log into the node as root.

b. Click Log In to log in to the node.

c. Click Next.
The Retrieving Installation Information screen displays temporarily.

4. The Specify Nodes screen displays.

a. If you want to install the Assure UI portal on more than one node, enter a
node name or IP address in the Node or IP address field, and click Add.
b. Click Next.
The Retrieving Installation Information screen displays temporarily.
5. After the installation information is successfully retrieved, the Install Assure
Unified Interface screen appears showing the node on which the Assure UI
server will be installed. Click Next.

The Installing Assure Unified Interface screen displays.

6. When the installation completes, the Summary screen displays.

NOTE
To enable HTTPS (SSL), refer to the Assure Unified Interface User’s
Guide packaged with Assure MIMIX for AIX.

After you have installed the Assure MIMIX for AIX portal application and the
Assure UI server, you can log into the Assure UI portal. You can access the
portal from the Launch Portal button. You must have a valid user ID and
password for the node on which the Assure UI server is installed. See “Logging
in to the Assure UI portal” on page 88.

Assure MIMIX for AIX User Guide v5.2.04.00 73

 Click Done to exit the installation wizard.

User roles
The installation process creates the scrt group in /etc/group, identifying the
category of users allowed to access the portal application.

IMPORTANT
The root user is always allowed access to the portal application.

Reinstall Assure MIMIX for AIX

Before you reinstall Assure MIMIX for AIX:

• You must stop your application and Assure MIMIX for AIX on the node(s)
where Assure MIMIX for AIX is being reinstalled.

• If you have Assure MIMIX for AIX fixes (epkg files) installed they must be
uninstalled before you can perform the reinstall. Assure MIMIX for AIX fixes
(epkg files) begin with the letters ES.

Use one the following methods to list all installed fixes (epkg files).

a. From the command line: emgr -l

b. From SMIT: use fast path emgr by running smit emgr
Use one the following methods to remove installed Assure MIMIX for AIX
fixes.

From the command line:

a. From the command line: emgr -rL <LABEL>

b. From SMIT: use fast path emgr by running smit emgr
To reinstall Assure MIMIX for AIX:

1. Download the Assure MIMIX for AIX installation program from either the:

• Precisely Support web page at https://support.precisely.com/.

• Assure MIMIX for AIX installation CD. Proceed to step 2.
a. Under My Products, select Assure MIMIX for AIX.
b. Click the Downloads tab.
c. Select and download the Assure MIMIX for AIX product zip file.
2. Do one of the following:

• Click Setup.exe, to display the Assure MIMIX for AIX Installation splash
screen. Then, click Install Assure MIMIX for AIX.
• Execute install.bin, to run the Assure MIMIX for AIX Installation Wizard.

74 Assure MIMIX for AIX User Guide v5.2.04.00

 The Assure MIMIX for AIX Welcome screen displays.

• Run install.exe to install onto a remote AIX machine.

The Assure MIMIX for AIX Welcome screen displays.

3. The Assure MIMIX for AIX Installation Wizard runs and displays the Assure
MIMIX for AIX Welcome screen. Click Next.

4. The Terms And Conditions screen displays. Read and accept the terms of the
License Agreement and click Next.

5. The Select Product screen displays. From the Select Product screen select
Assure MIMIX for AIX and Assure Unified Interface and click Next.

6. The Installation Options screen displays. Select or reinstall an existing

installation and click Next.

7. The Node Login screen displays.

a. Enter the User and root password.

NOTE
You must log into the node as root.

b. Click Log In to log in to the node.

c. Click Next.
8. The Specify Node screen displays. Enter the node name and click Add. This
points the installer to the target node where you want to install Assure MIMIX
for AIX. Alternatively, you may enter an IP address.

Click Next.

9. The Product Options screen displays. Click Next.

10. The Documentation Options screen displays. Click Next.

11. The License Key options screen displays.

You have two options:

• If you select Use existing license keys, the License Key Check screen
displays.
• If you select Specify the location of license keys, the License Key Location
screen displays.

After you specify license keys and they are validated, click Next.

12. The Product Shutdown Required screen displays. You must manually ensure
that Assure MIMIX for AIX is shut down, the wizard does not perform this task.
Click Next.

Assure MIMIX for AIX User Guide v5.2.04.00 75

 13. Once the installation wizard has verified that Assure MIMIX for AIX has been
shutdown, the Installing Assure MIMIX for AIX screen displays. Click Next to
reinstall Assure MIMIX for AIX.

14. When the Assure MIMIX for AIX reinstall completes, the Install Assure
Unified Interface screen appears. Click Next to reinstall Assure Unified
Interface and the portal application.

15. The Installing Assure Unified Interface screen briefly displays.

When the Assure Unified Interface and the portal application reinstall
completes, the Installation Complete screen displays.

16. After you have reinstalled Assure MIMIX for AIX, you can log into the Assure
UI portal. You can select one of the highlighted nodes to launch the Assure UI
portal and log in. See “Logging in to the Assure UI portal” on page 88.

17. Click Done to exit the installation wizard.

Upgrade Assure MIMIX for AIX

Before upgrading Assure MIMIX for AIX to the current version:

• You must stop your application and Assure MIMIX for AIX on the node(s)
being upgraded.

• If you have Assure MIMIX for AIX fixes (epkg files) installed they must be
uninstalled before you can perform the upgrade. Assure MIMIX for AIX fixes
(epkg files) begin with the letters ES and EC.

Use one the following methods to list all installed fixes (epkg files).

a. From the command line: emgr -l

b. From SMIT: use fast path emgr by running smit emgr
Use one the following methods to remove installed Assure MIMIX for AIX
fixes.

From the command line:

a. From the command line: emgr -rL <LABEL>

b. From SMIT: use fast path emgr by running smit emgr
To upgrade to the current version of Assure MIMIX for AIX:

1. Obtain the Assure MIMIX for AIX installation program from either the:

• Precisely Support web page at https://support.precisely.com/.

• Assure MIMIX for AIX installation CD. Proceed to step 2.

To download, do the following:

a. Under My Products, select Assure MIMIX for AIX.

76 Assure MIMIX for AIX User Guide v5.2.04.00

 b. Click the Downloads tab.
c. Select and download the Assure MIMIX for AIX product zip file.
2. Do one of the following:

• Click Setup.exe, to display the Assure MIMIX for AIX Installation splash
screen. Then, click Install Assure MIMIX for AIX.
• Execute install.bin, to run the Assure MIMIX for AIX Installation Wizard.

The Assure MIMIX for AIX Welcome screen displays.

• Run install.exe to install onto a remote AIX machine.

The Assure MIMIX for AIX Welcome screen displays.

The Assure MIMIX for AIX Installation Wizard runs and displays the
Assure MIMIX for AIX Welcome screen.

Click Next.

3. The Terms And Conditions screen displays. Read and accept the terms of the
License Agreement and click Next.

4. The Select Product screen displays. From the Select Product screen select
Assure MIMIX for AIX and Assure Unified Interface and click Next.

5. The Installation Options screen displays. Click Next.

6. The Node login screen displays.

a. Enter the node name—Points the installer to the target node where you want
to install Assure MIMIX for AIX. Alternatively, you may enter an IP
address.
b. Click Next.
7. The Specify Nodes screen displays.
a. Enter the Node name or IP address and click Add. The node is added to the
list.
b. Click Next.
8. The Node Login screen displays. Specify the password and click Log In, then
click Next.

9. The Retrieving Installation Information screen displays temporarily. After the

installation information is successfully retrieved, the Assure MIMIX for AIX
Product Options screen displays. Click Next.

10. The Documentation Options screen displays.

a. Select the node on which the documentation will be installed.

b. Click Next.
11. The License Key Options screen displays. You have two options:

Assure MIMIX for AIX User Guide v5.2.04.00 77

 • If you select Use existing license keys, the License Key Check screen
displays.
• If you select, Specify the location of license keys, the License Key Location
screen displays.

After you specify license keys and they are validated, click Next.

12. The Product Shutdown Required screen displays. You must manually ensure
that Assure MIMIX for AIX is shutdown, the wizard does not perform this task.
Click Next.

13. Once the installation wizard has verified that Assure MIMIX for AIX has been
shut down, the Shutdown Verification Complete screen displays. Click Next.

14. If you have efixes, the Efix Removal Required screen displays. You must
manually remove the efixes, the wizard does not perform this task. Refer to
page 76 for information on how to remove efixes.

After you remove the efixes, click Next.

15. The Verify Efix Removal screen displays. When the efix verification
successfully completes the Efix Removal Verification Complete screen
displays. Click Next.

16. The Installing screen displays. When the installation upgrade completes, the
Install Assure Unified Interface screen displays.

Click Next.

17. The Shut Down Assure Unified Interface screen displays. It is recommended to
shut down the Assure Unified Interface. Click Next.

18. The Installing Assure Unified Interface screen displays. When the Assure
Unified Interface installation completes, the Installation Complete screen
displays.

After you have upgraded the Assure MIMIX for AIX portal application, you can
log into the Assure UI portal from the Launch Portal button. You must have a
valid user ID and password for the node on which the Assure UI server is
installed. See “Logging in to the Assure UI portal” on page 88.

Click Done.

Using smit to install Assure MIMIX for AIX, the Assure UI

server, and the portal application
To use smitty to install Assure MIMIX for AIX, the Assure UI server, and the
Assure MIMIX for AIX portal application:

• “Step 1. Request a License” on page 79

78 Assure MIMIX for AIX User Guide v5.2.04.00

 • “Step 2: Install Assure MIMIX for AIX, the Assure UI server, and the portal
application” on page 79

Step 1. Request a License

1. Identify the Machine ID/Host ID number. From a UNIX prompt, issue the
command:

a. Mount the CD
b. Run bin/AIX/machine_id.bin
2. Check the Precisely Support web page https://support.precisely.com/ for the
email address for your geographical location in the Contact Us information
displayed when you have signed into the Support website. Send the following
information in email to Precisely Customer Accounting:

• Company Name
• Product(s) for which you are requesting a license
• Machine ID
• Operating system
• Operating system version
• Node name (hostname)

A license file is generated, attached to an email, and sent back to you.

3. Save the license file in a location of your choice.

Step 2: Install Assure MIMIX for AIX, the Assure UI server, and the portal
application
1. Download the Assure MIMIX for AIX installation program from the Precisely
Support web page at https://support.precisely.com/.
2. Extract and copy the appropriate directory and files from your PC to the AIX
server.

3. Log into the AIX system as root.

4. Navigate to the Assure MIMIX for AIX software.

5. Enter the following command:

smit

The System Management screen displays.

6. Select Software Installation and Maintenance.

7. Select Install and Update Software.

8. Select Install Software.

Assure MIMIX for AIX User Guide v5.2.04.00 79

 9. Select the current directory as the INPUT device/directory and enter a dot (.).

10. Press OK.

The Software to Install screen displays.

11. Click List to the right of SOFTWARE to install.

12. Click to select the components you want to install.

NOTE
Before selecting the components you want to install, see “Installing using
native interface commands” on page 80 on page 76 for more information.

13. After you have made your selections, press OK to initiate smit and install the
selected components.

After you have installed Assure MIMIX for AIX and, the Assure MIMIX for AIX
portal application, you can log into the Assure UI portal. See “Logging in to the
Assure UI portal” on page 88.

Installing using native interface commands

Assure MIMIX for AIX, the Assure UI server, and the Assure MIMIX for AIX
portal application can all be installed on the same node, or the Assure UI server and
the Assure MIMIX for AIX portal application can be installed on a separate node.

• “Installing Assure MIMIX for AIX, Assure UI server, and the portal application
on the same node” on page 80

• “Installing the Assure UI server and the portal application on a separate node”
on page 81

Installing Assure MIMIX for AIX, Assure UI server, and the

portal application on the same node
Installing Assure MIMIX for AIX, the Assure UI server, and the Assure MIMIX for
AIX portal application on the same node is a multi-step process. Assure MIMIX for
AIX must be installed before installing the Assure UI server and the Assure MIMIX
for AIX portal application.

Installing Assure MIMIX for AIX

Select the following filesets to install Assure MIMIX for AIX:

• Vision.Common

• Vision.EchoCluster

• Vision.EchoStream

80 Assure MIMIX for AIX User Guide v5.2.04.00

 • Vision.EchoStream.sztool

• Vision.MXWS

Installing Assure Unified Interface

Select the following fileset to install Vision.VSP <version> VSP:

• Vision.VSP <version> VSP

NOTE
Vision.VSP <version> VSP must be installed before installing
Vision.VSP <version> Link to IBM JDK.

Select the following fileset to install Vision.VSP <version> Link to IBM JDK:

• Vision.VSP <version> Link to IBM JDK

Installing the Assure MIMIX for AIX portal application

Select the following fileset to install the Assure MIMIX for AIX portal application:

• Vision.VSP.MIMIX.pa

NOTE
Vision.VSP <version> VSP and Vision.VSP <version> Link to IBM
JDK must be installed before installing the Assure MIMIX for AIX portal
application.

Installing the Assure UI server and the portal application on a

separate node
Installing the Assure UI server and the Assure MIMIX for AIX Portal application on
a separate node is a multi-step process. The Vision.Common fileset must be
installed on the node before installing the Assure UI server and the Assure MIMIX
for AIX Portal application.

Installing Vision Common

Select the following fileset to install Vision.Common:

• Vision.Common

Installing Assure Unified Interface

Select the following fileset to install Vision.VSP <version> VSP:

• Vision.VSP <version> VSP

Assure MIMIX for AIX User Guide v5.2.04.00 81

 NOTE
Vision.VSP <version> VSP must be installed before installing
Vision.VSP <version> Link to IBM JDK.

Select the following fileset to install Vision.VSP <version> Link to IBM JDK:

• Vision.VSP <version> Link to IBM JDK

Installing the Assure MIMIX for AIX portal application

Select the following fileset to install the Assure MIMIX for AIX portal application:

• Vision.VSP.MIMIX.pa

NOTE
Vision Common, Vision.VSP <version> VSP and Vision.VSP
<version> Link to IBM JDK must be installed before installing the
Assure MIMIX for AIX portal application.

Define user groups

The installation process creates the ECadm and ECops groups in /etc/group. If you
are working with Assure MIMIX HA for AIX you must be a member of one of these
groups. Once the installation has added the groups, a system administrator must add
individual system users to those groups.

User roles
The installation process creates the scrt group in /etc/group, identifying the
category of users allowed to access the portal application.

IMPORTANT
The root user is always allowed access to the portal application.

Log files
There are two types of log files:

• install.log—Stores all user inputs in the directory from which the installer is run
if you have copied your inputs to an AIX machine. This log file also stores
details of the installation process.

• verifier.log—Stores the details of verification information on the remote or local

machine in the directory from which the installer is run.

82 Assure MIMIX for AIX User Guide v5.2.04.00

 Run the validate_license command
After you apply the license, run the validate license command:
/usr/scrt/bin/validate_license

A license validation message appears:

License validated or License validation failed

If you receive the License validation failed message ensure that the
information specified in license.inf is correct and that the output of the hostname
command matches the hostname in license.inf. If the problem persists, email or
contact Customer Support. Refer to the readme.txt file for contact information.

License expiration
When the license expires for Assure MIMIX for AIX, the application on the
production server is not affected. However, data replication to the recovery server
will be stopped, and you will no longer be able to use the Continuous Data
Protection functionality. You can check the license file for the data replication
component for information about the expiration of the license. The file is named:
/usr/scrt/run/node_license.properties.

NOTE
Assure MIMIX for AIX verifies the contents of the license file. Do not
alter this file.

Assure MIMIX for AIX User Guide v5.2.04.00 83

Uninstall Assure MIMIX for AIX
Before you uninstall Assure MIMIX for AIX:

• Shutdown Assure MIMIX for AIX and unload the drivers using the following
command:
rtstop -FC <Context ID>

• Use the gc_shutdown.sh script to gracefully shutdown all the managed

applications and the cluster services. This script is installed in the directory
/usr/EchoCluster/bin/AIX

To uninstall Assure MIMIX for AIX:

1. Download the Assure MIMIX for AIX installation program. Choose from one
of the following methods:

• Precisely Support web page at https://support.precisely.com/.

• Assure MIMIX for AIX installation CD.

2. Do one of the following:

• Click Uninstall Assure MIMIX for AIX on the Assure MIMIX for AIX
Installation splash screen or click uninstall.exe.
• Run uninstall.bin.

3. Run the Uninstall wizard to remove Assure MIMIX for AIX from your nodes.

The Assure MIMIX for AIX Uninstall Wizard runs and displays the Assure
MIMIX for AIX Welcome screen. Click Next.

4. The Node Login screen displays.

a. Enter the node name—Points the installer to the target node where you want
to uninstall Assure MIMIX for AIX.
b. Click Next.
5. The Specify Nodes screen displays. Click Next.

6. The Node Login screen re-displays. Log in to the node and press Next.

7. The Retrieving Installation Information screen briefly displays. Then the

Uninstall Options screen displays.

Select the components you want to uninstall from each node and click Next.

8. The Product Shutdown Required screen displays.

You must manually ensure that Assure MIMIX for AIX is shutdown, the wizard
does not perform this task. Click Next.

9. Once the uninstall wizard has verified that Assure MIMIX for AIX has been
shutdown the Shutdown Verification Complete screen displays. Click Next.

84 Assure MIMIX for AIX User Guide v5.2.04.00

 10. If you have efixes, the Efix Removal Required screen displays. You must
manually remove the efixes, the wizard does not perform this task. After you
remove the efixes, click Next.

11. The Verify Efix Removal screen displays. When the fix verification successfully
completes, the Efix Removal Verification Complete screen displays.

Click Next to uninstall Assure MIMIX for AIX and Assure Unified Interface.

12. The Uninstall Assure MIMIX for AIX screen displays.

When the uninstall process completes, the Uninstall Complete screen displays.

Assure MIMIX for AIX User Guide v5.2.04.00 85

Using smit to uninstall Assure MIMIX for AIX
To uninstall Assure MIMIX for AIX:

IMPORTANT
You must shutdown Assure MIMIX for AIX and unload the drivers before
you run the uninstall program. Use the following command:
rtstop -FC <Context ID>

1. Enter smit

The System Management screen displays.

2. Select Software Installation and Maintenance.

3. Select Software Maintenance and Utilities.

4. Select Remove Installed Software.

5. Select List to the right of SOFTWARE name.

6. Select the software you wish to remove, and press OK.

Installing the Assure UI server and the portal application on

Windows
The Assure UI Portal and Assure MIMIX for AIX portal application Installation
Wizard for Windows provides a way to install, upgrade, or reinstall the Assure UI
server and the Assure MIMIX for AIX portal application on your local Windows
machine.

NOTE
The Assure MIMIX for AIX software can only be installed on an AIX
machine. Only the Assure UI server and the portal application can be
installed on a Windows machine.

Download the Assure MIMIX for AIX installation program from:

• Precisely Support at https://support.precisely.com/.

• Assure MIMIX for AIX installation CD.

1. Run 5.2.02.00.MIMIXAIX.WINDOWS.EXE to install the portal application

and the Assure UI server to your local Windows machine.

The Installation Wizard runs and displays the Assure UI Portal Welcome screen.
Click Next.

86 Assure MIMIX for AIX User Guide v5.2.04.00

 2. The Terms And Conditions screen displays. Read and accept the terms of the
License Agreement. Click Next.

3. The Installation Options screen displays.

You can decide to start the portal server automatically after the installation
completes. Click Next.

NOTE
If the portal application is currently active, the Shut Down Assure Unified
Interface screen displays. The installation wizard will enable you to shut
down Assure Unified Interface.

4. The Installing screen displays, showing the status of the installation. Click Next.

5. When the installation completes, the Summary screen displays.

NOTE
To enable HTTPS (SSL) refer to the Assure Unified Interface User’s
Guide.

6. After you have installed the Assure MIMIX for AIX portal application, you can
log into the Assure UI portal. Select the highlighted machine-name address to
launch the Assure UI portal and log in. See “Logging in to the Assure UI portal”
on page 88.

7. Click Done to exit the installation wizard.

Uninstalling the Assure UI server and the portal application from

Windows
Use this wizard to uninstall product portal applications or the Assure UI server and
all product portal applications from your local Windows machine. The Assure UI
portal will be shut down and portal users will be automatically logged out during the
uninstall.

1. Navigate to Start>Assure Unified Interface>Uninstall

2. The Assure Unified Interface Welcome screen displays. Click Next.

3. The Assure Unified Interface Options screen displays.

Decide which components you wish to uninstall and click Next.

4. The Shut Down Assure Unified Interface screen displays.

When the shut down of Assure Unified Interface completes, the Ready to
Uninstall screen displays. Click Next.

Assure MIMIX for AIX User Guide v5.2.04.00 87

 5. The Preparing to Uninstall screen displays.

6. When the uninstall processing completes, the Summary screen displays.

Click Done, to complete the Assure Unified Interface uninstallation.

Post-installation tasks
These sections contain the post-installation tasks:

• “Logging in to the Assure UI portal” on page 88

• “Maintaining the node_config.properties file” on page 90

• “Using the Assure UI portal to configure replication groups” on page 108

• “Using the Assure UI portal to configure clusters” on page 162

Logging in to the Assure UI portal

You must have a valid user ID and password for the node on which the Assure UI
server is installed. Do the following:

1. Enter the following URL in your web browser:

http://server:port
The server is the IP address or host name for the node on which the Assure UI
server is installed and active. The default port number is 8410. For example, if
the Assure Unified Interface server was installed on node vsp-53, you would
copy the following url into the address field in your browser window:

http://vsp-53:8410

2. The portal appears showing the Log In page. Log in using your user ID and
password. Depending on the platform, the user ID and password may be
case-sensitive.

NOTE
If you have a problem logging into the Assure UI portal, refer to the Assure
Unified Interface User’s Guide packaged with Assure MIMIX for AIX.

After you have logged in, the portal opens to the Home page. A default portal
connection exists for the node on which you logged in.

NOTE
Refer to the Assure Unified Interface User’s Guide packaged with Assure
MIMIX for AIX.

88 Assure MIMIX for AIX User Guide v5.2.04.00

 Enable automatic startup
IMPORTANT
If Automatic Startup was enabled in versions prior to 5.2.02.00, the entry
“scrt:2:wait:"/usr/scrt/bin/sccfgd_boot >>
/var/log/EchoStream/sccfgd_boot.log 2>&1" in the /etc/inittab
file must be placed after the entry
“mxws:2:once:/opt/visionsolutions/mxws/service/bin/sta
rt_mxws.sh >>/var/log/EchoStream/mxws_start_stop.log
2>&1”.

IMPORTANT
Do not enable automatic startup of Assure MIMIX HA for AIX if your
nodes are in a clustered environment protected by Assure MIMIX HA for
AIX.

After you install Assure MIMIX DR for AIX on your production and recovery
servers, you can enable automatic startup of Assure MIMIX DR for AIX, only if
your nodes are not in a clustered environment protected by Assure MIMIX DR for
AIX, so that it is started as part of the boot process. Assure MIMIX DR for AIX
needs to be started before the application starts so that it can protect the application
data.

1. Using the cat command, determine the entry for the protected application in the
/etc/inittab file.

2. Note the entry that precedes it. The identifier for this entry is an argument in the
mkitab command. The mkitab command inserts the Assure MIMIX DR for AIX
boot command after the identifier into the /etc/inittab file. This causes Assure
MIMIX DR for AIX to start automatically before the protected application
during a reboot.

3. Execute the following command from a shell as root:

mkitab -i mxws scrt:2:wait:"/usr/scrt/bin/sccfgd_boot >>
/var/log/EchoStream/sccfgd_boot.log 2>&1"

This command inserts the sccfgd_boot command after the identifier mxws in
the /etc/inittab file. It is recommended to use mxws as the identifier so that
/usr/scrt/bin/sccfgd_boot is executed after
/opt/visionsolutions/mxws/service/bin/start_mxws.sh is started.

Assure MIMIX for AIX User Guide v5.2.04.00 89

 IMPORTANT
After a system reboot the output log file
/var/log/EchoStream/sccfgd_boot.log should be examined. It provides
detailed information about the automatic startup of Assure MIMIX DR for
AIX.

Example:
Jan 03 11:18:06 sccfgd_boot
Loading MIMIX DR for AIX context 1
Mounting MIMIX DR for AIX file system /xyz1
The current volume is: /dev/lvxyz1
Primary superblock is valid.
Mounting MIMIX DR for AIX file system /xyz2
The current volume is: /dev/lvxyz2
Primary superblock is valid.
0513-059 The scrt_lca-1 Subsystem has been started. Subsystem
PID is 5243042.

Loading MIMIX DR for AIX context 4

ERROR: Filesystem /xyz3 is mounted, cannot start
!!! Context 4 initialization failure !!!

Maintaining the node_config.properties file

The node_config.properties file is the configuration file that controls many aspects
of the local node operation. If it does not already exist, the cluster creates it with
defaults upon the first startup. This file is located in /usr/EchoCluster/etc/. Keep in
mind the following considerations when working with the node_config.properties
file.

When you start the listener, a new node_config.properties file is created only if the
file does not already exist. To maintain the integrity of an upgraded
node_config.properties file, in which any of the default configuration parameters
have been modified:
• Rename the current node_config.properties file.

• When you start the listener, ensure that you move any modifications made to the
original/renamed node_config.properties file to the new node_config.properties
file.

If any static parameter is modified in the node_config.properties file, run the

following listener commands from the /usr/EchoCluster/ directory to make the static
parameter changes effective for the new node_config.properties file:

• stop_listener.sh

• start_listener.sh

90 Assure MIMIX for AIX User Guide v5.2.04.00

 Additional options for the node_config.properties file
The following options have been added to the node_config.properties file. You can
use these parameters to resolve the issues described in this section.

• ICMP_TYPE=0 # ICMP type.

Problem
A router blocks ICMP type 0.

Solution
Use the ICMP_TYPE parameter to specify a different ICMP type that will not
be blocked. You must use the same value on both nodes.

Related topics

• Refer to “Configuring Replication Groups” on page 107.

• Refer to “Configuring Clusters” on page 161.

• Refer to “Starting and Stopping” on page 187.

Assure MIMIX for AIX User Guide v5.2.04.00 91

92 Assure MIMIX for AIX User Guide v5.2.04.00
Using the SMIT Interface
6

In service pack 5.2.4 and above the Assure MIMIX for AIX product includes an
interface that uses the AIX System Management Interface Tool (SMIT) to manage
the Assure MIMIX for AIX product. This chapter describes using this SMIT
interface

This chapter contains:

• “Getting started” on page 94

• “Nodes” on page 95

• “Replication Groups” on page 96

• “Operations” on page 98

• “Advanced Configurations” on page 101

• “Snapshots/Rollbacks” on page 103

• “Rollback by LFC number” on page 105

• “Monitoring” on page 106

Assure MIMIX for AIX User Guide v5.2.04.00 93

Getting started
The MIMIX for AIX SMIT interface can be started by typing the following on a
command line:

smit mimix

A MIMIX for AIX Main Menu will be shown:

The main menu provides options to:

• Configure Nodes, and Replication groups

• Do operations such as Start, Stop, Failover and Failback, Resync
• Configure advanced options
• Process snapshots
• Monitor of one or more instances

From this menu, you can select the relevant option and explore further to
accomplish the task.

General Navigation Tips and Techniques

The section contains general navigation tips and techniques. The following is an
example of a menu that is referenced in the descriptions of some of the actions.

94 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Scrolling Use the up and down arrows to scroll from line to line.
Cancel/Return PF3 or ESC+3
List PF4 or ESC+4
Entry Fields • ‘*’ in left hand column is a required field.
• ‘#’ in right hand column signifies numeric value
only.
• ‘+’ in right hand column signifies only specified
values allowed.
• ‘[ ]’ entry is changeable – no list
• No ‘[ ]’. Entry is changeable via list (PF4)
More…n More pages/options exist. Use the page up/page down
to navigate.
Red text The requested operation failed.
Green text The requested operation was successful.

All the options can also be accessed using the smit command line.

Nodes
To work with nodes, move the cursor to highlight Nodes of the MIMIX Main
Menu and press enter. The Nodes configuration menu will appear. From here nodes
can be added, changed, shown, or removed.

Add a node
To add a node,

1. Move the cursor to Add a Node and press enter.

Assure MIMIX for AIX User Guide v5.2.04.00 95

 2. Add the Node name and IP address on the resulting Add a Node panel, a and
press enter. The request to add a node is submitted.

Change a node
To change a node,

1. Move the cursor to Change a Node and press enter.

2. Select the node to be changed, and press enter.
3. Update the IP address accordingly on the resulting Change a Node panel,
and press enter. The request to update the IP address is submitted.

Show nodes
To show nodes, move the cursor to Show Nodes and press enter. All currently
defined nodes and IP addresses are shown.

Remove a node
To remove a node,

1. Move the cursor to Remove a Node and press enter.

2. Select the node to be removed and press enter. The request to remove the
selected nodes is submitted.

Replication Groups
To work with replication groups, on the MIMIX Main Menu move the cursor to
Replication Groups and press enter. The Replication Groups configuration menu
will appear. From here replication groups can be added/configured, removed, or
shown.

Add/Configure a Replication Group

To add a replication group,

1. Move the cursor to Add/configure a Replication Group and press enter.

2. The Add/Configure a Replication Group menu that appears provides
choices for defining a replication group, running a volume discovery, adding
or removing volumes from replication groups, and
configuring/synchronizing a replication group.

Define a Replication Group

To define a replication group,

96 Assure MIMIX for AIX User Guide v5.2.04.00

 1. Move the cursor to Define a Replication Group’and press enter.
The Define a Replication Group appears.
2. Enter the primary and failover context numbers, the replication group name,
the production node, and the recovery node in Define a Replication Group
panel. The request to define the replication group is submitted.

Run a Volume Discovery

To run a volume discovery,

1. Move the cursor to Run a Volume Discovery and press enter.

2. Select a replication group to run the volume discovery from the resulting
Select Replication Group panel and press enter.

NOTE
This action may take several minutes to complete. Return to the previous
menu once the command status is OK.

Add Volumes to a Replication Group

To add volumes to a replication group,

1. Move the cursor to Add Volumes to a Replication Group and press enter.
2. Select a replication group to add discovered volumes on the resulting Select
Replication Group panel and click enter.
Discovered volumes will appear on the resulting “Select Logical Volumes”
panel.
3. Select one or more volumes by moving the cursor to them and pressing F7.
The Select a Target Volume Group panel appears.

NOTE
A preceding ‘@’ indicates the volume was already added. After all
desired volumes are selected, press enter.

4. Select one or more recovery volume groups by moving the cursor to them
and pressing F7. Once all desired volume groups have been selected, press
enter. The request to add the volumes to the replication group is submitted.

Remove Volumes from a Replication Group

To remove volumes from a replication group,

1. Move the cursor Remove Volumes from a Replication Group and press
enter.

Assure MIMIX for AIX User Guide v5.2.04.00 97

 2. On the resulting “Select Replication Group” panel, select a replication group
to remove volumes from and press enter.
The Select Logical Volumes panel appears.

Select one or more volumes by moving the cursor to them and pressing F7. Once all
desired volumes are selected, press enter. The request to remove volumes from the
replication group is submitted.

Configure/Sync a replication group

To configure a replication group and upload to the nodes,

1. Move the cursor ‘Configure/Sync a Replication Group’ and press enter.

2. Select a replication group to configure/upload on the resulting Select
Replication Group panel, and press enter. The Configure/Sync a
Replication Group panel appears.
3. Fill in all required entry fields and press enter. The request to
configure/synchronize the replication group is submitted.

Remove a Replication Group

To remove a replication group,

1. Move the cursor to highlight Remove a Replication Group and press enter.
2. Select a replication group to remove from the resulting Select Replication
Group panel, and press enter. The request to remove the replication group is
submitted.

Show a Replication Group

To show a configured replication group,

1. Move the cursor to Show a Replication Group and press enter.

2. Select a replication group to be shown on the resulting Select Replication
Group panel and press enter. he selected replication group will be displayed.
To navigate across the various panels, use page up and page down.

Operations
To do replication group operations such as start, stop, failover or failback, on the
Main Menu move the cursor to Operations and press enter. The Operations menu
will appear.

Start a Replication Group

To start a replication group,

98 Assure MIMIX for AIX User Guide v5.2.04.00

 1. Move the cursor to Start a Replication Group and press enter.
2. Select a replication group to start from the resulting Select Replication
Group panel, and press enter.
3. Replication groups can be started either Normal (default) or non-Disruptive
modes.
• Normal - Is intended to start a Replication Group if file systems are not
mounted
• Non-Disruptive - Is intended to start a Replication Group if file systems
are mounted.
4. Select the pertinent mode and press enter. The request to start the replication
group is submitted.

Stop a Replication Group

To stop a replication group,

1. Move the cursor to Stop a Replication Group and press enter.

2. Select a replication group to stop on the resulting Select Replication Group
panel, and press enter.

NOTE
Stopping a replication group will attempt to unmount protected
filesystems, potentially resulting in an application/database outage.

Replication groups can be stopped via modes Sync (default), No-Sync or

Agent-Only.

• Sync - Stop processes will synchronize all dirty regions and then stop a
Replication Group. This means that agents will be stopped and drivers
unloaded.
• No-Sync - Stop processes stop the replication group. This means that
agents will be stopped and drivers unloaded. Processing will not
synchronize dirty regions prior to stopping.
• Agent-Only - Stop processes will stop the agents and keep drivers
loaded.
3. Select the pertinent mode and press enter. The request to stop the replication
group is submitted.

Failover a Replication Group

To failover a replication group,

1. Move the cursor to Failover a Replication Group and press enter.

Assure MIMIX for AIX User Guide v5.2.04.00 99

 2. Select a replication group to failover from the resulting Select Replication
Group panel, and press enter.

Replication groups can failover through modes Planned (default),

Unplanned, Migration or One-Sided.

• Planned - Failover processes will synchronize all dirty regions from

production node to recovery and complete the failover.
Replication will flow in the opposite direction after the operation is
completed.
• Unplanned - Failover processes will failover a recovery node only since
it is assumed that production node is down.
After a production node is back up “Resync after Unplanned Failover”
should be performed to start replication in the opposite direction.
• Migration - Failover processes will stop a Replication Group on the
production node with Sync-option and failover the recovery node. No
sync in the opposite direction is done.
• One-Sided - Is intended to failover the recovery node while the
production still has primary context active. The replication is not running
after the operation is completed. It can be used for testing purposes on the
recovery node. After testing is completed Failback with “After One Sided
Failover” should be performed.
3. Select the pertinent mode and press enter. The request to failover the
replication group is submitted.

Failback a Replication Group

To failback a replication group,

1. Move the cursor to Failback a Replication Group and press enter.

2. Select a replication group to failover from the resulting Select Replication
Group panel, and press enter.

Replication groups can failback through modes Normal (default) or After

One-Sided Failover.

• Normal - Failback processes will synchronize over all dirty regions from
the configured recovery, current production to the configured production,
current recovery and perform Failback so that replication will take place
from the configured production to the configured recovery.
• After One-Sided Failover - Failback processes will failback the
configured recovery node only. The configured production node still has
primary context active.
LCA/ABA Hard Reset and Synchronize Logical Volumes should be
performed after After One-Sided Failover Failback operation to resume
replication from the configured production to the configured recovery.

100 Assure MIMIX for AIX User Guide v5.2.04.00

 3. Select the pertinent mode and press enter. The request to failback the
replication group is submitted.

Advanced Configurations
The Advanced Configuration menu allows the user to do the following:

• Change the number of Replication Threads

• Change the network timeout
• LCA/ABA hard Reset
• Extend logical volumes (LV)
• Import LV Information from a Replication Group Node
• Synchronize Logical Volumes
• Remove replication groups from a local database
• Export Configuration to Another Node

To do any of these options, move the cursor to Advanced Configurations from the
MIMIX Main Menu and press enter. The Advanced Configurations menu
appears.

Change Number of Replication Threads

To change the number of replication threads,

1. Move the cursor to Change Number of Replication Threads, and press

enter.
2. Select a replication group to change the number of threads from the resulting
Select Replication Group panel, and press enter.
3. Specify the new number of threads from Change Number of Replication
Threads menu, and press enter. The request to change the number of
replication group threads is submitted.

Change Network Timeout

To change the network timeout,
1. Move the cursor to Change Network Timeout, and press enter.
2. Select a replication group to change the network timeout value in the
subsequent Select Replication Group panel, and press enter.
3. Specify the new timeout value in the Change Network Timeout menu that
appears, and press enter. The request to change the network timeout value for
the replication group is submitted.

Assure MIMIX for AIX User Guide v5.2.04.00 101

 LCA/ABA Hard Reset
To perform a hard reset of the LCA/ABA agents,
1. Move the cursor to LCA/ABA Hard Reset and press enter.
2. Select a replication group to reset from the resulting Select Replication
Group panel, and press enter.
3. On the resulting LCA/ABA Hard Reset menu, press enter. The request for
an LCA/ABA hard reset is submitted.

Extend Logical Volumes

To extend a logical volume,
1. Move the cursor to Extend Logical Volume, and press enter.
2. Select a replication group to extend from the resulting Select Replication
Group panel and press enter. Then, select the logical volume to extend from
the Select Logical Volume menu.
3. Enter the new volume size in the resulting Extend Logical Volume menu,
and press enter. The request to extend the logical volume is submitted.

Synchronize Logical Volumes

To synchronize logical volumes,
1. Move the cursor to Synchronize Logical Volumes, and press enter.
2. Select a replication group to synchronize the volumes on the resulting Select
Replication Group panel and press enter.
3. Select the Logical Volume and Sync Type option of either Full or
Checksum on the resulting Synchronize Logical Volumes panel.
• Full - Synchronize all regions.
• Checksum - Synchronize only the regions that have different checksums.
4. Press enter and the request to synchronize the volume is submitted.

Import LV Information from a Replication group Node

To import logical volume information from a replication group node,

1. Move the cursor to Import LV Information from a Replication Group

Node and press enter.
2. Select a replication group from the location to import the logical volume
information on the resulting Select Replication Group, and press enter. The
request to import the logical volume information is submitted.

102 Assure MIMIX for AIX User Guide v5.2.04.00

 Remove Replication Group From a Local Database
To remove a replication group from a local database,

1. Move the cursor to Remove RG From a Local Database and press enter.
2. Select a replication group from the resulting Select Replication Group
panel, and press enter. The request to remove the selected replication group
is submitted.

Export Configuration to Another Node

To export the configuration to another node,
1. Move the cursor to Export Configuration To Another Node and press
enter.
2. Select a node to export the configuration to from the resulting Select a Node
panel, and press enter. The request to export the configuration to the node is
submitted.

When a configuration is created, it is only stored on the node where it was created.
As a result, all operations are only available on that node. Additionally, it is useful
to have the configuration on more than one node for the operations to run from other
nodes as well.
For example, there are 2 nodes aix-01 and aix-02. Replication groups were created
on aix-02. All smit operations (start, stop, failover etc.) can only be performed from
aix-02. If a user wants to run “smit mimix” commands on another node (aix-01),
use this command to export it from aix-02 to aix-01. After the configuration is
exported all smit operations are available on the node where it was exported to.

Snapshots/Rollbacks
To work with snapshots and rollbacks, on the MIMIX Main Menu move the cursor
to Snapshots/Rollbacks and press enter. The Snapshots/Rollbacks menu appears.

Create a Snapshot by Time

To create a snapshot by time,
1. Move the cursor to Create a Snapshot by Time, and press enter.
2. Select a replication group to create the snapshot from the resulting Select
Replication Group panel, and press enter.
3. On the resulting Create a Snapshot by Time menu, select the Date, Time,
and Available Rollback Windows.

Assure MIMIX for AIX User Guide v5.2.04.00 103

 NOTE
The Available Rollback Windows exists just to display the time at which
the replica can be rolled back.

Also, select a mode of either Normal or Failover.

• Normal - Snapshot processes create a regular snapshot.

• Failover - Snapshot processes rollback a replica in time and prepare the
replica for future Failover operation. It should be followed by Failover
operation.

After selecting the mode, press enter. The request to create the snapshot by time is
submitted.

Create a Snapshot by LFC number

To create a snapshot by LFC number,
1. Move the cursor to Create a Snapshot by LFC Number and press enter.
2. Select a replication group to create the snapshot from the resulting Select
Replication Group panel, and press enter.
3. Select the LFC number, and Available Rollback Windows from the resulting
Create a Snapshot by LFC Number menu.

NOTE
The Available Rollback Windows exists just to display the time at which
the replica can be rolled back.

Also, select a mode of either Normal or Failover.

• Normal - Snapshot processes create a regular snapshot.

• Failover - Snapshot processes rollback a replica in time and prepare the
replica for future Failover operation. It should be followed by Failover
operation.

After selecting the mode, press enter. The request to create the snapshot by time is
submitted.

Remove a Snapshot
To remove a snapshot,
1. Move the cursor to Remove a Snapshot and press enter.
2. On the resulting “Select Replication Group” panel, select a replication group
to remove the snapshot for and press enter.

104 Assure MIMIX for AIX User Guide v5.2.04.00

 3. Select a replication group to remove the snapshot from the resulting Select
Replication Group panel and press enter.
4. On the resulting Remove a Snapshot menu, press enter to submit the
request. The request to remove the snapshot is submitted.

Rollback by Time
To rollback by time,
1. Move the cursor to Rollback by Time and press enter.
2. Select a replication group to rollback from the resulting Select Replication
Group panel, and press enter.
3. Select the Available Rollback Windows, Date and Time from the resulting
Rollback by Time menu, and press enter. The request to create the rollback
is submitted.

NOTE
The Available Rollback Windows exists just to display the time at which
the replica can be rolled back.

Rollback by LFC number

To rollback by LFC number,
1. Move the cursor to Rollback by LFC Number and press enter.
2. Select a replication group to rollback from the resulting Select Replication
Group panel, and press enter.
3. Select the Available Rollback Windows and LFC number from the
resulting Rollback by LFC Number menu, and press enter. The request to
rollback is submitted.

NOTE
The Available Rollback Windows exists just to display the time at which
the replica can be rolled back.

Extend Snapshot Journal

To extend a journal snapshot,
1. Move the cursor to Extend Snapshot Journal and press enter.
2. Select a replication group to extend from the resulting Select Replication
Group panel and press enter.

Assure MIMIX for AIX User Guide v5.2.04.00 105

 3. Select the Additional temporary space from the resulting Extend Snapshot
Journal menu and press enter.
The request to extend the snapshot journal is submitted.

Monitoring
To monitor one or more replications groups or change the monitoring refresh rate,
move the cursor to Monitoring and press enter on the MIMIX Main Menu. The
Monitoring menu is displayed.

Monitor all Replication Groups

To monitor the status of all replication groups, move the cursor to Monitor all
Replication Groups and press enter.

The status of the replication groups will be shown. The status will update at the
refresh rate specified.

Monitor Specific Replication Group

To monitor the status of a specific replication group,
1. Move the cursor to Monitor Specific Replication Group and press enter.
2. On the resulting Select Replication Group panel, select a replication group
to monitor and press enter.

The status of the replication group will be shown. The status will update at the
refresh rate specified.

Set Monitor Refresh Rate

To set the monitor refresh rate,
1. Move the cursor to Monitor Refresh Rate and press enter.
2. On the resulting Set Monitor Refresh Rate menu, select the new refresh
rate and press enter.
The request to change the refresh rate is submitted.

106 Assure MIMIX for AIX User Guide v5.2.04.00

Configuring Replication Groups
7

After you install Assure MIMIX for AIX, the Assure UI server, and the portal
application, you can use the Replication Group wizard to configure new
replication groups and change, rename, and delete existing ones and the Cluster
Configuration wizard to create and configure clusters. See “Create and configure
a cluster” on page 162.

This chapter contains:

• “Using the Assure UI portal to configure replication groups” on page 108

• “Create and configure a new replication group” on page 108

• “Configuration initialization progress (new configuration)” on page 128

• “Change a replication group’s configuration” on page 130

• “Configuration initialization progress (Change Configuration)” on page 146

• “Rename a replication group” on page 7-149

• “Delete a replication group” on page 7-151

• “Configuration window for Replication Groups” on page 152

• “Using the command line to perform configuration tasks” on page 152

Assure MIMIX for AIX User Guide v5.2.04.00 107

Using the Assure UI portal to configure replication groups
You can use the Replication Group Configuration Wizard to:

• “Create and configure a new replication group” on page 108

• “Change a replication group’s configuration” on page 130

• “Rename a replication group” on page 149

• “Delete a replication group” on page 151

The volume group types of the production and recovery servers must be compatible.
Servers with big or scalable volume group types may be combined, but a production
server with a small volume group may only be combined with a recovery server
with a small volume group.

The following table summarizes the supported combinations of production and

recovery volume group types:

Production

Small Big Scalable

Small OK No No
Recovery
Big No OK OK

Scalable No OK OK

NOTE
AIX may refer to the Small volume group type as Normal or Original
volume group type.

Create and configure a new replication group

To create and configure a new replication group, do the following:

1. Navigate to the Replication Group or Clusters portlet.

2. Click Configuration

108 Assure MIMIX for AIX User Guide v5.2.04.00

 The Configuration window displays.

For detailed information refer to the Assure MIMIX for AIX online help.

3. Click New Replication Group to start the Replication Group Configuration

wizard.

This starts the Replication Group Configuration wizard and the New
Replication Group Servers panel displays.

The New Replication Group Servers panel contains the following fields:

Field Description

Servers—Section for specifying the host name or IP address for the servers in
this replication group.

Production Select from the list of portal connections that are associated
with the instance.
Recovery 1 Select the portal connection, host name, or IP address for
the server in the first recovery server role. Possible values
are any portal connection that is in the instance domain and
has not been selected for the production server.

Assure MIMIX for AIX User Guide v5.2.04.00 109

 Field Description

Recovery 2 Select the portal connection, host name, or IP address, for

(optional) the second recovery server. Possible values are any portal
connection that is in the instance domain and has not been
selected for the production or recovery server.

Failover Options are:

• Yes
• Do not failover
If you need to move production due to an unplanned outage
or for maintenance, select Yes, otherwise select, Do not
failover.

4. Click Next.

The New Replication Group Names panel displays.

The New Replication Group Names panel contains the following fields:

110 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Replication Specify the name of the replication group. Replication

group name group names:
• Can be 256 characters in length and can contain any
alphanumeric character.
• Must be unique across the servers specified for the
replication group. This is the same as for context IDs.
• Must start with an alphanumeric character. Hyphens ( - )
and underscores ( _ ) are allowed. Spaces or other special
characters are not allowed.

Primary context Defaults to the next available context ID on the specified

ID servers. Context IDs must be unique across the servers
specified for the replication group.Valid values are 1 to 999.

Failover context Defaults to the primary context ID number plus 16. If a

ID value greater than 983 is specified for the Primary context
ID, no default is provided. Valid values are 1 to 999.

NOTE
Only displays when the Failover server field on
the Servers panel has a value other than Do Not
Failover.

5. Click Next.

The New Replication Group Default Volume Groups panel displays.

The New Replication Group Default Volume Groups panel contains the following
fields:

Assure MIMIX for AIX User Guide v5.2.04.00 111

 Field Description

Default volume Select the default volume group for each server from the
group list.

Volume group Displays the volume group type of the volume group
type selected for Default volume group. If no volume group
is selected, this value is a dash.

6. Click Next.

The New Replication Group Logical Volumes panel displays.

Initially, a message indicating that Assure MIMIX for AIX is retrieving logical
volume information from the production server is displayed.
• The Add Logical Volumes dialog will not contain any logical volumes that
are in use by other replication groups on the node.
• AIX standard logical volume types (such as, raw, jfs, jfs2, jfslog, and
jfs21og) are allowed.
• AIX system internal logical volume types (such as, aio_cache, boot, copy,
paging, sysdump) are not allowed. Any other non-standard logical volume
types are allowed as “raw” logical volumes. If a logical volume is presented
without an associated filesystem path it will be treated as a raw logical
volume.

The New Replication Group Logical Volumes panel after Assure MIMIX for
AIX retrieved the logical volume information from the production server.

112 Assure MIMIX for AIX User Guide v5.2.04.00

 7. Click Add.

The Add Logical Volumes dialog displays.

a. Select one or more logical volumes to protect on the production server.

Assure MIMIX for AIX User Guide v5.2.04.00 113

 b. Select the volume group on the recovery servers where the replicated data
will be located.
The Add Logical Volumes dialog contains the following columns:

Column Description

Server Displays the name of the server in the recovery role or the
servers in the recovery 1 and recovery 2 roles.

Default Volume The default volume group specified for each server.
Group

Volume group Specifies where the selected logical volumes will be located
for replicated on the recovery servers when they are replicated.
data

Volume group The type of the default volume group specified for each
type server.

Production Filters the list of logical volumes on the production server.

server volume
group

Logical Volume Displays the logical volumes on the production server.

Logical volumes used internally by the product or have
already been added to the list of protected logical volumes
do not appear in this list.

Volume Group Displays the name and type of the volume group on the
production server for the logical volume.

Size (GB) Displays the size in gigabytes (GB) of the logical volume.

Type Displays the type of logical volume. For example, raw, jfs,
jfs2, and jfs2log.

File System Displays the file system or mount point for the logical
volume. Typically, around 20 characters but can be as long
as 2048. If the length exceeds 76, the text is truncated with
an ellipsis in the middle. Flyover text shows the entire path
name.

FS Log Displays the FS log for the logical volume. If length

exceeds 76, the text is truncated with an ellipsis in the
middle.

Recovery 2 Displays the server information for a 3 node configuration.

Only displayed if more than one recovery server is
configured. The volume group for replicated data cannot be
changed in a three node configuration.

8. Click OK. The following checks occur to ensure there are no errors.

– Unprotected file systems do not use the same JFS or JFS2 outline logs
of protected file systems.

114 Assure MIMIX for AIX User Guide v5.2.04.00

 – Outline log logical volumes are not selected without the
corresponding file system logical volume.
– File system logical volumes with outline logs have the corresponding
outline log logical volume selected as well.

Refer to “Setting up JFS log isolation” on page 231 for detailed information.

The New Replication Group Logical Volumes panel displays with the
selected logical volumes you want protected.

9. Click Next.

The New Replication Group Replication IP Addresses panel displays. Use this
panel to specify IP labels or addresses that will be used specifically for
replication. By default, replication uses the IP addresses of the servers. There
are two options:

Assure MIMIX for AIX User Guide v5.2.04.00 115

 • If you select, Use server IP addresses for replication, the New Replication
Group Replication IP Addresses panel displays in the following format.

• If you select, Use specified IP addresses for replication, the Replication

Group Replication IP Addresses panel displays in the following format.

The Replication Group Replication IP Addresses panel contains the following

fields:

116 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Replication IP Indicates if the user wants to use the server IP address for
Addresses replication or specify alternates. Possible values:
• Use server IP addresses for replication
• Use specified IP addresses for replication

Production Server—Section heading for the production server.

Production Identifies the name of the server in the production role.

Server - Host
name

Production Identifies the resolved IP address from the host name.

Server - IP Possible values are any valid IPv4 and IPv6 addresses.
address

Recovery Server—Section heading for the recovery server.

Recovery Server Identifies the name of the server in the recovery role.
- Host name

Recovery Server Identifies the resolved IP address from the host name.
- IP address Possible values are any valid IPv4 and IPv6 addresses.

10. Click Next.

The New Replication Group Containers panel displays. Use this panel to
configure how data is moved between servers. Containers are used by internal
processes and replication to move the changed data between servers. A larger
total container size provides a larger rollback window. Smaller sized containers
may replicate more frequently. Specify the quantity and size of the containers,
the default volume group where the containers are located, and the number of
logical volumes to use to balance IO and improve replication performance.

Assure MIMIX for AIX User Guide v5.2.04.00 117

 The Replication Group Containers panel contains the following fields:

Field Description

Server Identifies the name of the server in the production and

recovery roles.

Number of Specify the number of containers to use on each server.

containers Default values are 64 for the production server, and 128 for
the recovery servers.

Size of each Specify the size of each container in MB. Since the size
container must match on all configured servers, the recovery and
replicated values are display only. Possible values are 2, 4,
8, 16, 32, 64, 128, 256, and 512. Default is 16.

Total size Displays the total space required for the containers on each
server.

Default volume The default volume group specified for each server.
group

118 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Logical volumes Specify the number of logical volumes to create when

creating containers. By default, the logical volumes are
created on the default volume group. However if you
choose, Use alternate volume groups or physical volumes
for replication containers, then the logical volumes are
created on the alternate volume groups or physical volumes.
Default values are 2 for the production server and 3 for the
recovery servers.

Use alternate Indicates if the you want to specify volume groups and
volume groups physical volumes that will be used for the containers used
or physical for replication. If checked, the Replication Containers panel
volumes for is displayed. If not checked, the Replication Containers
replication panel is skipped. This box, is unchecked, by default.
containers

11. Click Next. There are two possible actions:

• If you leave the Use alternate volume groups or physical volumes for
replication containers checkbox unchecked on the Containers panel, the
New Replication Group Container Options panel displays. See page 120.
• If you check the Use alternate volume groups or physical volumes for
replication containers checkbox, the New Replication Group Replication
Containers panel displays. If the checkbox is not checked, this panel is
skipped.

Use the New Replication Group Replication Containers panel to select the volume
groups and physical volumes where you want to locate the containers used
specifically for replication.

Assure MIMIX for AIX User Guide v5.2.04.00 119

 The New Replication Group Replication Containers panel contains the following
fields:

Field Description

Production Server—Section heading for each server (production and recovery)

Server Displays the name of the server.

Total container Displays the total space (in MB) required for the containers
size on the server.

Volume Group Displays the list of volume groups on the specified server.

Add Use this button to adds the volume group to the list and
defaults the physical volume to Any.

Volume Group Displays the name of a selected volume group.

Physical Volume Displays a list of physical volumes (disks) on the specified

volume group.

Remove Removes the volume group from the list. This action is
available after you add a volume group.

12. Click Next.

The New Replication Group Container Options panel displays. Use this panel to
specify if you want to:

• Use compression during replication.

• Use encryption during replication.

120 Assure MIMIX for AIX User Guide v5.2.04.00

 • Send partially filled containers after a specified amount of time. Otherwise,
containers are sent when they become full.

The New Replication Group Container Options panel contains the following fields:

Field Description

Use compression By default, the “Use compression during replication”

during checkbox is checked. To disable this option, remove the
replication checkmark from the checkbox. In the Configuration
Summary window, possible values are “Yes” (enabled) or
“No” (disabled).
LFCs are compressed before being sent to the recovery
server, where they are then uncompressed. When you
compress LFCs a smaller amount of data is sent across the
network. This activity requires additional CPU bandwidth
to compress and uncompress the LFC on each server.

Use encryption By default, the “Use encryption during replication”

during checkbox is unchecked. To enable this option, add a
replication checkmark to the checkbox.
LFCs are encrypted before being sent to the recovery
servers, where they are then unencrypted. This activity
requires additional CPU bandwidth to encrypt and
unencrypt the LFC on each server. See “Support for data
encryption in Assure MIMIX DR for AIX” on page 19.

Assure MIMIX for AIX User Guide v5.2.04.00 121

 Field Description

Send partially By default, the “Send partially filled containers

filled containers automatically” checkbox is checked. To disable this option
automatically remove the checkmark from the checkbox. In the
Configuration Summary window, possible values are “Yes”
(enabled) or “No” (disabled).
The Send partially filled containers automatically option
enables you to control the frequency of shipping containers
(LFCs) to the recovery server during low I/O periods.
The container is examined when the frequency to check
value is reached. If at that time the minimum percent filled
value has not been reached, the container will not be sent.
When the container reaches the minimum percent filled
value, containers will not be immediately sent. There is a 5
second delay before the containers are sent. The 5 second
delay is provided to account for the possibility that the
container could become completely full. When the
container is sent, the frequency to check value is reset and
the entire process starts again.
Note you can also use the command line to Send partial
containers automatically. Refer to “Send partially filled
containers automatically” on page 153.

Frequency to Indicates how often to check for partially filled containers

check in seconds.
Keep in mind the following:
• Only enabled if the “Send partially filled containers
automatically” checkbox is checked.
• Default value is 300 seconds
• Valid range is 1 to 86,400, only numeric values are
accepted. You must specify a value.

Minimum Indicates how full the container must be before it can be

percent filled sent.
Keep in mind the following:
• Only enabled if the “Send partially filled containers
automatically” checkbox is checked.
• Default value is 50%.
• Valid range is 0 to 99, only numeric values are accepted.
You must specify a value.

Additional Options

122 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Mirrors—Section heading for mirror options.

• Replication containers—Specifies the number of copies to make of the
replication container logical volumes on the production server and the
recovery server.
• Replica—Specifies the number of copies to make of the replica logical
volumes on the recovery server.
• Snapshot—Specifies the number of copies to make of the snapshot container
logical volumes on the production server and recovery server.
• Internal—Specifies the number of copies to make of the internal container
logical volumes on the production server and recovery server.
Usage notes for mirroring
1. If the number of available physical volumes is less than the number of copies
requested, use the "-s n" (non-strict) flag to create the LV copies to avoid a
configuration failure.
2. If the number of available physical volumes is more than or equal to the
number of copies requested, use the "-s" flag to create the LV copies.
3. If you change a configuration and reduce the number of logical volume
copies, the Configuration wizard does not remove all of the logical volume
copies. You can use the "rmlvcopy" AIX command to manually remove the
logical volume copies.
4. When the configuration is deleted, Assure MIMIX DR for AIX deletes all
replication, snapshot, and internal logical volume copies (except the replica).

13. Click Next.

The New Replication Group Snapshot Buffer panel displays. When a snapshot is
created, the snapshot buffer is used to hold the changes between the location in the
rollback window where the snapshot was created and the current time. As changes
are replicated, the snapshot buffer fills up.

Assure MIMIX for AIX User Guide v5.2.04.00 123

 The New Replication Group Snapshot Buffer panel contains the following fields:

Field Description

Snapshot Indicates how much space to reserve for the snapshot buffer.
Buffers - Size The value is a percent of the size of the logical volumes that
have been selected to protect. Valid values are integers from
1 to 100. Default is 10.

Warning Indicates how full the snapshot buffer must be before you
threshold are warned that it is filling up.Valid values are integers from
1 to 100. Default is 75.

Location Indicates that the snapshot buffers are located on default

volume group of the production, on the production server
and recovery server.

Production Production server information. Only displayed if a failover

server is configured.

14. Click Next.

The New Replication Group Ports panel displays. Port numbers are used for
communication by the agents on each server. You must change the port number
if it is not unique or it is already assigned to a different service.

The Configuration Wizard reads the /etc/services file to find ports numbers that
are unassigned and populates the Port fields with the unassigned values. You
can use the values discovered by the Configuration Wizard or change them.
When the new replication group is deployed, the /etc/services file will be
updated to include the port numbers for the replication group.

Keep in mind the following when assigning port numbers:

• If you enter a port number value that is already in use, the service name that
is using the port will be displayed in an error message.
• When a replication group is deleted through the portal application, the
entries that were previously added to the /etc/services file will be changed by
inserting a " # " at the beginning of each entry associated with the replication
group.

124 Assure MIMIX for AIX User Guide v5.2.04.00

 NOTE
You can edit the /etc/services file and manually assign port assignments.
However, this is not recommended. Refer to “Assure MIMIX for AIX
default ports” on page 156.

The New Replication Group Ports panel contains the following fields:

Field Description

Control Port Agent control ports column.

Data Port Agent data ports column.

Archive (AA) Specify the control and data ports used by the Archive
Agent.
Possible values:
• 1024-65535
• The default control port is 5747, the default data port is
5752.

Apply (ABA) Specify the control and data ports used by the Apply Agent.
Possible values:
• 1024-65535
• The default control port is 5753, the default data port is
5750.

Assure MIMIX for AIX User Guide v5.2.04.00 125

 Field Description

Send (LCA) Specify the control and data ports used by the Send Agent.
Possible values:
• 1024-65535
• The default control port is 5754, the default data port is
5751.

Restore client Specify the control and data ports used by the Restore
(CA/RA) client/agent.
Possible values:
• 1024-65535
• The default control port is 5749, the default data port is
5748.

15. Click Next.

The New Replication Group Tivoli Storage Manager panel displays. The Tivoli
Storage Manager (TSM) can archive containers which allows you to rollback or take
snapshots farther back in time. Full backups of the server where the TSM client is
running can also be performed.

The New Replication Group Tivoli Storage Manager panel contains the following
fields:

126 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Enable Tivoli Indicates if Tivoli Storage Manager is enabled for this

Storage Manager replication group. Checkbox is unchecked by default.
(TSM)

TSM client - Displays the name of the server where the TSM client is
Server running. This is always the recovery server. Enabled only
when Enable Tivoli Storage Manager (TSM) is checked.

TSM client - Specify the user ID for TSM to use to log into the server
User ID where the TSM client is running. Enabled only when Enable
Tivoli Storage Manager (TSM) is checked.

TSM client - Specify the password for TSM to use to log into the server
Password where the TSM client is running. Enabled only when Enable
Tivoli Storage Manager (TSM) is checked.

TSM client - Specify the location of the TSM options file on the TSM
Options file client server. The default location is
/usr/tivoli/tsm/client/ba/bin/dsm.opt. You can
specify any valid path and file name. Enabled only when
Enable Tivoli Storage Manager (TSM) is checked.

TSM client - Specify the domain for TSM to use. Enabled only when
Domain Enable Tivoli Storage Manager (TSM) is checked.

TSM server Specify the host name or IP address of the server where the
TSM server software is running. Valid values are any valid
IPv4 and IPv6 addresses or host name. Enabled only when
Enable Tivoli Storage Manager (TSM) is checked.

16. Click Next.

Assure MIMIX for AIX User Guide v5.2.04.00 127

 The New Replication Group Summary panel is a summary of this replication
group's configuration. To save and initialize this configuration on the specified
servers, click Finish. To cancel, click Cancel.

The content of this panel is the same as the Configuration Summary section in the
Configuration window. Refer to the Assure MIMIX for AIX online help for
additional information for the Configuration Window for replication groups. Refer
to “Configuration window for Replication Groups” on page 152.

IMPORTANT
When you initially configure a replication group the Finish button will be
enabled, so that you can save the configuration to the servers and initialize
the configuration.

17. Click Finish to configure the replication group.

IMPORTANT
Assure MIMIX for AIX prevents configurations from being created or
changed if there is not enough space available. Once you have allocated
additional space, you can click “Check Required Space” to verify that you
have sufficient space.

Configuration initialization progress (new configuration)

When a configuration is created, the Configuration Summary area lists the steps
required to initialize the configuration and shows which steps have been completed

128 Assure MIMIX for AIX User Guide v5.2.04.00

 or are in progress. When the initialization is successfully completed, the summary
area displays the normal Configuration Summary content. Configuration
initialization cannot be stopped once it is started.

When the new configuration is saved and validated, you can view the progress of
the configuration initialization in the Configuration Initialization Progress section in
the Configuration Window. As each step is successfully completed, a checkmark
appears next to the step. When you create a new configuration, Assure MIMIX for
AIX runs commands for each step. The table below describes steps and commands
that are run when you create a new configuration.

Order Step Command

1. Save configuration. This was done when you clicked Finish in the
New Replication Group wizard on the
Summary panel.

2. Copy configuration to S (S is sccfgd_putcfg <Context ID>

production server, recovery
server, recovery server 1, or
recovery server 2). You will
see a row for each server in
the configuration.

3. Create containers and logical scsetup -C <Primary Context ID> -M

volumes on S (S is
production server, recovery
server, recovery server 1, or
recovery server 2). You will
see a row for each server in
the configuration.

4. Create failover context on S rtdr -C <Primary Context ID> -F

(S is production server, <Failover Context ID> setup
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

Assure MIMIX for AIX User Guide v5.2.04.00 129

 Order Step Command

5. Set agent port numbers. Shell script that adds the agent port numbers
to the /etc/services file.

6. Verify configuration on S. (S sccfgchk -C <Primary Context ID>

production server, recovery
server, recovery server 1, or
recovery server 2).

Notes:

• These steps may be run on one or more servers.

• step 4 only runs if a failover server was specified in the configuration.

Related topics
• “Configuration initialization progress (Change Configuration)” on page 146.

Change a replication group’s configuration

Before you change the configuration for a replication group, keep in mind the
following:

• Configuration changes cannot be saved until the replication group is stopped.

You will be allowed to continue through the Change Replication Group wizard
and make changes. However, when you click Finish on the Summary panel, a
message will appear that instructs to stop the replication group. To stop the
replication group navigate to the Replication Groups portlet in the Assure UI
portal window and stop the replication group.

• You cannot change the replication group name or context ID with the Change
Replication Group wizard.

• A replication group cannot be changed if the production and recovery servers

and are not at the same version.

• Certain types of configuration changes can be made dynamically while the

replication group is partially active. Changes that are not explicitly identified in
the table below must be made manually using the instructions in “Manually
changing configuration of a replication group” on page 134.

Replication Configuration Wizard Panels and Fields Field Support for Dynamic Update

Servers panel
Failover - change from Yes to Do not failover Dynamic change supported

Failover - change from Do not failover to Yes Dynamic change supported

Names panel
No changes can be made.

130 Assure MIMIX for AIX User Guide v5.2.04.00

Replication Configuration Wizard Panels and Fields Field Support for Dynamic Update

Default Volume Groups panel - 2 Node Configuration

Change Production Default volume group Manual change only

Change Recovery Default volume group Dynamic change supported

Default Volume Groups panel - 3 Node Configuration

Change Production Default volume group Manual change only

Change Recovery 1 Default volume group Manual change only

Change Recovery 2 Default volume group Manual change only

Logical Volumes panel - 2 Node Configuration

Add Manual change only

Change Dynamic change supported

Remove Manual change only

Logical Volumes panel - 3 Node Configuration

Add Manual change only

Change Manual change only

Remove Manual change only

Replication IP Addresses panel - 2 Node and 3 Node Configurations

Use server IP addresses for replication Dynamic change supported to value “Use
specified IP addresses for replication”

Use specified IP addresses for replication Dynamic change supported to value “Use
server IP addresses for replication”

Containers panel - 2 Node Configuration

Increase the number of Production containers Dynamic change supported
Decrease the number of Production containers Dynamic change supported

Increase the size of each Production container Dynamic change supported

Increase the number of Recovery containers Dynamic change supported

Decrease the number of Recovery containers Dynamic change supported

Increase the size of each Recovery container Dynamic change supported

Increase the number of Production Logical volumes Dynamic change supported

Decrease the number of Recovery Logical volumes Dynamic change supported

Use alternate volume groups or physical volumes for Dynamic change supported
replication containers

Assure MIMIX for AIX User Guide v5.2.04.00 131

 Replication Configuration Wizard Panels and Fields Field Support for Dynamic Update

Containers panel - 3 Node Configuration

Increase the number of Production containers Dynamic change supported
Decrease the number of Production containers Dynamic change supported

Increase the size of each Production container Dynamic change supported

Increase the number of Recovery containers Dynamic change supported

Decrease the number of Recovery containers Dynamic change supported

Increase the size of each Recovery container Dynamic change supported

Increase the number of Production Logical volumes Dynamic change supported

Decrease the number of Production Logical volumes Dynamic change supported

Increase the number of Recovery Logical volumes Dynamic change supported

Decrease the number of Recovery Logical volumes Dynamic change supported

Use alternate volume groups or physical volumes for Dynamic change supported
replication containers

Container Options panel - 2 Node and 3 Node Configurations

Use compression during replication. Enable/Disable Dynamic change supported

Use encryption during replication. Enable/Disable Dynamic change supported

Send partially filled containers automatically. Enable/Disable Dynamic change supported

Frequency to check. Increase/Decrease Dynamic change supported.

Minimum percent filled. Increase/Decrease Dynamic change supported.

Additional Options (Mirrors)

Replication containers: add mirrored copies Dynamic change supported

Replication containers: remove mirrored copies Dynamic change supported

Snapshot: add mirrored copies Dynamic change supported

Snapshot: remove mirrored copies Dynamic change supported

Replica: add mirrored copies Dynamic change supported

Replica: remove mirrored copies Dynamic change supported

Internal: add mirrored copies Dynamic change supported

Internal: remove mirrored copies Dynamic change supported

Snapshot Buffer panel - 2 Node and 3 Node Configurations

Snapshot buffer:
Size: Increase/Decrease Dynamic change supported
Warning threshold: Increase/Decrease Dynamic change supported

Ports panel - 2 Node and 3 Node Configurations

132 Assure MIMIX for AIX User Guide v5.2.04.00

Replication Configuration Wizard Panels and Fields Field Support for Dynamic Update

Primary Ports Dynamic change supported

Failover Ports Dynamic change supported

Tiviol Storage Manager panel - 2 Node and 3 Node Configurations

Enable Tivoli Storage Manager. Enable/Disable Manual change only

Dynamically changing configuration of a replication group

For environments running version 5.2.02.00 or higher of Assure MIMIX for AIX,
certain types of replication group configuration changes can be made dynamically
without affecting the production environment. The changes listed as supported
dynamically in the previous table do not require stopping user’s applications and
unmounting the filesystems on the production server.

Any replication group changes listed in the previous table that are not supported for
dynamic update must be made manually using instructions in “Manually changing
configuration of a replication group” on page 134.

Before launching the Configuration Wizard to change the replication group

configuration, do the following:

1. On the Production server, stop the LCA replication agent for the replication
group that you are changing.
stopsrc -cs scrt_lca-<primary context id>

2. On the Production server, run esmon to verify that all outstanding LFCs have
been sent to the Recovery servers. Depending on the backlog of containers to be
applied, this could take some time.
esmon <primary context id>

Wait for the message "LFC information is not available" before stopping the
replication group on the Recovery servers.

3. On each of the Recovery servers, stop the Assure MIMIX for AIX replication
group you are changing to unload the Recovery server drivers.
rtstop -FC<primary context id>

Stopping the Assure MIMIX for AIX replication group on the Recovery servers
does not impact the production environment.

4. Use the configuration wizard to make the changes. From the Replication Group
portlet, click Configuration. From the resulting Configuration Window, click the
Change Replication action for the replication group you want to change. Follow
the wizard to make changes.

Assure MIMIX for AIX User Guide v5.2.04.00 133

 When you click Finish in the wizard to change the configuration, the
Configuration Summary area lists the steps required to initialize the
configuration and shows which steps have been completed or are in progress as
described in “Configuration initialization progress (Change Configuration)” on
page 146.

5. After the reconfiguration process has successfully completed. Start the

replication group in the following order:

a. On each of the Recovery servers, start the replication group that you
changed.
rtstart -C<primary context id>

b. On the Production server, start the LCA replication agent for the
replication group that you changed.
startsrc -s scrt_lca-<primary context id>

Manually changing configuration of a replication group

To change a replication group, do the following:

1. Navigate to the Replication Group portlet.

2. Click Configuration.

The Configuration Window displays. For detailed information refer to the

Assure MIMIX for AIX online help.

134 Assure MIMIX for AIX User Guide v5.2.04.00

 3. Click Change Replication from the Actions dropdown. The following messages
may appear:

a. The Change Replication Group dialog displays with a warning:

“Replication group cannot be changed because it is either failed over or the
partition has been migrated using Live Partition Mobility.”

b. The Change Replication Group Servers panel displays with a warning.

“Replication group is currently active. Configuration changes cannot be

saved until the replication group is stopped.”
Configuration changes cannot be saved until the replication group is
stopped. However, when you click Finish on the Summary panel, a message
will appear that instructs you to stop the replication group. To stop the
replication group, navigate to the Replication Groups portlet in the Assure
UI portal window and stop the replication group.

If these issues do not occur, the following panel displays.

Assure MIMIX for AIX User Guide v5.2.04.00 135

 4. Click Next.

The Change Replication Group Servers Login panel displays if you are not
logged in. Use this panel to log into the server specified in the panel.

5. Specify the username and password and click Log In. Log in to each server to
retrieve information. When you run commands, context IDs are used to identify
the replication group. The context IDs specified have been defaulted to unique
IDs on the servers in this replication group.

6. The Change Replication Group Servers panel displays again showing the login
status of each server.

136 Assure MIMIX for AIX User Guide v5.2.04.00

 7. Click Next.

The Change Replication Group Names panel displays.

8. Click Next.

The Change Replication Group Default Volume Groups panel displays.

Assure MIMIX for AIX User Guide v5.2.04.00 137

 9. Click Next.

The Change Replication Group Logical Volumes panel displays.

a. Click Add to add a logical volume using the Add Logical Volumes
dialog, shown below. For detailed information, refer to the Assure
MIMIX for AIX online help.

138 Assure MIMIX for AIX User Guide v5.2.04.00

 b. Select one or more logical volumes to protect on the production server.
c. Select the volume group on the recovery servers where the replicated data
will be located.

IMPORTANT
The Add Logical Volumes dialog will not contain any logical volumes that
are in use by other replication groups on the node.

AIX standard logical volume types (such as, raw, jfs, jfs2, jfslog, and
jfs21og) are allowed. AIX system internal logical volume types (such as,
aio_cache, boot, copy, paging, sysdump) are not allowed. Any other
non-standard logical volume types are allowed as “raw” logical volumes.
If a jfs or jfs2 logical volume is presented without an associated filesystem
path, it will not be available for protection.

Click OK.

The Change Replication Group Logical Volumes panel displays with the
selected logical volumes you want protected.

Assure MIMIX for AIX User Guide v5.2.04.00 139

 • Select the logical volume(s) you wish to change for this replication group
and click Change.

Use the Change Logical Volumes dialog, shown below, to choose a different
volume group for the replica logical volumes, on the recovery servers. By
default, the default volume group specified is used for this purpose. For
detailed information refer to the Assure MIMIX for AIX online help.

• Select the logical volume(s) you wish to change or remove for this
replication group and click Remove.

Use the Remove Logical Volumes dialog, shown below, to remove the
selected logical volumes from the replication group. These logical volumes
will no longer be protected. For detailed information refer to the Assure
MIMIX for AIX online help.

140 Assure MIMIX for AIX User Guide v5.2.04.00

 10. Click OK on either the Change or Remove Logical Volumes dialogs.

The Change Replication Group Logical Volumes panel displays.

11. Click Next.

The Change Replication Group Replication IP Addresses panel displays. By

default, replication uses the IP addresses of the servers. You can specify IP
labels or addresses that will be used specifically for replication. There are two
options:

• If you select, Use server IP addresses for replication, the following panel
appears.

• If you select, Use specified IP addresses for replication, the following panel
appears.

Assure MIMIX for AIX User Guide v5.2.04.00 141

 12. Click Next.

The Change Replication Group Containers panel displays. Containers are used
by internal processes and replication to move changed data between servers.

142 Assure MIMIX for AIX User Guide v5.2.04.00

 IMPORTANT
If you make configuration changes on the Container panel you could lose
CDP. For example, if you change the Size of each container field, you
will lose CDP. This will be reflected in the Change Replication Group
Summary panel displays, as shown page 146.

13. Click Next.

The Change Replication Group Container Options panel displays. Use this
panel to specify if you want to:

• Use compression during replication.

• Use encryption during replication. See “Support for data encryption in Assure
MIMIX DR for AIX” on page 19.

• Send partially filled containers after a specified amount of time. Otherwise,

containers are sent when they become full.

14. Click Next.

The Change Replication Group Snapshot Buffer panel displays. When a

snapshot is created, the snapshot buffer is used to hold the changes between the
location in the rollback window where the snapshot was created and the current
time. As changes are replicated, the snapshot buffer fills up.

Assure MIMIX for AIX User Guide v5.2.04.00 143

 15. Click Next.

The Change Replication Group Ports panel displays. Port numbers are used for
communication by the agents on each server. If you enter a port number value
that is already in use, the service name that is using the port will be displayed in
an error message.

16. Click Next.

The Change Replication Group Tivoli Storage Manager panel displays. Tivoli
Storage Manager (TSM) can archive containers which allows you to rollback or

144 Assure MIMIX for AIX User Guide v5.2.04.00

 take snapshots farther back in time. Full backups of the server where the TSM
client is running can also be performed.

17. Click Next.

The Change Replication Group Summary panel displays and shows a summary
of this replication group's configuration. If you have made configuration
changes on the Containers panel (see page 143), proceed to “Configuration
changes will reset the rollback window (CDP is lost)” on page 146.

IMPORTANT
When you decide to make configuration changes to the replication group,
they can only be saved if the replication group is stopped. Use the
Replication Group portlet on the Replication page to stop the replication
group.

Assure MIMIX for AIX User Guide v5.2.04.00 145

 18. To save and initialize this configuration on the specified servers, click Finish.
To view a summary of the changes you made, refer to “Configuration window
for Replication Groups” on page 152. The content of this panel is the same as
the Configuration Summary section in the Configuration Window. Refer to the
Assure MIMIX for AIX online help for additional information for the
Configuration Window. Refer to “Configuration window for Replication
Groups” on page 152.

Configuration changes will reset the rollback window (CDP is lost)

If you have made configuration changes on the Containers panel (see page 143), the
Change Replication Group Summary panel displays with the warning:
Configuration changes will reset the rollback window. This means you will lose
CDP.

Configuration initialization progress (Change Configuration)

When a configuration has been changed, the Configuration Summary area lists the
steps required to initialize the configuration and shows which steps have been
completed or are in progress. When the initialization is successfully completed, the
summary area displays the normal Configuration Summary content. Configuration
initialization cannot be stopped once it is started.

When the configuration is saved and validated, you can view the progress of the
configuration initialization in the Configuration Initialization Progress section in the
Configuration Window. As each step is successfully completed, a checkmark
appears next to the step. When you change an existing configuration, Assure
MIMIX for AIX runs commands for each step.

146 Assure MIMIX for AIX User Guide v5.2.04.00

 The step and command sequence can change depending upon the configuration
changes that you make. The table below describes steps and commands that are run
when you change a configuration:

Order Step Command

1. Save configuration. This was done when you clicked Finish in the
Change Replication Group wizard on the
Summary panel.

2. Copy configuration to S (S sccfgd_putcfg

is production server,
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

3. Delete internal logical scsetup -R -t smbitmap

volumes.

4. Delete replication scsetup -R -t lfc

container logical volumes or
on S (S is production scsetup -R -t lfc -t smfc
server, recovery server,
recovery server 1, or
recovery server 2). You
will see a row for each
server in the configuration.

5. Delete log record file scsetup -R -t lrfc -t pool

container and snapshot
logical volumes on S (S is
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

6. Delete replication scsetup -R -t lfc -t pool

container and snapshot or
logical volumes on S (S is scsetup -R -t lfc -t smfc -t lrfc -t
recovery server, recovery lifc -t pool
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

7. Delete all containers and scsetup -R

logical volumes on S (S is
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

Assure MIMIX for AIX User Guide v5.2.04.00 147

 Order Step Command

8. Delete snapshot logical scsetup -R -t pool

volumes on S (S is recovery
server, recovery server 1,
or recovery server 2). You
will see a row for each
server in the configuration.

9. Delete snapshot container scsetup -R -t jcontainer

logical volumes on S (S is
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

10. Delete replication scsetup -R -t lfc -t lrfc -t pool

container, snapshot, and
log record file container
logical volumes.

11. Create containers and scsetup -M

logical volumes on S (S is
production server or
recovery server). You will
see a row for each server in
the configuration.

12. Set all logical volumes as scconfig -W

replicated.

13. Set new logical volume X scconfig -M -L

as requiring replication (X
is a device such as /dev/
rLV_p520-95_0001).

14. Reset Send process (LCA) scrt_lca -fr

15. Reset Apply process scrt_aba -fr

(ABA) on S. (S is recovery
server, recovery server 1,
or recovery server 2)

16. Load drivers on S (S is scconfig -l

production server or
recovery server). You will
see a row for each server in
the configuration.

148 Assure MIMIX for AIX User Guide v5.2.04.00

 Order Step Command

17. Delete logical volume scsetup -X

device special files on S. (S
is production server,
recovery server, recovery
server 1, or recovery server
2). You will see a row for
each server in the
configuration.

18. Delete failover context on rtdr setup

S. (S is production server,
recovery server, recovery
server 1, or recovery server
2) You will see a row for
each server in the
configuration.

19. Delete failover context on sccfgd_delcfg

S (S is production server or
recovery server). You will
see a row for each server in
the configuration.

20. Verify configuration on S. sccfgchk

(S is production server,
recovery server, recovery
server 1, or recovery server
2)

NOTE
The steps that are run depend on what is changed in the configuration.

Related Topic:

“Configuration initialization progress (new configuration)” on page 128

Rename a replication group

To rename a replication group, do the following:

Assure MIMIX for AIX User Guide v5.2.04.00 149

 1. Navigate to the Replication Group portlet.

2. Click Configuration.

The Configuration Window displays. For detailed information refer to the Assure
MIMIX for AIX online help.
.

3. Click Rename from the Actions dropdown. There are two possible results:

a. The Rename Replication Group dialog displays with a warning:

Replication group cannot be renamed because it is either active and must be
stopped, failed over, or the partition has been migrated using live partition
mobility. Use the Replication Group portlet on the Replication page to stop
the replication group.

b. The Rename Replication Group displays:

150 Assure MIMIX for AIX User Guide v5.2.04.00

 Specify the new replication group name, and click OK. To view a summary
of the changes you made, refer to “Configuration window for Replication
Groups” on page 152.

Delete a replication group

To delete a replication group, do the following:

1. Navigate to the Replication Group or Clusters portlet.

2. Click Configuration.

The Configuration Window displays. For detailed information refer to the Assure
MIMIX for AIX online help.

3. Click Delete from the Actions dropdown. There are two possible results:

a. The Delete Replication Group dialog displays with a warning:

The Replication group cannot be deleted because it is either active and must
be stopped, failed over, or the partition has been migrated using live partition
mobility Use the Replication Group portlet on the Replication page to stop
the replication group.

b. The Delete Replication Group displays with a warning:

The Logical volumes configured in this replication group will no longer be
protected.

c. Click OK to delete the replication group. To view a summary of the changes

you made, refer to “Configuration window for Replication Groups” on
page 152.

Using earlier versions of Assure MIMIX for AIX to configure replication

groups
If you configured replication groups with a previous version of Assure MIMIX for
AIX, if the context ID is 1 then the replication group appears in the Assure UI portal
as RG-1.

Assure MIMIX for AIX User Guide v5.2.04.00 151

 Configuration window for Replication Groups
The Configuration window for replication groups lists all the replication groups in
the instance. The Configuration Window Summary section displays a summary of
the configuration for the selected replication group. See the Assure MIMIX for AIX
online help for information about each field.

Using the command line to perform configuration tasks

You can use the command line to perform the following configuration tasks:

• “Initialize a context” on page 153

• “Send partially filled containers automatically” on page 153

• “Verify your configuration using the sccfgchk command” on page 153

152 Assure MIMIX for AIX User Guide v5.2.04.00

 Initialize a context
Use the command line to initialize a context on the production, recovery, and
replication servers. Execute the following command on each server.
scsetup -C <Context ID> -M

Send partially filled containers automatically

The “Send partially filled containers automatically” option can be managed via the
command line using the scconfig command. Refer to “scconfig” on page 329. You
can also use the Replication Group Configuration Wizard. Refer to “Using the
Assure UI portal to configure replication groups” on page 108. Specifically, refer to
the New Replication Group Container Options panel, and the field, “Send partially
filled containers automatically” on page 122.

The Send partially filled containers automatically option enables you to control the
frequency of shipping containers (LFCs) to the recovery server during low I/O
periods.

The container is examined when the frequency to check value is reached. If at that
time the minimum percent filled value has not been reached, the container will not
be sent. When the container reaches the minimum percent filled value, containers
will not be immediately sent. There is a 5 second delay before the containers are
sent. The 5 second delay is provided to account for the possibility that the container
could become completely full. When the container is sent, the frequency to check
value is reset and the entire process starts again.

When changing either of the scconfig options (-a, -b), the command returns output
displaying the values for both options. If the frequency to check value is changed to
zero, the command output will also display “Send Partial Container Automatically
is not active”.

Verify your configuration using the sccfgchk command

Execute the following command on each node after the configuration has been
initialized. For information on the command syntax, refer to “sccfgchk” on
page 342.
sccfgchk -C <Context ID>

Support for LVM commands when the Assure MIMIX for AIX
drivers are loaded
The AIX Logical Volume Manager (LVM) manages Logical Volumes (LVs) that
Assure MIMIX for AIX protects.

Assure MIMIX for AIX User Guide v5.2.04.00 153

 Because Assure MIMIX for AIX manages Logical Volumes, not all the AIX LVM
commands are supported. The table below shows the LVM commands supported
when the Assure MIMIX for AIX drivers are loaded.

LVM Command Status

chfs -a Must execute es_swmaj command before and after using

freeze=0|off|<n> this LVM command when non-disruptive start was used
with jfs2 file systems.
es_swmaj is not necessary when using the normal start.
Freeze is not a valid option with jfs file systems

chlv OK

chlvcopy OK

chvg OK

cplv OK. LV must be closed

defragfs OK

exportvg OK

extendlv OK

extendvg OK

fileplace OK

importvg OK

joinvg Must execute es_swmaj command before and after using

this LVM command.

lslv OK

lsvg OK

lvmstat OK

migratepv Must execute es_swmaj command before and after using

this LVM command.

mirrorvg Must execute es_swmaj command before and after using

this LVM command.

mirscan OK

mklv OK

mklvcopy Must execute es_swmaj command before and after using

this LVM command.

mkvg OK

readlvcopy OK

redefinevg OK

154 Assure MIMIX for AIX User Guide v5.2.04.00

 LVM Command Status

reducevg OK

reorgvg Must execute es_swmaj command before and after using

this LVM command.

rmlv OK, if the LV is not in PVS.

rmlvcopy OK

snapshot Must execute es_swmaj command before and after using

this LVM command.

splitlvcopy OK

splitvg OK

syncvg Must execute es_swmaj command before and after using

this LVM command.

synclvodm Not allowed. Use es_swmaj command instead to run

certain AIX LVM commands. For example, joinvg,
migratepv, and other commands listed in this table.

unmirrorvg OK

varyoffvg OK. All LVs must be closed

varyonvg OK

es_swmaj
Usage
Use this command to switch and restore the LV major number for all LVs in an
Assure MIMIX for AIX context. This will allow AIX LVM commands such as
“migratepv” to function when the Assure MIMIX for AIX drivers are loaded.

Syntax
es_swmaj -C <Context ID> [-s | -f | -u]
-s: Switch to major number(raw LVs are excluded)
-f: Switch to major number(including raw LVs)
-u: Restore major number
-v: Verify switch to major number.

IMPORTANT
If the “-f” option is selected for raw LVs, they must be open before
executing this command. The raw LVs must remain open and no additional
opens should be done until this command is executed with the “-u” option.

Assure MIMIX for AIX User Guide v5.2.04.00 155

Assure MIMIX for AIX default ports
Assure MIMIX for AIX always checks the /etc/services file for port assignments to
be used by a Context ID. If no port assignments are found in the /etc/services file,
Assure MIMIX for AIX will use the default ports listed below. If the default port
assignments are in use by another application, then specific port assignments must
be added to the /etc/services file for a Context ID.

The default port assignments shown are not added to the /etc/services file when
Assure MIMIX for AIX is installed.
sc<Context ID>aa_channel 5747/tcp # Archive Agent
sc<Context ID>ra_channel 5748/tcp # Restore Agent (scrt_rs)
sc<Context ID>ca_channel 5749/tcp # Restore Client Agent
sc<Context ID>aba_dchannel 5750/tcp # Assured Backup Agent
sc<Context ID>lca_dchannel 5751/tcp # Log Control Agent
sc<Context ID>aa_achannel 5752/tcp # Archive Agent
sc<Context ID>aba_channel 5753/tcp # Assured Backup Agent
sc<Context ID>lca_channel 5754/tcp # Log Control Agent

On the Configuration Wizard Ports panel, when you are creating a new replication
group configuration, the Configuration Wizard reads the /etc/services file to find
port numbers that are unassigned, including the default port assignments if they are
not in use by another application, and populates the Port fields with the unassigned
values. You can use the values discovered by the Configuration Wizard or change
them.

When the new replication group is deployed, the /etc/services file will be updated to
include the port numbers for the replication group.

On the Configuration Wizard Ports panel, when you are changing a replication
group configuration, the Configuration Wizard reads the /etc/services file to find
port numbers that are already assigned to the replication group and populates the
Port fields with the assigned values. If the Configuration Wizard does not find any
port numbers for the replication group in the /etc/services file, port numbers that are
unassigned, including the default port assignments if they are not in use by another
application, will be used to populate the values in the Port fields.

You can use the values discovered by the Configuration Wizard or change them.

When the new replication group is deployed, the /etc/services file will be updated to
include the port numbers for the replication group.

Editing the /etc/services file to add specific port assignments

You can go to step 14 on page 124 and use the New Replication Group Ports panel
(of the Configuration wizard) to automatically assign port numbers when you create
a new replication group. Alternatively, you can edit the /etc/services file.

156 Assure MIMIX for AIX User Guide v5.2.04.00

 IMPORTANT
Precisely recommends that you use the Configuration wizard to assign port
numbers.

If multiple Context IDs are configured, each Context ID must have a unique port
assignment. Port assignments for Primary and Failover Context IDs must also be
unique.

For example, if the Primary Context ID is 25 and the Failover Context ID is 250,
add the following entries to the /etc/services file on all servers.

IMPORTANT
Do not include the # Description shown below when adding entries to the
/etc/services file on all servers. For example, do not include, # Assured
Backup Agent.

sc25aba_channel 6901/tcp # Assured Backup Agent

sc25lca_channel 6902/tcp # Log Control Agent
sc25aa_channel 6903/tcp # Archive Agent
sc25ra_channel 6904/tcp # Restore Agent (scrt_rs)
sc25ca_channel 6905/tcp # Restore Client Agent
sc25aba_dchannel 6906/tcp # Assured Backup Agent
sc25lca_dchannel 6907/tcp # Log Control Agent
sc25aa_achannel 6908/tcp # Archive Agent

sc250aba_channel 6909/tcp # Assured Backup Agent

sc250lca_channel 6910/tcp # Log Control Agent
sc250aa_channel 6911/tcp # Archive Agent
sc250ra_channel 6912/tcp # Restore Agent (scrt_rs)
sc250ca_channel 6913/tcp # Restore Client Agent
sc250aba_dchannel 6914/tcp # Assured Backup Agent
sc250lca_dchannel 6915/tcp # Log Control Agent
sc250aa_achannel 6916/tcp # Archive Agent

The default port assignments shown below for the Push Server are added to
the/etc/services file when Assure MIMIX for AIX is installed.
mxws 17835/tcp
mxwsmgmt 17836/tcp

If the default ports assignment for the Push Server are in use by another application,
then the port numbers used by the Push Server must be changed.

To change the port numbers used by the Push Server:

• Use stopsrc to stop the Push Server on all servers

stopsrc -cs mxws

Assure MIMIX for AIX User Guide v5.2.04.00 157

 • Use endvsisvr to stop the Assure UI server and the Assure MIMIX for AIX
portal application on the servers where the Assure UI portal is running.
/opt/visionsolutions/http/vsisvr/httpsvr/bin/endvsisvr

• Change the port numbers for the Push Server in the configuration file
/opt/visionsolutions/mxws/service/httpsvr/conf/mxws.properties on all servers
to unused port numbers.
server.port=17835 <replace 17835 with an unused port number>
management.port=17836 <replace 17836 with an unused port number>

You must also update the Push Server port configured for the Assure MIMIX
for AIX portal application in: /opt/visionsolutions/http/vsisvr/httpsvr/
webapps/mimixaix-pa/WEB-INF/classes/com/visionsolutions/mimixaix/mxws.
properties. There is no need to configure the management port for the Push
Server here as it is not used by the Portal Application.
mxws.port=17835 <replace 17835, this must match the server.port
number used in the
/opt/visionsolutions/mxws/service/httpsvr/conf/mxws.properties
configuration file.>

• Use startsrc to start the Push Server on all servers

startsrc -s mxws

• Use strvsisvr to start the Assure UI server and the Assure MIMIX for AIX
portal application on the servers where the Assure UI portal was running.
/opt/visionsolutions/http/vsisvr/httpsvr/bin/strvsisvr

NOTE
On Windows, the Push Server portal application configuration will be in
the default install location at C:\Program
Files\VisionSolutions\http\vsisvr\httpsvr\webapps\mimixaix-pa\WEB-INF
\classes\com\visionsolutions\mimixaix\ mxws.properties.

• End the Assure UI server.

To end the Assure UI server, refer to the Assure Unified Interface User’s Guide.

• Change the Push Server port number for the portal application.
mxws.port=17835 <replace 17835, this must match the server.port
number used in the
/opt/visionsolutions/mxws/service/httpsvr/conf/mxws.properties
configuration file on the AIX servers.>

• Start the Assure UI server.

To start the Assure UI server, refer to the Assure Unified Interface User’s Guide.

158 Assure MIMIX for AIX User Guide v5.2.04.00

Activating syslog debug
1. During the installation process, the following debug line is automatically added
to /etc/syslog.conf.
*.debug var/log/EchoStream/es_syslog.out rotate size 10m files
7 compress # EchoStream

2. tail –f var/log/EchoStream/es_syslog.out

After you complete the Assure MIMIX for AIX post-installation tasks, refer to
“Starting and Stopping” on page 187 for information on how to start and stop
Assure MIMIX for AIX.

Assure MIMIX for AIX User Guide v5.2.04.00 159

160 Assure MIMIX for AIX User Guide v5.2.04.00
Configuring Clusters
8

After you created and configured replication groups you can use the Cluster
Configuration wizard to configure new clusters and add a replication group to a
cluster. In addition you can use the Change Application wizard to change the
existing clustered application settings of a replication group.

This chapter contains the following sections:

• “Using the Assure UI portal to configure clusters” on page 162

• “Change Application wizard” on page 172

• “Add replication group to Cluster” on page 179

Assure MIMIX for AIX User Guide v5.2.04.00 161

Using the Assure UI portal to configure clusters
You can use the Cluster Configuration Wizard to “Create and configure a cluster” on
page 162.

NOTE
If you plan to use a highly available host name, append the highly
available host name to the host entries in the /etc/hosts file on both nodes
configured in the cluster before changing the existing clustered application
settings of a replication group.

Example: /etc/hosts file on Cluster NodeA

10.22.31.98 NodeA <Highly available host name>
10.22.31.99 NodeB <Highly available host name>

Example: /etc/hosts file on Cluster NodeB

10.22.31.98 NodeA <Highly available host name>
10.22.31.99 NodeB <Highly available host name>

Create and configure a cluster

To create and configure a new cluster, do the following:

1. Navigate to the Summary, Clusters or Replication portlet.

2. Click Configuration.

The Configuration window displays.

For detailed information refer to the Assure MIMIX for AIX online help.

162 Assure MIMIX for AIX User Guide v5.2.04.00

 3. Click New Cluster.

This starts the Configuration wizard and the New Cluster - Cluster Name and
Servers panel displays.

This screen is displayed when there are only 2 servers configured in the
instance.

This screen is displayed when there are more than 2 servers configured in the
instance.

Assure MIMIX for AIX User Guide v5.2.04.00 163

 The Cluster Name and Servers panel contains the following fields:

Field Description

Cluster Name and Servers—Section for specifying the name of the cluster, an
optional description, and a portal connection for each server in the cluster.

Cluster name Specify the name of the cluster. Cluster names can be 256
characters long and can contain any alphanumeric character.
Whitespace is not allowed.

Description Optional description for the cluster. Cluster descriptions can

be 256 characters long and can contain any alphanumeric
character. Whitespace is allowed.

164 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Server 1 Select from the list of portal connections that are associated
with the instance. The host name from the portal connection
is used for the server. This ensures the newly configured
cluster will appear in the instance. If there are only two
available portal connections, both drop-downs will default
to the available portal connections. When a portal
connection is selected from one drop-down, it will not be
available in the other drop-down.
If there are more than two servers:
• Select...
• Any portal connection that is in the instance domain and
has not been selected for Server 1.
If exactly two servers:
• One of the available portal connections.

Server 2 Specify the portal connection for the second server in the
cluster. If there are only two available portal connections,
both drop-downs will default to the available portal
connections.When a portal connection is selected from one
drop-down, it will not be available in the other drop-down.
If there are more than two servers:
• Select...
• Any portal connection that is in the instance domain and
has not been selected for Server 1.
If exactly two servers:
One of the available portal connections.

The Cluster Name and Servers - Servers panel contains the following fields:

4. Click Next.

The New Cluster - Network and Heartbeats panel displays. Initially, a message
indicates that Assure MIMIX for AIX is retrieving network information from
each server. Use this panel to specify the networks to add and the heartbeat
threshold for each network.

Assure MIMIX for AIX User Guide v5.2.04.00 165

 The New Cluster - Network and Heartbeats panel contains the following fields:

Field Description

Add Action to add networks to the cluster. See the Add Networks
dialog section for details.

Add WAN Action to add a WAN network to the cluster. You can
specify a network name, missed heartbeat threshold and
local area networks. See the Assure MIMIX for AIX online
help for field descriptions.

Remove Action to remove networks from the cluster. See the Assure
MIMIX for AIX online help for field descriptions.

Select all Used to select all networks in the list.

checkbox

Network Specifies networks configured for this replication group.

Type Specifies the type of network.

Description Specifies a user supplied description of the network.

Heartbeat Specifies a heartbeat threshold for the network.

Threshold

Actions Action to change the name, description, and heartbeat

threshold of a network. See the Assure MIMIX for AIX
online help for field descriptions.

166 Assure MIMIX for AIX User Guide v5.2.04.00

 5. Click Add, to Add Network. There are two versions of this dialog, based on the
type that is selected. Options include LAN or Serial.

The dialog below is shown when a LAN network is selected. See the Assure
MIMIX for AIX online help for field descriptions.

6. Specify a Network name, select a network and click OK. The New Cluster -
Network and Heartbeats panel displays with the selections you made.

Assure MIMIX for AIX User Guide v5.2.04.00 167

 7. Click Next. The New Cluster - User Exits panel displays.

The New Cluster - User Exits panel contains the following fields:

Field Description

Add Action to add a user network to the cluster. See the Dialog -
Add User Exit dialog for details.

Remove Action to remove user exits from the cluster. See the Assure
MIMIX for AIX online help for field descriptions.

Resource Type Specifies the Resource type for the user exit. Possible
values:
• Application
• Application Processes
• Cluster Services
• Replication Group
• Hostname
• Network
• Network Interface
• Server
• Service IP Address
• Custom Monitor
• WAN

Event Specifies the event type for the user exit. Possible values:
• Start
• Stop
• Failure

168 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Notification Displays the login status for the specified server.

Script Statuses can be:
• Logged in
• Not logged in
• Validating user name
• Error text

Pre-Event Script Yes or No. Yes indicates that a script is configured. No

indicates that no script has been configured.

Post-Event Yes or No. Yes indicates that a script is configured. No

Script indicates that no script has been configured.

Actions Action to change the scripts for a user exit. Possible values
are Change and Remove. See the Assure MIMIX for AIX
online help for field descriptions.

8. Click Next on the User Exits panel if you do not want to add user exits,
otherwise click Add - the Add User Exits dialog displays.

The Add User Exit dialog enables you to add user exits for the cluster. Specify
the resource type, event and the path to the user scripts, and click OK.

9. The New Cluster - User Exits panel displays with the added user exit.

Assure MIMIX for AIX User Guide v5.2.04.00 169

 Click Add to add more user exits.

10. Click Next on the User Exits panel.

The Summary panel displays. This panel provides a summary of the cluster
configuration.

By default the Add a replication group to this cluster check box contains a
check mark which will launch the New Replication Group configuration wizard
if no replication groups are configured, or the Add Replication Group to Cluster
configuration wizard when replication groups are configured. Uncheck the Add
a replication group to this cluster check box if you do not want to add a
replication group at this time.

170 Assure MIMIX for AIX User Guide v5.2.04.00

 11. Click Finish - To save this configuration on the specified servers and create the
cluster.

Configuration window for Clusters

The Configuration window for clusters displays summary information for the
selected cluster. See the Assure MIMIX for AIX online help for information about
each field.

Assure MIMIX for AIX User Guide v5.2.04.00 171

Change Application wizard
Use the Change Application wizard to change the existing clustered application
settings of a replication group.

1. From the Replication Group or Cluster portlets click Configuration.

2. From the Configuration window, select Change Application from the Actions
dropdown for a replication group.

The Change Application - Select Cluster panel displays. This panel shows the
selected replication group that is participating in the specified cluster. Cluster
services will be stopped while configuration changes are deployed. Replication

172 Assure MIMIX for AIX User Guide v5.2.04.00

 groups participating in the cluster will not be managed until cluster services are
started again

The Change Application - Select Cluster panel contains the following fields:

Field Description

Replication Specifies the name of the replication group.

group

Cluster Specifies the name of the cluster that this replication group
is assigned to.

3. Click Next. The Change Application - Application panel displays. Specify the
application name, description, and an optional highly available host name that
follows the application when a failover occurs to the recovery server.

Assure MIMIX for AIX User Guide v5.2.04.00 173

 The Change Application - Application panel contains the following fields:

Field Description

Application Specifies the name of the application. Application names can

name be 256 characters long and can contain any alphanumeric
character. Application names must start with an alphanumeric
character. Hyphens ( - ) and underscores ( _ ) are allowed.
Spaces or other special characters are not allowed.

Description Specifies an optional description for the application.

Application descriptions can be 256 characters long and can
contain any alphanumeric character. Whitespace is allowed,

Highly Specifies an optional highly available host name for the

available host application. When a planned or unplanned failover procedure
name is run, the highly available host name will take effect on the
recovery server. Highly available host names must start with an
alphanumeric character. Hyphens ( - ) and underscores ( _ ) are
allowed. Spaces or other special characters are not allowed.

4. Click Next. The Change Application - Application Processes and Monitoring

panel displays. Enabling the cluster to manage the availability of the application
is recommended. Specify scripts to start and stop the application processes and
which processes to monitor for availability.

174 Assure MIMIX for AIX User Guide v5.2.04.00

 The Change Application - Application Processes and Monitoring panel contains
the following fields:

Field Description

Enable the Indicates if this replication group has start and stop scripts
cluster to and application monitoring defined.
manage
application
availability

Start script Specifies the command that starts the application process.
The start script is also responsible for ensuring that the
correct number of instances of a process is running, and for
starting instances as needed. The Start script can be a script
or a binary file. The field includes the absolute path to the
command. Possible values:
• valid path
• blank

Stop script Specifies the command that stops the application's process
or processes anytime the application is stopped. The Stop
command can be a script or a binary file. The field includes
the absolute path to the command.
Possible values:
• valid path
• blank

Processes to Specifies the name of the process started by the Start script
monitor and monitored by the clustering component. For possible
values see the description for match criteria.

Assure MIMIX for AIX User Guide v5.2.04.00 175

 Field Description

match criteria Specifies the criteria to use to find the process to monitor.
Possible values:
• Simple match—The specified string is matched against
the output of ps -eo args. If the supplied string
appears as a part of any output lines, then the process is
assumed to be started. If you are monitoring more than
one process, enter each additional process name
separated by a semi-colon. In that case, the application is
reported to be started only if all specified processes are
found.
• Regex match—The specified string is a regular
expression matched against the output of ps -eo
args. If the specified string appears as a part of any
output lines, then the process is assumed to be started. If
you are monitoring more than one process, enter each
additional process string separated by a semi-colon. In
that case, the application is reported to be started only if
all specified processes are found. The regular expression
match uses POSIX Regular Expression matching.
Precisely recommends that you use the Simple Match
option and match the string exactly as it appears in the
ps -eo args output.
• PID file— The specified string is taken as the path of the
processes PID (process identification number) file. The
process is reported to be started only if the PID file
exists, and the PID contained in it matches a running
process.
• Script—The specified string is taken as a shell command,
whose exit code indicates the status of the process.
Exit code value Status of the process
Less than zero Agent Error
0 Running
1 Stopped
Greater than 1 Failed

Polling interval: Specifies how often, in seconds, the clustering component

checks for this process. Possible values are 0-999 or dash.

Delay before Specifies the time in seconds that the clustering component
starting will wait after the application starts before it begins
monitoring the process. Possible values are 0-999 or dash.

5. Click Next. The Change Application - Custom Monitors panel displays. Custom
monitors are optional and are used to monitor any resource.

176 Assure MIMIX for AIX User Guide v5.2.04.00

 The Change Application - Custom Monitors panel contains the following fields:

Field Description

Add Displays the Add Custom Monitor dialog you can use to
add a custom monitor.

Remove Displays the Add Custom Monitor dialog you can use to
remove a custom monitor. This action will remove a row
from the table.

Select all Used to select all items in the list.

checkbox

Monitor Specifies the name of the custom monitor. The name can be
up to 32 characters in length and can contain any characters
except space.

Command Specifies the script or command to run to monitor the

application. Possible values are:
• A valid path. The script is abbreviated to 40 characters
with an ellipsis in the middle of the path.
• A dash

Delay Specifies the amount of time to wait in seconds of when to

begin running the monitor. Possible values are 0-999 or
dash.

Interval Specifies the time interval in seconds of how often to run

the monitor. Possible values are 0-999 or dash.

Assure MIMIX for AIX User Guide v5.2.04.00 177

 Field Description

Retries Specifies the maximum number of times to retry the

monitor before a failure is flagged. possible values are
0-999 or dash.

Actions Select Details to display the Custom Monitor Details dialog

box. Select Remove to display the Remove Custom Monitor
dialog box.

6. Click Next. The Change Application - Service IP Addresses panel displays.

Service IP addresses are optional and follow the application when a failover
occurs to the recovery server.

The Change Application - Service IP Addresses panel contains the following

fields:

Field Description

Service IP Specifies the service IP address.

Address

Network Name Specifies the name of the network.

Network ID Specifies the network ID of the network.

Subnet Mask Specifies the subnet mask of the network selected

Actions Select Details to display the Service IP Address Details

dialog box. Select Remove to display the Remove Service
IP Address dialog box.

7. Click Next. The Change Application Summary panel displays. The following is
a summary of the application configuration for the replication group being

178 Assure MIMIX for AIX User Guide v5.2.04.00

 added to the cluster. To save this configuration, click Finish. To cancel, click
Cancel.

Add replication group to Cluster

Use the Add Replication Group to Cluster wizard to add an existing non-clustered
replication group to a cluster.

NOTE
If you plan to use a highly available host name, append the highly
available host name to the host entries in the /etc/hosts file on both nodes
configured in the cluster before adding an existing non-clustered
replication group to a cluster.

Example: /etc/hosts file on Cluster NodeA

10.22.31.98 NodeA <Highly available host name>
10.22.31.99 NodeB <Highly available host name>

Example: /etc/hosts file on Cluster NodeB

10.22.31.98 NodeA <Highly available host name>
10.22.31.99 NodeB <Highly available host name>

1. From the Replication Group or Cluster portlets click Configuration.

2. From the Configuration window, select Add to Cluster from the Actions
dropdown for a replication group.

The Add Replication Group to Cluster - Select Cluster panel displays. Adding a
replication group to a cluster configures an application to manage and makes the

Assure MIMIX for AIX User Guide v5.2.04.00 179

 application and replication highly available. Cluster services will be stopped
while configuration changes are deployed. Replication groups participating in
the cluster will not be managed until cluster services are started again.

The Add Replication Group to Cluster - Select Cluster panel contains the
following fields:

Field Description

Replication Specifies the name of the replication group. This is the

group replication group row that was selected from the Add
Replication Group to Cluster action or the Change
Replication Group action.

Cluster This list contains valid clusters for this replication group.
Clusters must have the same 2 nodes as the replication
group in order to be included in the list. Possible values:
If more than one cluster:
• Select…
• Valid cluster for this replication group.
If only one cluster:
• Then one cluster can be selected.

3. Click Next. The Add Replication Group to Cluster - Application panel displays.
Specify the application name, description, and an optional highly available host
name that follows the application when a failover occurs to the recovery server.

180 Assure MIMIX for AIX User Guide v5.2.04.00

 The Add Replication Group to Cluster - Application panel contains the following
fields:

Field Description

Application Specifies the name of the application. Application names can

name be 256 characters long and can contain any alphanumeric
character. Application names must start with an alphanumeric
character. Hyphens ( - ) and underscores ( _ ) are allowed.
Spaces or other special characters are not allowed.

Description Specifies an optional description for the application.

Application descriptions can be 256 characters long and can
contain any alphanumeric character. Whitespace is allowed.

Highly Specifies an optional highly available host name for the

available host application. When a planned or unplanned failover procedure
name is run, the highly available host name will take effect on the
recovery server. Highly available host names must start with
an alphanumeric character. Hyphens ( - ) and underscores ( _
) are allowed. Spaces or other special characters are not
allowed.

4. Click Next. The Add Replication Group to Cluster - Application Processes and
Monitoring panel displays. Enabling the cluster to manage the availability of the
application is recommended. Specify scripts to start and stop the application
processes and which processes to monitor for availability.

Assure MIMIX for AIX User Guide v5.2.04.00 181

 The Add Replication Group to Cluster - Application Processes and Monitoring
panel contains the following fields:

Field Description

Enable the Indicates if this replication group has start and stop scripts
cluster to and application monitoring defined.
manage
application
availability

Start script Specifies the command that starts the application process.
The start script is also responsible for ensuring that the
correct number of instances of a process is running, and for
starting instances as needed. The Start script can be a script
or a binary file. The field includes the absolute path to the
command. Possible values:
• valid path
• blank

Stop script Specifies the command that stops the application's process
or processes anytime the application is stopped. The Stop
command can be a script or a binary file. The field includes
the absolute path to the command.
Possible values:
• valid path
• blank

Processes to Specifies the name of the process started by the Start script
monitor and monitored by the clustering component. For possible
values see the description for match criteria.

182 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

match criteria Specifies the criteria to use to find the process to monitor.
Possible values:
• Simple match—The specified string is matched against
the output of ps -eo args. If the supplied string
appears as a part of any output lines, then the process is
assumed to be started. If you are monitoring more than
one process, enter each additional process name
separated by a semi-colon. In that case, the application is
reported to be started only if all specified processes are
found.
• Regex match—The specified string is a regular
expression matched against the output of ps -eo
args. If the specified string appears as a part of any
output lines, then the process is assumed to be started. If
you are monitoring more than one process, enter each
additional process string separated by a semi-colon. In
that case, the application is reported to be started only if
all specified processes are found. The regular expression
match uses POSIX Regular Expression matching.
Precisely recommends that you use the Simple Match
option and match the string exactly as it appears in the
ps -eo args output.
• PID file— The specified string is taken as the path of the
processes PID (process identification number) file. The
process is reported to be started only if the PID file
exists, and the PID contained in it matches a running
process.
• Script—The specified string is taken as a shell command,
whose exit code indicates the status of the process.
Exit code value Status of the process
Less than zero Agent Error
0 Running
1 Stopped
Greater than 1 Failed

Polling interval: Specifies how often, in seconds, the clustering component

checks for this process. Possible values are 0-999 or dash.

Delay before Specifies the time in seconds that the clustering component
starting will wait after the application starts before it begins
monitoring the process. Possible values are 0-999 or dash.

5. Click Next. Add Replication Group to Cluster - Custom Monitors panel

displays. Custom monitors are optional and are used to monitor any resource.

Assure MIMIX for AIX User Guide v5.2.04.00 183

 The Add Replication Group to Cluster - Custom Monitors panel contains the
following fields. For information on the Add Custom Monitor dialog refer to the
Assure MIMIX for AIX online help.

Field Description

Add Displays the Add Custom Monitor dialog you can use to
add a custom monitor.

Remove Displays the Add Custom Monitor dialog you can use to
remove a custom monitor. This action will remove a row
from the table.

Select all Used to select all items in the list.

checkbox

Monitor Specifies the name of the custom monitor. The name can be
up to 32 characters in length and can contain any characters
except space.

Command Specifies the script or command to run to monitor the

application. Possible values are:
• A valid path. The script is abbreviated to 40 characters
with an ellipsis in the middle of the path.
• A dash

Delay Specifies the amount of time to wait in seconds of when to

begin running the monitor. Possible values are 0-999 or
dash.

Interval Specifies the time interval in seconds of how often to run

the monitor. Possible values are 0-999 or dash.

184 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Retries Specifies the maximum number of times to retry the

monitor before a failure is flagged. Possible values are
0-999 or dash.

Actions Select Details to display the Custom Monitor Details dialog

box. Select Remove to display the Remove Custom Monitor
dialog box.

6. Click Next. The Add Replication Group to Cluster - Service IP Addresses panel
displays. Service IP addresses are optional and follow the application when a
failover occurs to the recovery server.

The Add Replication Group to Cluster - Service IP Addresses panel contains the
following fields. For information on the Add Service IP Address dialog refer to
the Assure MIMIX for AIX online help.

Field Description

Service IP Specifies the service IP address.

Address

Network Name Specifies the name of the network.

Network ID Specifies the network ID of the network.

Subnet Mask Specifies the subnet mask of the network selected

Actions Select Details to display the Service IP Address Details

dialog box. Select Remove to display the Remove Service
IP Address dialog box.

Assure MIMIX for AIX User Guide v5.2.04.00 185

 7. Click Next. The Add Replication Group to Cluster Summary panel displays.
The following is a summary of the application configuration for the replication
group being added to the cluster. To save this configuration, click Finish. To
cancel, click Cancel.

186 Assure MIMIX for AIX User Guide v5.2.04.00

Starting and Stopping
9

Assure MIMIX for AIX provides capabilities to start up and shut down both the
production and the recovery servers.

This chapter contains:

• “Using the Assure UI portal to start and stop Assure MIMIX for AIX” on
page 187

• “Using the command line to start and stop Assure MIMIX for AIX” on
page 189

Using the Assure UI portal to start and stop Assure MIMIX for
AIX
This topic contains two sections:

• “Using the Assure UI portal to start Assure MIMIX for AIX” on page 187

• “Using the Assure UI portal to stop Assure MIMIX for AIX” on page 188

Using the Assure UI portal to start Assure MIMIX for AIX

The start action takes any necessary actions to get replication started. This
includes starting the processes and loading the drivers. For detailed information
refer to the Assure MIMIX for AIX online help.

To start Assure MIMIX for AIX:

1. Log in to the Assure UI portal. See “Logging in to the Assure UI portal” on

page 88.

2. Navigate to the Replication Group portlet.

3. Do one of the following for a specific replication group:

• Click Start from the Action toolbar.

• Select Start from the Actions dropdown.

The Start Replication Group dialog displays:

Assure MIMIX for AIX User Guide v5.2.04.00 187

 4. Click OK, to start the replication group for the selected servers.

The Start Replication Group dialog remains displayed until the action completes
successfully.

Using the Assure UI portal to stop Assure MIMIX for AIX

The stop action takes any necessary actions to stop replication.For detailed
information refer to the Assure MIMIX for AIX online help.

NOTE
Applications must be stopped before stopping replication. File systems are
unmounted and data is no longer protected when replication is stopped.

To stop Assure MIMIX for AIX:

1. Log in to . See “Logging in to the Assure UI portal” on page 88.

2. Navigate to the Replication Group portlet.

3. Do one of the following for a specific replication group:

• Click Stop from the Action toolbar.

• Select Stop from the Actions dropdown.

The Stop Replication Group dialog displays:

188 Assure MIMIX for AIX User Guide v5.2.04.00

 4. Click OK, to stop the replication group for the selected servers.

The Stop Replication Group dialog remains displayed until the action completes
successfully.

Using the command line to start and stop Assure MIMIX for AIX
This topic contains two sections:

• “Using the command line to start Assure MIMIX for AIX” on page 189

• “Using the command line to stop Assure MIMIX for AIX” on page 191

Using the command line to start Assure MIMIX for AIX

If you wish to install Assure MIMIX for AIX, configure a non-clustered replication
group, and start replication without stopping your applications that are already
running refer to “non-Disruptive Startup Mode” on page 190. Otherwise, proceed
as follows:

1. On the production server, start Assure MIMIX for AIX:

NOTE
Step 2 and Step 3 are done for the first start after Assure MIMIX for AIX
is configured.

2. Stop any applications that are using the Assure MIMIX for AIX PVS
(Production Volume Set) LVs (Logical Volumes).

Assure MIMIX for AIX User Guide v5.2.04.00 189

 3. Make sure that any file systems associated with the PVS LVs are unmounted.
Use the AIX “umount” command.
umount /filesystem

4. Start Assure MIMIX for AIX. Enter the following command:

rtstart -C <Context ID>

The following output will display:

# rtstart -C 74
Loading Assure MIMIX DR for AIX Production drivers
Starting scrt_lca
fsck -fp -y /dev/rlvFS_C74_11

/dev/rlvFS_C74_11 (/FS_C7): ** Unmounted cleanly - Check

suppressed
Mounting /FS_C74_11...

5. Start the application.

On the recovery server, start Assure MIMIX for AIX by performing the following
steps:

6. Start Assure MIMIX for AIX.

rtstart -C <Context ID>

This displays:
# rtstart -C 74
Loading Assure MIMIX DR for AIX Recovery Server Drivers
Starting scrt_aba

non-Disruptive Startup Mode

This feature is for customers to be able to install Assure MIMIX for AIX, configure
a non-clustered replication group, and start replication without stopping their
applications that are already running.

NOTE
ALL file systems must be mounted BEFORE loading the drivers for
non-Disruptive Startup Mode. A full synchronization will occur for
non-clustered replication groups with mounted file systems. This may take
an extended period of time.

For a non-clustered replication group, you can start replication in non-Disruptive

Startup Mode in two ways:

190 Assure MIMIX for AIX User Guide v5.2.04.00

 • From the command line, use the rtstart command with the -r option on the
production and recovery server to start the replication group. Refer to “rtstart”
on page 323.
rtstart -C <Context ID> -r

• From the Assure UI portal, select “Mounted” in the File Systems column
drop-down menu in the Start Replication Group dialog.

NOTE
Refer to “Support for LVM commands when the Assure MIMIX for AIX
drivers are loaded” on page 153. The table shows the LVM commands
supported when the Assure MIMIX for AIX drivers are loaded.

This feature is intended to be used only once during the initial configuration, the
loading of the Assure MIMIX for AIX drivers and the full synchronization of data.

Before stopping the replication group, the user's application must be stopped first.
When the replication group is stopped the filesystems will be unmounted by Assure
MIMIX for AIX and the drivers will be unloaded. Refer to “rtstop” on page 324.

To restart the replication group:

• From the command line, use the rtstart command without the -r option on the
production and recovery server to start the replication group. Refer to “rtstart”
on page 323.
rtstart -C <Context ID>

• From the Assure UI portal, select Not Mounted in the File Systems column
drop-down menu in the Start Replication Group dialog.

Monitoring the log files

Use the tail command to check the log files on all servers to check that processes are
running properly.

1. Examine log files on the production server.

tail –f /var/log/EchoStream/scrt_lca-<ContextID>.out

2. Examine log files on the recovery server.

tail –f /var/log/EchoStream/scrt_aba-<ContextID>.out

Using the command line to stop Assure MIMIX for AIX

On the production server, stop Assure MIMIX for AIX.

Assure MIMIX for AIX User Guide v5.2.04.00 191

 1. Stop the application.

2. Unmount the protected volumes.

rtumnt -C <Context ID>

3. Stop Assure MIMIX for AIX, synchronize data, and unload the drivers on the
production server.
rtstop -FSC <Context ID>

4. On the recovery server, stop Assure MIMIX for AIX and unload the drivers:
rtstop -FC <Context ID>

192 Assure MIMIX for AIX User Guide v5.2.04.00

Creating Snapshots
10

Overview
Assure MIMIX for AIX enables you to restore a complete copy of the data on the
production server to any time in the past. You can quickly restore a database that
has crashed and rollback the data to a point before the corruption occurred.

This chapter contains:

• “Using snapshots to protect your data” on page 193

• “Using the Assure UI portal to create a snapshot” on page 194

– “Using the Assure UI portal to increase the snapshot buffer size” on

page 196

• “Using the command line to create a snapshot” on page 197

Using snapshots to protect your data

If damage to your data is limited to a single volume or group of volumes, you can
choose to rollback the affected volume(s). You do not have to restore the entire
data set.

Assure MIMIX for AIX enables you to create and use snapshots for production
restores and snapshot-based backups to media such as tape. You can also create a
snapshot when you want to use a copy of the data on the recovery server. Having a
snapshot—a read or write copy of the data—on the recovery server enables you to
investigate and use the data without affecting the operation of the production
server. For example, you can:

• Perform data mining without affecting performance on the production server.

• Repair individual objects such as files, tables, and records on the production
server without stopping the application or replacing all of the application files.

• Test whether the snapshot is the correct one to use for rolling back the data on
the production server.

Assure MIMIX for AIX User Guide v5.2.04.00 193

Using the Assure UI portal to create a snapshot
There are two ways to create a snapshot:

1. Do one of the following:

• Navigate to the Recovery page, and select Create Snapshot from the Actions
dropdown.

• Navigate to the Snapshot Details portlet, and select Create from the
dropdown to the right of Snapshot.

The Create Snapshot dialog displays.

194 Assure MIMIX for AIX User Guide v5.2.04.00

 2. In Location in rollback window, specify the type of information to use to locate
in the rollback window, where to take the snapshot:

• Point in Time—Specify the date and time, within the rollback window, from
where the snapshot will be created. This is displayed when Point in Time is
selected in the Location in rollback window field. This value is always
displayed in the dropdown. This only applies to the Date and time field.
• Container ID—Identify the container ID, within the rollback window, from
where the snapshot will be created. This is displayed when Container ID is
selected in the Location in rollback window field. This value is always
displayed in the dropdown. This only applies to the Container ID field.
Container IDs must be even numbers in the range specified in the rollback
window. When a change is made on the production server an even container
ID is created to represent that change. The even container ID is then applied
to the recovery server. When you create a snapshot, you use the even
container ID, that contains the change.
• Event Marker—Select one of the event markers, within the rollback window,
for where the snapshot will be created. Only one event marker can be
selected at a time.
• Most Recently Applied Container—Specify the most recent confirmed apply
(committed) container, within the rollback window, from where the snapshot
will be created. This option is used when all the data is synchronized and no
changes are being made. You can use this option to create a snapshot at that
point in which you know you have stable and consistent data.
3. Date and Time—Specify the date and time, within the rollback window, from
where the snapshot will be created. The default is the most recent date in the
rollback window. It is only displayed when Point in Time is selected.

4. Mount file systems—Specifies whether or not to mount file systems in the

snapshot. The default is Yes.

Assure MIMIX for AIX User Guide v5.2.04.00 195

 5. Check file system consistency—Specify whether or not to check the
consistency of the file system after mounting it. This can only be specified if
Yes is specified for mount file systems. The default is No. You can use the fsck
command to check and interactively repair inconsistent file systems.

6. Send partial container—Specifies whether or not to send a partial container

before taking the snapshot. The default is Yes.

7. Click OK.

Using the Assure UI portal to increase the snapshot buffer size

Use the Increase Snapshot Buffer Size dialog to temporarily increase the snapshot
buffer size. To do so, specify the amount of additional space and the volume group
for the temporary logical volume. Larger snapshot buffers allow snapshots to be
used for longer periods of time. When the snapshot buffer is increased, a temporary
logical volume is added. The logical volume is removed when the snapshot is
deleted.

To access the Increase Snapshot Buffer Size dialog, navigate to the Snapshot Details
portlet, and select Increase Size from the dropdown to the right of Snapshot.

IMPORTANT
The snapshot buffers can be increased before or after a snapshot is created.
If the snapshot buffer has reached 100% the Increase Size option will not
be available.

The Increase Snapshot Buffer Size dialog displays.

196 Assure MIMIX for AIX User Guide v5.2.04.00

 IMPORTANT
The Increase Size option can be executed a maximum of 64 times to add
additional space on different volume groups.

The Increase Snapshot Buffer Size dialog contains the following fields:

Field Description

Instance Identifies the user-defined name of the instance with which

the portlet interacts. An Assure MIMIX for AIX instance is
configured within the Assure UI portal to represent the set
of nodes with replication groups you want to manage.

Replication Identifies the servers and logical volumes that are being .
group Replication occurs from the production server to the
recovery server.

Server Identifies the name of the server where additional

temporary snapshot buffer space will be added.

Current size Identifies the configured snapshot buffer space for this
server. Integers are in MB units. The displayed value is
from the configuration.

Volume group Displays a list of volume groups to insert the temporary

logical volume.

Additional Identifies the amount of additional temporary space to add

temporary space to the snapshot buffer. Integers are in MB. The range is
shown to the right of the input field. The size you enter must
be a multiple of the physical partition size.

Range Identifies the range of values allowed for the Additional

temporary space field. The minimum and maximum values
will change based on which volume group is selected in the
Volume group drop down. Valid values range from the size
of 1 physical partition to the number of available free
physical partitions × the partition size

You can also use the command line to increase the snapshot buffer size. For infor-
mation, refer to “rn_temp_journal” on page 312.

Using the command line to create a snapshot

You can use the command line to create a snapshot based on the current redo log, a
specific date and time, event mark, or a specific LFCID. For detailed command line
information, refer to Chapter 10, “CLI Assure MIMIX DR for AIX Commands” on
page 309.

This section contains the following:

Assure MIMIX for AIX User Guide v5.2.04.00 197

 • “Creating snapshots based on the current redo log” on page 198

• “Creating snapshots based on a specific date and time” on page 199

• “Creating a snapshot based on a specific event mark” on page 202

Creating snapshots based on the current redo log

You can create a snapshot based on the current redo log. You can use this snapshot
for data mining and object repair on the production server.

1. On the recovery server, make sure all snapshot file systems are unmounted
before trying to release the snapshot.
rtumnt -C <Context ID>

2. Make sure no snapshots already exist on the recovery server.

scrt_ra -C <Context ID> -W

3. On the recovery server, enter the following command to create a snapshot based
on the current redo log:
scrt_ra -C <Context ID> -X

You should see output similar to the following:

Making SNAP /dev/rsnc1lif_bk_1, 66.306
Making SNAP /dev/rsnc1lif_bk_2, 66.310
Making SNAP /dev/rsnc1lif_bk_3, 66.314
Making SNAP /dev/rsnc1dbmf_bk_1, 66.318
Making SNAP /dev/rsntestlv, 66.450
Making SNAP /dev/rsnrtlog, 66.454
Making SNAP /dev/rtestlv, 66.448
Making SNAP /dev/rrtlog, 66.452
Snap Devs (read only, raw) Minor rj wj Snap level Vdev
level Vdevs (read/write, block)
------------------------------ ----- -- -- --------------
/dev/rsnc1lif_bk_1 304 ON -- 10
0 N/A
/dev/rsnc1lif_bk_2 308 ON -- 10
0 N/A
/dev/rsnc1lif_bk_3 312 ON -- 10
0 N/A
/dev/rsnc1dbmf_bk_1 316 ON -- 10
0 N/A
/dev/rsntestlv 448 ON ON 10
10 /dev/testlv
/dev/rsnrtlog 452 ON ON 10
10 /dev/rtlog

4. Mount the volumes on the recovery server. Enter the following command:

198 Assure MIMIX for AIX User Guide v5.2.04.00

 rtmnt -C <Context ID>

You should see output similar to the following:

Determining Filesystems to mount...
fsck -fp -y /dev/rtestlv
log redo processing for /dev/rtestlv
syncpt record at 7028
end of log 7028
syncpt record at 7028
syncpt address 7028
number of log records = 1
number of do blocks = 0
number of nodo blocks = 0
/dev/rtestlv (/test): ** Unmounted cleanly - Check suppressed
Mounting /test...

Creating snapshots based on a specific date and time

In this section you:

• Verify that the DATEMSK environment variable is defined

• Establish the date format for the DATEMSK environment variable

• Create snapshots based on a specific date and time

Verify that the DATEMSK environment variable is defined

Before you can create a snapshot you must establish the date format for the
DATEMSK environment variable that is used by the recovery server.

To verify that the DATEMSK environment variable is defined:

1. Type, echo $DATEMSK

• If no value is returned, the DATEMSK environment variable is undefined.
Proceed to “Establish the date format for the DATEMSK environment
variable” on page 199.
• If, for example, /tmp/mdm, is returned, the date format for DATEMSK
environment is defined. To view the contents of /tmp/mdm, type: cat
/tmp/mdm.

Establish the date format for the DATEMSK environment variable

To specify a date format:

Assure MIMIX for AIX User Guide v5.2.04.00 199

 1. Create a file that contains the date format for the DATEMSK environment
variable. In this example, create /tmp/mdm.

NOTE
The DATEMSK environment variable must be set to the full-path of a file
that contains the date format template.

2. Enter the following:

export DATEMSK=/tmp/mdm

The following shows two examples based on the different date formats.

If the content of /tmp/mdm Then the date format for DATEMSK is...
is...

%m/%d/%y %H:%M:%S scrt_ra -C310 -D "05/05/18 16:15:00"

%y.%m.%d %H%M%S scrt_ra -C310 -D "09.05.18 161500"

where:

• %m–Month
• %d–Day
• %y–Year
• %H–Hour
• %M–Minute
• %S–Second

IMPORTANT
The date format must be specified exactly as it is in the DATEMSK
environment variable. For example, if you do not specify seconds (%S) in
DATEMSK, you cannot specify it in the command.

Create snapshots based on a specific date and time

You can create a snapshot based on a time in the past. You can use this snapshot for
data mining and object repair on the production server.

To create a snapshot:

1. On the recovery server, make sure all snapshot file systems are unmounted
before trying to release the snapshot.
rtumnt -C <Context ID>

200 Assure MIMIX for AIX User Guide v5.2.04.00

 2. Make sure that a snapshot does not already exist on the recovery server.
scrt_ra -C <Context ID> -W

3. On the recovery server, enter the following command to create a snapshot based
on a specific date and time.
scrt_ra -C <Context ID> -D date

The date format depends on the DATEMSK environment variable that is

used by the recovery server.

If you enter 06/15/18 09:33:40 as the date and 34 for the Context ID, the
output is similar to the following:
scrt_ra -C34 -D "06/15/18 09:33:40"
You have requested a virtual incremental LFC restore to
time (1529055220) Fri Jun 15 09:33:40 2018
c(ontinue) or a(bort)? c
Making SNAP /dev/rsnc1lif_bk_1, 66.306
Making SNAP /dev/rsnc1lif_bk_2, 66.310
Making SNAP /dev/rsnc1lif_bk_3, 66.314
Making SNAP /dev/rsnc1dbmf_bk_1, 66.318
Making SNAP /dev/rsntestlv, 66.450
Making SNAP /dev/rsnrtlog, 66.454
Making SNAP /dev/rtestlv, 66.448
Making SNAP /dev/rrtlog, 66.452
Trying to match LFC to time: 1529055220
Found time 1159536820 in-between LFC #12 and LFC #14
Fetching LFC #17
Applying LFC #17
Fetching LFC #15
Applying LFC #15
Fetching LFC #13
Applying LFC #13
Fetching LFC #14
Applying LFC #14
The BackingStore Vdevs are at level 12+. ABA is at level 18.

4. Mount the volumes on the recovery server:

rtmnt -C <Context ID>

You will see output similar to the following:

Verifying Operating Context ID.
Determining role of this system in the Context.
Determining Filesystems to mount...
Mounting /pfs00...
Replaying log for /dev/esplv00.
Mounting /pfs01...
Mounting /pfs02...

Assure MIMIX for AIX User Guide v5.2.04.00 201

 Creating a snapshot based on a specific event mark
You can create a snapshot based on a specific event mark. You can use this snapshot
for data mining and object repair on the production server.

Use the scrt_ra command to display the available event mark rollback window.
scrt_ra -C <Context ID> -ve
Available event marks for rollback:

-------------------------------------------------------------
Event Name Date/Time (Epoch Time) Description
---------- ---------------------- -----------

Event-2 Tue Jan 14 14:21:28 2014 (1389727288)

Event-1 Tue Jan 14 14:13:49 2014 (1389726829)

1. On the recovery server, ensure all snapshot file systems are unmounted before
trying to release the snapshot.
rtumnt -C <Context ID>

2. Ensure that no snapshots already exists on the recovery server.

scrt_ra -C <Context ID> -W

3. On the recovery server, create a snapshot based on a specific event mark. Use
the target seconds (Epoch Time) value from the "Available event marks for
rollback " output. The Event mark should precede the sequence of the current
redo log, but should not be so far in the past that it has been archived to media
such as tape.

Example:
scrt_ra -C <Context ID> -S<target seconds> which is (Epoch Time)

If the target seconds is 1529601179, then the output is similar to the following:
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_83, 62.6
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_82, 62.10
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_81, 62.14
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_80, 62.18
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_89, 62.22
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_88, 62.26
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_87, 62.30
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_86, 62.34
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_85, 62.38
Jun 21 17:12:59 Making SNAP /dev/rsnlvFS_C71_84, 62.42
Jun 21 17:12:59 Making SNAP /dev/rsnc71lif_bk_1, 62.46
Jun 21 17:12:59 Making SNAP /dev/rsnc71lif_bk_2, 62.50
Jun 21 17:12:59 Making SNAP /dev/rsnc71lif_bk_3, 62.54
Jun 21 17:12:59 Making SNAP /dev/rsnc71dbmf_bk_1, 62.58
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_83, 62.4
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_82, 62.8

202 Assure MIMIX for AIX User Guide v5.2.04.00

 Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_81, 62.12
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_80, 62.16
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_89, 62.20
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_88, 62.24
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_87, 62.28
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_86, 62.32
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_85, 62.36
Jun 21 17:12:59 Making SNAP /dev/rlvFS_C71_84, 62.40
Jun 21 17:12:59 Trying to match LFC to time: 1529601179
Jun 21 17:12:59 Found time 1529601179 in-between LFC #2270
and LFC #2272
Jun 21 17:12:59 Fetching LFC #2271
Jun 21 17:12:59
Jun 21 17:12:59 Applying LFC #2271
Jun 21 17:12:59 Fetching LFC #2272
Jun 21 17:12:59
Jun 21 17:12:59 Applying LFC #2272
Jun 21 17:12:59 The BackingStore Vdevs are at level 2270+. ABA is
at level 2272

4. Mount the volumes on the recovery server.

rtmnt -C <Context ID> -f

You should see output similar to the following:

Determining Filesystems to mount...
Mounting /FS_C71_80...
Replaying log for /dev/lvFS_C71_80.
Mounting /FS_C71_81...
Replaying log for /dev/lvFS_C71_81.

Creating a snapshot based on a specific LFCID

You can create a snapshot based on a specific LFCID. You can use this snapshot for
data mining and object repair on the production server.

1. On the recovery server, make sure all snapshot file systems are unmounted
before trying to release the snapshot.
rtumnt -C <Context ID>

2. Make sure that no snapshot already exists on the recovery server.

scrt_ra -C <Context ID> -W

3. On the recovery server, create a snapshot based on a LFCID. The LFCID should
precede the sequence of the current redo log, but should not be so far in the past
that it has been archived to media such as tape.
scrt_ra -C <Context ID> -t <LFCID>

Assure MIMIX for AIX User Guide v5.2.04.00 203

 If the LFCID is 30, then the output is similar to the following:
Making SNAP /dev/vx/rdsk/rootdg/snvol2, 215.6
Making SNAP /dev/vx/rdsk/rootdg/snvol1, 215.10
Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_1, 215.14
Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_2, 215.18
Making SNAP /dev/vx/rdsk/rootdg/snc34lif_bk_3, 215.22
Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_1, 215.26
Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_2, 215.30
Making SNAP /dev/vx/rdsk/rootdg/snc34dbmf_bk_3, 215.34
Making SNAP /dev/vx/rdsk/rootdg/vol2, 215.4
Making SNAP /dev/vx/rdsk/rootdg/vol1, 215.8
Fetching LFC #33
Applying LFC #33
Fetching LFC #31
Applying LFC #31
The BackingStore Vdevs are at level 30. ABA is at level 34.

4. Mount the volumes on the recovery server.

rtmnt -C <Context ID> -f

You should see output similar to the following:

log redo processing for /dev/rtestlv
syncpt record at 9028
end of log 9028
syncpt record at 9028
syncpt address 9028
number of log records = 1
number of do blocks = 0
number of nodo blocks = 0
/dev/rtestlv (/test): ** Unmounted cleanly - Check suppressed
Mounting /test...

For information on database repair and database resurrection, refer to Chapter 12,
“Working with Assure MIMIX for AIX Applications” on page 247.

204 Assure MIMIX for AIX User Guide v5.2.04.00

Administrative Tasks
11

This chapter describes Assure MIMIX for AIX administrative tasks:

• “Verify the configuration using the sccfgchk command” on page 206

• “Updating the Assure MIMIX for AIX configuration” on page 206

• “Verifying available free space” on page 206

• “Using the Assure UI portal to configure events and subscriptions” on

page 206

• “Using the Assure UI portal to extend logical volumes and file systems” on
page 211

• “Using the command line to extend an Assure MIMIX for AIX-protected file
system” on page 222

• “Increasing the snapshot journal space on the recovery server” on page 225

• “Removed Logical Volume corrective action” on page 226

• “Setting up JFS log isolation” on page 231

• “Removing a File system from an Assure MIMIX for AIX protected jfslog”
on page 232
• “Setting up error notification” on page 232

• “Sync While Active - full synchronization” on page 236

• “Sync While Active - checksum-based synchronization” on page 237

• “Verify that replica logical volumes are synchronized with logical volumes on
the production server” on page 239

• “Alternative method for performing initial synchronization” on page 240

• “Using IBM Power Systems Live Partition Mobility with Assure MIMIX for
AIX” on page 241

• “Using the rn_shutdown script” on page 244

Assure MIMIX for AIX User Guide v5.2.04.00 205

 • “Using the gc_shutdown.sh script to gracefully shutdown all configured
applications in an Assure MIMIX HA for AIX clustered environment” on
page 245

• “IOCTL call handling” on page 246

Verify the configuration using the sccfgchk command

Use the sccfgchk command to check a configuration before you start Assure
MIMIX for AIX. Execute the following command on each node after the
configuration has been initialized. For information on the command syntax, refer to
“sccfgchk” on page 342.
sccfgchk -C <Context ID>

Updating the Assure MIMIX for AIX configuration

If you update the Assure MIMIX for AIX configuration you must stop Assure
MIMIX for AIX processes and unload the Assure MIMIX for AIX drivers on the
production site. This means that you must also stop the production application and
close and unmount the production data.

After you install Assure MIMIX for AIX, the Assure UI server, and the portal
application, you can use the Replication Group wizard or the command line to
configure new replication groups and change, rename, and delete existing ones.
Refer to “Configuring Replication Groups” on page 107.

Verifying available free space

Anytime a protected file system needs to be extended always check:

• The State map limit is not exceeded.

• On the production server, the protected logical volumes (LV)V “MAX LPs:” size
is not exceeded.

• On the recovery server, the replica LV (“pt” LV) “MAX LPs:” size is not
exceeded.

• On the protected and replica Volume Groups (VGs), there is enough free space.

Refer to “Using the Assure UI portal to extend logical volumes and file systems” on
page 211 or “Using the command line to extend an Assure MIMIX for
AIX-protected file system” on page 222 for additional information.

Using the Assure UI portal to configure events and subscriptions

The following events are available for Assure UI subscriptions that monitor Assure
MIMIX for AIX instances.

206 Assure MIMIX for AIX User Guide v5.2.04.00

 The New Subscription Defaults columns in Table 2 identify whether an event is
automatically added when a new subscription is created and its initial delay value. A
numeric delay value specified in an event overrides the delay value specified in a
subscription. New subscriptions default to a delay value of 0 minutes.

For additional information, refer to “Subscribing to instance events” in the refer to

the Assure Unified Interface User’s Guide packaged with Assure MIMIX for AIX.

Table 2. Events available for Assure MIMIX for AIX instances

Category Event / Description Severity New Subscription Defaults OID for SNMP Trap

Delay After Automati-

Event (min) cally Added

Cluster Clusters with action Action Use Yes .1.3.6.1.4.1.47240.1.3.0.3

required status Required subscription
value

Checks for clusters with an

overall status of action
required, such as network,
communication failure, or
status is unknown.

Cluster Clusters with stopped status Stopped Use No .1.3.6.1.4.1.47240.1.3.0.4

subscription
value

Checks for clusters with an

overall status of stopped.
Cluster will have stopped
status only when you stop
the cluster services.

Instance Cannot monitor instance. Action Use Yes .1.3.6.1.4.1.47240.1.3.0.5

required subscription
value

Checks for conditions that prevent the Assure UI portal from monitoring the
instance, such as not being able to connect to the instance or the portal
connection may not be configured correctly. There is a network error or the
configuration daemon is not running. Also, you may have specified the
incorrect password in the portal connection.

Instance Detect instance problems Action 0 and cannot Yes .1.3.6.1.4.1.47240.1.3.0.6

when the Assure UI portal required be changed
starts monitoring the
instance.

Event for instance problems when the Assure UI portal starts monitoring the
instance. Other subscribed events, if used, provide additional monitoring.

Assure MIMIX for AIX User Guide v5.2.04.00 207

Table 2. Events available for Assure MIMIX for AIX instances

Category Event / Description Severity New Subscription Defaults OID for SNMP Trap

Delay After Automati-

Event (min) cally Added

Logical Protected logical volumes Attention Use Yes .1.3.6.1.4.1.47240.1.3.0.11

Volume size on recovery server 1 or subscription
recovery server 2 does not value
match production server

Event for when the size of a protected logical volume on the recovery 1 or
recovery server 2 does not match the size on the production server.

Logical Logical volume removed. Action Use Yes .1.3.6.1.4.1.47240.1.3.0.19

Volume required subscription
value

Event for when a protected logical volume on the production server is

removed.

Node Licenses that are expired or Action 0 and cannot Yes .1.3.6.1.4.1.47240.1.3.0.8
not valid. required be changed

Checks for licenses that have either expired or not valid.

Node Licenses about to expire. Attention 0 and cannot Yes .1.3.6.1.4.1.47240.1.3.0.7

be changed

Checks for licenses that will expire in the next 30 days. Replication will be
stopped when the license expires and cannot be started until the license is
updated on the server. While the Assure UI server is up and running, this
event will be sent out once every 24 hours until the problem is corrected or
until the license expires. Users can replace the expiring license with a valid
license on the node. At the next license check interval, the warning status
will be cleared.

208 Assure MIMIX for AIX User Guide v5.2.04.00

Table 2. Events available for Assure MIMIX for AIX instances

Category Event / Description Severity New Subscription Defaults OID for SNMP Trap

Delay After Automati-

Event (min) cally Added

Node Maintenance about to Attention 0 and cannot Yes. This .1.3.6.1.4.1.47240.1.3.0.10

expire. be changed event will also
be added to all
existing
Assure
MIMIX for
AIX
subscriptions
automatically
when the
portal
application is
updated.
Event for when maintenance is about to expire. Current maintenance is
required for product upgrades, efixes, and product support. While the Assure
UI server is up and running, this event will be sent out once every 24 hours
until the problem is corrected or until the license expires. Users can replace
the expiring license with a valid license on the node. At the next license
check interval, the warning status will be cleared.

Node Maintenance expired. Attention 0 and cannot Yes.This .1.3.6.1.4.1.47240.1.3.0.9

be changed event will also
be added to all
existing
Assure
MIMIX for
AIX
subscriptions
automatically
when the
portal
application is
updated.

Event for when maintenance is expired. Current maintenance is required for

product upgrades, efixes, and product support.While the Assure UI server is
up and running, this event will be sent out once every 24 hours until the
problem is corrected. Users can replace the expired license with a valid
license on the node. At the next license check interval, the warning status
will be cleared.

Assure MIMIX for AIX User Guide v5.2.04.00 209

Table 2. Events available for Assure MIMIX for AIX instances

Category Event / Description Severity New Subscription Defaults OID for SNMP Trap

Delay After Automati-

Event (min) cally Added

Node Server IP address changed. Action Use Yes. This .1.3.6.1.4.1.47240.1.3.0.18

required subscription event will also
value be added to all
existing
Assure
MIMIX for
AIX
subscriptions
automatically
when the
portal
application is
updated.
Event for when the network IP address of the server does not match the
configured IP address.

Node Replication groups with Stopped Use No .1.3.6.1.4.1.47240.1.3.0.16

stopped or partially stopped subscription
status. value

Checks for replication groups with an overall status of stopped or partially

stopped.

Procedure Procedures with action Action Use Yes .1.3.6.1.4.1.47240.1.3.0.12

required status. required subscription
value

Checks for procedures with a status of action required, such as a step has
failed.

Procedure Procedures with stopped Stopped 5 No .1.3.6.1.4.1.47240.1.3.0.13

status.

Checks for procedures with a status of stopped and waiting for the next step
to be started.

Replication Replication groups with Action Use Yes .1.3.6.1.4.1.47240.1.3.0.14

Group action required status required subscription
value

Checks for replication groups with an overall status of action required, such
as snapshot buffer is full, synchronization did not complete, production
server rollback failed, or status is unknown.

210 Assure MIMIX for AIX User Guide v5.2.04.00

Table 2. Events available for Assure MIMIX for AIX instances

Category Event / Description Severity New Subscription Defaults OID for SNMP Trap

Delay After Automati-

Event (min) cally Added

Replication Applications not being Attention Use Yes 1.3.6.1.4.1.47240.1.3.0.1

Group managed. subscription
value

Checks for applications that are not being managed by the cluster. In the
Clusters portlet on the Summary page use the Manage Applications action to
enable cluster management of the application.

Replication Configuration Action Use Yes .1.3.6.1.4.1.47240.1.3.0.15

Group initializations with action required subscription
required status value

Checks for replication group configuration initialization with a status of

action required. For example, a step during the initial configuration of a
replication group or reconfiguration of a replication group failed.
Replication Snapshot buffer thresholds Attention Use Yes .1.3.6.1.4.1.47240.1.3.0.17
Group exceeded. subscription
value

Checks for replication backlog thresholds that have been exceeded.

Replication Replication backlog Attention 5 Yes .1.3.6.1.4.1.47240.1.3.0.02

Group threshold exceeded.

Checks for snapshot buffer thresholds that have been exceeded.

Using the Assure UI portal to extend logical volumes and file

systems
This section describes the following topics:

• Using the Extend Logical Volume Size Wizard. See “Using the Extend Logical
Volume Size wizard” on page 211.

• Using the Extend File System Size Wizard. See “Using the Extend File System
Size wizard” on page 218.

Using the Extend Logical Volume Size wizard

Extending a logical volume increases its size on each server in the replication group.
Configuration for the replication group may need to be updated to support the new
size.

To extend a logical volume:

Assure MIMIX for AIX User Guide v5.2.04.00 211

 1. Navigate to the Logical Volumes portlet.

2. Select a logical volume, and click Extend from the Actions dropdown.

The Extend Logical Volume wizard displays:

The Logical Volume Size panel contains the following fields:

212 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Extend Logical Title of the panel.

Volume
NOTE
If the logical volume has a mount point, then the
title will be Extend File System. See “Using the
Extend File System Size wizard” on page 218.

Logical Volume The current step in the Extend Logical Volume wizard.
Size

Logical Volume Size: The title of the panel.

Logical Volume Name of the logical volume. This can be any logical volume
in the replication group.

Type Type of logical volume. Examples are raw, jfs, jfs2, and
jfs2log.

Current size The current size of the logical volume in MB.

New size The new size of the logical volume in MB of the logical
volume. The size must be greater than the current size and
not greater than the maximum size.

Maximum size If a size is chosen that is greater than this value, then
without replication must be stopped and the configuration update
configuration Values are specified as integers
update

Additional Server Details

Server Host name of the servers that are part of this replication
group.

Recovery 1 Displays first recovery server information. If only one

recovery server has been configured, then this column label
is Recovery.

Recovery 2 Displays second server 2 information. If a second recovery

server has not been configured, then this column is hidden.
Only displayed if a second recovery server is configured.

Volume group Name of the volume group on the production server and the
volume group for the replica on the recovery server for the
logical volume.

Physical The total number of physical partitions in the volume group.

partitions

Free The number of physical partitions available to this logical

volume from the volume group.

Used The number of used physical partitions in the volume group.

Assure MIMIX for AIX User Guide v5.2.04.00 213

 Field Description

Partition size Physical partition size in megabytes (MB).

Logical volume Size in gigabytes (GB) of the logical volume.

size

Maximum size The maximum size that the logical volume can be grown.

Physical The total number of physical partitions in the logical

partitions volume.

3. Click Next.

The second and final panel of the Extend Logical Volume wizard panel
displays.

4. Click Finish.

The logical volume will be extended, replication will be stopped, and the
configuration will be updated.

The Extend Logical Volume panel contains the following fields:

214 Assure MIMIX for AIX User Guide v5.2.04.00

 Field Description

Extend Logical Title of the panel.

Volume
NOTE
If the logical volume has a mount point, then the
title will be Extend File System. See “Using the
Extend File System Size wizard” on page 218.

Extend Logical The current step in the Extend Logical Volume wizard.
Volume

Extend Logical Volume: Title of the panel.

Instance Instance for which information is being displayed.

Replication Displays the name of the replication group for which

group: information is being displayed. This also includes the
production and recovery servers to fully qualify which
replication group.

Cluster Displays the name of the cluster that this replication group
belongs. Dash (-) if none.

Logical volume Name of the logical volume.

Current logical The current size of the logical volume or file system.
volume size

New logical The new size of the file system or logical volume that was
volume size specified on the previous panel.

Steps run to extend a logical volume

The table below shows the order of the steps and commands that are run to extend a
logical volume:
Order Step Command When displayed

1. Increase the maximum chlv -x <new LPs> <LV> If the maximum logical
number of logical partitions value for the
partitions on S. (S is file system or logical
production server, volume will not support
recovery server, recovery the new size.
server 1, or recovery
server 2)

Assure MIMIX for AIX User Guide v5.2.04.00 215

 Order Step Command When displayed

2. Extend the logical extendlv <LV name> <LP(s)> Always

volume on the production
server

3. Extend the logical /usr/scrt/bin/extend_replica_l Always

volume on recovery v -C <Context ID> -L <PVS LV>
servers (Operates on all
recovery servers)

Steps run when a configuration must be changed to increase the state map
and region size
The table below shows the order of the steps and commands that are run when a
configuration must be changed to increase the state map and region size. These steps
are only run as a result of the Extend Logical Volume wizard. Steps 1 through 4 are
run before the wizard is dismissed. The other steps will be displayed in the
Configuration Window.

Order Step Command When displayed

1. Increase the maximum chlv -x <new LPs> <LV> If the maximum logical
number of logical partitions value for the
partitions on S. (S is file system or logical
production server, volume will not support
recovery server, recovery the new size.
server 1, or recovery
server 2)

2. Unmount the file system rtumnt -C <Context ID> If there is a mount point.
on the production server.

3. Extend the logical extendlv <LV name> <LP(s)> If there is no mount point.
volume on the production
server

4. Extend the file system on chfs -a size=<new size>M <file If there is a mount point.
the production server system>

5. Stop replication on the rtstop -FSC <Context ID> Always

production server.

6. Stop replication on the rtstop -FC <Context ID> Always

recovery server.

7. Stop replication on the rtstop -FC <Context ID> If there is a recovery

recovery server 2. server 2 in this
configuration.

8. Save configuration. - Always

216 Assure MIMIX for AIX User Guide v5.2.04.00

Order Step Command When displayed

9. Delete logical volume scsetup -X Always

device special files on S. One message is displayed
(S is production server, for each server.
recovery server, recovery
server 1, or recovery
server 2)

10. Delete snapshot container scsetup -R -t jcontainer Replication container

logical volumes on S. (S logical volume(s)
is the recovery server, removed.
recovery server 1, or One message is displayed
recovery server 2) for each server.

11. Delete internal logical scsetup -R -t smbitmap Always

volumes. One message is displayed
for each server.

12. Delete snapshot logical scsetup -R -t pool One message is displayed

volumes on S. (S is the for each server.
recovery server, recovery
server 1, or recovery
server 2)

13. Copy configuration to S. sccfgd_putcfg Always

(S is production server, One message is displayed
recovery server, recovery for each server.
server 1, or recovery
server 2)

14. Create failover context rtdr setup If configuration has a

on S. (S is production failover server.
server, recovery server, One message is displayed
recovery server 1, or for each server.
recovery server 2)

15. Create containers and scsetup -M Always

logical volumes on
production server.

16. Set all logical volumes as scconfig -W Always

replicated.

17. Create containers and scsetup -M Always

logical volumes on S. (S One message is displayed
is the recovery server, for each server.
recovery server 1, or
recovery server 2)

18. Start replication on the rtstart -C <Context ID> If there is a recovery

recovery server 2. server 2 in this
configuration.

Assure MIMIX for AIX User Guide v5.2.04.00 217

 Order Step Command When displayed

19. Start replication on the rtstart -C <Context ID> Always

production server.

20. Start replication on the rtstart -C <Context ID> Always. If there are more
recovery server. than one recovery servers
configured, the label is:
Start replication on
recovery server 1.

21. Extend replica logical /usr/scrt/bin/extend_replica_l If there is no configured

volume on the recovery v -C <Context ID> -L <PVS LV> second recovery server.
server.

22. Extend replica logical /usr/scrt/bin/extend_replica_l If there are more than one
volume on the recovery v -C <Context ID> -L <PVS LV> recovery servers
servers. configured.

Using the Extend File System Size wizard

Extending a file system increases its size on each server in the replication group.
Configuration for the replication group may need to be updated to support the new
size. Specify a larger size for the file system and click Next.

To extend a file system:

1. Navigate to the Logical Volumes portlet.

2. Select a file system, and click Extend from the Actions dropdown.

The Extend File System wizard displays:

218 Assure MIMIX for AIX User Guide v5.2.04.00

 The File System Size panel contains the following fields:

Field Description

Extend File Title of the panel.

System

File System Size The current step in the Extend File System wizard.

File System Size: The title of the panel.

Logical Volume Name of the logical volume. This can be any logical volume
in the replication group.

Type Type of logical volume. Examples are raw, jfs, jfs2, and
jfs2log.

File System File system/mount point for the logical volume.

Possible values:
• Path names.
• Dash ( - ) if the logical volume does not have a mount
point.
Typically, around 20 characters but can be as long as 2048.
If the length exceeds 76, the text is truncated with an ellipsis
in the middle.

Current size The current size of the file system in MB.

New size The new size of the file system in MB. The size must be
greater than the current size and not greater than the
maximum size.

Assure MIMIX for AIX User Guide v5.2.04.00 219

 Field Description

Maximum size If a size is chosen that is greater than this value, then
without replication must be stopped and the configuration update
configuration Values are specified as integers.
update

Additional Server Details

Server Host name of the servers that are part of this replication
group.

Volume group Name of the volume group on the production server and the
volume group for the replica on the recovery servers for the
logical volume.

Physical The total number of physical partitions in the volume group.

partitions

Free The number of physical partitions available to this logical

volume from the volume group.

Used The number of used physical partitions in the volume group.

Partition size Physical partition size in megabytes (MB).

Logical volume Size in gigabytes (GB) of the logical volume.

size

Maximum size The maximum size that the logical volume can be grown.

Physical The total number of physical partitions in the logical

partitions volume.

3. Click Next.

The second and final panel of the Extend File System wizard panel displays.

220 Assure MIMIX for AIX User Guide v5.2.04.00

 4. Click Finish.

The file system will be extended, replication will be stopped, and the
configuration will be updated.

The Extend File System panel contains the following fields:

Field Description

Extend File Title of the panel.

System

Extend File The current step in the Extend File System wizard.
System

Extend File System: Title of the panel.

Instance Instance for which information is being displayed.

Replication Displays the name of the replication group for which

group: information is being displayed. This also includes the
production and recovery servers to fully qualify which
replication group.

Logical volume Name of the logical volume.

File system File system/mount point for the logical volume.

Possible values:
• Path names.
• Dash ( - ) if the logical volume does not have a mount
point.
Typically, around 20 characters but can be as long as 2048.
If the length exceeds 76, the text is truncated with an ellipsis
in the middle

Assure MIMIX for AIX User Guide v5.2.04.00 221

 Field Description

Current size The current size of the file system in MB.

New size The new size of file system in MB, that was specified on the
previous panel.

Steps run to extend a file system

The table below shows the order of the steps and commands that are run to extend a
file system:
Order Step Command When displayed

1. Increase the maximum chlv -x <new LPs> <LV> If the maximum logical
number of logical partitions value for the
partitions on S (S is file system or logical
production, recovery volume will not support
server, recovery server 1, the new size.
or recovery server 2)

2. Extend the file system on chfs -a size=<new size>M <file Always

the production server system>

3. Extend the filesystem on /usr/scrt/bin/extend_replica_l Always

recovery servers v -C <Context ID> -L <PVS LV>

Using the command line to extend an Assure MIMIX for

AIX-protected file system
NOTE
In versions prior to 5.2.01.00, the default state map size supported a file
system size of 1 TB. As of version 5.2.01.00, the default state map size has
been increased to support a file system size of 3.984375 TB (4177920
MB). The state map size will be changed during the upgrade install to
version 5.2.01.00.

A file system can only be extended to a size within the limits of the region size
(blocks). The default region size of 8192 blocks supports a max file system size of
3.984375 TB (4177920 MB).

The following table provides max file system sizes for several combinations of
Region Size in blocks and SMBitmap size in bytes. The SMBitmap size is set to
131072 bytes and should never be changed.

222 Assure MIMIX for AIX User Guide v5.2.04.00

 Region Max File Max File
Region Size Size SMBitmap System Size System
(blocks) (MB) Size (bytes)
(MB) Size (TB)

8192 4 131072 4177920 3.984375

16384 8 131072 8355840 7.96875
32768 16 131072 16711680 15.9375
65536 32 131072 33423360 31.875

If a protected file system needs to be extended, verify the following.

• The RegionSize will not be exceeded.

The RegionSize for a protected LV can be checked using the command

/usr/scrt/bin/rtattr -C 1 -o smf_<LV> -a RegionSize

The unit of the region size is the number of blocks. Each block is 512 bytes. If
the RegionSize will be exceeded, refer to “Extending a protected file system
beyond the limit of the region (block) size” on page 224.

• The protected LV "MAX LPs:" will not be exceeded.

• The replica LV ("pt" LV) "MAX LPs:" will not be exceeded.

• There is enough free space in the protected and replica VGs.

Assure MIMIX for AIX-protected file systems can be extended when Assure
MIMIX for AIX is active using the smit chfs command. When the file system is
extended:

• On the production server, the replica ("pt" LV) is automatically extended when
data is written to the expanded area.

NOTE
To manually extend the replica (“pt” LV), use the extend_replica_lv
command to force the expansion of a Replica LV (Logical Volume):

extend_replica_lv -C <Context ID> -L <PVS LV>

• On the recovery server, the write journal associated with the file system is not
extended.

Assure MIMIX for AIX User Guide v5.2.04.00 223

 Extending a protected file system beyond the limit of the
region (block) size
To extend a protected file system beyond the max file system size supported by the
region size in blocks, the logical volume region size must be increased. See the
Region Size (blocks) column in the table above.

1. On the production server, stop applications that are using the Assure MIMIX for
AIX protected logical volumes.

2. On the recovery server, stop applications that are using logical volumes from an
active snapshot.

3. On the production server, use rtstop to unmount protected file systems, transfer
any current LFC data to the recovery server and unload the Assure MIMIX for
AIX Production Server Drivers.
/usr/scrt/bin/rtstop -FSC <Context ID>

NOTE
If you cannot unmount file systems, specify the fuser -c command to
locate the processes that are holding the file system(s) open.

4. On the recovery server, use rtstop to unmount any snapshot file systems and
unload the Assure MIMIX for AIX recovery server drivers.
/usr/scrt/bin/rtstop -FC <Context ID>

NOTE
If you cannot unmount file systems, specify the fuser -c command to
locate the processes that are holding the file system(s) open.

5. On the production and recovery servers, use rtattr to change the region size. See
the Region Size (blocks) column in the table above.
rtattr -C <Context ID> -o smf_<LV> -a Size -v <new size>

6. On the production and recovery servers, use scsetup to delete device special
files from /dev.
scsetup -XC <Context ID>

7. On the production and recovery servers, use scsetup to remove configured

Assure MIMIX for AIX LV's:
scsetup -RC <Context ID>

8. On the production and recovery servers, use sccfgd_delcfg to delete the

Failover Context ID if one was configured.

224 Assure MIMIX for AIX User Guide v5.2.04.00

 sccfgd_delcfg <Failover Context ID>

9. On the production and recovery servers, use scsetup to create new configured
logical volumes.
scsetup -MC <Context ID>

10. On the production and recovery servers, use rtdr to create a failover context if
one was configured.
rtdr -C <Primary Context ID> -F <Failover Context ID> setup

11. On the production server, use scconfig to wipe the state maps clean (0.000%
dirty).
scconfig -WC <Context ID>

12. On the Production and Recovery Servers, use rtstart to start Assure MIMIX for
AIX.
rtstart -C <Context ID>

13. On the production server, use “smit chfs” command to extend the file system.

Increasing the snapshot journal space on the recovery server

The snapshot journal space can be increased on the recovery server without
impacting the production environment. To increase the Snapshot Journal space on
the recovery server:

1. Stop Assure MIMIX for AIX on the recovery server.

2. Unmount any snapshot file systems.

/usr/scrt/bin/rtumnt -C <Context ID>

3. Release a snapshot if it exists.

/usr/scrt/bin/scrt_ra -C <Context ID> -W

4. Stop Assure MIMIX for AIX.

/usr/scrt/bin/rtstop -C <Context ID> -Fk

5. Use rtattr to increase the size of an existing snapshot journal volume.

NOTE
Any snapshot journal can be increased in size since all snapshot volumes
are available for use during snapshot creation/use.

6. Determine the name of the snapshot journal to increase.

Assure MIMIX for AIX User Guide v5.2.04.00 225

 7. Use the following command to find the snapshot journal volume sizes:
/usr/scrt/bin/rtattr -C <Context ID> -t
SCRT/containers/WJournal -a Size

The ObjectName of a snapshot volume that you want to increase.

8. Select one of the snapshot journals and increase the size of the volume.
/usr/scrt/bin/rtattr -C <Context ID> -o <ObjectName> -a Size
-v <new size value in bytes>

9. Find the logical volume name for the snapshot journal.

rtattr -C <Context ID> -o <ObjectName from step 8 on page 226>
-t SCRT/containers/WJournal -a FileName

10. Remove the existing snapshot journal volume that you want to increase
rmlv -f <ObjectAttributeValue from step 9 on page 226 minus
the /dev/r prefix>

11. Create the new snapshot journal volume.

/usr/scrt/bin/scsetup -C <Context ID> -M

12. Restart Assure MIMIX for AIX.

/usr/scrt/bin/rtstart -C <Context ID>

Removed Logical Volume corrective action

This is a critical error that needs to be addressed immediately. Assure MIMIX DR
for AIX can no longer function properly.

Starting in version 5.1.00.01, the Assure MIMIX for AIX portal application can
detect when a configured logical volume has been removed from the system while
the replication group is active. When this condition is detected, all actions to stop
the replication group from the Assure UI portal will be disabled, including the
planned failover and failback procedures.

IMPORTANT
Do not attempt to stop the replication group from the command line;
unloading the drivers will fail and you will not be able to restart the
replication group. If the production server is rebooted you will not be able
to restart the replication group.
Contact Support if you need assistance with these instructions.

226 Assure MIMIX for AIX User Guide v5.2.04.00

 If the replication group is not configured in a cluster:
Perform the following steps to recreate the jfs or jfs2 logical volume and associated
filesystem or logical volume with no associated file system that was removed from
the system:

Example: logical volume “lvFS_C18_10” and associated filesystem

“/FS_C18_10” were removed from the system while the replication group is
active.

1. On the production server, stop all applications associated with the replication
group.
2. On the production server, remove the device entries in the /dev/ directory for
the logical volume(s) that was removed from the system. Substitute the
example lv names with the actual lv names.

Example: rm /dev/ lvFS_C18_10 and rm /dev/rlvFS_C18_10

3. On the production server, remake the jfs or jfs2 logical volume(s) and
associated filesystem(s) or logical volume(s) with no associated file system
that was removed from the system.

IMPORTANT
The Logical Volume size, type and location must match the original size,
type and location it had before it was removed from the system, and the
filesystem must be recreated on the original volume group and mount
point it had before it was removed from the system.

4. On the production server, stop replication, from the command line..

IMPORTANT
Do not use the “S” option in the stop command.

Example: rtstop -FC<Context ID>

5. On the recovery server, stop replication, from the command line.

Example: rtstop -FC<Context ID>

6. On the production server, remove the jfs or jfs2 logical volume and
associated filesystem or logical volume with no associated file system that
was recreated in step 3 on page 227.
7. From the Assure UI portal, use the Configuration Wizard to remove the
logical volume(s) that were removed in step 6 on page 227 from the
replication group's configuration.
a. Click Configuration in the Replication Groups portlet to launch the
Configuration Wizard.

Assure MIMIX for AIX User Guide v5.2.04.00 227

 b. Click Change Replication for the replication group being changed.
c. Navigate to the Logical Volumes dialog. If the logical volume being
removed has an associated filesystem that uses a JFS outline log,
select all filesystems that use the same outline log and the outline log.
d. Click Remove.
e. Click OK to remove the selected entries from the configuration.
If any of the filesystems that were selected to be removed from the
configuration because they use the same outline log, still require protection,
add them to the configuration.

a. Click Add.
b. Select the Volume group for replicated data from the Select dropdown
list. Select the same volume group that originally contained the
replicated data.
c. Select only the removed logical volume(s) and the JFS outline log that
need to be protected.
d. Click OK, the logical volumes are added to the list of logical volumes
to be protected.
e. Click Next and navigate to the Summary panel.
f. Click Finish to remake the configuration.
8. From the Assure UI portal, start the replication group and verify the
replication group is active before starting your application(s).

If the replication group is configured in a cluster:

Perform the following steps to recreate the removed jfs or jfs2 logical volume and
associated filesystem or raw logical volume with no associated file system.

1. Stop the cluster from managing the application associated with the
replication group.
a. From the Assure UI portal, click on the Clusters tab.
b. Click on the Select dropdown in the Clusters portlet.
c. Click Manage Applications.
d. In the Manage Application dialog click the No radio button then click
OK.
2. On the production server, stop all applications associated with the replication
group.
3. On the production server, remove the device entries in the /dev/ directory for
the logical volume(s) that was removed from the system. Substitute the
example lv names with the actual lv names.

Example: rm /dev/ lvFS_C18_10 and rm /dev/rlvFS_C18_10

228 Assure MIMIX for AIX User Guide v5.2.04.00

 4. On the production server, remake the jfs or jfs2 logical volume(s) and
associated filesystem(s) or logical volume(s) with no associated file system
that was removed from the system.

IMPORTANT
The logical volume size, type and location must match the original size,
type and location the logical volume had before it was removed from the
system. Additionally, the filesystem must be recreated on the original
volume group and mount point it had before it was removed from the
system.

5. On the production server stop replication, from the command line.

IMPORTANT
Do not use the “S” option in the stop command.

Example: rtstop –FC<Context ID>

6. On the recovery server, stop replication, from the command line.

Example: rtstop –FC<Context ID>

7. On the production server, remove the jfs or jfs2 logical volume and
associated filesystem or logical volume with no associated file system that
was recreated in step 4 on page 229.
8. From the Assure UI portal, use the Configuration Wizard to remove the
logical volume(s) that were removed in step 7 on page 229, from the
replication group’s configuration.
a. Click the Configuration action in the Replication Groups portlet to
launch the Configuration Wizard.
b. Click the Change Replication action button for the replication group
being changed.
c. Navigate to the Logical Volumes dialog. If the logical volume being
removed has an associated filesystem that uses a JFS outline log,
select all filesystems that use the outline log and the outline log.
d. Click the Remove action.
e. Click OK to remove the selected entries from the configuration.
If any of the filesystems that were selected to be removed from the
configuration because they use the same outline log, still require protection,
add them to the configuration.

a. Click the Add action.

Assure MIMIX for AIX User Guide v5.2.04.00 229

 b. Select the Volume group for replicated data from the “Select” action
drop down list. Select the same volume group that originally
contained the replicated data.
c. Select only the removed logical volume(s) that need to be protected
and JFS outline log.
d. Click OK, the logical volumes appear in the list of logical volumes to
be protected.
e. Click the Next action and navigate to the Summary panel.
f. Click the Finish button to remake the configuration.
9. From the Assure UI portal, start the replication group and verify the
replication group is active before you Manage your application(s).
10.Allow the cluster to manage the application associated with the replication
group.
a. From the Assure UI portal, click on the Clusters tab.
b. Click the Select action dropdown button in the Clusters portlet.
c. Click Manage Applications.
d. In the Manage Application dialog click the Yes radio button then click
OK.

230 Assure MIMIX for AIX User Guide v5.2.04.00

Setting up JFS log isolation
When selecting logical volumes with jfs or jfs2 file systems that have associated
outline logs, ensure that the outline logs are also protected by Assure MIMIX for
AIX. Do not select outline logs unless you select the corresponding file system for
protection.

The Add Logical Volumes dialog, (invoked from the Logical Volumes panel of the
New or Change Replication Group Configuration Wizard), checks to ensure that
unprotected file systems do not use the same jfs or jfs2 outline logs that a protected
file system uses.

For example, if there are 4 jfs2 logical volumes /lvfs1, /lvfs2, /lvfs3, /lvfs4 that use
the same jfs2log /dev/fsloglv00, and Assure MIMIX for AIX only protects /lvfs1,
you need to have separate jfs2logs for the protected and unprotected logical
volumes.

NOTE
When using inline logs with jfs2 file systems, there is no jfs2log isolation
requirement.

To maintain jfslog2 isolation:

1. Unmount the file system that you will assign to the new jfslog.
umount /fs1

2. Create a new logical volume with a type of jfslog.

mklv -t jfs2log -y <newjfslog> <vgname> 1 ; where <newjfslog>
is the name of the new jfslog and <vgname> is the volume
group where the jfslog is created

3. Format the new jfslog.

logform /dev/<newjfslog>

4. Respond yes to allow the jfslog to be formatted.

5. Assign the new jfslog to the file system.

chfs -a log=/dev/<newjfslog> /fs1

Assure MIMIX for AIX User Guide v5.2.04.00 231

Removing a File system from an Assure MIMIX for AIX
protected jfslog
When you decide to remove a file system from a PVS, this file system needs to use
a different jfslog from the Assure MIMIX for AIX protected jfslog. Follow the steps
below to associate the newly removed file system with a non-protected jfslog.

Assumption: The file system /jfslog is being removed from the Assure MIMIX for
AIX PVS. The Assure MIMIX for AIX protected file systems are unmounted, the
Assure MIMIX for AIX processes are stopped and the Assure MIMIX for AIX data
tap is unloaded.

1. If a jfslog exists in the volume group that is not currently part of the PVS, you
can assign that jfslog to the file system that is being removed from the PVS.
umount /jfslog

chfs -a log=/dev/<nonrtjfslog> /jfslog

where nonrtjfslog is a jfslog that exists in the volume group but is not part the
PVS.

2. If a jfslog does not exist in the volume group:

mklv -t jfslog -y< newjfslog> <vgname> 1

where <newjfslog> is the name of the jfslog that you are creating for the
non-protected file system to use.

3. Format the jfslog.

logform /dev/<newjfslog>

4. Assign the jfslog to the non-protected file system

chfs -a log=/dev/<newjfslog> /jfslog

Setting up error notification

Use the AIX Error Notification feature to notify the administrator via email or take
action when certain errors are recorded in the AIX error log.

The following example script /home/scrt/enm_1 can be used to record this

information in /tmp/enm_1.out and notify the administrator via email when certain
errors occur.
#!/bin/ksh
PROGNAME=${0##*/}
exec 1>> /tmp/${PROGNAME}.out
exec 2>&1
printf "error notify method\n"

232 Assure MIMIX for AIX User Guide v5.2.04.00

 errpt -Al ${1}
errpt -Al ${1} | mail -s Error root

To enable AIX Error Notification for one or more of the Assure MIMIX for AIX
errors, you must add a stanza to the errnotify ODM. When the error is logged, the
error notification daemon will call the notify method specified in the errnotify
ODM stanza. The errnotify ODM is located in the /etc/objrepos directory.
For example, the following errnotify stanzas are added to file /tmp/ern_1.add for
error labels SCRT_LFC_READ_ERROR, SCRT_LFC_WRITE_ERROR,
"SCRT_NETWORK_ERROR" and "SCRT_ABORT_ERROR.

errnotify:
en_name = "SCRT_LFC_READ_ERROR"
en_class = "S"
en_type = "PERM"
en_method = "/home/scrt/enm_1 $1"

errnotify:
en_name = "SCRT_LFC_WRITE_ERROR"
en_class = "S"
en_type = "PERM"
en_method = "/home/scrt/enm_1 $1"

errnotify:
en_name = "SCRT_NETWORK_ERROR"
en_class = "S"
en_type = "PERM"
en_method = "/home/scrt/enm_1 $1"

errnotify:
en_name = "SCRT_ABORT_ERROR"
en_class = "S"
en_type = "PERM"
en_method = "/home/scrt/enm_1 $1"

ODM commands
The errnotify stanzas are added to the errnotify ODM using the following command.
odmadd /tmp/ern_1

To list the errnotify stanzas added for Assure MIMIX for AIX errors do the
following command.
odmget -q"en_name LIKE SCRT_*" errnotify|more

To delete all the errnotify stanzas added for Assure MIMIX for AIX errors:
odmdelete -q"en_name LIKE SCRT_*" -o errnotify

Assure MIMIX for AIX User Guide v5.2.04.00 233

 To delete a particular stanza:
"SCRT_LFC_WRITE_ERROR" "errnotify" stanzas:
odmdelete -qen_name=SCRT_LFC_WRITE_ERROR -o errnotify

Error Notify Messages

Table 3 shows the Error Notify Messages that are written to the AIX error log.

Table 3: Error Notify Messages

Error Description
SCRT_AAGENT_ABORTED_ERROR: PERM S Archive Agent Aborted
Operation
SCRT_AAGENT_API_ERROR: PERM S Error conversing with Archive
Program
SCRT_ABORT_ERROR: PERM S Generic/Fatal RealTime Error
SCRT_ARCHIVEMGR_ERROR: PERM S Archive Manager Error
SCRT_BSFC_READ_ERROR: PERM S Read error from store
SCRT_BSFC_WRITE_ERROR: PERM S Write Error to store
SCRT_CONFIG_ERROR: PERM S Configuration Error
SCRT_CONFIG_UPDATE_ERROR: TEMP S Configuration update failure
SCRT_DBMFC_APPLY_ERROR: PERM S Logical error applying LFC to
DBMFC
SCRT_DBMFC_READ_ERROR: PERM S Reading from DevBlockMap
failed
SCRT_DBMFC_WRITE_ERROR: PERM S Writing to DevBlockMap failed
SCRT_DEVREAD_ERROR: PERM S Failure to read to required device
SCRT_DEVWRITE_ERROR: PERM S Failure to write to required device
SCRT_LFC_READ_ERROR: PERM S Read error on an LFC
SCRT_LFC_WRITE_ERROR: PERM S Write error on an LFC
SCRT_LIFC_FULL_ERROR: TEMP S LIFC is full
SCRT_LIFC_READ_ERROR: PERM S Read of LIFC failed
SCRT_LIFC_WRITE_ERROR: PERM S Write of Log Record to LIFC
failed
SCRT_LRFC_READ_ERROR: PERM S Read of LogRecord from LRFC
failed
SCRT_LRFC_WRITE_ERROR: PERM S Writing of LogRecord to LRFC
failed

234 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 3: Error Notify Messages
Error Description
SCRT_NETWORK_ERROR: PERM S Cannot connect to peer process
over network
SCRT_POOL_EMPTY: TEMP S Storage pool empty
SCRT_POOL_HWM: TEMP S Storage pool usage at/above high
water mark
SCRT_SCJ_COWREAD_ERROR: PERM S Copy-On-Write read failed
SCRT_SCJ_COWWRITE_ERROR: PERM S Journal Copy-On-Write write
failed
SCRT_SCJ_FULL_ERROR: PERM S Journal Copy-On-Write log is full
SCRT_SCLM_WANCHORCB_ERROR PERM S Log anchor write call back failed
SCRT_SCLM_WANCHOR_ERROR: PERM S Log anchor write failed
SCRT_SCSM_BMWRITE: PERM S Write to statemap bitmap device
failed
SCRT_SCSM_LOGWRITE: PERM S Write to statemap log device
failed
SCRT_SHAREDD_EXPORT_ERROR: PERM S Failure to export shared disk
SCRT_SHAREDD_IMPORT_ERROR PERM S Failure to import shared disk
SCRT_SMFC_READ_ERROR PERM S StateMap File Container Read
Error
SCRT_SMFC_WRITE_ERROR PERM S StateMap File Container Write
Error
SCRT_SM_ERROR PERM S StateMap creation error
SCRT_SNAP_OFF: PERM O Snapshots taken down
SCRT_SRC_ERROR PERM S System Resource Controller
Error

Assure MIMIX for AIX User Guide v5.2.04.00 235

Sync While Active - full synchronization
There are two ways that you can execute sync while active to perform a full
synchronization of the Production Volume Set (PVS) or one or more Logical
Volumes (LVs) in the PVS.

1. From the Assure UI portal, navigate to the Logical Volumes portlet:

• To synchronize specific logical volumes, select the logical volumes to

synchronize and click the Synchronize action, or select Synchronize from
the Action dropdown.
• To synchronize all logical volumes, select the check box to the left of the
Logical Volumes column, and click the Synchronize action.

NOTE
Synchronize actions are not available when a synchronize action is already
in progress or the replication group processes are not running.

2. From the command line:

• To synchronize all logical volumes in the replication group use the following
command:
scconfig -C<Context ID> -B
Keep in mind the following while scconfig -B is running:
– Do not cycle Assure MIMIX for AIX or the servers.
– Ensure that you do not lose your terminal session, use (nohup scconfig -B
&).

If the scconfig –C<Context ID> -B command was interrupted and the

command is re-executed, any logical volume in the replication group that is
partially synchronized, 0.000% synchronized or 100.000% synchronized
will be started from the beginning.

• To restart synchronization of all logical volumes in the replication group

from where the previous operation left off, use the following command:
scconfig –C<Context ID> -B -G (Restarts from where the previous
operation left off.)

The following conditions apply:

– Any logical volume in the replication group that is partially synchronized

will be restarted from where the previous operation left off.
– Any logical volume in the replication group that is 100.000%
synchronized will be not be restarted.

236 Assure MIMIX for AIX User Guide v5.2.04.00

 – Any logical volumes in the replication group that is 0.000% synchronized
will be started from the beginning.
• To synchronize one or more specific logical volumes in the replication
group, use the following command:
scconfig -C<Context ID> -B -L (name from sclist -ZC<Context
ID>) -L (name from sclist -ZC<Context ID>)

If this command was interrupted and the command is re-executed, any

specific logical volume that is partially synchronized, 0.000% synchronized
or 100.000% synchronized will be started from the beginning.

• To restart synchronization of one or more specific logical volumes in the

replication group from where the previous operation left off, use the
following command:
scconfig -C<Context ID> -B -G -L (name from sclist -ZC<Context
ID>) -L (name from sclist - ZC<Context ID>)

The following conditions apply:

– Any specific logical volume in the replication group that is partially

synchronized will be restarted from where the previous operation left off.
– Any specific logical volume in the replication group that is 100.000%
synchronized will be not be restarted.
– Any specific logical volumes in the replication group that is 0.000%
synchronized will be started from the beginning.

Sync While Active - checksum-based synchronization

The sync while active checksum-based synchronization performs a checksum by
region of the Production Volume Set (PVS) or one or more Logical Volumes (LVs)
in the PVS and the replica logical volumes on the recovery server(s) and only
synchronizes the region if the checksums do not match.

In release 5.2.01.00, this option is only available from the command line.

From the command line:

• To synchronize all logical volumes in the replication group, use the following
command:
scconfig -C<Context ID> -T

Keep in mind the following while scconfig -T is running:

• Do not cycle Assure MIMIX for AIX or the servers.

• Ensure that you do not lose your terminal session, use (nohup scconfig -T
&).

Assure MIMIX for AIX User Guide v5.2.04.00 237

 If the scconfig -C<Context ID> -T command was interrupted and the command
is re-executed, any logical volume in the replication group that is partially
synchronized, 0.000% synchronized or 100.000% synchronized will be started
from the beginning.

• To restart synchronization of all logical volumes in the replication group from

where the previous operation left off, use the following command:
scconfig -C<Context ID> -T -G

(Restarts from where the previous operation left off.)

The following conditions apply:

• Any logical volume in the replication group that is partially synchronized

will be restarted from where the previous operation left off.
• Any logical volume in the replication group that is 100.000% synchronized
will be not be restarted.
• Any logical volumes in the replication group that is 0.000% synchronized
will be started from the beginning.

• To synchronize one or more specific logical volumes in the replication group,

use the following command:
scconfig -C<Context ID> -T -L (name from sclist -ZC<Context
ID>) -L (name from sclist -ZC<Context ID>)

If this command was interrupted and the command is re-executed, any specific
logical volume that is partially synchronized, 0.000% synchronized or
100.000% synchronized will be started from the beginning.

• To restart synchronization of one or more specific logical volumes in the

replication group from where the previous operation left off, use the following
command:
scconfig -C<Context ID> -T -G -L (name from sclist -ZC<Context
ID>) -L (name from sclist - ZC<Context ID>)

The following conditions apply:

• Any specific logical volume in the replication group that is partially

synchronized will be restarted from where the previous operation left off.
• Any specific logical volume in the replication group that is 100.000%
synchronized will be not be restarted.
• Any specific logical volumes in the replication group that is 0.000%
synchronized will be started from the beginning.

238 Assure MIMIX for AIX User Guide v5.2.04.00

Verify that replica logical volumes are synchronized with logical
volumes on the production server
Use the Verify Logical Volume dialog to verify that the replica logical volumes on
the recovery server are synchronized with the selected logical volumes on the
production server. Before verifying, stop all applications that are using the selected
logical volumes.

To access the Verify Logical Volume dialog, select Verify from the toolbar on the
Logical Volumes portlet.

Refer to the Assure MIMIX for AIX online help for specific information for this
dialog.

Assure MIMIX for AIX User Guide v5.2.04.00 239

Alternative method for performing initial synchronization
To optimize the time to transfer the PVS data onto a remote recovery server at a
remote site:

NOTE
You can also use the -L option with the scconfig command for specific
logical volumes to mark the state map zero percent dirty.

1. On the production server:

– Stop any application(s)

– Stop Assure MIMIX for AIX and unload the drivers:
rtstop -FC <Context ID>

2. On the recovery server

– Stop any application(s) that are using a snapshot

– Unmount the file systems on a snapshot
rtumnt -C <Context ID>

– Release any snapshots

scrt_ra -WC <Context ID>

– Stop Assure MIMIX for AIX and unload the drivers.

rtstop -FC <Context ID>

3. Save the protected data on the production server to tape or disk. You must save
at the LV level in block sequence.

– Save to tape:
dd if=/dev/db2 of=/dev/rmt0 bs=1024

– Save to disk:
dd if=/dev/db2 of=/dev/db2bu bs=16m

4. Clean the state map on the production server.

scconfig -WC <Context ID>

5. Start Assure MIMIX for AIX on the production server.

rtstart -C <Context ID>

6. Restore the data from tape or disk to the Replica on the recovery server.

NOTE
The restore must be done to the pt LVs.

240 Assure MIMIX for AIX User Guide v5.2.04.00

 – Restore data from tape:
dd of=/dev/ptdb2 if=/dev/rmt0 bs=1024

– Restore data from disk:

dd of=/dev/ptdb2 if=/dev/db2bu bs=16m

7. Start Assure MIMIX for AIX on the recovery server. The changes made after
the save to tape or disk synchronize to the recovery server.
rtstart -C <Context ID>

Using IBM Power Systems Live Partition Mobility with Assure

MIMIX for AIX
This section contains:

• “Overview” on page 241

• “Automatically registering the es_migrate script” on page 241

• “Manually registering the es_migrate script” on page 242

• “Before you migrate a partition” on page 243

• “Migrating a partition” on page 243

Overview
Assure MIMIX for AIX supports Live Partition Mobility for partitions running AIX
5300-07 or later or AIX 6.1 or later or AIX 7.1 or later on POWER6 or POWER7
technology-based systems. Live Partition Mobility allows a partition that is
replicating with Assure MIMIX for AIX to be migrated to another system without
interrupting replication.

Automatically registering the es_migrate script

To support IBM Power Systems Live Partition Mobility, Assure MIMIX for AIX
must be Migration-aware.

To make Assure MIMIX for AIX Migration-aware, when you install Assure
MIMIX for AIX, the es_migrate script is automatically registered on systems
capable of Live Partition Mobility, with the Dynamic Logical Partition (DLPAR)
function of AIX.

Assure MIMIX for AIX User Guide v5.2.04.00 241

 IMPORTANT
The es_migrate script is registered at installation time if the partition is
capable of migration. In which case you do not have to register the
es_migrate script. You should initially verify if it is registered, if not,
proceed to register the es_migrate script.

Manually registering the es_migrate script

If you have installed Assure MIMIX for AIX when the partition was not
migration-capable, and then upgraded so the partition is migration-capable, you
must manually register the es_migrate script to make the node capable of Live
Partition Mobility.

To register the es_migrate script, execute the following command:

/usr/sbin/drmgr -f -i /usr/scrt/bin/es_migrate

The command output displays:

DR script file /usr/scrt/bin/es_migrate installed successfully

242 Assure MIMIX for AIX User Guide v5.2.04.00

 Before you migrate a partition
Before you migrate a partition, use the drmgr –l command to verify the existence of
the following stanza:
# /usr/sbin/drmgr -l

DR Install Root Directory: /usr/lib/dr/scripts

Syslog ID: DRMGR-

-------------------------------------------------------------------
/usr/lib/dr/scripts/all/es_migrate MIMIX DR for AIX Partition Migration Script
Vendor:Vision Solutions, Version:5.1.0.1, Date:2016.10.21
Script Timeout:10, Admin Override Timeout:0
Memory DR Percentage:100
Resources Supported:
Resource Name: pmig Resource Usage: Partition migration
-------------------------------------------------------------------

Migrating a partition
Each time you migrate a partition, if the Assure MIMIX for AIX license is valid,
Assure MIMIX for AIX will be licensed to run on the migrated partition for up to 30
consecutive days. When a partition is migrated back to the original server it was
migrated from, the license expiration date is returned to its original value.

IMPORTANT
When you migrate a partition back to the original server it was migrated
from, you may not get the partition ID the partition originally had. In this
case, the expiration date in the license file will be changed to expire in 30
days.

IMPORTANT
Assure MIMIX for AIX configuration changes are not allowed if a
partition has been migrated from its original server. To make configuration
changes, the partition must be migrated back to its original server.
Extending protected file systems is allowed while in the failover mode. In
addition, follow the steps in “Extending a protected file system beyond the
limit of the region (block) size” on page 224 if it is applicable due to
increase in the size.

Assure MIMIX for AIX User Guide v5.2.04.00 243

Using the rn_shutdown script
Use the rn_shutdown script to stop and unload the drivers for all Assure MIMIX for
AIX Context IDs on the system where the AIX shutdown command is executed.

Steps performed by the rn_shutdown script

The rn_shutdown script performs the following actions:

• Kills all processes associated with a mounted file system that is configured in an
Assure MIMIX for AIX Context ID.

• Kills all processes associated with a character device that is configured in an

Assure MIMIX for AIX Context ID.

• Stops Assure MIMIX for AIX and unloads the drivers.

If “rtstop” fails for a Context ID it will be marked failed and then continue to do
“rtstop” on any remaining Context IDs. After all the Context IDs are processed the
“exit” status will be set to “0”, or a value equal to the number of Context IDs that
were previously marked as failed. The reason for failure will be recorded in the
“/usr/scrt/log/rn_shutdown.out” file. A non “0” exit will abort the AIX shutdown.

To have “/usr/scrt/bin/rn_shutdown” execute when the AIX “shutdown” command

is executed, it must be called from “/etc/rc.shutdown.”

For example, add the following to /etc/rc.shutdown.

#!/bin/ksh
/usr/scrt/bin/rn_shutdown
if(($? != 0))
then
printf "ERROR: rn_shutdown failed aborting.\n"
exit 1
fi

IMPORTANT
To gracefully stop replication groups that are not configured in an Assure
MIMIX for AIX clustered environment, that are running in a production or
recovery role on the node where the AIX “shutdown” command is
executed, use the /usr/scrt/bin/rn_shutdown script in conjunction
with “/usr/EchoCluster/bin/AIX/gc_shutdown.sh.”

The /usr/EchoCluster/bin/AIX/gc_shutdown.sh script must precede

the /usr/scrt/bin/rn_shutdown script in /etc/rc.shutdown file.

244 Assure MIMIX for AIX User Guide v5.2.04.00

Using the gc_shutdown.sh script to gracefully shutdown all
configured applications in an Assure MIMIX HA for AIX
clustered environment
Use the gc_shutdown.sh script to gracefully shutdown all configured user
applications and associated Assure MIMIX DR for AIX replication groups on both
nodes configured in an Assure MIMIX for AIX clustered environment, and stop
cluster services on the node where the AIX shutdown command is executed. This
script creates a log file /usr/EchoCluster/log/gc_shutdown.sh.out.

The gc_shutdown.sh script uses the dynamically tunable parameter

APPLICATION_STOP_GRACETIME located in the file
/usr/EchoCluster/etc/node_config.properties. The parameter is set
with a default limit of 600000 milliseconds (10 minutes). If stopping any of your
applications exceed these limits, the AIX shutdown will be aborted and the
application stop process will continue until the application is completely stopped.

Steps performed by the gc_shutdown.sh script

The gc_shutdown.sh script performs the following actions:

• Stops all configured user applications protected in an Assure MIMIX for AIX
clustered environment on the node where the AIX “shutdown” command is
executed.

IMPORTANT
Each application must be configured with an application stop script.

• Stop all resources (such as, Service IP Address) if configured with the user’s
application on the node where the AIX “shutdown” command is executed.

• Assure MIMIX DR for AIX replication group associated with the user’s
application on both cluster nodes.

• Stops cluster services on the node where the AIX “shutdown” command is
executed.

To have “/usr/EchoCluster/bin/AIX/gc_shutdown.sh” execute when the AIX

“shutdown”command is executed, it must be called from “/etc/rc.shutdown.”
For example, add the following to /etc/rc.shutdown.
#!/bin/ksh
/usr/EchoCluster/bin/AIX/gc_shutdown.sh
if(($? != 0))
then
printf "ERROR: gc_shutdown.sh failed, aborting the shutdown
sequence.\n"

Assure MIMIX for AIX User Guide v5.2.04.00 245

 printf "INFO: See log file
/usr/EchoCluster/log/gc_shutdown.sh.out for details. \n"
exit 1
fi

IMPORTANT
To gracefully stop replication groups that are not configured in an Assure
MIMIX for AIX clustered environment, that are running in a production or
recovery role on the node where the AIX shutdown command is executed,
use the /usr/scrt/bin/rn_shutdown script in conjunction with
/usr/EchoCluster/bin/AIX/gc_shutdown.sh.

The /usr/EchoCluster/bin/AIX/gc_shutdown.sh script must precede

the /usr/scrt/bin/rn_shutdown script in /etc/rc.shutdown file.

IOCTL call handling

Your system may crash if kernel extensions are written which invoke fp_ioctlx() on
devices, and use addresses passed in from userspace.

With Assure MIMIX DR for AIX version 5.0 drivers loaded on AIX 6.1 nodes
without APAR IV50876 installed, or your AIX 7.1 nodes without APAR IV50842
installed, the AIX commands topas -V, fileplace and lvmstat will not function
correctly. Assure MIMIX DR for AIX will prevent a system crash by trapping the
FP_IOCTLs and returning ENOTSUP.

If your AIX 6.1 nodes have APAR IV50876 installed, or your AIX 7.1 nodes have
APAR IV50842 installed, Assure MIMIX DR for AIX version 5.0 will not trap the
FP_IOCTLs. The AIX commands topas -V, fileplace and lvmstat will function
correctly.

246 Assure MIMIX for AIX User Guide v5.2.04.00

Working with Assure MIMIX for
AIX Applications 12

This chapter describes working with Assure MIMIX for AIX applications.

This chapter contains:

• “Overview” on page 247

• “Database recovery operations scenarios” on page 247

– “Database resurrection concept” on page 248

– “Database repair concept” on page 248

• “Performing a volume restore” on page 249

• “Performing a production restore” on page 255

• “Using theAssure UI portal for a production restore” on page 256

• “Using the command line to perform a production restore” on page 259

Overview
You can apply the redo and undo logs from the recovery server to rollback
application data on the production server and restore the data to an earlier point in
time. When you rollback the application data the information is synchronized with
the replica on the recovery server similar to any other write action.

Database recovery operations scenarios

This section describes two database recovery scenarios that demonstrate how to
utilize Assure MIMIX for AIX's production and virtual restore capabilities. These
two recovery scenarios are database resurrection and database repair.

• Database resurrection is a restore from a database "crash and burn" scenario,

where the database could not come up.

• Database repair is a restore of a burning, but living database with corrupted

data.

Keep in mind that the majority of all database recovery operations require
database repairs that are typically performed by Database Administrators (DBAs).

Assure MIMIX for AIX User Guide v5.2.04.00 247

 Also, the remaining minority of recovery operations need database resurrections
that are done by IT administrators. In the burning repair scenario, for example,
Assure MIMIX for AIX makes the DBA's job more precise.

Database resurrection concept

To perform a database resurrection, you may use Assure MIMIX for AIX's
production restore operation to recover an image of the actual production database
to some point in the past directly on the production disk itself (not a snapshot image
of the data).

LAN
Recovery
Production Server
Server

Data tap
Data tap

Application Undo
Undo Replica
Data Storage Storage

Logs Logs

In the resurrection scenario, the database is crashed and will not be coming back up.
If you need to rollback to 55 seconds, you do not need to restore last day’s full
backup and replay a full week of database redo (roll forward) logs. In this case,
Assure MIMIX for AIX can rollback a totally crashed and burned database in a
matter of moments—many orders of magnitude faster.

Keep in mind that during a production restore, you do not need the database instance
up. In fact, the database cannot be up while Assure MIMIX for AIX rolls its image
around on disk. By definition, the database is down since it crashed. As a result, the
best and fastest way to restore your database is while it is still down. The Assure
MIMIX for AIX production restore operation provides this capability.

Database repair concept

To perform a database repair, you may use the Assure MIMIX for AIX's “virtual
restore” operation, recovering a snapshot image of the database to some point in the

248 Assure MIMIX for AIX User Guide v5.2.04.00

 past on the writable snapshot, and then a “pick and pull” operation to extract pieces
of data from that snapshot for reinsertion into the production database.

LAN
Recovery
Production Server
Server

Data tap Data tap

Snapshot

Log File Log File

Containers Containers
Application Replica
Data Storage Storage COW

In this repair scenario, only some pieces of data are corrupted but the production
database is still running. After you restore a historical, non-burning image of the
database on the snapshot, you can pull pieces out of it and put them back into the
live production database to repair the bad pieces of data. You can put out the fire
with information. Assure MIMIX for AIX restores automatically on the back-end
snapshot.

Using the Assure MIMIX for AIX snapshot to visualize complete historical images
of the database enables DBAs to forgo spending time on a daily basis saving pieces
of database for possible use at a later time. Also, DBAs have access to the exact
historical image they want (typically by reviewing logs, etc.).

Performing a volume restore

You can restore failed production volumes without having to do a full production
restore by doing the following tasks:

• “Step 1: Stop Assure MIMIX for AIX on the production server” on page 250

• “Step 2: Create new volumes to replace failed volumes” on page 250

• “Step 3: Create a snapshot on the recovery server” on page 251

• “Step 4: Validate the information provided by the snapshot” on page 252

• “Step 5: Destroy the snapshot” on page 252

Assure MIMIX for AIX User Guide v5.2.04.00 249

 • “Step 6: Recreate the snapshot on the recovery server” on page 253

• “Step 7: Copy volumes on recovery server to replacement volumes on

production server” on page 253

• “Step 8: Restart Assure MIMIX for AIX on the production server” on page 253

• “Step 9: Rollback the appropriate context on the production server” on

page 253

• “Step 10: Mount the volumes for the context” on page 255

• “Step 11: Destroy the snapshot” on page 255

These tasks are described in detail in the subsequent sections.

Step 1: Stop Assure MIMIX for AIX on the production server

Stop Assure MIMIX for AIX on the production server by executing the following
command:
rtstop –C <Context ID> -F

Step 2: Create new volumes to replace failed volumes

The new volumes must have the same names, be in the same volume group, and be
of the same size as the original volumes. Execute the following command on the
production server to display this information:
sclist –C <Context ID> –t pdfc

EXAMPLE:
In this example, the Context ID is 1. The volume that needs to be replaced is
/dev/rrtctx1. Display information about the volume.

sclist –C 1 –t pdfc

The output shows that /dev/rrtctx1 belongs to volume group rtvg1. The volume size
is shown in bytes (1073741824).
Object: <loglv00>, Type: <SCRT/containers/PDFC>, Serial <355>:
HostName (string) = <production> (No Default)
FileName (string) = </dev/rloglv00> (No Default)
HeaderFileName (string) = </usr/scrt/loglv00.hdr> (No Default)
Size (longlong) = <16777216> (No Default)
DiskGroupHint (string) = <rtvg1> (No Default)
Type (string) = <jfslog> (raw)
Location (string) = <No Value> (No Default)
AccessGroupID (int) = <0> (0)
Object: <rtlv2>, Type: <SCRT/containers/PDFC>, Serial <362>
HostName (string) = <production> (No Default)
FileName (string) = </dev/rrtlv2> (No Default)
HeaderFileName (string) = </usr/scrt/rtlv2.hdr> (No Default

250 Assure MIMIX for AIX User Guide v5.2.04.00

 Size (longlong) = <1073741824> (No Default)
DiskGroupHint (string) = <rtvg1> (No Default)
Type (string) = <jfs> (raw)
Location (string) = </ctx12> (No Default)
AccessGroupID (int) = <0> (0)
Object: <rtctx1>, Type: <SCRT/containers/PDFC>, Serial <369>:
HostName (string) = <production> (No Default)
FileName (string) = </dev/rrtctx1> (No Default)
HeaderFileName (string) = </usr/scrt/rtctx1.hdr>(No Default)
Size (longlong) = <1073741824> (No Default)
DiskGroupHint (string) = <rtvg1> (No Default)
Type (string) = <jfs> (raw)
Location (string) = </ctx1> (No Default)
AccessGroupID (int) = <0> (0)

Step 3: Create a snapshot on the recovery server

Create a snapshot on the recovery server that contains a copy of each volume to be
restored. The snapshot provides the data to be copied to the replacement volumes.
Select a time for the snapshot that is before the time that the disk failed. To
determine the time at which the disk failed, you need to inspect the system logs.

To create the snapshot, enter one of the following commands on the recovery server:
scrt_ra –C <Context ID> –D <time>

or
scrt_ra –C <Context ID> –t <LFCID>

The allowable formats for times entered with the –D option are specified in the file
identified by the DATEMSK environment variable.

EXAMPLE:
In this example, the LFCID is 158. The Context ID is 1.
scrt_ra –C 1 -t 158

The following output results.

Making SNAP /dev/rsnloglv00, 41.6
Making SNAP /dev/rsnrtlv2, 41.10
Making SNAP /dev/rsnrtctx1, 41.14
Making SNAP /dev/rsnc1lif_bk_1, 41.18
Making SNAP /dev/rsnc1lif_bk_2, 41.22
Making SNAP /dev/rsnc1lif_bk_3, 41.26
Making SNAP /dev/rsnc1dbmf_bk_1, 41.30
Making SNAP /dev/rsnc1dbmf_bk_2, 41.34
Making SNAP /dev/rsnc1dbmf_bk_3, 41.38
Making SNAP /dev/rloglv00, 41.4
Making SNAP /dev/rrtlv2, 41.8
Making SNAP /dev/rrtctx1, 41.12

Assure MIMIX for AIX User Guide v5.2.04.00 251

 Fetching LFC #173
Applying LFC #173
Fetching LFC #171
Applying LFC #171
Fetching LFC #169
Applying LFC #169
Fetching LFC #167
Applying LFC #167
Fetching LFC #165
Applying LFC #165
Fetching LFC #163
Applying LFC #163
Fetching LFC #161
Applying LFC #161
Fetching LFC #159
Applying LFC #159
The BackingStore Vdevs are at level 158. ABA is at level 174.

Step 4: Validate the information provided by the snapshot

Validate the information provided by the snapshot by running the application on the
recovery server.

IMPORTANT
Do not try to validate the information by running the application on the
production server after the data is restored. If the data turns out to be
incorrect, you need to rollback the data included in all previous attempts to
restore data.

If the data is valid, stop the application. Note the Context ID and the time or LFCID
used to create the snapshot.

If the data is not valid, then stop the application and create the snapshot again as
described in “Step 3: Create a snapshot on the recovery server” on page 251.
Continue until you have a snapshot with valid data.

Step 5: Destroy the snapshot

Verifying the data in the snapshot may involve mounting the snapshot on the
recovery server and incurring I/O or other causing other changes to the snapshot.
Thus, you need to destroy and recreate the snapshot before you use it for recovery.

Destroy the snapshot by using the following command:

scrt_ra –C <Context ID> -W

EXAMPLE:
The Context ID in this example is 1. Enter the following command:
scrt_ra -C 1 –W

252 Assure MIMIX for AIX User Guide v5.2.04.00

 This results in output similar to the following:
Snap Devs (read only, raw) Minor rj wj Snap level Vdev level Vdevs(read/write, block)
-------------------------- ----------- ---------- ---------- -----------------------
/dev/rsnloglv00 4 -- -- 0 0 /dev/loglv00
/dev/rsnrtlv2 8 -- -- 0 0 /dev/rtlv2
/dev/rsnrtctx1 12 -- -- 0 0 /dev/rtctx1
/dev/rsnc1lif_bk_1 16 -- -- 0 0 N/A
/dev/rsnc1lif_bk_2 20 -- -- 0 0 N/A
/dev/rsnc1lif_bk_3 24 -- -- 0 0 N/A
/dev/rsnc1dbmf_bk_1 28 -- -- 0 0 N/A
/dev/rsnc1dbmf_bk_2 32 -- -- 0 0 N/A
/dev/rsnc1dbmf_bk_3 36 -- -- 0 0 N/A

Step 6: Recreate the snapshot on the recovery server

Recreate the snapshot on the recovery server using the same command that you used
before.
scrt_ra –C <Context ID> –D <time>

or
scrt_ra –C <Context ID> –t <LFCID>

Step 7: Copy volumes on recovery server to replacement volumes on

production server
If you have rsh enabled on the production server, then you can use the dd command
to copy the data.

EXAMPLE:
dd if=/dev/rrtctx1 ibs=1024k | rsh production_server_name -l root
dd of=/dev/rrtctx1 obs=1024k

Step 8: Restart Assure MIMIX for AIX on the production server

Use the following command to restart Assure MIMIX for AIX:
rtstart –C <Context ID> -M

Restarting Assure MIMIX for AIX on the production server begins a region
synchronization between the production server and the recovery server. Monitor the
system log or the Assure MIMIX for AIX log until the following message appears:
-------------------------------------------------------------
--- Dynamic SuperTransaction recovery complete ---
-------------------------------------------------------------

Step 9: Rollback the appropriate context on the production server

Enter the following command on the recovery server:
scrt_rc –C <Context ID>

You will be prompted for the time or LFCID that you used to create the snapshot.

Assure MIMIX for AIX User Guide v5.2.04.00 253

 EXAMPLE:
scrt_rc –C 1

The following is a sample rollback session.

------------------------------------------------
Assure MIMIX for AIX Production Restore Shell
------------------------------------------------

Ensuring LCA and ABA are up.

LCA checked in.
ABA checked in.
Checking initial conditions...
Checking production status...
Bringing up restore server...
RestoreServer checked in.
Checking backend status...
Initializing LCA restore session...
LCA is in restore mode.
Initializing RS restore session...
Session is in production lead restore mode.

--- Restore session initialized! ---

type "help" at the prompt for a list of available commands.

rc>

At this prompt, enter restore.

rc> restore

Restore target type:

t - time
e - event marker
l - lfc
a - abort

At this prompt, enter l for LFCID or t for “time.” Use the same information that you
used to create the snapshot in “Step 3: Create a snapshot on the recovery server” on
page 251.
> l

LFC target >158

You have requested an incremental LFC restore
from Tue May 15 08:16:24 2018 (1526372184)
to Mon May 14 11:17:29 2018 (1526296649),
LFCIDs 250+ to 158.
c(ontinue) or a(bort)? c

254 Assure MIMIX for AIX User Guide v5.2.04.00

 Rolling LFC restore status.
---------------------------
Production at LFCID 248.
Production at LFCID 246.
Production at LFCID 244.
Production at LFCID 242.
Production at LFCID 240.
...
Production at LFCID 160.
Production at LFCID 158.
Production restored to LFCID 158.
Backingstore remains stable at LFCID 250.
rc> commit
committing...
RestoreServer is down, exit code 0.
Restore Client session complete.

Step 10: Mount the volumes for the context

On the production server, enter the following command to mount the volumes for
the context:
rtmnt –C <Context ID>

You may need to use fsck on the file systems before they can be mounted. If this is
necessary, then unmount the volumes using the rtumnt command, run fsck, and then
mount the volumes using the rtumnt command shown above.

Step 11: Destroy the snapshot

On the recovery server, use the following command to destroy the snapshot:
scrt_ra –C <Context ID> –W

Performing a production restore

Assure MIMIX for AIX’s production restore operation allows you to rollback the
protected volumes on the production server. You can roll them back to a specific
LFCID or to a specific time. Before you commit the rollback, however, you need to
verify that you have chosen the correct time or LFCID to rollback to.

NOTE
Even if you decide later that you would like to pick a better time or a
LFCID, you can roll forward or rollback to that point. This is possible
because Assure MIMIX for AIX keeps all of the change information on
the recovery server.

Assure MIMIX for AIX User Guide v5.2.04.00 255

 Using theAssure UI portal for a production restore
Use the Rollback Production Server wizard to rollback the production server to a
specific location in the rollback window. For rollback progress, see the Production
Server Rollback portlet on the Recovery page.

Before starting the rollback, validate the rollback location using a snapshot and stop
all applications that are using the logical volumes. Use the Replication Group portlet
on the Replication page to stop the replication group. During the rollback, file
systems must be unmounted. For rollback progress, see the Production Server
Rollback portlet on the Recovery page.

NOTE
Data changed on the production server between the rollback location and
your most recent changes will be lost.

To start a production server rollback:

1. Select a replication group in the Recovery portlet.

2. Do one of the following:

• Select Rollback, from the Action dropdown menu on the Recovery portlet.
• Click Rollback on the Production Server Rollback portlet.

NOTE
For 3-node configurations the first panel that displays is Select Replica.
Refer to “Broadcast replication configuration” on page 55 for additional
information.

256 Assure MIMIX for AIX User Guide v5.2.04.00

 IMPORTANT
In the Rollback from recovery server dropdown, select the recovery server
used to validate the rollback location.

NOTE
For 2-node configurations, the first panel that displays is Unmount File
Systems.

Assure MIMIX for AIX User Guide v5.2.04.00 257

 a. Unmount file systems—Specify whether to automatically or manually
unmount the file systems. During the rollback, file systems must be
unmounted.

For rollback progress, see the Production Server Rollback portlet on

the Recovery page.
3. Click Next.

The Rollback Production Server (Start Rollback) wizard displays.

258 Assure MIMIX for AIX User Guide v5.2.04.00

 4. Use the Location in rollback section, to specify the type of information to use to
locate in the rollback window, where the production server will be rolled back
to. Select either Point in Time, Container ID, or Event Marker:

• Point in Time—Specify the date and time, within the rollback window,
where the production server will be rolled back to.
• Container ID—Specify the container ID, within the rollback window, where
the production server will be rolled back to.
• Event Marker—Specify the event marker, within the rollback window,
where the production server will be rolled back to.

5. Mount file systems—Specify whether to automatically or manually unmount

and mount and the file systems.

6. Click Finish to start the rollback.

The Production Server portlet shows the progress of the rollback.

Using the command line to perform a production restore

To perform a production restore, complete the following tasks:

1. Stop the application on the production server.

2. Unmount the protected volumes on the production server. Enter the following
command:
rtumnt -C <Context ID>

You should see output similar to the following:

rtumnt -C <Context ID>
Determining Filesystems to unmount...
Unmounting /dev/testlv from /test...
Sync: transferring current LFC to Recovery Server.
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

3. On the recovery server, start the production restore shell.

scrt_rc -C <Context ID>

This should result in output similar to the following:

------------------------------------------------
Assure MIMIX for AIX Production Restore Shell
------------------------------------------------
Ensuring LCA and ABA are up.
LCA checked in.
ABA checked in.
Checking initial conditions...
Checking production status...

Assure MIMIX for AIX User Guide v5.2.04.00 259

 Bringing up restore server...
RestoreServer checked in.
Checking backend status...
Initializing LCA restore session...
LCA is in restore mode.
Initializing RS restore session...
Session is in production lead restore mode.

--- Restore session initialized! ---

type "help" at the prompt for a list of available commands.

rc>

4. Enter restore. This results in the following output:

Restore target type:
t - time
e - event marker
l - lfc
a - abort

5. You can choose to rollback the production server to a specific time or a specific
LFCID. If the current redo LFCID is 36 and you choose to rollback to LFCID
30, you should see output similar to the following:
You have requested an incremental LFC restore
from Tue May 15 15:02:08 2018 (1526396528)
to Mon May 14 15:38:03 2018 (1526312283),
LFCIDs 36+ to 30.
c(ontinue) or a(bort)?

6. Enter c to continue.
Rolling LFC restore status
--------------------------
Production at LFCID 34
Production at LFCID 32
Production at LFCID 30
Production restored to LFCID 30.
Backingstore remains stable at LFCID 36

rc>

NOTE
Although you have rolled back the production server to LFCID 30, the
snapshot on the recovery server still contains information up to and
including LFCID 36. This allows you to verify that LFCID 30 is the one
you want to rollback to. If it is not, enter abort. Determine the proper
LFCID and start the production restore shell as described in step 3.

260 Assure MIMIX for AIX User Guide v5.2.04.00

 7. If you are satisfied that LFCID 30 is correct, then enter commit. You should see
output similar to the following:
committing....
RestoreServer is down, exit code 0.
Restore Client session complete.

8. On the production server, mount the protected volumes. Enter the following
command:
rtmnt -C <Context ID> -f

You should see output similar to the following:

Determining Filesystems to mount...
fsck -fp -y /dev/rlvesp00

/dev/rlvesp00 (/pfs00): ** Unmounted cleanly - Check suppressed

Mounting /pfs00...

fsck -fp -y /dev/rlvesp01

The current volume is: /dev/lvesp01

Primary superblock is valid.
Mounting /pfs01...

Assure MIMIX for AIX User Guide v5.2.04.00 261

262 Assure MIMIX for AIX User Guide v5.2.04.00
Working with Archived Data
13

Assure MIMIX for AIX supports media management products such as Tivoli
Storage Manager on AIX platforms. This chapter contains:

• “Overview of working with archived data” on page 263

• “Performing a snapshot-based backup to archive media” on page 263

• “Performing a production restore from archived logs” on page 264

Overview of working with archived data

You can have additional data protection by keeping complete copies of the data on
archive media such as tape. To create copies on the archive media use snapshots
from the recovery server.

Archived copies of the data are useful to:

• Perform a production restore on the production server. You may want to do

this if the data on the recovery server is unavailable or if you need to rollback
to a point in the data that is no longer stored on the recovery server.

• Create a snapshot on the recovery server. You may want to do this if you need
to restore the data on the recovery server or if you want additional copies of
the data for data mining.
• Create additional copies of the data on alternate devices, such as, logical
volumes.

Performing a snapshot-based backup to archive media

This section explains how to put a complete copy of your protected data on
archive media. You may back up your data to archive media as often as you like.

NOTE
The Tivoli Storage Manager must be defined in the Assure MIMIX for
AIX configuration before using this command.

On the recovery server, enter the following command:

Assure MIMIX for AIX User Guide v5.2.04.00 263

 scrt_vfb -C <Context ID>

Performing a production restore from archived logs

You can perform a production restore from archived LFCs when the LFCs on the
recovery server do not go back far enough or when they are unavailable. Like any
other production restore, you must stop the application on the Production Server and
unmount the protected volumes before you roll them back.

To perform a production restore from archived LFCIDs, do the following:

1. Stop the application on the production server.

2. Unmount the protected volumes on the production server. Enter the following
command:
rtumnt -C <Context ID><Context ID>

You should see output similar to the following:

rtumnt -C <Context ID>
Determining Filesystems to unmount...
Unmounting /dev/testlv from /test...
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

3. On the recovery server, start the production restore shell. Enter the following
command:
scrt_rc -C <Context ID>

This results in output similar to the following:

------------------------------------------------
Assure MIMIX DR for AIX Production Restore Shell
------------------------------------------------

Ensuring LCA and ABA are up.

LCA checked in.
ABA checked in.
Checking initial conditions...
Checking production status...
Bringing up restore server...
RestoreServer checked in.
Checking backend status...
Initializing LCA restore session...
LCA is in restore mode.
Initializing RS restore session...
Session is in production lead restore mode.

--- Restore session initialized! ---

264 Assure MIMIX for AIX User Guide v5.2.04.00

 type "help" at the prompt for a list of available commands.

rc>

4. To display available restore target windows. Enter targets.

This should result in output similar to the following:

Current Snap Time:
1529922170 (LFCID: 1466): Mon Jun 25 10:22:50 2018

Available internal & external (tape) rollback windows:

--------------------------------------------------------

Start: 1529922170 (LFCID: 1466): Mon Jun 25 10:22:50 2018

End: 1529920798 (LFCID: 1352): Mon Jun 25 09:59:58 2018

Available VFBs:
--------------------------------------------------------
1529916625 (LFCID: 1342): Mon Jun 25 08:50:25 2018
1526957343 (LFCID: 1986): Tue May 22 14:49:03 2018
1526609678 (LFCID: 1456): Fri May 18 14:14:38 2018

rc>

5. Enter restore. This results in the following output:

Restore target type:
t - time
e - event marker
l - lfc
a - abort
>

6. Choose l for Log File Container.

This results in the following output:

LFC target >

If you are restoring from archived data, then the LFCID that you choose
identifies data that is no longer stored on the recovery server.

7. Enter a LFCID <example 1360>

This results in the following output:

You have requested an incremental LFC restore
from Fri Jun 22 10:22:50 2018 (1529662970)
to Fri Jun 23 10:01:26 2018 (1529661686),
LFCID’s 1466+ to 1360.
c(ontinue) or a(bort)?

Assure MIMIX for AIX User Guide v5.2.04.00 265

 8. Enter c to continue.

This should result in output similar to the following:

Rolling LFC restore status.
---------------------------
Production at LFCID 1464.
Production at LFCID 1462.
Production at LFCID 1460.
Production at LFCID 1458.
Production restored to LFCID 1360.
Backingstore remains stable at LFCID 1466.
rc>

NOTE
Although you have rolled back the production server to LFCID 1360, the
snapshot on the recovery server still contains information up to and
including LFCID 1464. This allows you to verify that LFCID 1360 is the
one you want to rollback to. If it is not, enter abort. Determine the proper
LFCID and start the production restore shell as described in step 3 on
page 264.

9. If you are satisfied that LFCID 1360 is correct, enter commit.

You will see output similar to the following:
committing...
RestoreServer is down, exit code 0.
Restore Client session complete.

10. On the production server, mount the protected volumes. Enter the following
command:
rtmnt -C <Context ID> -f

You should see output similar to the following:

Determining Filesystems to mount...
fsck -fp -y /dev/rtestlv

The current volume is: /dev/testlv

Primary superblock is valid.
J2_LOGREDO:log redo processing for /dev/testlv
Primary superblock is valid.
Mounting /test...

266 Assure MIMIX for AIX User Guide v5.2.04.00

Introduction to Disaster Recovery
14

Introduction
Assure MIMIX for AIX provides highly available data recovery and protection
through failover, resync, and failback operations on both local and remote
recovery servers, providing solutions for local failovers, as well as remote
failovers.

In a local failover operation, the production server fails over to a local (on-site)
recovery server, whereas in a remote failover operation, the production server fails
over to a remote (off-site) recovery server. Failing over to a remote server is
defined as Disaster Recovery, since it applies to the situation where an entire site
is lost due to a disaster such as a flood or hurricane. Disaster recovery is also used
for situations where failing over to a local server is adequate for keeping data
available and applications running.

This chapter contains:

• “Introduction” on page 267

• “Assure MIMIX for AIX Disaster Recovery” on page 268

• “Assure MIMIX for AIX Disaster Recovery management” on page 269

Assure MIMIX for AIX User Guide v5.2.04.00 267

Assure MIMIX for AIX Disaster Recovery
The Assure MIMIX for AIX disaster recovery capability is the process of switching
the production server to a recovery server that is located either locally or remotely
from the production server. The failover operation could be due to a system
hardware or software failure, a scheduled maintenance period, or a disaster at your
production or local site.

This section contains:

• “Assure MIMIX for AIX recovery process” on page 268

• “How Assure MIMIX for AIX Disaster Recovery works” on page 268

Assure MIMIX for AIX recovery process

The Assure MIMIX for AIX disaster recovery process consists of three operations:

• failover—swapping from the production server to the recovery server

• resync— bring the production server data up to date with the recovery server
data

• failback—swapping back to the production server from a local or a remote

recovery server.

A failover operation is typically followed by a resync and then a failback operation,

which is the process of returning the role of production server to its original location
after a system failover or a disaster has taken place.

These operations use remote mirror Backing Store File Container (BSFC) replicas
as the “failover-production” data. This requires only a configuration change and no
data movement, resulting in reducing the time that is required to resync the volumes
after switching sites.

Use of the statemap tracking mechanism increases the efficiency of the data resync,
as it minimizes the amount of data transfer that must take place. The Production
application continues to run during the resync operation.

How Assure MIMIX for AIX Disaster Recovery works

The resync operation eliminates the need to perform a full volume resync copy from
your recovery server to the production server. This reduce the time required to
resume operations at your production site.

Since the failover process puts the volumes into a suspended state, changes are
tracked within a statemap. Assuming that recording these changes is enabled, only
the changed data is sent to the production site to synchronize the volumes. This
reduces the time required to complete the failback operation.

268 Assure MIMIX for AIX User Guide v5.2.04.00

 Assure MIMIX for AIX Disaster Recovery management
NOTE
Although the production application must be down during the failover
operation, this transition is usually very fast.

This section contains:

• “Failover context overview” on page 269

• “Failover context specifications” on page 269

• “How the Failover context works” on page 270

• “rtdr Failover command” on page 271

Failover context overview

If the production server fails, you can temporarily run the production systems on the
recovery server through the failover operation.

NOTE
You can choose to configure the recovery server as the failover server
where you temporarily run the production system.

This transition requires that the configuration of the failover operation is specified in
a failover context. You create a failover context to configure a context that is
specific to your failover operations.

The failover context provides Assure MIMIX for AIX with the configuration
information used to operate as if the original recovery was actually a production
server, and the original production server, when it comes back on-line, was actually
the recovery server.

You set up the failover context in association with the primary context for the
production server. This failover context enables you to perform the system failover
and failback operations, including managing all the required transitions from the
Production environment to the recovery server.

To accomplish this, Assure MIMIX for AIX uses the block-ordered replica
maintained on the recovery as the failover disk, on which it brings up the production
server.

Failover context specifications

To configure a context, specify:

• Sizes, names, locations of all raw logical volumes (LVs)

Assure MIMIX for AIX User Guide v5.2.04.00 269

 • Names of all special files associated with devices (access points to LVs)

• File system information

• Host information (host name, host ID, and IP addresses

• Information about relationships between a production volume and its associated

replica logical volume, as well as the designated production server, and
recovery server

• All of this information is identified with a single Context ID

Failover context and primary context relationship

Although closely related to the primary context, a failover context has all of its own
attributes for handling a failover and needs its own content identifier or Context ID.

A failover context is the same as its associated primary context, where all
relationships and flows are reversed. Many of the logical volumes used by the
primary context, such as LFCs, are shared with the failover context. However, some
of the volumes are not shared and therefore may be in different locations depending
on which server the production is operating on. For example, on the production
server during normal operations, or on the recovery during failover operations.

Set up a Failover context

A failover context can be setup with the New configuration wizard or the Change
configuration wizard.

After you setup a failover context by using the rtdr command, all other attributes
used with the rtdr command can then take the primary Context ID. This provides
an environment in which it appears as if you are dealing with one context, either in a
primary or a failover mode. The underlying configurations are really two different,
tightly related, contexts. You only need to remember the primary Context ID to
failover, resync, and failback.

Failover context naming conventions

A primary or a failover context can be up to three digits long (1 - 999). You can
assign a number as a primary Context ID, for example 100. You can then add “1” to
the ID to identify the failover Context ID; for example, 101.

How the Failover context works

The primary context has all the information for the servers in a Production-recovery
server configuration, as well as in a production-recovery- server configuration.

Similar to a primary context, the failover context has all the information for all the
servers in a configuration. However, the difference is that the configuration settings
the failover context contains are derived from the primary context and that it shares
several attributes with the primary context.

270 Assure MIMIX for AIX User Guide v5.2.04.00

 NOTE
You must setup one Failover Context for each additional server in a
configuration where you need to create only one Primary Context for your
production server.

By default, in a configuration (Production, Recovery), the recovery server becomes

the failover server. In a failover event, it becomes the production server. All three
servers will still be connected when a resync operation is active.

In the same configuration, to change the failover server to the recovery server
change the configuration associated with the failover context by specifying the
hostname of the recovery server in the following command:
rtdr -C <Primary Context ID> -F <Failover Context ID> setup

rtdr Failover command

This section describes the Assure MIMIX for AIX Disaster Recovery failover
command rtdr and its associated attributes.

Use the Assure MIMIX for AIX disaster recovery and failover rtdr command to:

• Setup a failover context

• Validate data integrity prior to a failover

• Perform failover, resynchronize, and failback operations.

Syntax
rtdr -C <ID> -fhmnqv failover | resync | failback
rtdr -C <ID> -F <ID> [-s <hostname>] [-fhmnv] setup

-C Primary Context ID of Production, Recovery, Remote Replica

servers
-F Failover Context ID
-f Forced execution *
-h Help, prints usage
-m Man style help
-n No execution, just print commands
-q quiet, do not ask for confirmation
-s Select failover site server from multiple Recovery Servers
(default is the first replication hop's server). <hostname>
must be a configured SCRT/info/host HostName attribute.
-v Verbose output

Assure MIMIX for AIX User Guide v5.2.04.00 271

 IMPORTANT
Use the -f attribute with the rtdr command with caution. If you do not
resync, this attribute forces a failback and leaves the Production Volume
Set (PVS) file systems and replica out of sync.

Assure MIMIX for AIX Disaster Recovery operations

The previous section contains an overview of the Assure MIMIX for AIX Disaster
capability and its associated failover context and commands. In the event of a
failover, follow the procedures described in the following sections.

This section contains:

• “Failover process overview” on page 272

• “Preparing before a Failover” on page 273

• “Before performing Failover operations” on page 273

Failover process overview

The failover process involves:

1. Creating a primary context using the procedures described in the Chapter 7

“Configuring Replication Groups” on page 107.

NOTE
If you have changed a primary context you must delete the corresponding
failover context and recreate the failover context.

rtdr -C <Primary Context ID> -F <Failover Context ID> setup

2. Creating a failover context using the rtdr command. This command creates a
failover context definition associated with the primary context. Refer to
“Preparing before a Failover” on page 273.

3. Validating data integrity of the replica prior to a failover. If necessary, perform a

failover restore, as shown in “Before performing Failover operations” on
page 273.

4. Performing the following operations after you validate the replica:

• Failover
• Resync
• Failback

272 Assure MIMIX for AIX User Guide v5.2.04.00

 Refer to “Disaster Recovery Operations” on page 275 for instructions on how
to perform these operations.

Preparing before a Failover

To prepare for a potential system failure, you set up a failover context so that your
production server can switch operations to the designated recovery server.

Setting up a Failover context

You must create a failover context to be associated with a configured primary
context prior to a system failover. The Failover Context ID must be unique on the
associated servers. Refer to “Failover context naming conventions” on page 270 for
information on valid Failover Context ID names.

To create a failover context associated with the primary context:

On the production and target servers execute:

rtdr -C <Primary Context ID> -F <Failover Context ID> setup

where:

<Primary Context ID> is the primary context on the production server, and
<Failover Context ID> is the failover context on the recovery server.

NOTE
If there is more than one target server and you do not want to use the
default for the Failover Server, then use the -s <Hostname> option on
the rtdr command to specify the Failover Server. Refer to “Syntax” on
page 271 for the rtdr command.

Before performing Failover operations

Do not perform a failover restore on a restore target that has not been validated.
After a system failover occurs, Assure MIMIX for AIX cannot rollback to a point in
time before the failover.

This section provides guidelines to execute before performing failover operations:

Validating data integrity

Validating the data integrity of the replica is critical. Prior to performing the failover
operations, validate the data integrity of the replica on the recovery server and
restore it. To validate the data, first create a snapshot of the replica and then analyze
it with the application itself.

Assure MIMIX for AIX User Guide v5.2.04.00 273

 Verify restore point
On the recovery server execute:

1. Create the snapshot:

scrt_ra -C <Primary Context ID> -X

2. Mount file systems:

rtmnt -C <Context ID>

3. Check the data.

4. Unmount file systems:

rtumnt -C <Context ID>

5. Remove the snapshot:

scrt_ra -WC <Context ID>

Create a virtual restore snapshot

Once you create a snapshot of the replica, you can analyze the integrity of the data.
If analysis indicates data corruption, remove the snapshot and use a virtual restore
to locate and validate an optimal restore point. A virtual restore leaves a snapshot in
place for analysis at the restored point in time.

1. To perform a virtual restore on the recovery server:

scrt_ra -C <Primary Context ID> -t|-D|-S

For example, to make a restore snapshot to July 27, 2018 at 17:21:57:

scrt_ra -C <Context ID> -D "7/27/18 17:21:57"

2. Mount file systems:

rtmnt -C <Context ID>

3. Check the data.

4. Unmount file systems:

rtumnt -C <Context ID>

5. Remove the snapshot:

scrt_ra -WC <Context ID>

You can perform failover operations after you validate the replica.

274 Assure MIMIX for AIX User Guide v5.2.04.00

Disaster Recovery Operations
15

This chapter describes:

• “Using the Assure UI portal to perform failover and failback” on page 275

• “Using the command line to perform failover and failback for 2-node
non-clustered replication groups” on page 299

• “Using the command line to perform failover and failback for 2-node
clustered replication groups” on page 307

Using the Assure UI portal to perform failover and failback

The following steps show how to perform a failover (planned or unplanned) or
failback procedures. Refer to the Assure MIMIX for AIX online help for specific
information for each portlet and dialog. The following sections describe:

• “Run a procedure” on page 275

• “Failover and failback for 2-node non-clustered replication groups” on

page 276

• “Failover and failback for 2-node clustered replication groups” on page 283

• “Failover and failback for 3-node non-clustered broadcast replication groups”

on page 290

Run a procedure
The Procedures portlet and Steps portlet on the Procedures page will guide you
through each step.

1. Use one of the following methods to run a procedure. Use the method that is
most convenient for you based on the page you are currently on:

• From the Replication Group portlet, select Planned Failover, Unplanned

Failover, or Failback from the Actions dropdown for a replication group.
• From the Procedures portlet, select Run from the Actions dropdown for a
specific replication group.

Assure MIMIX for AIX User Guide v5.2.04.00 275

 • From the Procedures portlet, select the Procedure name (Planned Failover,
Unplanned Failover, or Failback) and select Run on the Action toolbar on
the Steps portlet.

2. Use one of the following methods to run the next step in a procedure (if
required) or retry a failed step:

• From the Replication Group portlet, select Resume Procedure from the
Actions dropdown for a specific replication group.
• From the Procedures portlet, select Resume from the Actions dropdown for
a specific procedure and replication group.
• From the Steps portlet, select Resume from the Action toolbar.

About procedure and step processes

• For any procedure that you run, the Sequence Number shows the sequence
number of the step in the procedure. The sequence begins with integers starting
at 10 and incremented by 10. The purpose of sequence numbers is to help
identify problem steps when communicating with Support.

• When a procedure successfully completes, the Steps portlet shows a green

check in the status column as each step successfully completes, and a green
check in the Status row.

Failover and failback for 2-node non-clustered replication groups

The following sections describe failover and failback procedures for 2-node
non-clustered replication groups.:

• “Planned Failover for 2-node non-clustered replication groups” on page 276

• “Unplanned Failover for 2-node non-clustered replication groups” on page 279

• “Failback for 2-node non-clustered replication groups” on page 282

NOTE
Before failing over, all applications using the logical volumes must be
stopped. You may want to validate that your applications run properly on
the failover server by using a snapshot and running your applications with
the snapshot.

Planned Failover for 2-node non-clustered replication groups

The Steps portlet shows the steps that you must manually run to perform a planned
failover for 2-node non-clustered replication groups. Select Run on the Action
toolbar on the Steps portlet.

276 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 4 on page 277 shows the commands that are run on the servers, while you
execute the procedure steps with the Assure UI portal.

Table 4: Run Planned Failover for 2-node non-clustered replication groups

Sequence Step Dialog for this step Command for this step
Number

10 Unmount the file “Run Planned Failover rtumnt -R -C <Primary Context id>
systems on the Procedure dialog for 2-node
current production non-clustered replication
server; groups: Unmount file systems
on current production server”
on page 278

20 Stop replication on “Resume Planned Failover rtstop -S -F -C <Primary Context

the current Procedure dialog for 2-node id>
production server non-clustered replication
groups: Stop replication on
current production server” on
page 278

30 Failover the “Resume Planned Failover rtdr -q -C <Primary Context id>

replication group. Procedure dialog for 2-node failover
Server roles change non-clustered replication
groups: Failover replication
group: Server roles change” on
page 278

40 Start replication on “Resume Planned Failover rtdr -q -C <Primary Context id>

the new recovery Procedure dialog for 2-node resync
server non-clustered replication
groups: Start replication on the
new recovery server” on
page 278

Assure MIMIX for AIX User Guide v5.2.04.00 277

 Table 4: Run Planned Failover for 2-node non-clustered replication groups

Sequence Step Dialog for this step Command for this step
Number

50 Start replication on “Resume Planned Failover rtdr -q -C <Primary Context id>

the new production Procedure dialog for 2-node resync
server non-clustered replication
groups: Start replication on new
production server” on
page 278

NOTE
When the procedure completes, and you are ready to move production
back to the configured production server, run the failback procedure.

Run Planned Failover Procedure dialog for 2-node non-clustered

replication groups: Unmount file systems on current production server
This step unmounts the file systems on the current production server. You requested
to move production to the failover server. Before running this procedure, all
applications using the logical volumes in this replication group must be stopped.
Applications are not available until this procedure completes.

Resume Planned Failover Procedure dialog for 2-node non-clustered

replication groups: Stop replication on current production server
This step stops replication on the current production server. Replication stops after
all data in the backlog has been replicated. After replication stops and before you
continue, it is recommended that you create a snapshot on the failover server and
validate that your applications run properly.

Resume Planned Failover Procedure dialog for 2-node non-clustered

replication groups: Failover replication group: Server roles change
This step changes the roles of the servers in the replication group. Data is not
replicated and failback is not available until you complete the remaining steps in
this procedure.

Resume Planned Failover Procedure dialog for 2-node non-clustered

replication groups: Start replication on the new recovery server
This step starts replication on the recovery server. Data is not replicated and failback
is not available until you complete the remaining steps in this procedure.

Resume Planned Failover Procedure dialog for 2-node non-clustered

replication groups: Start replication on new production server
This step starts replication on the new production server. Data can start replicating.
When the step completes, and you are ready to move production back to the
configured production server, run the failback procedure.

278 Assure MIMIX for AIX User Guide v5.2.04.00

 Unplanned Failover for 2-node non-clustered replication
groups
An unplanned failover could be due to a hardware or software failure or power
outage with the production server. Because the production server is not available,
you may need to failover to the failover server. This procedure guides you through
the failover, including validating the rollback location, using a snapshot.

The Steps portlet shows the steps that you must manually run to perform an
unplanned failover for 2-node non-clustered replication groups.Each step is run,
with pauses after each step.

1. Select Run on the Action toolbar on the Steps portlet.

Table 5 on page 279 shows what steps you must manually run to perform an
unplanned failover for non-clustered replication groups.

Table 5: Run Unplanned Failover for 2-node non-clustered replication groups

Sequence
Step Dialog for this step Command for this step
number

10 Create a snapshot “Run Unplanned Failover Procedure scrt_ra -S timestamp (if by

on failover server. dialog for 2-node non-clustered Point in Time or Event
replication groups: Create snapshot on Marker) -C <Primary
failover server” on page 280 Context id>
or
scrt_ra -t <Container ID> (if
by Container ID ) -C
<Primary Context ID>,
followed by rtmnt -f -C
<Primary Context id>

Assure MIMIX for AIX User Guide v5.2.04.00 279

 Table 5: Run Unplanned Failover for 2-node non-clustered replication groups

Sequence Step Dialog for this step Command for this step
number

20 Delete a snapshot “Resume Unplanned Failover Procedure rtumnt -f -R -C <Primary

on failover server. dialog for 2-node non-clustered Context id>, followed by
replication groups: Delete snapshot on scrt_ra -W -C <Primary
failover server” on page 281 Context id>

30 Rollback the “Resume Unplanned Failover Procedure scrt_ra -F -S <timestamp> (if

failover server dialog for 2-node non-clustered by Point in Time or Event
replication groups: Rollback failover Marker) <Primary Context
server” on page 281 id>
or
scrt_ra -F -t <Container ID>
(if by Container ID) -C
<Primary Context id>

40 Failover the “Resume Unplanned Failover Procedure rtdr -q -C <Primary Context id>
replication group. dialog for 2-node non-clustered failover
Server roles replication groups: Failover replication
change. group: Server roles change” on page 281

50 Start replication on “Resume Unplanned Failover Procedure rtdr -q -C <Primary Context

the new recovery dialog for 2-node non-clustered id> resync
server replication groups: Start replication on
the recovery server” on page 281

60 Start replication on “Resume Unplanned Failover Procedure rtdr -q -C <Failover Context

the new production dialog for 2-node non-clustered id> resync
server replication groups: Start replication on
the new production server” on page 281

Run Unplanned Failover Procedure dialog for 2-node non-clustered

replication groups: Create snapshot on failover server
Because the production server is not available, you may need to rollback the failover
server before failing over. Validating the rollback location using a snapshot is
recommended. To create a snapshot:

1. Specify a location in the Location in failover server rollback window.

2. Click OK, to confirm the snapshot location and create a snapshot.

3. Mount the file systems and run your applications with the snapshot to validate
the rollback location.

4. You may need to use more than one snapshot to find a valid location.

280 Assure MIMIX for AIX User Guide v5.2.04.00

 Resume Unplanned Failover Procedure dialog for 2-node non-clustered
replication groups: Delete snapshot on failover server
This step deletes the snapshot on the failover server that was used to validate the
rollback location. All applications using the snapshot must be stopped. File systems
are unmounted when the snapshot is deleted.

You can decide whether or not you have a validated rollback location and how to
proceed. If you decide to create another snapshot, the procedure returns to the
Create snapshot step and waits for you to resume the procedure. The dialog for this
step is the Resume - Create Snapshot dialog and not the Run Procedure dialog.

In the section, Do you have a validated rollback location?

• If you select Yes, continue to the next step. If selected, click OK to delete the
snapshot and go to the next step in the procedure. Note, that you will need to
use the Resume action.
• If you select No, return to previous step and create another snapshot with a
different rollback location. Note, that you will need to use the Run action.

Resume Unplanned Failover Procedure dialog for 2-node non-clustered

replication groups: Rollback failover server
This step will rollback the failover server to the location you specify. If you do not
want to rollback the failover server, select Do Not Rollback from the Location to
rollback failover server field.

Resume Unplanned Failover Procedure dialog for 2-node non-clustered

replication groups: Failover replication group: Server roles change
This step changes the roles of the servers in the replication group. Data is not
replicated and failback is not available until you complete the remaining steps in
this procedure. Applications can be started when this step completes.

NOTE
The servers in the replication group have changed now that the replication
group has failed over.

Resume Unplanned Failover Procedure dialog for 2-node non-clustered

replication groups: Start replication on the recovery server
This step starts replication on the recovery server. Data is not replicated and failback
is not available until you complete the remaining steps in this procedure.

Resume Unplanned Failover Procedure dialog for 2-node non-clustered

replication groups: Start replication on the new production server
This step starts replication on the new production server. Data can start replicating.

Assure MIMIX for AIX User Guide v5.2.04.00 281

 Failback for 2-node non-clustered replication groups
The failback procedure is used to move production back to the configured
production server. The failback procedure is only available when the replication
group is in a failed over state.

The Steps portlet shows the steps for the failback procedure selected in the
Procedures portlet.

1. Select Run on the Action toolbar on the Steps portlet.

Table 6 on page 282 shows what steps you must manually run to perform a failback
for 2-node non-clustered replication groups

Table 6: Failback for 2-node non-clustered replication groups

Sequence Step Dialog for this step Command for this step
number

10 Unmount the file systems “Run Failback Procedure dialog rtumnt -R -C <Failover
on the current production for 2-node non-clustered Context id>
server replication groups: Unmount file
systems on current production
server” on page 283

20 Stop replication on the “Resume Failback Procedure rtstop -S -F -C <Failover

current production server dialog for 2-node non-clustered Context id>
replication groups: Stop
replication on current production
server” on page 283

30 Failback the configured “Resume Failback Procedure rtdr -q -C <Primary Context

production server dialog for 2-node non-clustered id> failback
replication groups: Failback
configured production server” on
page 283

282 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 6: Failback for 2-node non-clustered replication groups

Sequence Step Dialog for this step Command for this step
number

40 Failback the configured “Resume Failback Procedure rtdr -q -C <Failover Context

recovery server dialog for 2-node non-clustered id> failback
replication groups: Failback
configured recovery server” on
page 283

Run Failback Procedure dialog for 2-node non-clustered replication

groups: Unmount file systems on current production server
This step unmounts the file systems on the current production server. You requested
to move production to the failover server. Before running this procedure, all
applications using the logical volumes in this replication group must be stopped.
Applications are not available until this procedure completes.

Resume Failback Procedure dialog for 2-node non-clustered replication

groups: Stop replication on current production server
This step stops replication on the current production server. Replication stops after
all data in the backlog has been replicated. After replication stops and before you
continue, it is recommended that you create a snapshot on the configured production
server and validate that your applications run properly.

Resume Failback Procedure dialog for 2-node non-clustered replication

groups: Failback configured production server
This step returns the production server role to the configured production server and
starts the replication processes. Data is not replicated until the remaining steps in
this procedure are completed.

NOTE
After this step completes, applications can be started on the configured
production server.

Resume Failback Procedure dialog for 2-node non-clustered replication

groups: Failback configured recovery server
This step returns the recovery server role to the configured recovery server role and
starts the replication processes. Data can replicate from the production server to the
recovery server.

Failover and failback for 2-node clustered replication groups

The following sections describe failover and failback procedures for 2-node
clustered replication groups

Assure MIMIX for AIX User Guide v5.2.04.00 283

 • “Planned failover for 2-node clustered replication groups” on page 284

• “Unplanned Failover for 2-node clustered replication groups” on page 285

• “Failback for 2-node clustered replication groups” on page 288

Planned failover for 2-node clustered replication groups

Use the planned failover procedure to switch the roles of the production and failover
server when both production and recovery servers are available.Use the Steps
portlet to begin the automated planned failover process for 2-node clustered
replication groups.

1. Select Run on the Action toolbar on the Steps portlet.

NOTE
The Run Planned Failover Procedure dialog displays. This is the only
dialog displayed when running a Planned Failover procedure for a 2-node
clustered replication group. All the steps are run continuously, without
user interaction.

284 Assure MIMIX for AIX User Guide v5.2.04.00

 2. Click OK to start the planned failover procedure.

After the procedure completes successfully, the replication starts from the new
production server to the new recovery server. When you are ready to move the
production server back to the configured production server, run the Failback
procedure. See “Failback for 2-node clustered replication groups” on page 288.

Unplanned Failover for 2-node clustered replication groups

An unplanned failover could be due to a hardware or software failure or power
outage with the production server. Because the production server is not available,
you may need to failover to the failover server. This procedure guides you through
the failover, including validating the rollback location, using a snapshot.

The Steps portlet shows the steps that are run by the cluster in the case of unplanned
failover. Steps 10 and 20 need to be run by the user one step at a time. Steps 30-50
are run by the cluster continuously.

Assure MIMIX for AIX User Guide v5.2.04.00 285

 1. Select Run on the Action toolbar on the Steps portlet.

Table 7 on page 286 shows the steps that are run by the cluster.

Table 7: Run Unplanned Failover for a 2-node clustered replication group

Sequence Step Dialog for this step Command for this step
number

10 Create a snapshot “Run Unplanned Failover Procedure If by Point in Time or Event

on failover server. dialog for 2-node clustered replication Marker:
groups: Create snapshot on failover scrt_ra -S timestamp -C
server” on page 287 <Primary Context id>
or if by Container ID:
scrt_ra -t Container ID -C
<Primary Context id>

followed by

rtmnt -f -C <Primary
Context id>

20 Delete a snapshot “Resume Unplanned Failover rtumnt -f -R -C <Primary

on failover server. Procedure dialog for 2-node clustered Context id>
replication groups: Delete snapshot on (followed by)
failover server” on page 287
scrt_ra -W -C <Primary
Context id>

30 Rollback the “Resume Unplanned Failover If by Point in Time or Event

failover server Procedure dialog for 2-node clustered Marker:
replication groups: Rollback failover scrt_ra -F -S timestamp
server” on page 288 <Primary Context id>
If by Container ID”
scrt_ra -F -t <Container ID>
-C <Primary Context ID>

286 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 7: Run Unplanned Failover for a 2-node clustered replication group

Sequence Step Dialog for this step Command for this step
number

40 Failover the “Resume Unplanned Failover rtdr -q -C <Primary Context

replication group. Procedure dialog for 2-node clustered id> failover
Server roles replication groups: Failover
change. replication group: Server roles
change” on page 288

50 Start application “Resume Unplanned Failover

on the new Procedure dialog for 2-node clustered
production server. replication groups: Start replication on
(if an application the new production server” on
start script is page 288
specified in the NOTES:
configuration)
This step is automatically started by
cluster services if an application start
script is specified in the configuration.
When the new recovery server comes
back online replication will be
automatically started by cluster
services.

Run Unplanned Failover Procedure dialog for 2-node clustered replication

groups: Create snapshot on failover server
Because the production server is not available, you may need to rollback the failover
server before failing over. Validating the rollback location using a snapshot is
recommended. To create a snapshot:

1. Specify a location in the Location in failover server rollback window.

2. Click OK, to confirm the snapshot location and create a snapshot.

3. Mount the file systems and run your applications with the snapshot to validate
the rollback location.

4. You may need to use more than one snapshot to find a valid location.

Resume Unplanned Failover Procedure dialog for 2-node clustered

replication groups: Delete snapshot on failover server
This step deletes the snapshot on the failover server that was used to validate the
rollback location. All applications using the snapshot must be stopped. File systems
are unmounted when the snapshot is deleted.

You can decide whether or not you have a validated rollback location and how to
proceed. If you decide to create another snapshot, the procedure returns to the
Create snapshot step and waits for you to resume the procedure. The dialog for this
step is the Resume - Create Snapshot dialog and not the Run Procedure dialog.

In the section, Do you have a validated rollback location?

Assure MIMIX for AIX User Guide v5.2.04.00 287

 • If you select Yes, continue to the next step. If selected, click OK to delete the
snapshot and go to the next step in the procedure. Note that you will need to use
the Resume action.

• If you select No, return to previous step and create another snapshot with a
different rollback location. Note, that you will need to use the Run action.

Resume Unplanned Failover Procedure dialog for 2-node clustered

replication groups: Rollback failover server
This step will rollback the failover server to the location you specify. If you do not
want to rollback the failover server, select Do Not Rollback from the Location to
rollback failover server field.

Resume Unplanned Failover Procedure dialog for 2-node clustered

replication groups: Failover replication group: Server roles change
This step changes the roles of the servers in the replication group. Data is not
replicated and failback is not available until you complete the remaining steps in
this procedure.

NOTE
The servers in the replication group have changed now that the replication
group has failed over.

Resume Unplanned Failover Procedure dialog for 2-node clustered

replication groups: Start replication on the new production server
This step starts your application on the new production server. Data is not replicated
and failback is not available until the new recovery server comes back online.

Failback for 2-node clustered replication groups

The failback procedure is used to move production back to the configured
production server. The failback procedure is only available when the replication
group is in a failed over state. The Steps portlet shows the steps for the Failback
procedure selected in the Procedures portlet.

288 Assure MIMIX for AIX User Guide v5.2.04.00

 .

1. Select Run on the Action toolbar on the Steps portlet.

NOTE
The Run Failback Procedure dialog displays. This is the only dialog
displayed when running a Failback procedure for a clustered replication
group. The steps are run automatically by the cluster.

Assure MIMIX for AIX User Guide v5.2.04.00 289

 2. Click OK to begin the automated failback procedure. For the remaining steps,
the following single command is executed by Assure UI portal on the
production server: cli.sh [<general options>] moveApplication [<command
options>] <ApplicationName>

Failover and failback for 3-node non-clustered broadcast

replication groups
The following sections describe failover and failback procedures for 3 node
broadcast replication groups:

• “Planned Failover for 3-node non-clustered broadcast replication groups” on

page 290

• “Unplanned Failover for 3-node non-clustered broadcast replication groups” on

page 293

• “Failback for 3-node non-clustered broadcast replication groups” on page 297

NOTE
Before failing over, all applications using the logical volumes must be
stopped. You may want to validate that your applications run properly on
the failover server by using a snapshot and running your applications with
the snapshot.

Planned Failover for 3-node non-clustered broadcast

replication groups
The Steps portlet shows the steps that you must manually run to perform a planned
failover for 3-node non-clustered broadcast replication groups.

1. Select Run on the Action toolbar on the Steps portlet.

IMPORTANT
In the first step of the Planned Failover Procedure dialog, you can select
either Recovery 1 or Recovery 2 to be the New production server.

290 Assure MIMIX for AIX User Guide v5.2.04.00

 Table 8 on page 291 shows the commands that are run on the servers, while you
execute the procedure steps with the Assure UI portal.

Table 8: Run Planned Failover for 3-node non-clustered broadcast replication groups

Sequence Step Dialog for this step Command for this step
Number

10 Unmount the file “Run Planned Failover rtumnt -R -C <Primary Context id>
systems on the Procedure dialog for 3-node
current production non-clustered broadcast
server; replication groups: Unmount
Note: You can select file systems on current
the failover recovery production server” on
server on this dialog. page 292

20 Stop replication on “Resume Planned Failover rtstop -S -F -C <Primary Context

the current Procedure dialog for 3-node id>
production server non-clustered broadcast
replication groups: Stop
replication on current
production server” on
page 292

30 Prepare current “Resume Planned Failover rtdr -q -C <Primary Context id> -F

recovery server for Procedure dialog for 3-node <Failover Context ID> -t <new
failover non-clustered broadcast production server> setup
replication groups: Prepare
current recovery server for
failover” on page 293

40 Prepare current “Resume Planned Failover rtdr -q -C <Primary Context id> -F

production server for Procedure dialog for 3-node <Failover Context ID> -t <new
failover non-clustered broadcast production server> setup
replication groups: Prepare
current production server for
failover” on page 293

Assure MIMIX for AIX User Guide v5.2.04.00 291

 Table 8: Run Planned Failover for 3-node non-clustered broadcast replication groups

Sequence Step Dialog for this step Command for this step
Number

50 Failover the “Resume Planned Failover rtdr -q -C <Primary Context id> -F

replication group. Procedure dialog for 3-node <Failover Context ID> -t <new
Server roles change non-clustered broadcast production server> setup
replication groups: Failover
replication group: Server roles
change” on page 293

60 Start replication on “Resume Planned Failover rtdr -q -C <Failover Context ID>

the new recovery Procedure dialog for 3-node resync
server non-clustered broadcast
replication groups: Start
replication on new recovery
server 2” on page 293

70 Start replication on “Resume Planned Failover rtdr -q -C <Primary Context id>

the new recovery Procedure dialog for 3-node resync
server non-clustered broadcast
replication groups: Start
replication on new recovery
server 1” on page 293

80 Start replication on “Resume Planned Failover rtdr -q -C <Failover Context ID>

the new production Procedure dialog for 3-node resync
server non-clustered broadcast
replication groups: Start
replication on new production
server” on page 293

NOTE
When the procedure completes, and you are ready to move production
back to the configured production server, run the failback procedure.

Run Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Unmount file systems on current production
server
This step unmounts the file systems on the current production server. You requested
to move production to the failover server. Before running this procedure, all
applications using the logical volumes in this replication group must be stopped.
Applications are not available until this procedure completes.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Stop replication on current production
server
This step stops replication on the current production server. Replication stops after
all data in the backlog has been replicated. After replication stops and before you

292 Assure MIMIX for AIX User Guide v5.2.04.00

 continue, it is recommended that you create a snapshot on the failover server and
validate that your applications run properly.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Prepare current recovery server for failover
This step prepares the configured recovery server to recognize the new production
server.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Prepare current production server for
failover
This step prepares the configured recovery server to recognize the new production
server.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Failover replication group: Server roles
change
This step changes the roles of the servers in the replication group. Data is not
replicated and failback is not available until you complete the remaining steps in
this procedure.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Start replication on new recovery server 2
This step starts the replication processes on recovery server 2. Data is not replicated
and failback is not available until you complete the remaining steps in this
procedure.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Start replication on new recovery server 1
This step starts the replication processes on recovery server 1. Data is not replicated
and failback is not available until you complete the remaining steps in this
procedure.

Resume Planned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Start replication on new production server
This step starts replication on the new production server. Data can start replicating.

After this step completes and you are ready to move production back to the
configured production server, run the Failback procedure.

Unplanned Failover for 3-node non-clustered broadcast

replication groups
An unplanned failover could be due to a hardware or software failure or power
outage with the production server. Because the production server is not available,
you may need to failover to the failover server. This procedure guides you through
the failover, including validating the rollback location, using a snapshot.

Assure MIMIX for AIX User Guide v5.2.04.00 293

 The Steps portlet shows the steps that you must manually run to perform an
unplanned failover for 3-node non-clustered broadcast replication groups. Each step
is run with pauses after each step.

1. Select Run on the Action toolbar on the Steps portlet.

IMPORTANT
In the first step of the Unplanned Failover Procedure dialog, you can select
either Recovery 1 or Recovery 2 to be the New production server.

Table 9 on page 294 shows the commands that are run on the servers, while you
execute the procedure steps with the Assure UI portal.

Table 9: Run Unplanned Failover for 3-node non-clustered broadcast replication groups

Sequence Step Dialog for this step Command for this step
Number

10 Create a snapshot on “Run Unplanned Failover (if by Point in Time or Event

failover server. Procedure dialog for 3-node Marker)
non-clustered broadcast scrt_ra -S <timestamp> -C <Primary
replication groups: Create Context id>
snapshot on failover server” on
page 296 (if by Container ID)
scrt_ra -t <Container ID> -C
<Primary Context id>
(followed by)
rtmnt -f -C <Primary Context id>

294 Assure MIMIX for AIX User Guide v5.2.04.00

Table 9: Run Unplanned Failover for 3-node non-clustered broadcast replication groups

Sequence Step Dialog for this step Command for this step
Number

20 Delete a snapshot on “Resume Unplanned Failover rtumnt -f -R -C <Primary Context

failover server. Procedure dialog for 3-node id>
non-clustered broadcast (followed by)
replication groups: Delete
snapshot on failover server” on scrt_ra -W -C <Primary Context id>
page 296

30 Rollback the failover “Resume Unplanned Failover (if by Point in Time or Event
server. Procedure dialog for 3-node Marker)
non-clustered broadcast scrt_ra -F -S <timestamp> <Primary
replication groups: Rollback Context id>
failover server” on page 296
(if by Container ID)
scrt_ra -F -t <Container ID> -C
<Primary Context id>

40 Failover the “Resume Unplanned Failover rtdr -q -C <Primary Context id> -F

replication group. Procedure dialog for 3-node <Failover Context ID> -t <new
Server roles change. non-clustered broadcast production server> setup
replication groups: Failover (followed by)
replication group. Server roles
change” on page 296 rtdr -q -C <Primary Context id>
failover

50 Start replication on “Resume Unplanned Failover rtdr -q -C <Primary Context id> -F

the new recovery Procedure dialog for 3-node <Failover Context ID> -t <new
server 2. non-clustered broadcast production server> setup
replication groups: Start
replication on new recovery
server 2” on page 297

60 Start replication on “Resume Unplanned Failover rtdr -q -C <Failover Context ID>

the new recovery Procedure dialog for 3-node resync
server 1. non-clustered broadcast
replication groups: Start
replication on new recovery
server 1” on page 297

70 Start replication on “Resume Unplanned Failover rtdr -q -C <Failover Context ID>

the new production Procedure dialog for 3-node resync
server. non-clustered broadcast
replication groups: Start
replication on new production
server” on page 297

NOTE
When the procedure completes, and you are ready to move production
back to the configured production server, run the failback procedure.

Assure MIMIX for AIX User Guide v5.2.04.00 295

 Run Unplanned Failover Procedure dialog for 3-node non-clustered
broadcast replication groups: Create snapshot on failover server
Because the production server is not available, you may need to rollback the failover
server before failing over. Validating the rollback location using a snapshot is
recommended.

To create a snapshot:

1. Specify a location in the rollback window on the new production server.

2. Click OK, to confirm the snapshot location and create a snapshot.

3. Mount the file systems and run your applications with the snapshot to validate
the rollback location.

4. You may need to use more than one snapshot to find a valid location.

Resume Unplanned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Delete snapshot on failover server
This step deletes the snapshot on the failover server that was used to validate the
rollback location. All applications using the snapshot must be stopped. File systems
are unmounted when the snapshot is deleted.

You can decide whether or not you have a validated rollback location and how to
proceed. If you decide to create another snapshot, the procedure returns to the
Create snapshot step and waits for you to resume the procedure. The dialog for this
step is the Resume - Create Snapshot dialog and not the Run Procedure dialog.

In the section, Do you have a validated rollback location?

• If you select Yes, continue to the next step, click OK to delete the snapshot
and go to the next step in the procedure.

• If you select No, return to previous step and create another snapshot with a
different rollback location, click OK to return to previous step and create
another snapshot with a different rollback location.

Resume Unplanned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Rollback failover server
This step will rollback the new production server to the location you specify. If you
do not want to rollback the new production server, select Do Not Rollback.

Resume Unplanned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Failover replication group. Server roles
change
This step will failover the replication group which changes the role of the servers.
Data is not replicated and failback is not available until the remaining steps in this
procedure are completed.

When this step completes, applications can be started on the new production server.

296 Assure MIMIX for AIX User Guide v5.2.04.00

 Resume Unplanned Failover Procedure dialog for 3-node non-clustered
broadcast replication groups: Start replication on new recovery server 2
This step starts the replication processes on recovery server 2. Data is not replicated
and failback is not available until you complete the remaining steps in this
procedure.

Resume Unplanned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Start replication on new recovery server 1
This step starts the replication processes on recovery server 1. Data is not replicated
and failback is not available until you complete the remaining steps in this
procedure.

Resume Unplanned Failover Procedure dialog for 3-node non-clustered

broadcast replication groups: Start replication on new production server
This step starts replication on the new production server. Data can start replicating.
After this step completes and you are ready to move production back to the
configured production server, run the Failback procedure.

Failback for 3-node non-clustered broadcast replication

groups
The Steps portlet shows the steps that you must manually run to perform a failback
for 3-node non-clustered broadcast replication groups.

1. Select Run on the Action toolbar on the Steps portlet.

Table 10 on page 298 shows the commands that are run on the servers, while you
execute the procedure steps with the Assure UI portal.

Assure MIMIX for AIX User Guide v5.2.04.00 297

 Table 10: Run Failback for 3-node non-clustered broadcast replication groups

Sequence Step Dialog for this step Command for this step
Number

10 Unmount the file “Run Failback Procedure rtumnt -R -C <Primary Context id>
systems on the dialog for 3-node non-clustered
current production broadcast replication groups:
server. Unmount file systems on
current production server” on
page 298

20 Stop replication on “Resume Failback Procedure rtstop -S -F -C <Primary Context

the current dialog for 3-node non-clustered id>
production server. broadcast replication groups:
Stop replication on current
production server” on
page 298

30 Failback the “Resume Failback Procedure rtdr -q -C <Primary Context id>

configured dialog for 3-node non-clustered failback
production server. broadcast replication groups:
Stop replication on current
production server” on
page 298

40 Failback the “Resume Failback Procedure rtdr -q -C <Failover Context ID>

configured recovery dialog for 3-node non-clustered failback
server 1. broadcast replication groups:
Failback configured recovery
server 1” on page 299
50 Failback the “Resume Failback Procedure rtdr -q -C <Failover Context ID>
configured recovery dialog for 3-node non-clustered failback
server 2. broadcast replication groups:
Failback configured recovery
server 2” on page 299

Run Failback Procedure dialog for 3-node non-clustered broadcast

replication groups: Unmount file systems on current production server
This step unmounts the file systems on the current production server. You requested
to move production to the failover server. Before running this procedure, all
applications using the logical volumes in this replication group must be stopped.
Applications are not available until this procedure completes.

Resume Failback Procedure dialog for 3-node non-clustered broadcast

replication groups: Stop replication on current production server
This step stops replication on the current production server. Replication stops after
all data in the backlog has been replicated.

After replication stops and before you continue, it is recommended that you create a
snapshot on the failover server and validate that your applications run properly.

298 Assure MIMIX for AIX User Guide v5.2.04.00

 Resume Failback Procedure dialog for 3-node non-clustered broadcast
replication groups: Failback configured production server
This step returns the production server role to the configured production server and
starts the replication processes. Data is not replicated until the remaining steps in
this procedure are completed.

After this step completes, applications can be started on the configured production
server.

Resume Failback Procedure dialog for 3-node non-clustered broadcast

replication groups: Failback configured recovery server 1
This step returns the recovery server 1 role to the server configured to be recovery
server 1 and starts the replication processes. Data can replicate from the production
server to recovery server 1.

Resume Failback Procedure dialog for 3-node non-clustered broadcast

replication groups: Failback configured recovery server 2
This step returns the recovery server 2 role to the server configured to be recovery
server 2 and starts the replication processes. Data can replicate from the production
server to recovery server 2.

Using the command line to perform failover and failback for

2-node non-clustered replication groups
In the event of a failover or failback for 2-node non-clustered replication groups,
follow the procedures described in the following sections.

• “Failover process overview” on page 300

• “Preparing before a Failover” on page 300

• “Before performing Failover operations” on page 301

• “Failover operations” on page 302

• “Performing failback” on page 304

Assure MIMIX for AIX User Guide v5.2.04.00 299

 Failover process overview
The failover process involves:

1. Creating a primary context using the procedures described in the Chapter 7

“Configuring Replication Groups” on page 107.

NOTE
If you have changed a primary context you must delete the corresponding
failover context and recreate the failover context.

rtdr -C <Primary Context ID> -F <Failover Context ID> setup

2. Creating a failover context using the rtdr command. This command creates a
failover context definition associated with the primary context. Refer to
“Preparing before a Failover” on page 300.

3. Validating data integrity of the replica prior to a failover. If necessary, perform a

failover restore, as shown in “Before performing Failover operations” on
page 301.

4. Performing the following operations after you validate the replica:

• Failover
• Resync
• Failback

Refer to “Failover operations” on page 302 for instructions on how to perform

these three operations.

Preparing before a Failover

To prepare for a potential system failure, you set up a failover context so that your
production server can switch operations to the designated recovery server.

Setting up a Failover context

You must create a failover context to be associated with a configured primary
context prior to a system failover. The Failover Context ID must be unique on the
associated servers. Refer to “Failover context naming conventions” on page 270 for
information on valid Failover Context ID names.

To create a failover context associated with the primary context:

On the production and target servers execute:

rtdr -C <Primary Context ID> -F <Failover Context ID> setup

where:

300 Assure MIMIX for AIX User Guide v5.2.04.00

 <Primary Context ID> is the primary context on the production server, and
<Failover Context ID> is the failover context on the recovery server.

NOTE
If there is more than one target server and you do not want to use the
default for the Failover Server, then use the -s <Hostname> option on
the rtdr command to specify the Failover Server. Refer to “rtdr” on
page 315.

Before performing Failover operations

Do not perform a failover restore on a restore target that has not been validated.
After a system failover occurs, Assure MIMIX for AIX cannot rollback to a point in
time before the failover.

This section provides guidelines to execute before performing your failover

operations:

Validating data integrity

Validating the data integrity of the replica is critical. Prior to performing the failover
operations, validate the data integrity of the replica on the recovery server and
restore it. To validate the data, first create a snapshot of the replica and then analyze
it with the application itself.

Verify restore point

On the recovery server execute:

1. Create the snapshot:

scrt_ra -C <Primary Context ID> -X

2. Mount filesystems:
rtmnt -C <Context ID>

3. Check the data.

4. Unmount filesystems:
rtumnt -C <Context ID>

5. Remove the snapshot:

scrt_ra -WC <Context ID>

Create a virtual restore snapshot

Once you create a snapshot of the replica, you can analyze the integrity of the data.
If analysis indicates data corruption, remove the snapshot and use a virtual restore

Assure MIMIX for AIX User Guide v5.2.04.00 301

 to locate and validate an optimal restore point. A virtual restore leaves a snapshot in
place for analysis at the restored point in time.

1. To perform a virtual restore on the recovery server:

scrt_ra -C <Primary Context ID> -t|-D|-S

For example, to make a restore snapshot to October 26, 2018 at 17:21:57:

scrt_ra -C <Context ID> -D "10/26/18 17:21:57"

2. Mount filesystems:
rtmnt -C <Context ID>

3. Check the data.

4. Unmount filesystems:
rtumnt -C <Context ID>

5. Remove the snapshot:

scrt_ra -WC <Context ID>

You can perform failover operations after you validate the replica.

Failover operations
This section describes how to perform the failover operations from the production
server to the recovery server when the production server has failed.

• “Performing a Failover restore” on page 302

• “Performing resync” on page 303

• “Performing failback” on page 304

• “Manual resynchronization process if production server data is lost” on

page 305

IMPORTANT
Do not perform a failover restore on an invalidated restore target. After
validating the replica, the failover procedures are failover, resync, and
failback.

Performing a Failover restore

You can now use a failover restore to roll the data back. You can:

• “rollback to the actual data replica” on page 303

• “Failover to the latest point in the data” on page 303

302 Assure MIMIX for AIX User Guide v5.2.04.00

 rollback to the actual data replica
To rollback to the actual data replica, not a snapshot of the replica, to a validated
point in time and then failover:
scrt_ra -C <Primary Context ID> -F [-t | -D | -S]

NOTE
Do not do execute scrt_ra -X -F if you want to failover to the latest
point in time.

For example, to restore the replica to a previously validated target time

(1529584788 seconds from Jan. 1, 1970):
scrt_ra -C <Primary Context ID> -F -S 1529584788

Failover to the latest point in the data

To failover to the recovery server, on the recovery server execute:
rtdr -C <Primary Context ID> failover

NOTE
This stops the aba for the primary context.

Start the application

After performing the failover restore procedure, start the application on the recovery
server. At this point, the application operates in the production environment until the
failback operation takes place. Next, the resync operation tracks all data
modification and sends them back to the original production server.

Performing resync
A resync operation is required when the Production Volumes and Recovery Replica
Volumes diverge. This occurs after a failure of the production server and a failover
to the recovery server. When the application is started on the recovery server the
updates result in a divergence from the data on the production server.

After restoring the original production server, use the resync operation to ensure that
the production server data is current with the recovery server data.

To resynchronize the revived production server from the recovery server, on all
servers (production, recovery):
rtdr -qC <Primary Context ID> resync

This command takes the following actions:

• On the recovery server:

Assure MIMIX for AIX User Guide v5.2.04.00 303

 start aba for failover context

• On the production server:

start aba for failover context
start lca for failover context if there is a configured recovery
server

• On recovery server:
start lca for failover context

IMPORTANT
The resync operation assumes the original production data was not lost,
and is available in its entirety after the production server is revived. If the
production data is lost, the statemap on the recovery server must be
marked as dirty prior to resync. This forces a complete region recovery
and initializes the production data.

Resync with region recovery

This procedure marks statemap bitmaps as dirty for all devices in the failover
context.

On the recovery server, which is now the acting production server, execute:
rtstop -C <Failover Context ID> -F
scconfig -C <Failover Context ID> -M
rtstart -C <Failover Context ID> -M

Wait for the region recovery completes before performing the failback procedure, as
described in “Performing failback” on page 304.

NOTE
Performing a complete region recovery should be avoided since this will
require production down time and significant network resources.

You can mark only specific state maps dirty, using the -L option of the scconfig
command. Refer to “CLI Assure MIMIX DR for AIX Commands” on page 309 for
more information.

Performing failback

IMPORTANT
Before you failback ensure that you stop the application on the recovery
server.

304 Assure MIMIX for AIX User Guide v5.2.04.00

 After a resync operation completes, failback to return to the original production and
recovery server roles. All servers must be active and running to execute resync and
failback operations.

To initiate failback to the original production server, on the Recovery or Replicated

and production servers execute:
rtdr -qC <Primary Context ID> failback

Manual resynchronization process if production server data is lost

If the failover from the production server to the recovery server was necessary
because all protected data was lost on the production server, then the data must be
restored to the production server before doing a failback. This data loss could occur
if a disk or disk subsystem failed or was destroyed on the production server.

The data can be restored to the production server from the recovery using the
following procedure after the necessary volume groups and logical volumes have
been recreated.

1. On the recovery server stop the application.

2. On the production server execute the following command which will start
scrt_aba:
rtdr -qC <Failover Context> resync

3. On the recovery server execute the following command which will unmount
any filesystems if the context has filesystems and unload the drivers.
rtstop -FC <failover context>

4. On the recovery server execute the following command which will mark the
state maps dirty.
scconfig -MC <failover context>

5. On the recovery server execute the following command which will synchronize
the data to the production server.
rtdr -qC <Failover Context ID> resync

6. On the recovery server execute the following command which will show the
state maps.
scconfig -PC <failover context>

7. If the state maps are not clean on the recovery server wait until all the data is
synchronized to the production server.

8. On the production server execute the following command which will create a
snapshot to allow the integrity of the data to be checked.

Assure MIMIX for AIX User Guide v5.2.04.00 305

 scrt_ra -XC <failover context>

9. On the production server execute the following command if the context has
filesystems. This command will mount the filesystems.
rtmnt -C <failover context>

10. On the production server verify the validity of the data.

11. On the production server execute the following command which will unmount
any filesystems which were mounted in step 9.
rtumnt -C <failover context>

12. On the production server execute the following command which will remove
the snapshot created in step 8.
scrt_ra -WC <failover context>

13. On the recovery servers execute the following command which will failback to
the primary context.
rtdr -qC <Failover Context ID> failback

14. On the production server execute the following command which will failback to
the primary context.
rtdr -qC <Failover Context ID> failback

306 Assure MIMIX for AIX User Guide v5.2.04.00

Using the command line to perform failover and failback for
2-node clustered replication groups
To perform a failover or failback for 2-node clustered replication groups use the
following single command. For failover, run the command on the recovery server,
For failback, run the command on the production server.
cli.sh [<general options>] moveApplication [<command options>]
<ApplicationName>

Assure MIMIX for AIX User Guide v5.2.04.00 307

308 Assure MIMIX for AIX User Guide v5.2.04.00
CLI Assure MIMIX DR for AIX
Commands 16

This chapter provides a comprehensive list of Command Line Interface (CLI)

commands for Assure MIMIX DR for AIX.

• “esmon” on page 310

• “es_swmaj” on page 311

• “extend_replica_lv” on page 311

• “rn_temp_journal” on page 312

• “rtattr” on page 313

• “rtdr” on page 315

• “rtmark (and Event Marks)” on page 319

• “rtmnt” on page 322

• “rtstart” on page 323

• “rtstop” on page 324

• “rtumnt” on page 325

• “sclist” on page 326

• “scconfig” on page 329

• “scsetup” on page 331

• “scrt_ra” on page 333

• “scrt_rc” on page 336

• “scrt_vfb” on page 339

• “sccfgd_cron_schedule” on page 340

• “sccfgd_putcfg” on page 341

• “sccfgchk” on page 342

• “sztool” on page 343

Assure MIMIX for AIX User Guide v5.2.04.00 309

esmon

Usage
You can use the esmon command to view the current utilization of the configured
production server Log File Containers (LFC) for a specified Context ID.

Syntax
esmon <Context ID>

Below is sample output:

esmon 1
Dec 10 04:34:59 Total LFC Size=6000M, Free size=5931M, Used Size=69M,
Usage=2/100

where:

• Total LFC Size = 6000 MB: The number of LFCs configured (400), multiplied
by container size (16 MB), minus the space required for metadata.

NOTE
In the Assure UI Replication Group Details portlet the Total size would be
6.3 GB: The number of containers configured (400), multiplied by
container size (16 MB) = 6400 MB converted to 6.25 GB and rounded to
6.3 GB.

• Free size = 5931 MB: The Total LFC Size minus Used Size.
• Used Size = 69 MB: 69 MB of data writes stored in LFCs waiting to be applied
to the replica.

• Usage = 2/100: The percentage of LFCs used. Used Size divided by Total LFC
Size.

310 Assure MIMIX for AIX User Guide v5.2.04.00

extend_replica_lv

Usage
You can use the extend_replica_lv command to force the expansion of a Replica LV
(Logical Volume) that is associated with a specified PVS (Production Volume Set)
LV, so that the Replica LV will be equal in size to the PVS LV. This command will
only run on the production server and the LCA must be active.

Syntax
extend_replica_lv -C <Context ID> -L <PVS LV>
extend_replica_lv -h help
-C <Context ID>
-L <PVS LV>
-h Help, prints this usage

NOTE
This command is only required for PVS LVs that are extended and have no
associated file system, or PVS LVs that have an associated file system with
an outline log and the file system is extended.

es_swmaj

Usage
Use this command to switch and restore the LV major number for all LVs in an
Assure MIMIX for AIX context. This will allow AIX LVM commands such as
"migratepv" to function when the Assure MIMIX for AIX drivers are loaded.

Syntax
es_swmaj -C <Context ID> [-s | -f | -u]
-s: Switch to AIX major number(raw LVs are excluded)
-f: Switch to AIX major number(including raw LVs)
-u: Restore Assure MIMIX DR for AIX major number
-v: Verify switch to AIX major number.

IMPORTANT
If the "-f" option is selected for raw LVs, they must be open before
executing this command. The raw LVs must remain open and no additional
opens should be done until this command is executed with the "-u" option.

Assure MIMIX for AIX User Guide v5.2.04.00 311

rn_temp_journal

Usage
You can use the rn_temp_journal command to create a temporary write journal
which will extend the snapshot buffer size available for a snapshot. This command
is executed on the node that has the recovery server role. It can be executed before
or after a snapshot is created. When the snapshot is deleted the temporary write
journal may be removed.

NOTE
This command can be issued up to a maximum of 64 times to add
additional space on different volume groups.

Syntax
The following parameters are used:
-C <Context ID>
-v <Volume Group for temp LV>
-s <Size of temp LV in Logical Partitions>
-r Remove temporary Write Journals.
-h help

When creating a temporary write journal LV, allocating and configuring the
associated storage pool the "-C, -v and -s" parameters are required. To deallocate a
storage pool and remove the temporary write journal LV the "-C and -r" parameters
are required.

IMPORTANT
If the snapshot buffer has reached 100%, the command will fail and you
will see the following message:
[rn_temp_journal] ERROR: The Write Journal extension cannot be
created for Context ID (nn). A Write Journal extension cannot be created
when the Write Journal pool is full. Delete the snapshot, create the Write
Journal extension and create the snapshot. [rn_temp_journal] ERROR:
Failed to create the Write Journal extension.

312 Assure MIMIX for AIX User Guide v5.2.04.00

rtattr

Usage
Use this command to query and change attributes in the Assure MIMIX for AIX
Object Data Manager (ODM) files:

• SCCuAttr

• SCCuObj

• SCCuRel

Syntax
rtattr -C ID [-a attribute] [-o object] [-t type]
rtattr -C ID -a attribute -v value {-o object | -t type}
rtattr -h
-a Attribute for query/edit (ObjectAttributeName)
-C <Context ID>
-h Help, prints this usage
-o Object for query/edit (ObjectName)
-t Type for query/edit (ObjectType)
-v Value for edit (ObjectAttributeValue)

You can use the –v parameter with the commands to edit. If you do not specify the –
v parameter only query is available.

Example 1
View all the machine hostids:
rtattr -C <Context ID> -a HostId
SCCuAttr:
ObjectName = "backup"
ConfigObjectSerial = 4
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "0xc0a801f7"
ObjectAttributeType = "ulong"
SerialNumber = 4006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1
SCCuAttr:
ObjectName = "replica"
ConfigObjectSerial = 8
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "0xc0a801f2"
ObjectAttributeType = "ulong"

Assure MIMIX for AIX User Guide v5.2.04.00 313

 SerialNumber = 8006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1
SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 16
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "0xc0a801f3"
ObjectAttributeType = "ulong"
SerialNumber = 16006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

Example 2
View only the production server’s hostid:
rtattr -C <Context ID> -o production -a HostId
SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 16
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "0xc0a801f3"
ObjectAttributeType = "ulong"
SerialNumber = 16006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

314 Assure MIMIX for AIX User Guide v5.2.04.00

rtdr

Usage
This command manages Assure MIMIX for AIX's disaster recovery processes as
well as failover and failback operations. Given a primary context <X> configured
on both a “Production” and a “Recovery” Server, note:

• To create an associated failover context <Y>, on both the production and

recovery servers execute:
rtdr -C <X> -F <Y> setup

• To failover to the Recovery server, on the recovery server execute:

rtdr -C <X> failover

• To re-synchronize the revived production server, on both the production and

recovery servers execute:
rtdr -C <X> resync

• To failback to the production server, first on the recovery server, and then on the
production server execute:
rtdr -C <X> failback

• To select and configure from one of many recovery servers (a cascaded

replication configuration) as the target machine for all subsequent failover,
resync and failback operations execute:
rtdr -C <X> -F <Y> -s <hostname> setup

NOTE
A failover context associated with a configured primary context must be
created and setup prior to executing a failover. The failover Context ID is
arbitrary, but must be unique on the associated servers.

• To create and setup a failover context, on both the production and recovery
servers:
rtdr -C <X> -F <Y> setup

• Prior to failover, you should validate the data integrity of the Replica, and if
necessary, validate the data if necessary.

To validate data integrity of the Replica, create a snapshot of the replica, then
analyze it with the application itself. To create the snapshot, on the recovery
server:

scrt_ra -C <X> -X

Assure MIMIX for AIX User Guide v5.2.04.00 315

 • If your analysis indicates data corruption, use a virtual restore to locate and
validate an optimal restore point. A virtual restore leaves a snapshot in place for
analysis at the restored point in time. To perform a virtual restore, on the
recovery server:
scrt_ra -C <X> [-D | -S | -t]

• Given a corrupt replica, and a validated restore point in time, use a failover
restore to roll the actual data replica, not a snapshot of the replica, back to the
validated point in time. To perform a failover restore, on the recovery server
execute:
scrt_ra -C <X> -F [-D | -S | -t]

NOTE
Do not perform a failover restore on an invalidated restore target. After
validating the replica, the disaster recovery procedure is failover, resync,
then failback.

After failover, start the application on the recovery server. It will be the acting
production environment until failback. All data modifications will be tracked
and shipped back to the original production server by resync.

After reviving the original production server, use resync to bring the production
server data up to date with the recovery server data.

After the resync completes, use failback to return to the original production and
recovery server roles. Both the production and recovery servers must be live to
execute resync and failback.

NOTE
Resync assumes the original production data was not lost, and is available
in its entirety after the production server is revived. In the event that
production data was lost, statemap on the recovery server must be dirtied
prior to resync to force a complete region recovery, and re-initialize the
production data.

• To dirty all statemaps, in the failover context on the recovery server (the acting
production server):
rtstop -C <X> -F
scconfig -C <X> -M

NOTE
Do not perform a failover restore on an invalidated restore target.

316 Assure MIMIX for AIX User Guide v5.2.04.00

 After validating the replica, the disaster recovery procedure is to failover,
resync, then failback.

After failover, start the application on the recovery server. It will be the
acting production environment until failback. All data modifications will be
tracked and shipped back to the original production server by resync.

After reviving the original production server, use resync to bring the
production server data up to date with the recovery server data.

After resync completes, use failback to return to the original production and
recovery server roles. Both the production and recovery servers must be live
to execute resync and failback.

NOTE
Resync assumes the original production data was not lost, and is available
in its entirety after the production server is revived. In the event that
production data was lost, statemap on the recovery server must be dirtied
prior to resync to force a complete region recovery, and re-initialize the
production data.

• To dirty all statemaps, in the failover context on the recovery server (the acting
production server):
rtstop -C <X> -F
scconfig -C <X> -M
rtstart -C <X>

After a system failover, Assure MIMIX for AIX cannot rollback to a point in time
before the failover. Likewise, after a system failback, Assure MIMIX for AIX
cannot rollback to a point in time before the failback. For this reason, replica data
integrity should be validated with a snapshot prior to executing a failover.

Syntax
rtdr -C <ID> [-fhmnqv] failover | resync | failback
rtdr -C <ID> -F <ID> [-s <hostname>] [-fhmnv] setup
-C Context ID (of the "primary" context)
-F Failover Context ID
-f Forced execution (use with caution)
-h Help, prints usage
-m Man style help
-n No execution, just print commands
-q quiet, do not ask for confirmation
-s Select failover site server from multiple recovery
servers (default is first replication hop's server.)
<hostname> must be a configured SCRT/info/host HostName
attribute.
-v Verbose output

Assure MIMIX for AIX User Guide v5.2.04.00 317

 NOTE
The “f” option prompts for confirmation unless combined with q.

318 Assure MIMIX for AIX User Guide v5.2.04.00

rtmark (and Event Marks)

Usage
Event Markers are tags that mark points in time or points in process that are
significant to you for the purposes of recovery. An Event Marker can be selected as
the Recovery Point Objective (RPO) during a data restore. They are typically
needed for applications which cannot take advantage of Assure MIMIX for AIX’s
Any Point-In-Time (APIT) data restores along with applications which do not have
live transactional durability on disk.

The following is an example of a script that could be called, with as many arbitrary
attributes to the event that you want, in addition to the time and date attribute
automatically assigned by rtmark. The customer-defined attributes between the cat
line and the second EOF would also be added to the event. The entire event would
be copied to the recovery server, and available for viewing and selection during
restores.
#!/usr/bin/ksh
cat <<-EOF | /usr/scrt/bin/rtmark -C <Context ID> -
name = test1
description = "This is a test."
owner = dave
priority = 2
another_attribute = “Just another attribute”
EOF

Syntax
rtmark [-C ] [-s <num>|-d <str>] [-iV] [<file>|-]
rtmark -rC <Context ID>
rtmark -h
-C ID Event is specific to Context ID.
-d <str> Date string, overrides event time.
-h Help, display this message.
-i Interactive query for event attributes.
-r Copies event marks from the production server to the
Recovery Server
-s <num> Seconds since epoch, overrides event time.
-V Print version.
<file> File containing the event mark attributes.

Event Marker File and the rtmark command

To use event markers, you need to a write an event marker file and a script that calls
the rtmark command. You also need to set up a call in your application that invokes
the rtmark script.

Assure MIMIX for AIX User Guide v5.2.04.00 319

 If event markers are used in multiple Context IDs, each Context ID must have a
unique event marker file and scripts that calls rtmark.

The following examples show the parameters you need to use in your application;
an event marker file, and a script that calls rtmark:
#example call in your application
<Context ID> <name> <description>

# example event mark script that calls rtmark and emf_1 file
rm -f /tmp/emf_1
printf "name = ${2}\n" >/tmp/emf_1
printf "description = ${3}\n" >>/tmp/emf_1
sync
/usr/scrt/bin/rtmark -C ${1} /tmp/emf_1

#example event marker file /tmp/emf_1

name = <event name>
description = chkpt

Event marker file replication from recovery server 1 to

recovery server 2
Event marks are written to file /usr/scrt/run/c<Context ID>/event_marker from the
production server to the recovery server. On the first recovery server, use the rtmark
command (shown below) to replicate the event marker information from the first
recovery server to the second recovery server.
rtmark –C <Context ID> -r

NOTE
Event markers are lost on failover and failback because the rollback
window is reset. The production server’s event_marker file is cleared
during a failback to the configured production server. The failover server’s
event_marker file is cleared during a failover to the configured failover
server.

Print available event marks for rollback

Use the scrt_ra command with the –ve parameters to print the “Available event
marks for rollback”.
scrt_ra –veC<Context ID>

320 Assure MIMIX for AIX User Guide v5.2.04.00

 Available event marks for rollback:
------------------------------------
Event Name Date/Time (Epoch Time) Description

End_of_day "Wed Apr 4 15:00:31 2018" (1522854031) End of day processing

DB_Migration "Fri May 25 08:12:14 2018"(1527235934) DB Migration completed

Assure MIMIX for AIX User Guide v5.2.04.00 321

rtmnt

Usage
This command is used to mount all file systems associated with the context
specified.

Syntax
rtmnt [-C ID][-fn]

Parameters

Parameter Description

-C ID Context ID. It must be specified if more than one context is

defined.

-f Perform fsck of file systems before mounting

-h Display help message

-n Do not mount file systems. Give present status.

-p Halt on errors instead of undoing (partial)

322 Assure MIMIX for AIX User Guide v5.2.04.00

rtstart

Usage
This command is used to load the Assure MIMIX for AIX data tap and to start the
data replication processes. On the production server, rtstart also mounts the
protected file systems.

Syntax
rtstart [-C ID][-BMnNpr]

Parameters

Parameter Description

-C ID Context ID. It must be specified if more than one context is

defined.

-B Boot/Autostart - used to ONLY during system startup.

-h Displays help message.

-n Does not actually start anything just to give present status.

-M (production server only) Disable, mount, and perform fsck of

production volume set (PVS) file systems.

-N (production server only) Disable and perform fsck of production

volume set file systems.

-p Halts on errors instead of undoing (partial).

-r non-Disruptive Startup Mode - ALL file systems must be

mounted BEFORE loading the drivers. A full synchronization
will occur for non-clustered replication groups with mounted
file systems. This may take an extended period of time.

Assure MIMIX for AIX User Guide v5.2.04.00 323

rtstop

Syntax
rtstop [-C ID][-FfhnkS]

Parameters

Parameter Description

-C ID Context ID. It must be specified if more than one context is

defined.

-F Forces an unload of drivers (use this command with caution).

-f Forces unmount if the snapshot journals are full.

-h Display help message.

-n Does not actually stop anything just give present status.

-k Attempt to kill an agent that is not stopping normally.

-S (production server only) Force log creation agent (LCA) to

synchronize before stopping.

324 Assure MIMIX for AIX User Guide v5.2.04.00

rtumnt

Usage
This command is used to:

• Stop the data replication process of Assure MIMIX for AIX,

• Optionally to unload the data tap.

• Unmount all the volumes associated with the specified context.

Syntax
rtumnt [-C ID][-Dfn]

Parameters

Parameter Description

-C ID Context ID. It must be specified if more than one context is

defined.

-D (production server only prevent log creation agent (LCA) from

synchronizing after unmounting.

-f Forces unmount if the snapshot journals are full.

-h Display help message.

-n Do not unmount. Give present status.

Assure MIMIX for AIX User Guide v5.2.04.00 325

sclist

Usage
This command provides information about containers used in Assure MIMIX for
AIX.

Syntax
sclist -t TYPE [-bR] [-A ATTR [ ... ]] [-R] [-C ID] [-d X]
sclist -t TYPE -o ATTR=VALUE [-bR] [-A ATTR [ ... ]] [-C ID] [-d X]
sclist -a [-A ATTR [ ... ]] [-C ID] [-d X]
sclist -r SERIAL [-r SERIAL ...] [-b | -c] [-C ID] [-d X]
sclist -O SERIAL [-O SERIAL ...] [-C ID] [-d X]
sclist [-BeiIjJlLmMpPstSTvVX] [-I] [-D[D]] [-C ID] [-d X]
sclist -h [-z]
sclist -fZ
-a Query all objects
-A ATTR Query specific attribute (repeatable)
-b Be Brief, useful for scripting output
-B List of StateMap bitmap devices
-c Expansive, if possible, expand on output.
-C ID Operate on Context ID.
-d X Debug level of X (0-9).
-D Query all driver/device objects from ODM.
(-D for just drivers, and -DD for devices & drivers.)
-e List pooling/journal configuration.
-f File system list.
-h Print Help Message
-i Query driver objects
-I Query whether drivers are loaded
-j Query the Journal objects
-J List of History Journal exported devices
-l Query the Logdev objects
-L List of LogDev access devices
-m Query the StateMap objects
-M List of StateMap access devices
-o ATTR=VAL Query within type list for attribute ATTR equal to
VAL.
-O SERIAL Query specific object with serial number SERIAL
-p Query the Passthru objects
-P List of PassThru access devices
-r SERIAL List given objects relationships.
-R List relationships in attribute list.
-s Query the SCID objects
-S List of SCID devices
-v List of Volume group/disk info for config
-V List of Write Journal exported devices
-t TYPE What objects to query ('sclist -hz' for list)

326 Assure MIMIX for AIX User Guide v5.2.04.00

 -X List of SCID exported devices
-z Print all known classes/object types.
-Z Print device names for current machine.

Parameter Description

-a Query all objects

-A attribute Query specific attribute (repeatable)

-b Be brief; useful for scripting output

-B List of statemap bitmap devices

-C ID Operate on Context ID

-d Query all driver objects

-D Query all driver objects and device objects

-E Query the pooling status

-f File system list

-h Print help message

-i Query driver objects

-I Query whether drivers are loaded

-j Query the journal objects

-J List of history journal exported devices

-l Query the Logdev objects

-L List of LogDev access devices

-m Query the StateMap objects

-M List of statemap access devices

-o ATTR=val Query within type list for attribute ATTR equal to val

-O serial Query specific object with serial number serial

-p Query the Passthru objects

-P List of PassThru access devices

-r serial List relationships of object with specified serial number

-R List relationships in attribute list

-s Query the SCID objects

-S List SCID devices

-v List volume group information for configuration

-V List write journal exported devices

Assure MIMIX for AIX User Guide v5.2.04.00 327

 Parameter Description

-t type Type of object to query (enter sclist –hz for list of object
types)

-X List of SCID exported devices

-z Print all known object types

-Z Print device names for current machine

328 Assure MIMIX for AIX User Guide v5.2.04.00

scconfig

Usage
Use this command to manage DataTap devices and drivers.

Syntax
scconfig -l [-cfinERtv] [-C ID] [-d X] [-I name]
scconfig -u | -U [-finEv] [-C ID] [-d X] [-I name]
scconfig -r [-nv] [-L name ...] [-C ID] [-d X] [-I name]
scconfig -M | -W | -P | -B [-G] [-nv] [-L name ...] [-C ID] [-d X]
scconfig -S [-C ID] [-d X] [-nv]
scconfig -s [-C ID] [-d X]
scconfig -t | -q | -Q | -h
scconfig -C ID -a seconds [-b percent]
scconfig -V

Parameters

Parameter Description

-a seconds Send Partial Container Automatically. Frequency to check in

seconds (0-86400).
-b percent Send Partial Container Automatically. Percent filled (0-99).
-c Send Partial Container Automatically display current values.
-C ID Operate on Context ID.
-d X Debug level of X (0-9).
-E Exported, defers device export to scsetup.
-f Create the filter special devices.
-h Print help message.
-i Ignore errors and continue.
-I name Operate on named context instance {prod | backup}. Only
useful in single system configuration.
-l Load/configure the Assure MIMIX for AIX kernel drivers and
devices.
-L name Select a device (by name in configuration) for operations. Use
sclist –Z to list names of the devices.

-M Mark statemap bitmaps dirty for all or specified devices (see

-L).

-n Don't execute, just echo commands.

-P Print statemap bitmaps for all or specified devices (see -L).

Assure MIMIX for AIX User Guide v5.2.04.00 329

 Parameter Description

-B Sync While Active - full synchronization

Resync data for all or specified devices (see -L). See “Sync
While Active - full synchronization” on page 236.
Warning: Keep in mind the following while scconfig -B is
running:
• Do not cycle Assure MIMIX for AIX and the server.
• Ensure that you do not lose your terminal session (nohup
scconfig -B &).
-B -G Sync While Active - full synchronization
Resync data for all or specified devices (see -L). Restart from
where the previous operation left off. See “Sync While Active
- full synchronization” on page 236.
-T Sync While Active - checksum-based synchronization
Resync data for all or specified devices (see -L). See “Sync
While Active - checksum-based synchronization” on
page 237.
Warning: Keep in mind the following while scconfig -T is
running:
• Do not cycle Assure MIMIX for AIX and the server.
• Ensure that you do not lose your terminal session (nohup
scconfig -T &).
-T -G Sync While Active - checksum-based synchronization
Resync data for all or specified devices (see -L). Restart from
where the previous operation left off. See “Sync While Active
- checksum-based synchronization” on page 237.
-Q Query kernel statemaps for system synchronization. Returns
"true" if replica is synchronized with production, "false" if not.
-q Query for a list of installed contexts.
-r Replay statemap logs ONLY.
-R Skip replay of statemap logs during log.
-s Status of kernel devices.
-S Send Partial Container. See “Send partial containers
automatically using the Replication Group Configuration
wizard” on page 331.
-t Trace kernel extensions (using this option twice enables
tracing on all kernel drivers).
-u Unload/unconfigure the Assure MIMIX for AIX kernel
devices.
-U Unload the Assure MIMIX for AIX kernel shared drivers. All
other local contexts must be unconfigured (see -u).

330 Assure MIMIX for AIX User Guide v5.2.04.00

 Parameter Description

-v Be verbose or display version when only option.

-V Display version.
-W Wipe statemap bitmaps clean for all devices or the specified
devices (see -L).

Send partial containers automatically using the Replication Group

Configuration wizard
The functionality to send partial containers automatically is also provided by the
Replication Group Configuration Wizard on the Replication Group Container
Options panels page 120 and page 142 in the section “Send partially filled containers
automatically.” For additional details, refer to “Send partially filled containers
automatically” on page 122.

scsetup

Usage
Makes or removes the Logical Volumes (LVs) used by Assure MIMIX for AIX in a
specific protection context, such as LFCs. Note however that scsetup will not
remove production LVs in the PVS or their associated replica LVs. Run this
command after defining and saving a context configuration using the Replication
Group wizard.

After you have defined a context, scsetup creates a log file and containers (logical
volumes) in the specified volume group.

Syntax
scsetup -M [-ijlnprsv] [-C ID] [-d X] [-o role] [ -t TYPE ]
scsetup -R [-inv] [-C ID] [-d X] [-o role] [ -t TYPE ]
scsetup -E [-cinv] [-C ID] [-d X] [-o role]
scsetup -I [-cinv] [-C ID] [-d X] [-o role]
scsetup -L [-inv] [-C ID] [-d X]
scsetup -X [-inv] [-C ID] [-d X]
scsetup -F [-inv] [-C ID] [-d X]
scsetup -h
-C ID Operate on Context ID.
-c Clear destination device files prior to export/import.
-d X Debug level of X (0-9).
-E Export production volumes.

Assure MIMIX for AIX User Guide v5.2.04.00 331

 Parameters
Parameter Description

-c Clean destination special device file before it is moved

-C ID Operate on Context ID

-i Initialize devices (fill with zeros)

-j Initialize journal containers (fill with zeros)

-L Perform a logform operation on the statemap log

-l Skip forming statemap log (if one exists)

-m Do not spread volume layout if disks are not specified

-M Create new configured logical volumes

-n Do not execute commands. Print commands.

-o Override the volume group or disk group hints in the

configuration with the configured default volume group or disk
group

-R Remove configured logical volumes (except PDFCs and

BSFCs). Any logical volume with true or production data will
not be destroyed.

-s Skip setting or clearing bitmaps for statemap (if there are any)

-v Verbose mode (using this option twice increases verbosity)

-X Delete or clean up device special files from the /dev directory

Notes:

Preparation for Assure MIMIX for AIX data protection.

-F Failover preparation. PDFC LV names are moved to BSFC LV names,
and vice versa.
-i Ignore volume manager errors.
-I Import production volumes.

Removes Assure MIMIX for AIX data protection, allowing direct access to
production data.
-j Initialize COW journal containers (fill with zeros).
-L Perform a logform on the statemap log
(implied with -M operation).
-l Skip forming statemap log (if one exists).
-M Make configured LV's from scratch.
-n Don't execute, just print commands.
-o role Operate on specific role { prod | back }.

Only necessary in a single server configuration.

332 Assure MIMIX for AIX User Guide v5.2.04.00

 -p Post processing during make (-M), skips volume creation.
-r Re-initialize devices (fill with zeros).
-R Remove configured LV's (all except PDFCs and BSFCs).

Any LV with true or production data will not be destroyed.

-s Skip setting/clearing bitmaps for statemap
filters (if there are any).
-t TYPE An exclusive container type to operate on.
Multiple -t specifications are allowed.

NOTE
Type must be of SCRT/container/*, and specified as the associated “Class”
name (see “sclist -hz” for a list).

-v Verbose mode (using this option twice increases verbosity).

-X Delete/Clean-up device special files from /dev.

scrt_ra

Usage
This command is the Restore Agent. It is used to display the available rollback
windows and to create snapshots on the recovery server.

Syntax to display the Available rollback windows

scrt_ra - C<Context ID> -vpe

Current Snap Time:

1528986243 (LFCID: 2272): Thu Jun 14 14:24:03 2018

Available internal rollback windows:

--------------------------------------------------------

Start: 1528986243 (LFCID: 2272): Thu Jun 14 14:24:03 2018

End: 1528985540 (LFCID: 2268): Thu Jun 14 14:12:20 2018

Start: 1528985515 (LFCID: 2252): Thu Jun 14 14:11:55 2018

End: 1528447457 (LFCID: 2250): Fri Jun 8 08:44:17 2018

Start: 1528447429 (LFCID: 2234): Fri Jun 8 08:43:49 2018

End: 1527763394 (LFCID: 2232): Thu May 31 10:43:14 2018

Start: 1527763377 (LFCID: 2216): Thu May 31 10:42:57 2018

End: 1527752985 (LFCID: 2214): Thu May 31 07:49:45 2018

Start: 1527752960 (LFCID: 2196): Thu May 07:49:20 2018

Assure MIMIX for AIX User Guide v5.2.04.00 333

 End: 1527752036 (LFCID: 2194): Thu May 31 07:33:56 2018

Start: 1527752005 (LFCID: 2178): Thu May 31 07:33:25 2018

End: 1527674437 (LFCID: 2146): Wed May 30 10:00:37 2018

Available VFBs:
---------------------------------------------------------
No recorded VFBs.

Available event marks for rollback:

---------------------------------------------------------
Event Name Date/Time (Epoch Time) Description

Event-2 Thu Jun 14 14:21:28 2018 (1528986088)

Event-1 Thu Jun 14 14:13:49 2018 (1528985629)

Syntax to create snapshots

scrt_ra -t <> [-C ID] [-V <>] [-d X] [-fFlLv]
scrt_ra -D <> [-C ID] [-V <>] [-d X] [-fFlLv]
scrt_ra -S <> [-C ID] [-V <>] [-d X] [-fFlLv]
scrt_ra -V <> [-d X] [-aflLv]

Parameters

Parameter Description

-a Restore to alternate devices.

-C Operate on context ID.

-d Debug level of X (0-9).

-D <target date/time> Restore Vdevs to target date/time.

-e Print available Event Marks to restore.

-f Force: Continue even if read journals are already

in place.

-F Restore to raw BS devices (only for Failover

processing.)

-h Display this message.

-l List status of devices.

-L Lock ABA for the duration of the restore.

-p Print valid restore time spans.

-P <path to script> Create Vdevs and run script.

334 Assure MIMIX for AIX User Guide v5.2.04.00

 Parameter Description

-S <target seconds> Restore Vdevs to target time (seconds since Jan 1,

1970).

-t <target LFC number> Restore Vdevs to target LFC number.

-v Verbose.

-V<vfb level> Restore Vdevs to target vfb level. The Tivoli

Storage Manager must be defined in the Assure
MIMIX for AIX configuration before using this
option.

-w Wipe write journals (Vdevs).

-W Wipe write and history journals (Vdevs &

snapshots).

-x Snap history journals (read only snapshots).

-X Snap write journals (write snapshots, a.k.a.

Vdevs).

Assure MIMIX for AIX User Guide v5.2.04.00 335

scrt_rc

Usage
The restore client is an interactive command line interface, or shell, for production
data restore. To enter the shell, type scrt_rc -C<ID> at the unix command prompt on
the recovery (a.k.a. backup) server.

Entering the restore client shell starts a production restore session. Ultimately, this
session should be terminated with either the commit or abort command. Problems
during the restore can be resolved with the recovery command.

Type help at the rc> prompt for all available commands.

NOTE
The -p option the scrt_rc command will not start the shell, but instead will
return with agent status.

Syntax
scrt_rc [-C ID] [-d X] [-p X] [-h[v]] [-v] [-V]
-d Debug level of X (0-9)
-h Help, display this message
-C Operation on Context ID (default is 17)
-p Ping agent X (aba|lca|rs), ref is 0 if up
-v Verbose help
-V Print version

Session restore targets

You can restore to three types of targets during a session with the restore command.
These targets are:

• LFC level

• Date/Time

• Seconds since epoch (Jan 1, 1970)

Session termination
A restore session may be terminated either with an abort or a commit command.
When aborted, all restored devices are brought back to pre-session levels. When
committed, all restored devices remain at the last target of the session.

A commit does not remove any forward or reverse incremental data from the Assure
MIMIX for AIX time line which allows for a subsequent restore to a time after the
committed target, if necessary. In fact, the restore itself is included in the time line
which allows it to be undone.

336 Assure MIMIX for AIX User Guide v5.2.04.00

 Process overview
Assure MIMIX for AIX performs a production data restore by writing reverse block
incremental data directly into the raw Logical Volumes (LVs) of the Production
Volume Set (PVS), rolling those LVs back in time as a single consistency group.
The PVS is treated as a consistency group since it encapsulates the entire storage
footprint of the protected application. The application's referential data integrity is
always maintained.

All block I/O during the restore occurs at the Logical Volume Manager (LVM) layer,
below all file systems and/or databases associated with the protected application. In
Assure MIMIX for AIX, the reverse block incremental data is recorded in odd
numbered LFCs, the Before Image Log File.

Containers (BILFCs), which are also raw LVs and reside on the backup/recovery
server, or in external tape archives, if any.

The length of the restore window is a function of how many BILFCs are available to
Assure MIMIX for AIX, the size of the BILFC, and the average application write
rate. Tape archives are used to extend the restore window.

During a restore, the PVS LVs must be opened exclusively for writing by Assure
MIMIX for AIX. No other application may have the LVs opened for writing. All
associated databases and file systems must be unmounted.

Two agent daemons work together to perform a production restore. On the

production server, the Log Creation Agent (LCA) receives BILFC transmissions
and makes the BILFC writes to the PVS. On the backup/recovery server, the Restore
Server (RS) handles the extraction of LFCs from either the Assured Backup Agent
(ABA) or the Archive Agent (AA) if available, and the transmission of those
BILFCs to LCA.

Prior to a production restore, LCA (scrt_lca) and ABA (scrt_aba) must be running in
daemon mode. If external tape archiving is enabled, AA (scrt_aa) should also be
running in daemon mode. RC (scrt_rc) will spawn RS (scrt_rs) automatically, and
stop RS automatically at the conclusion of the restore.

General procedure
1. Ensure required agent daemons are running.

2. On the production server - Stop/Unmount the corrupted production application

3. On the production server - Unmount file systems [rtumnt -Cx]

4. On the production server - Sync Assure MIMIX for AIX [scconfig -Cx -S]

5. On the recovery server - Execute RC [scrt_rc -Cx]

6. On the production server - Mount file systems [rtmnt -Cx]

7. On the production server - Start/Mount production database

Assure MIMIX for AIX User Guide v5.2.04.00 337

 Procedure notes
1. The rtumnt -Cx command will perform a switch [scconfig -Cx -S]
automatically.

2. One After Image Log File Container (AILFC) may be sent during the restore to
fine tune to the nearest second. BILFCs are optimized for I/O throughput, while
AILFCs maintain individual write fidelity.

3. Backup and recovery server are synonymous.

338 Assure MIMIX for AIX User Guide v5.2.04.00

scrt_vfb

Usage
This command is used to create a virtual full backup.

NOTE
The Tivoli Storage Manager must be defined in the Assure MIMIX for
AIX configuration before using this command.

Syntax
scrt_vfb [-bdDflLnUVrR] [-s <path to validation script>] [ -C ID ]

Parameters

Parameter Description

-b Backup from backing store devices.

-C Operate on Context ID.

-D Don't backup (useful with -d).

-f Force use of existing snaps.

-h Help.

-l Leave snaps/VDevs up when completed.

-L Lock ABA for entire backup.

-U Unlock ABA (If VFB crashed leaving ABA frozen).

-R Release read devices as they complete.

-s Run validation script prior to backup.

-V Create VDevs.

Assure MIMIX for AIX User Guide v5.2.04.00 339

sccfgd_cron_schedule

Usage
This command is used to schedule a virtual full backup.This command manages
entries in cron for Assure MIMIX for AIX Virtual Full Backups (VFB).

NOTE
The Tivoli Storage Manager must be defined in the Assure MIMIX for
AIX configuration before using this command.

Syntax
sccfgd_cron_schedule <Op> <Context_id> [<sched_type>] [<cron_info>]
[<vfb_opts>]

where:
Op -[a|q|d] for (add|query|delete respectively)
sched_type [once|daily|weekly|monthly]

cron_info mm:hh:DoM:MoY:DoW (see man crontab)

where: mm (minutes) 0-59
hh (hours) 0-23
DoM (Day of Month) 1-31
MoY (Month of Year) 1-12
DoW (Day of Week) 0-6 (0=Sun,6=Sat)
vfb_opts scrt_vfb command options:
[-bdDflLnUVrR] [-s <path to validation script>]
see scrt_vfb command documentation

Examples
sccfgd_cron_schedule add 3 daily 15:3:*:*:*
sccfgd_cron_schedule delete 3
sccfgd_cron_schedule query 3

340 Assure MIMIX for AIX User Guide v5.2.04.00

sccfgd_putcfg

Usage
This command is used to load the Assure MIMIX for AIX configuration file into the
Assure MIMIX for AIX ODM by creating and loading a failover context
configuration based on a previously loaded primary context configuration.

Syntax
sccfgd_putcfg primary_context_ID failover_context_ID

Parameters

Parameter Description

primary_context_ID Primary Context ID (an existing context that has been

created for normal operation)

failover_context_ID Failover Context ID (a new context based on the primary

context that will be created for failovers)

-h Display help message

Assure MIMIX for AIX User Guide v5.2.04.00 341

sccfgchk

Usage
This command is used to check a configuration before Assure MIMIX for AIX is
started. Issue this command on each node after the configuration is initialized and
before it is started.

Syntax
sccfgchk-C <Context ID>

Parameters

Parameter Description

-c class Check only listed class (can repeat)

(Use 'sclist -hz' to list possible classes)

-C CTX Run for this context

-d X Debug level of X (0-9)

-h Print this message

-i Check production instance uniqueness only

-s Check file access and sizes

-v Verbose

342 Assure MIMIX for AIX User Guide v5.2.04.00

sztool

Usage
You can use the Sizing Tool (sztool) to calculate configuration values before Assure
MIMIX for AIX is installed. It is also useful to run the tool after Assure MIMIX for
AIX is installed to determine if the number of LFCs or WJ percentage needs to be
adjusted. For more information, refer to Chapter 3, “Using the Sizing Tool to
Calculate LFC Size” on page 41.

Syntax
sztool

Parameters

sztool script
Command Description
Options

sztool If issued for the very first time, the working directory,
diskinfo file and sztool.cfg file are generated. You should
review the diskinfo file and then modify sztool.cfg,
accordingly. You can then re-run sztool.

sztool -c Assigns CDP_Window_Hours a value and run against

existing data log file. Only screen output. Example: sztool
-c24.

sztool -d Generates the /tmp/sztool/diskinfo file. Performed

automatically when you run sztool for the first time.

sztool -g Generates the sztool.cfg file in /tmp/sztool. Performed

automatically when you run sztool for the first time.

sztool -h Prints out a help message.

sztool -l When the log file is created, this command prints out the
calculation results for different LFC sizes based on the
existing log file. For example, sztool -l32 prints out the
results when the LFC size is at 32M. sztool -l16 -l512,
prints out all the calculation results from 32MB to
512MB. You cannot have spaces between -l and the LFC
size number. Only screen output, there is not any delay or
sleep.

sztool -r Assigns Replication_Out_Hours a value and runs against

the existing data log file. Only screen output. For
example: sztool -r24, or sztool -r24 -l2 -l32.

Assure MIMIX for AIX User Guide v5.2.04.00 343

344 Assure MIMIX for AIX User Guide v5.2.04.00
CLI Assure MIMIX HA for AIX
Commands 17

This chapter provides a comprehensive list of Command Line Interface (CLI)

commands for Assure MIMIX HA for AIX.

Command syntax
All commands follow the same basic syntax:
cli.sh [<general options>] <command> [<command options>]
[<name_or_id>]

where:

• cli.sh is the CLI shell script.

• [<general options>] are the supported general options (see General options).

• <command> is the command.

• [<command options>] are the options for the command.

• [<name_or_id>] is the name or ID of a configuration entity (for example, a

node, resource, or application).

General options
The following general options are available:

General Options Description

-c | --config <dir> Specify the configuration directory. The default is./etc.

-h | --help <command> Display the help for <command>.

-T | --socketTimeout Specify the TCP socket timeout in milliseconds. The

<n> default is 0 (infinite).

-v | --verbose Sets the logging level to INFO. If used twice, sets logging
level to DEBUG.

-V | --version Print the product version.

Assure MIMIX for AIX User Guide v5.2.04.00 345

Node commands
See the following for information on each of the node commands:

• deployConfig

• deconfigure

• validateLicense

• startCluster

• showCluster

• stopCluster

• supportSnapshot

deployConfig
Deploy the XML configuration file to the local node. If a node ID is not specified,
an attempt is made to guess it from the local IP addresses.

Syntax
cli.sh [<general options>] deployConfig <file> [<node_id>]

Example
cli.sh -v deployConfig file1 nodeB

deconfigure
Remove the current configuration from the local node.

Syntax
cli.sh [<general options>] deconfigure

Example
cli.sh -v deconfigure

validateLicense
Display license expiration on the local node.

Syntax
cli.sh [<general options>] validateLicense

Example
cli.sh -v validateLicense

346 Assure MIMIX for AIX User Guide v5.2.04.00

 startCluster
Does one of the following:

• If a listener is running, starts cluster services (the Local Administration Daemon

or LAD) on the local node.

• If a listener is not running, produces an error message. The listener must be

started separately using the start_listener.sh script.

Syntax
cli.sh [<general options>] startCluster

Example
cli.sh -v startCluster

showCluster
Outputs a status summary showing the active configuration version, the Global
Administration Daemon (GAD), which is the node that is coordinating the nodes in
the cluster, and the connectivity to the other node in the cluster.

Syntax
cli.sh [<general options>] showCluster

Example
cli.sh -v showCluster

stopCluster
Stop cluster services on the local node, or on all nodes if the allNodes option is
specified.

Syntax
cli.sh [<general options>] stopCluster <command options>

Command Options Description

-a | --allNodes Stop the cluster on all nodes (global shutdown).

Example
cli.sh -v stopCluster -a

supportSnapshot
Retrieves a support snapshot from the node and stores it in a file.

Assure MIMIX for AIX User Guide v5.2.04.00 347

 Syntax
cli.sh [<general options>] supportSnapshot <command option>
<file>

Command Options Description

supportSnapshot Retrieve support snapshot

-d <directory> Directory to hold the snapshot output file (default:

/usr/EchoCluster/tmp)

-H <hostname> Hostname used for output file name (default: the

hostname of the node)

Example
cli.sh supportSnapshot

cli.sh supportSnapshot -d /tmp

cli.sh supportSnapshot -H foo

348 Assure MIMIX for AIX User Guide v5.2.04.00

Application commands
See the following for additional information on the application commands:

• startApplication (see “startApplication” on page 349)

• clearApplication (see “clearApplication” on page 349)

• moveApplication (see “moveApplication” on page 350)

• stopApplication (see “stopApplication” on page 351)

• stopAllLocalApplications (see “stopAllLocalApplications” on page 351)

• setApplicationPolicy (see “setApplicationPolicy” on page 349)

startApplication
Starts the application on the local node.

Syntax
cli.sh [<general options>] startApplication [<command options>]
[<name_or_id>]

Command
Options Description

-C | --noClear Do not clear application resources prior to starting.

Example
cli.sh -C startApplication +m Application-1

clearApplication
Clears errors on all local resources of an application.

Syntax
cli.sh [<general options>] clearApplication [<name_or_id>]

Example
cli.sh -v clearApplication Application-1

setApplicationPolicy
Defines the level at which the application will be managed by the cluster. Possible
values are:

• MAINTAIN_ACTIVE

Assure MIMIX for AIX User Guide v5.2.04.00 349

 Syntax
cli.sh [<general options>] setApplicationPolicy [<command
options>][<name_or_id>] <policy>

Command Options Description

-s | --stopOnFailure Stop all resources when the application fails.

-r | --noRestart Clear all local resources of an application.

To enable stopOnFailure, run the command with the -s command option.

Example
cli.sh -v setApplicationPolicy -s MyApplication MAINTAIN_ACTIVE

INFO: Reading configuration values from etc/node_config.properties

INFO: local cache is up to date, using it

INFO: setting application MyApplication policy to MAINTAIN_ACTIVE SOF

To disable stopOnFailure, run the command without the -s command option.

Example
cli.sh -v setApplicationPolicy MyApplication MAINTAIN_ACTIVE

INFO: Reading configuration values from etc/node_config.properties

INFO: local cache is up to date, using it

INFO: setting application MyApplication policy to MAINTAIN_ACTIVE

moveApplication
Moves an application to the specified node, if possible. This action is carried out
regardless of the autoMove flag.

Syntax
cli.sh [<general options>] moveApplication [<command options>]
[<name_or_id>]

Command Options Description

-n | --targetNode Specifies targetNode <name_or_id>. This is

<name_or_id> required.

350 Assure MIMIX for AIX User Guide v5.2.04.00

 Example
cli.sh -v moveApplication -n nodeB Application-1

stopApplication
Stops an application on the local node by stopping the application’s resources. This
operation implicitly clears the autoStart and autoMove flags, effectively ‘pinning
the application.

Syntax
cli.sh [<general options>] stopApplication [<command options>]
[<nid>]

Command Options Description

-i | -- immediate Don't stop resources when stopping application.

-C | -- noClear Don't clear app resources prior to stopping

Example
cli.sh -v stopApplication Application-1

stopAllLocalApplications
Stops all applications running on this node. Returns 0 on success.

Syntax
cli.sh stopAllLocalApplications [-t <time>]

Command Options Description

-t| --time Time in seconds to wait for each application to stop,

before returning failure. Specify 0 to wait indefinitely
(no timeout)

Example
cli.sh -v stopAllLocalApplications -t 300

showApplication
Prints a clear-text rendering of the status of a single application. If name_or_id is
omitted, the status of all applications is shown.

Syntax
cli.sh [<general options>] showApplication <command options>
[<name_or_id>]

Assure MIMIX for AIX User Guide v5.2.04.00 351

 Command Options Description

-v | --verbose Provides the state of each local application resource.

Example
cli.sh showApplication -v Application-1.

352 Assure MIMIX for AIX User Guide v5.2.04.00

Resource commands
See the following for additional information on the Resource commands:

• startResource (see“startResource” on page 353)

• clearResource (see“clearResource” on page 353)

• showResource (see“showResource” on page 354)

• stopResource (see“stopResource” on page 354)

• showEvents (see “showEvents” on page 354)

• setLogLevel (see “setLogLevel” on page 355)

• performNetDicsovery (see “performNetDiscovery” on page 356)

• performDiscovery (see “performDiscovery” on page 356)

• exit (see “exit” on page 357)

startResource
Starts an individual resource on the local node.

Syntax
cli.sh [<general options>] startResource [<command options>]
[<name_or_id>]

Command
Options Description

-f | --force Performs a forced start.

Examples
cli.sh -v startResource -f Resource-1

clearResource
Clears errors or manual stops on a local resource. If name_or_id is omitted, then all
local resources are cleared.

Syntax
cli.sh [<general options>] clearResource [<name_or_id>]

Example
cli.sh -v clearResource Resource-1

Assure MIMIX for AIX User Guide v5.2.04.00 353

 showResource
Prints a clear-text rendering of the status of a local resource. If name_or_id is
omitted, then all local resources are shown.

Syntax
cli.sh [<general options>] showResource [<name_or_id>]

Example
cli.sh -v showResource Resource-1

stopResource
Stop a local resource. If the noAutoStart flag is specified, the resource will be
unavailable to the cluster until cleared. Otherwise, the cluster may start the resource
if the application requires it. If name_or_id is omitted, then all local resources are
stopped.

Syntax
cli.sh [<general options>] stopResource [<command options>]
[<name_or_id>]

Command
Options Description

-f | --force Disallows the restarting of a resource by marking it

manually stopped.

Example
cli.sh -v stopResource -f Resource-1

showEvents
Dump the local event log.

Syntax
cli.sh [<general options>] showEvents [<command options>]
[<name_or_id>]

354 Assure MIMIX for AIX User Guide v5.2.04.00

 Command Description
Options

time Optional time specification, either in absolute or relative

form. The absolute form is a number of milliseconds
since 1/1/1970. The relative form is -<number><units>,
where:
units can be s, m, H, d, w, M, y. Only events after the
specified time are dumped. If omitted, the entire log is
dumped.

Example
cli.sh -v showEvents -5m

NOTE
If you do not specify a time interval, the entire event log is dumped.

setLogLevel
Modifies the Log4J logging level which is in effect until the listener is restarted.

Syntax
cli.sh [<general options>] setLogLevel [<command options>]

Assure MIMIX for AIX User Guide v5.2.04.00 355

 Command Description
Options

level Log4J logging level. The valid logging levels are:

• FATAL—Severe errors that can lead the application to
abort.

• ERROR—Runtime error or unexpected conditions.

These can be error events that might still allow the
application to continue running.

• WARN—Runtime situations that indicate potentially

harmful situations.

• INFO—Informational events, such as startup and

shutdown status, that highlight the progress of the
application.

• DEBUG— Informational events that you can use to

debug an application. Expect this information to be
written to logs only.

• TRACE—Detailed information about the application.

Expect this information to be written to logs only.

category A Log4J category as displayed in the logfile. If it is

omitted, all categories are affected. Used to log debug and
error messages.

Example
cli.sh -v setLogLevel DEBUG

performNetDiscovery
Perform a network discovery and dump the results. This command must be run
simultaneously on all nodes.

<nid> represents a numerical node ID that must be unique between the nodes
participating in the discovery.

Syntax
cli.sh [<general options>] performNetDiscovery [<nid>]

Example
cli.sh -v performNetDiscovery aix_22

performDiscovery
Discover all other resources and dump the results.

356 Assure MIMIX for AIX User Guide v5.2.04.00

 Syntax
cli.sh [<general options>] performDiscovery

Example
cli.sh -v performDiscovery

exit
Terminate the listener. Resources won't be stopped, and no effort is made to
coordinate with other nodes. If the cluster was active, it will be restored when the
listener is restarted.

Syntax
cli.sh [<general options>] exit

Example
cli.sh -v exit

Assure MIMIX for AIX User Guide v5.2.04.00 357

358 Assure MIMIX for AIX User Guide v5.2.04.00
Integration of PowerHA (HACMP)
with Assure MIMIX for AIX A

This chapter describes:

• “Configuring a highly available Assure MIMIX for AIX/PowerHA

production server environment (option 1)” on page 359
Option 1:

• There are two production nodes with shared disks between them.
• Replication is to a third node that lies outside the cluster.
• Multiple Assure MIMIX for AIX Replication Group configurations are
supported and can be online on different nodes.

• “Configuring highly available production servers - Option 2” on page 386

Option 2:

• There are two production nodes with shared disks between them.
• Replication is to a third node that lies outside the cluster.
• Multiple Assure MIMIX for AIX Replication Group configurations are
supported, however they must be online on the same node.

• “Configuring an Assure MIMIX for AIX/PowerHA production to recovery

server environment (option 3)” on page 408

Option 3:

• There is one production node in the cluster.

• Replication is to the second node in the cluster.
• Multiple Assure MIMIX for AIX Replication Group configurations are
supported.

Configuring a highly available Assure MIMIX for AIX/PowerHA

production server environment (option 1)
An Assure MIMIX for AIX Highly Available (HA) production server
configuration is supported with PowerHA (HACMP). In this setup, the production

Assure MIMIX for AIX User Guide v5.2.04.00 359

 server is highly available under PowerHA with a 2-node cluster (primary and
secondary production servers). The data from the active production server will be
replicated to a single recovery server, which is outside the PowerHA cluster. This
section describes how you configure Assure MIMIX for AIX in a HA production
server environment.

In this mode:

• There are two production nodes with shared disks between them.

• Replication is to a third node that lies outside the cluster.

• A Resource Group can only be moved between the two production nodes, and
the Assure MIMIX for AIX roles of the nodes never changes.

• Multiple Assure MIMIX for AIX Replication Group configurations are

supported and can be online on different nodes.

Assure MIMIX for AIX configuration requirements

Review these guidelines before you configure Assure MIMIX for AIX:

• The file systems protected by Assure MIMIX for AIX should not be
automatically mounted at system restart.

• The file systems protected by Assure MIMIX for AIX should not be mounted or
unmounted when a Resource Group is brought online or offline. The mounting
and unmounting of the protected filesystems will be performed by Assure
MIMIX for AIX.

• Do not use the Assure MIMIX for AIX Enable Automatic Startup feature, as
documented in the User Guide.

• Assure MIMIX for AIX software must be installed on both PowerHA

production nodes and the recovery node.

• All volume groups associated with an Assure MIMIX for AIX configuration
must be enhanced concurrent mode volume groups on both PowerHA
production nodes. Use C-SPOC to create/change the volume group(s), selecting
Fast Disk Takeover or Disk Heart Beat for the Enable Fast Disk Takeover or
Concurrent Access option.

• Assure MIMIX for AIX file containers and the Assure MIMIX for AIX
configuration file systems /usr/scrt/run/c<Primary Context ID> and
/usr/scrt/run/c<Failover ContextID> can co-exist on the same
enhanced concurrent mode volume group(s) that are part of the Assure MIMIX
for AIX configuration. The file systems need to be at least 128MB in size and
must have a separate jfslog, jfs2log, or jfs2 inline log since they will not be part
of the protected file systems.

360 Assure MIMIX for AIX User Guide v5.2.04.00

 By default the Assure MIMIX for AIX File Containers are created on a volume
group (Default VG, selected when using the Replication Group wizard), unless
otherwise specified.

• Assure MIMIX for AIX must be configured with a Service IP address (an alias
address that follows the application when it is moved between nodes) so that the
recovery server can connect to either production server. To configure a Service
IP Address, change the production servers Initial host adapter IP Address to the
Service IP address used by your application. If your application did not use a
Service IP address, create one. The /etc/hosts file on all nodes must contain the
Service IP Address and associated IP label.

Configuring highly available production servers - Option 1

Follow the steps below to configure a Highly Available production server
environment:

NOTE
In the steps below, APPLICATION_RG is used as the name of the
PowerHA Resource Group that contains the application (production)
logical volumes and file systems that would be protected by Assure
MIMIX for AIX. MIMIX_COMMON_RG is used as the name of
PowerHA Resource Group, containing the Assure MIMIX for AIX
configuration. MIMIX_VG is the name of the shared volume group
containing the logical volumes of Assure MIMIX for AIX containers. You
can use any other names to suit your environment. 1 and 17 are used as the
Primary and Failover Context IDs respectively. If 1 and 17 are already
used by another Assure MIMIX for AIX Replication Group configuration,
change these values to next available unique ID values such as 2 and 18.

1. On the primary production server and recovery server, varyonvg all volume
group(s) associated with the Assure MIMIX for AIX configuration.
2. On the primary production server, use PowerHA C-SPOC to create file systems
/usr/scrt/run/c<Primary Context ID> and /usr/scrt/run/c<FailOver Context
ID> with inline logs on one of the shared enhanced concurrent mode volume
groups that contains the production server logical volumes you want protected.
The filesystem must be at least 128 MB in size.

3. On the primary production server, mount the file systems associated with the
Assure MIMIX for AIX configuration.

• mount /usr/scrt/run/c<Primary Context ID>

• mount /usr/scrt/run/c<Failover ContextID>

4. Use the Replication Group wizard to configure the Primary Context.

Refer to the section Chapter 7, “Configuring Replication Groups” on page 107.

Assure MIMIX for AIX User Guide v5.2.04.00 361

 After the creation of the Assure MIMIX for AIX Replication Group
Configuration perform the following steps.

NOTE
You must manually copy and load the Assure MIMIX for AIX
configuration onto the failover production server.

5. On the primary production server, create a file with the Primary Context ID
configuration.

• odmget -q ContextID=<Primary Context ID> SCCuObj

SCCuAttr SCCuRel >/tmp/C<Primary Context ID>.cfg

• Copy this configuration file to /tmp on the Failover Production Server.

6. On the primary production server, create a file with the Failover Context ID
configuration.

• odmget -q ContextID=<Failover Context ID> SCCuObj

SCCuAttr SCCuRel >/tmp/C<Failover Context ID>.cfg

• Copy this configuration file to /tmp on the Failover Production Server.

7. On the failover production server use rthostid to obtain its “HostId”.

/usr/scrt/bin/rthostid

8. On the failover production server edit the production HostId stanza in the
/tmp/C<Primary Context ID>.cfg file. Replace the contents of the
“ObjectAttributeValue” field with the output from the "rthostid"
command.

SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 15
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "6CABA7DF"
ObjectAttributeType = "ulong"
SerialNumber = 15006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

9. On the failover production server edit the backup HostId stanza in the
/tmp/C<Failover Context ID>.cfg file replacing the content of the
“ObjectAttributeValue” field with the output from the “rthostid”
command.

SCCuAttr:
ObjectName = "backup"

362 Assure MIMIX for AIX User Guide v5.2.04.00

 ConfigObjectSerial = 4
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "5FBBC3EF"
ObjectAttributeType = "ulong"
SerialNumber = 4006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 11

10. On the failover production server, use sccfgd_putcfg to load the

configurations onto the node.
• /usr/scrt/bin/sccfgd_putcfg <Primary Context ID>
/tmp/C<Primary Context ID>.cfg
• /usr/scrt/bin/sccfgd_putcfg <Failover Context ID>
/tmp/C<Failover Context ID>.cfg

11. On the primary production server, use /usr/sbin/lvlstmajor to obtain a

list of unused device major numbers:
lvlstmajor

46,50,54,57,64,67,70,73..75,82..93,95...

12. On the failover production server, use /usr/sbin/lvlstmajor to obtain a

list of unused device major numbers:
lvlstmajor

51,54,57,61,65,69,82...

13. On the primary production server, use es_ha_config to configure a device

major number for the Primary Context ID. Choose a device major number that
is the same on both production servers.
es_ha_config <Primary ContextID> [NewMajorNumber]

For example, when you execute:

es_ha_config 1 82

The Primary Context ID is 1, and the new device major number 82, is available
on both production servers.

14. On the failover production server, use es_ha_config to configure a device

major number for the Primary Context ID. Choose a device major number that
is the same on both production servers.
es_ha_config <Primary ContextID> [NewMajorNumber]

For example, when you execute

Assure MIMIX for AIX User Guide v5.2.04.00 363

 es_ha_config 1 82

The Primary Context ID is 1, and the new device major number 82, is available
on both production servers.

15. On the primary production server, unmount the file systems associated with the
Assure MIMIX for AIX configuration.
• unmount /usr/scrt/run/c<Primary Context ID>
• unmount /usr/scrt/run/c<Failover Context ID>

16. On the primary production server, varyoff all volume group(s) associated with
the Assure MIMIX for AIX configuration.

17. On both production servers, the file systems protected by Assure MIMIX for
AIX should not be automatically mounted at system restart. Change the
auto-mount attribute to “no”.

18. On the secondary production server, add the replication group port numbers to
/etc/services.

The port numbers to add can be found in the /etc/services file on the primary
production server.

For example, these port numbers are for primary context id 1 and failover
context id 17:

sc1aba_dchannel 5779/tcp
sc1aba_dchannel 5783/tcp
sc1lca_channel 5780/tcp
sc1lca_dchannel 5784/tcp
sc1aa_channel 5778/tcp
sc1aa_achannel 5782/tcp
sc1ra_channel 5785/tcp
sc1ca_channel 5781/tcp

sc17aba_channel 5787/tcp
sc17aba_dchannel 5791/tcp
sc17lca_channel 5788/tcp
sc17lca_dchannel 5792/tcp
sc17aa_channel 5786/tcp
sc17aa_achannel 5790/tcp
sc17ra_channel 5793/tcp
sc17ca_channel 5789/tcp
19. Before starting Assure MIMIX for AIX on the production server, you must stop
your application and unmount the protected file systems.

364 Assure MIMIX for AIX User Guide v5.2.04.00

 Assure MIMIX for AIX/PowerHA integration requirements
Keep in mind the following Assure MIMIX for AIX/PowerHA integration
requirements:

Application Server—If there are multiple Resource Groups that can failover
independently, there must be multiple Assure MIMIX for AIX Context IDs created,
one for each Resource Group. Likewise, each of these Resource Groups requires
scripts to manage the startup and shutdown of each Assure MIMIX for AIX
ContextID. The Assure MIMIX for AIX start script needs to be placed at the
beginning of the application server startup sequence, before applications are started.
The Assure MIMIX for AIX stop script needs to be executed at the end of the
application server shutdown sequence, after all applications have been stopped
gracefully.

1. On the primary production server, use PowerHA to add or change Application

Controller Scripts. For your convenience, sample start and stop scripts are
provided in the /usr/scrt/samples directory.

Copy the sample Assure MIMIX for AIX start and stop scripts to the location of
your choice and change the values for CONTEXT_ID and
FAILOVER_CONTEXT_ID and insert your application start and stop scripts
where indicated.

For example:

Application Controller Name: App_Controller_C1

Start Script: [/scripts/es_ha_start_script_C1.ksh]
Stop Script: [/scripts/es_ha_stop_script_C1.ksh]
Application Monitor Name(s)
Application startup mode: [background]

See the sample Assure MIMIX for AIX start and stop scripts below.

2. Configure a Service IP Label/Address if one does not already exist.

• Configure HACMP Service IP Labels/Addresses.

– Add a Service IP Label/Address
– Configurable on Multiple Nodes

NOTE
Use the IP Label/Address that was used by the Assure MIMIX for AIX
Replication Group wizard.

3. Application Resource Group Changes

• Enter the Service IP Labels/Addresses

Assure MIMIX for AIX User Guide v5.2.04.00 365

 • Enter the names of all volume groups associated with the Assure MIMIX for
AIX <Primary ContextID> to be varied on when the resource is initially
acquired.

IMPORTANT
The Assure MIMIX for AIX drivers must be loaded before the Assure
MIMIX for AIX protected file systems are mounted or written to. This is
managed during the execution of the Assure MIMIX for AIX startup
process. PowerHA determines which file systems to mount based on the
information provided in the resource group configuration. If no file
systems are specified, PowerHA will mount all file systems in all volume
groups that are defined in the resource group. This scenario is not
preferred for an Assure MIMIX for AIX environment. Assure MIMIX for
AIX should start before the file systems are mounted.

• Enter the file system mount points /usr/scrt/run/c<Primary

Context ID> and /usr/scrt/run/c<Failover Context ID>. This
will force only these file systems to be mounted when the resource group is
acquired.

4. Run HACMP Extended Verification and Synchronization.

5. On the recovery server use rtstart to manually start the Assure MIMIX for AIX
Primary Context ID.
/usr/scrt/bin/rtstart -C<PrimaryContextID>.

6. Start Cluster Services on both production nodes:

• Verify that the volume groups defined in the Resource Group are online in
concurrent mode.
• Verify that the /usr/scrt/run/c<Primary Context ID> and
/usr/scrt/run/c<Failover Context ID> file systems are mounted.
• Verify that all of the Assure MIMIX for AIX protected file systems are
mounted.
• Verify that the Service IP Address is aliased on the Ethernet Network
Interface.
• Verify that Assure MIMIX for AIX is replicating to the recovery server.
View the log files: /var/log/EchoStream/scrt_lca-<Primary
Context ID>.out on the production server and
/var/log/EchoStream/scrt_aba-<Primary Context ID>.out on
the recovery server.

366 Assure MIMIX for AIX User Guide v5.2.04.00

 Sample Assure MIMIX for AIX start script
This section shows a sample Assure MIMIX for AIX start script. The start script
needs to be placed at the beginning of the application server startup sequence,
before applications are started.
Sample Assure MIMIX for AIX Start script
#!/bin/ksh
#****** Modify the CONTEXT_ID (Primary ContextID) and ******
#****** FAILOVER_CONTEXT_ID (Failover ContextID) below ******
#****** to match your environment ######
CONTEXT_ID=1
FAILOVER_CONTEXT_ID=17

# Read Environment and Common Functions

. /usr/scrt/bin/sccfgd_arch

DATE_CMD=$(date +"%Y-%m-%d %T")

RTSTARTLOG=/usr/scrt/log/rtstart_c${CONTEXT_ID}.log
echo "${DATE_CMD}: Starting ${PRODUCT_NAME} ..." > ${RTSTARTLOG}

/usr/scrt/bin/rtattr -C${CONTEXT_ID} -o production -a HostId -v

$(/usr/scrt/bin/rthostid)
/usr/scrt/bin/rtattr -C${FAILOVER_CONTEXT_ID} -o backup -a HostId -v
$(/usr/scrt/bin/rthostid)

LVS=$(odmget -q"ContextID=${CONTEXT_ID} and

ObjectType=SCRT/containers/PDFC and ObjectAttributeName=FileName"
SCCuAttr | \
awk '
{
gsub(/"/,"")
if ($1=="ObjectName")
{
printf("%s\n",$3)
}
}')

for lv in $LVS
do
rm -f /dev/recd$lv
rm -f /dev/rrecd$lv
done

/usr/scrt/bin/rtstart -C${CONTEXT_ID} >> ${RTSTARTLOG} 2>&1

if [[ $? -ne 0 ]]
then
echo "${DATE_CMD}: ${PRODUCT_NAME} startup failed" >>
${RTSTARTLOG} 2>&1
exit 1

Assure MIMIX for AIX User Guide v5.2.04.00 367

 fi

echo "${DATE_CMD}: ${PRODUCT_NAME} startup successful" >>

${RTSTARTLOG} 2>&1

#****** <Insert your application start script here> ******

exit 0

Sample Assure MIMIX for AIX shutdown script

This section shows a sample Assure MIMIX for AIX shutdown script. The
shutdown script needs to be executed at the end of the application server shutdown
sequence, after all applications have been stopped gracefully.
Sample Assure MIMIX for AIX Shutdown script
#!/bin/ksh
#****** <Insert your application stop script here> ******

#****** Modify the CONTEXT_ID (Primary ContextID) below ******

#****** to match your environment ******
CONTEXT_ID=1

# Read Environment and Common Functions

. /usr/scrt/bin/sccfgd_arch
DATE_CMD=$(date +"%Y-%m-%d %T")

RTSTOPLOG=/usr/scrt/log/rtstop_c${CONTEXT_ID}.log
echo "${DATE_CMD}: Shutting down ${PRODUCT_NAME} ..." > $RTSTOPLOG

/usr/scrt/bin/rtumnt -C${CONTEXT_ID} >> $RTSTOPLOG 2>&1

if [[ $? -eq 0 ]]
then
echo "${DATE_CMD}: rtumnt failed" >> $RTSTOPLOG 2>&1
for i in `/usr/scrt/bin/sclist -C${CONTEXT_ID} -f`
do
fuser -k $i
done
/usr/scrt/bin/rtumnt -C${CONTEXT_ID} >> $RTSTOPLOG 2>&1
if [[ $? -ne 0 ]]
then
echo "${DATE_CMD}: rtumnt failure" >> $RTSTOPLOG 2>&1
exit 1
fi
fi

/usr/scrt/bin/rtstop -C ${CONTEXT_ID} -kFv >> $RTSTOPLOG 2>&1

if [[ $? -ne 0 ]]
then
echo "${DATE_CMD}: ${PRODUCT_NAME} shutdown failed" >> $RTSTOPLOG 2>&1
exit 1
fi

echo "${DATE_CMD}: ${PRODUCT_NAME} shutdown successful" >> $RTSTOPLOG 2>&1

exit 0

368 Assure MIMIX for AIX User Guide v5.2.04.00

 Managing Assure MIMIX for AIX in a HA production server
environment
Keep in mind the following when you manage Assure MIMIX for AIX in a HA
production server environment:

• “Changing the Assure MIMIX for AIX configuration” on page 369

• “Changing the Assure MIMIX for AIX configuration after extending a

filesystem in a PowerHA highly available production server environment” on
page 370

• “Updating the Assure MIMIX for AIX configuration on the secondary

production server” on page 371

• “Managing Failover to the recovery server” on page 375

Changing the Assure MIMIX for AIX configuration

Use the Assure MIMIX for AIX portal application’s Change Replication Group
wizard to change the Assure MIMIX for AIX Replication Group configuration. To
add additional logical volumes to be protected, the Resource Groups that are
associated with the Assure MIMIX for AIX Replication Group must be online so
that the new logical volumes can be discovered. Similarly, to add additional
containers, the logical volumes containing the containers must be online and
accessible.

Refer to “Change a replication group’s configuration” on page 130 for more

information.

Note that if the Replication Group is active, the following warning message is
displayed in the Servers panel:

Replication group is currently active. Configuration changes cannot be saved

until the replication group is stopped.

You will be allowed to continue through the Change Replication Group wizard and
make changes, until the Summary panel is displayed, after which the following
warning message will be displayed:

Replication group is currently active. Configuration changes cannot be saved

until the replication group is stopped. Go to the Replication Groups portlet in
the Assure UI portal and stop the replication group. After the replication group
is stopped, return to this wizard and click Finish to save your configuration.

At this time, the Replication Group must be stopped so that the configuration
changes can be deployed to the production and recovery servers. Please do not click
the Finish button or use the Assure UI portal to stop the Replication Group. Use
PowerHA to take the Resource Group offline, as described below:

Assure MIMIX for AIX User Guide v5.2.04.00 369

 1. Use PowerHA to bring Resource Group APPLICATION_RG offline. Wait for
the Resource Group to be offline before proceeding to the next step.

2. On the recovery server execute the following command to stop the Replication
Group:
rtstop -FC <Primary ContextID>

For example:
rtstop -FC1

3. Return to the Summary panel of the Assure UI portaland click the Finish button
when the following message displayed:

The following is a summary of this replication group's configuration. To save

and initialize this configuration on the specified servers, click Finish. To cancel,
click Cancel.

4. After the configuration changes have completed, execute the following

command to start the Replication Group on the recovery server:
rtstart -C <Primary ContextID>

For example:
rtstart -C1

5. On the production server, use PowerHA to bring Resource Group

APPLICATION_RG online.

NOTE
You must manually copy and load the updated Assure MIMIX for AIX
configuration onto the secondary production server.

6. Perform the steps in “Updating the Assure MIMIX for AIX configuration on the
secondary production server” on page 371.

IMPORTANT
This must be done before a resource group is moved from the primary
production server to the secondary production server

Changing the Assure MIMIX for AIX configuration after extending a

filesystem in a PowerHA highly available production server environment
Do not use the AIX command line or the Assure UI portal to extend file systems.
The filesystem must be extended from PowerHA so that the PowerHA environment
on the secondary production server is also updated.

370 Assure MIMIX for AIX User Guide v5.2.04.00

 Changes that you make to a PowerHA Highly Available production server
environment do not automatically propagate to the Assure MIMIX for AIX
configuration.

Perform the following step to update the Assure MIMIX for AIX configuration on
the recovery server:

1. On the primary production server execute the extend_replica_lv command to

update the Assure MIMIX for AIX configuration on the primary production
server and the recovery server.
extend_replica_lv -C <ContextID> -L <PVS LV>

NOTE
You must manually copy and load the updated Assure MIMIX for AIX
configuration onto the secondary production server.

2. Perform the steps in step “Updating the Assure MIMIX for AIX configuration
on the secondary production server” on page 371.

IMPORTANT
This must be done before a resource group is moved from the primary
production server to the secondary production server

Updating the Assure MIMIX for AIX configuration on the secondary

production server
Changes that you make to an Assure MIMIX for AIX Configuration do not
automatically propagate to the secondary PowerHA production server.

Perform the following steps to update the Assure MIMIX for AIX configuration on
the secondary production server.

1. On the secondary production server, delete the Primary and Failover Context
IDs for the replication group that was changed.

To delete the Primary Context ID execute:

/usr/scrt/bin/scsetup -XC1
/usr/scrt/bin/scsetup -RC1
/usr/scrt/bin/sccfgd_delcfg 1

Log file or path (/usr/scrt/archive/sccfgd_delcfg.1.add) does not exist

0518-307 odmdelete: 296 objects deleted.
0518-307 odmdelete: 1292 objects deleted.
0518-307 odmdelete: 178 objects deleted.
0513-083 Subsystem has been deleted.

To delete the Failover Context ID execute:

Assure MIMIX for AIX User Guide v5.2.04.00 371

 /usr/scrt/bin/scsetup -XC17
/usr/scrt/bin/scsetup -RC17
/usr/scrt/bin/sccfgd_delcfg 17

Log file or path (/usr/scrt/archive/sccfgd_delcfg.17.add) does not exist

0518-307 odmdelete: 296 objects deleted.
0518-307 odmdelete: 1292 objects deleted.
0518-307 odmdelete: 178 objects deleted.
0513-083 Subsystem has been deleted.

2. On the primary production server, create a file with the Primary Context ID
configuration.
odmget -q ContextID=1 SCCuObj SCCuAttr SCCuRel >/tmp/C1.cfg

Copy this configuration file to /tmp on the secondary production server.

3. On the primary production server, create a file with the Failover Context ID
configuration.
odmget -q ContextID=17 SCCuObj SCCuAttr SCCuRel >/tmp/C17.cfg

Copy this configuration file to /tmp on the secondary production server.

4. On the secondary production server use rthostid to obtain its HostId.

/usr/scrt/bin/rthostid

Sample output: 9C5FE66FB

5. On the secondary production server edit the production HostId stanza in the
/tmp/C<Primary Context ID>.cfg file. Replace the contents of the
ObjectAttributeValue field with the output from the rthostid command.
SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 15
ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "9C5FE66FB"
ObjectAttributeType = "ulong"
SerialNumber = 15006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

6. On the secondary production server edit the backup HostId stanza in the
/tmp/C<Failover Context ID>.cfg file replacing the content of the
ObjectAttributeValue field with the output from the rthostid command.
SCCuAttr:
ObjectName = "backup"
ConfigObjectSerial = 4

372 Assure MIMIX for AIX User Guide v5.2.04.00

 ObjectType = "SCRT/info/host"
ObjectAttributeName = "HostId"
ObjectAttributeValue = "9C5FE66FB"
ObjectAttributeType = "ulong"
SerialNumber = 4006
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 17

7. On the secondary production server, use sccfgd_putcfg to load the

configurations onto the node.
/usr/scrt/bin/sccfgd_putcfg 1 /tmp/C1.cfg
/usr/scrt/bin/sccfgd_putcfg 17 /tmp/C17.cfg

8. On the primary production server, use es_ha_config to display the device major
number assigned to the Primary Context ID.
/usr/scrt/bin/es_ha_config 1

Current major number: 82

9. On the secondary production server, use es_ha_config to display the device

major number assigned to the Primary Context ID. If the major number
displayed matches the major number displayed on the primary production
server no additional changes are needed, otherwise proceed to step 11.
/usr/scrt/bin/es_ha_config 1

Current major number: 83

10. On the secondary production server, use /usr/sbin/lvlstmajor to obtain a list of

unused device major numbers. If the major number assigned to the Primary
Context ID on the primary production server is available in the displayed
output, proceed to step 11, otherwise proceed to step 12.
lvlstmajor
51,54,57,61,65,69,82...

11. On the secondary production server, use es_ha_config to configure a device

major number for the Primary Context ID. Use the same device major number
that is assigned to the Primary Context ID on the primary production server.
es_ha_config <Primary ContextID> [NewMajorNumber]

For example, execute:

es_ha_config 1 82

The Primary Context ID is 1, and the new device major number 82, is assigned
to the Primary Context ID on both production servers.

12. If the device major number assigned to the Primary Context ID on the primary
production server is not available on the secondary production server, then an

Assure MIMIX for AIX User Guide v5.2.04.00 373

 outage is required to reconfigure the device major number on both the Primary
and Secondary PowerHA Production servers.

374 Assure MIMIX for AIX User Guide v5.2.04.00

 Managing Failover to the recovery server
There are two scenarios for failover from a HA production server to the
recovery server:
• “Unplanned Failover” on page 375

• “Planned Failover” on page 381

NOTE
Both scenarios require that you manually perform Failover operations.

Unplanned Failover
In this scenario, both Highly Available Production servers are unavailable due to a
disaster. For example, an entire site is lost due to a disaster such as a flood or
hurricane.

Unplanned Failover - the Failover Operation

Do not perform a failover until you have validated the integrity of the data on the
recovery server. After performing a failover, Assure MIMIX for AIX cannot be
rolled back to a point in time before the failover. This section provides guidelines to
execute before performing your failover operations.

Validating data integrity

Validating the data integrity of the replica is critical. Prior to performing the failover
operations, validate the data integrity of the replica on the recovery server and
restore it if necessary. To validate the data, first create a snapshot of the replica and
then analyze it with the application itself.

Follow these steps to perform the Unplanned Failover/Resync/Failback operations:

1. On the recovery server, make sure all snapshot filesystems are unmounted
before trying to release the snapshot.
/usr/scrt/bin/rtumnt -C <Context ID>

2. Make sure no snapshots already exist on the recovery server.

/usr/scrt/bin/scrt_ra -C <Context ID> -W

3. On the recovery server, create a Snapshot based on the current redo log and
validate the data integrity. Enter the following command to create a snapshot
based on the current redo log:
/usr/scrt/bin/scrt_ra -C <Primary Context ID> -X

You should see output similar to the following:

Making SNAP /dev/rsnc1lif_bk_1, 66.306
Making SNAP /dev/rsnc1lif_bk_2, 66.310

Assure MIMIX for AIX User Guide v5.2.04.00 375

 Making SNAP /dev/rsnc1lif_bk_3, 66.314
Making SNAP /dev/rsnc1dbmf_bk_1, 66.318
Making SNAP /dev/rsntestlv, 66.450
Making SNAP /dev/rsnrtlog, 66.454
Making SNAP /dev/rtestlv, 66.448
Making SNAP /dev/rrtlog, 66.452
Snap Devs (read only, raw) Minor rj wj Snap level
Vdev level Vdevs (read/write, block)
------------------------------ ----- -- -- --------------
/dev/rsnc1lif_bk_1 304 ON -- 10
0 N/A
/dev/rsnc1lif_bk_2 308 ON -- 10
0 N/A
/dev/rsnc1lif_bk_3 312 ON -- 10
0 N/A
/dev/rsnc1dbmf_bk_1 316 ON -- 10
0 N/A
/dev/rsntestlv 448 ON ON 10
10 /dev/testlv
/dev/rsnrtlog 452 ON ON 10
10 /dev/rtlog

4. Mount the snapshot filesystems on the recovery server. Enter the following
command:
/usr/scrt/bin/rtmnt -C <Context ID>
You should see output similar to the following:
Determining Filesystems to mount...
fsck -fp -y /dev/rtestlv
log redo processing for /dev/rtestlv
syncpt record at 7028
end of log 7028
syncpt record at 7028
syncpt address 7028
number of log records = 1
number of do blocks = 0
number of nodo blocks = 0
/dev/rtestlv (/test): ** Unmounted cleanly - Check
suppressed
Mounting /test...

"To validate the data, analyze it with your application.

"If analysis indicates the data is valid, use rtumnt to unmount the snapshot
filesystems, use scrt_ra to remove the snapshot then proceed to step 6 to
perform a failover to the latest point in the data.
/usr/scrt/bin/rtumnt -C <Context ID>
/usr/scrt/bin/scrt_ra -C <Context ID> -W

"If analysis indicates data corruption, use rtumnt to unmount the snapshot
filesystems, use scrt_ra to remove snapshot.
/usr/scrt/bin/rtumnt -C <Context ID>
/usr/scrt/bin/scrt_ra -C <Context ID> -W

376 Assure MIMIX for AIX User Guide v5.2.04.00

 Use the following command to display the Available rollback windows:
/usr/scrt/bin/scrt_ra -C<Context ID> -vpe

then create a snapshot based on one of the following to locate and validate an
optimal restore point.

– “Creating snapshots based on a specific date and time” on page 199

– “Creating a snapshot based on a specific event mark” on page 202
– “Creating a snapshot based on a specific LFCID” on page 203

Once you have located an optimal restore point, remove the snapshot. Proceed
to step 5 to Backup the replica or to step 6 to perform a failover restore.

5. On the recovery server, if you have TSM or SysBack, backup the replica. This
provides additional data protection by keeping complete copies of the data on
archive media such as tape. Refer to Chapter 13, “Working with Archived Data”
on page 263.

6. On the recovery server, depending on the results from step 4, either rollback the
replica to the validated rollback location before executing a failover or failover
using the current redo log.

To rollback the actual data replica, not a snapshot of the replica, to the validated
point in time, enter the following command:
scrt_ra -C <Primary Context ID> -F [-t | -S | -D].

For example, to restore the replica to a previously validated LFC:

scrt_ra -C <Primary Context ID> -F -t 70250

For example, to restore the replica to a previously validated epoch time

(1169584788 seconds from Jan. 1, 1970):
scrt_ra -C <Primary Context ID> -F -S 1169584788

For example, to restore the replica to a previously validated date and time:
scrt_ra -C <Primary Context ID> -F -D "05/15/09 09:33:40"

For example, to restore the replica to a previously validated event mark

(1389727288 which is the event mark Epoch Time):
scrt_ra -C <Primary Context ID> -F -S 1389727288

7. On the recovery server, failover the replication group, execute:

rtdr -C <Primary Context ID> failover

Assure MIMIX for AIX User Guide v5.2.04.00 377

 NOTE
At this point the configured recovery server has become the new
production server and the configured production server has become the
new recovery server.

8. On the new production server, start your application.

NOTE
At this point your application is running on the new production server and
both configured production servers are down. When one or both
configured production servers come online, Power HA will start and bring
the Resource Groups online on one of the configured production servers.

9. On the configured production server, use PowerHa Stop Cluster Services to

unmanage the resource groups.

Stop now, on system restart or both select [now]

Stop Cluster Services on these nodes select [both nodes]

Select an Action on Resource Groups select [Unmanage Resource Groups]

10. On the configured production server stop your application.

Unplanned Failover -the Resync Operation

A resync operation is required when the Production Volumes and Recovery Replica
Volumes diverge. This occurs after a failover to the recovery server.

When the application is started on the new production server the updates to the
Replica Volumes result in a divergence from the data on the new recovery server.

11. On the new recovery server, execute the resync command to start replication on
the new recovery server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

Answer “y” to the “Do you wish to” questions:

scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

12. On the new recovery server verify that the resync process completed.

Example:

378 Assure MIMIX for AIX User Guide v5.2.04.00

 -- Failover Context ID <Failover ContextID> is enabled and ready
for re-sync. ---

13. On the new production server, execute the resync command to start replication
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

14. On the new production server verify that the resync process completed.

Example:
--- System re-sync is activated. ---

NOTE
At this point your application is running on the new production server and
data is being replicated to the new recovery server.

IMPORTANT
Important: If the failover from the production server to the recovery server
was necessary because all protected data was lost on the production server,
then the data must be restored to the production server before doing a
failback.

15. On the new production server, use the scconfig command to resync all protected
data from the new production server to the new recovery server.
/usr/scrt/bin/scconfig -B -G -C <Failover Context ID>

Unplanned Failover - the Failback Operation

16. Before performing the failback operation, ensure that you stop your application
on the new production server.

17. On the new production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.
/usr/scrt/bin/rtumnt -C<FailoverContextID>

18. On the new production server verify that the protected file systems are
unmounted and synchronization of data has successfully completed.

Example:
Determining Filesystems to unmount...
Unmounting /dev/lvFS_1_C1 from /FS_1_C1...
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

Assure MIMIX for AIX User Guide v5.2.04.00 379

 19. On the new production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<FailoverContextID>

20. On the new production server verify that the synchronization of data has
successfully completed.

Example:
No mounted filesystems
Sync: transferring any current LFC data to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.
Stopping scrt_lca................
Unloading Assure MIMIX DR for AIX Production Server Drivers

21. On the new recovery server execute the failback command to start the failback
process. Wait for failback to successfully complete before performing failback
on the new production server.
/usr/scrt/bin/rtdr -qC <Primary Context ID> failback

22. On the new recovery server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Production Server Drivers are already
loaded for Context ID 1.
Starting scrt_lca
fsck -fp -y /dev/rlvFS_1_C1
The current volume is: /dev/lvFS_1_C1
Primary superblock is valid.
Mounting /FS_1_C1...
--- Primary Context ID <1> is enabled. ---

23. On the new production server execute the failback command to start the
failback process. Wait for failback to successfully complete before starting your
application.
/usr/scrt/bin/rtdr -qC <Failover Context ID> failback

24. On the new production server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Recovery Server Drivers are already
loaded for Context ID 1.
Starting scrt_aba
--- Primary Context ID <1> is enabled. ---

380 Assure MIMIX for AIX User Guide v5.2.04.00

 NOTE
At this point the production and recovery servers have been returned back
to their original roles and replication is active.

25. On the production server start your application.

26. Use PowerHa Start Cluster Services to manage the resource groups.

Start now, on system restart or both select [both]

Start Cluster Services on these nodes select [both nodes]

Manage Resource Groups select [Automatically]

NOTE
This concludes the Unplanned Failover Operations (Failover, Resync, and
Failback).

Planned Failover
In this scenario, the administrator has a scheduled maintenance period and switches
operations that run on the production server to the designated recovery server.

Follow these steps to perform the Planned Failover, Resync and Failback
operations:

Planned Failover - the Failover Operation

Perform the following steps for a planned failover:

1. Use PowerHa Stop Cluster Services to unmanage the resource groups.

Stop now, on system restart or both select [now]

Stop Cluster Services on these nodes select [both nodes]

Select an Action on Resource Groups select [Unmanage Resource Groups]

2. On the production server stop your application.

3. On the production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.

4. On the production server verify that the synchronization of data has successfully
completed.

Example:
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

Assure MIMIX for AIX User Guide v5.2.04.00 381

 5. On the production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<PrimaryContextID>

6. On the production server verify that the synchronization of data has successfully
completed.

Example:
All data has been synchronized to the Recovery Server.
Stopping scrt_lca..............
Unloading Assure MIMIX DR for AIX Production Server Drivers

7. On the recovery server execute the failover command to initiate the failover
process:
/usr/scrt/bin/rtdr -C <Primary Context ID> failover

Answer “y” to the “Do you wish to” questions:

scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

On the recovery server verify that the failover process completed.

Example:
--- Failover Context ID <Failover ContextID> is enabled. ---

NOTE
At this point the configured recovery server has become the new
production server and the configured production server has become the
new recovery server.

8. On the new production server start your application.

NOTE
At this point your application is running on the new production server and
replication is not active. Perform the resync operation to start replication.

Planned Failover - the Resync Operation

A resync operation is required when the Production Volumes and Recovery Replica
Volumes diverge. This occurs after a failover to the recovery server.

382 Assure MIMIX for AIX User Guide v5.2.04.00

 When the application is started on the recovery server the updates to the Replica
Volumes result in a divergence from the data on the production server.

9. On the new recovery server, execute the resync command to start replication on
the new recovery server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

Answer “y” to the “Do you wish to” questions:

scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

10. On the new recovery server verify that the resync process completed.

Example:
-- Failover Context ID <Failover ContextID> is enabled and ready
for re-sync. ---

11. On the new production server, execute the resync command to start replication
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

12. On the new production server verify that the resync process completed.

Example:
--- System re-sync is activated. ---

NOTE
At this point your application is running on the new production server and
data is being replicated to the new recovery server. To return the
production and recovery server back to their original roles, perform the
failback operation.

Planned Failover - the Failback Operation

13. Before performing the failback operation, ensure that you stop your application
on the new production server.

14. On the new production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.
/usr/scrt/bin/rtumnt -C<FailoverContextID>

15. On the new production server verify that the protected file systems are
unmounted and synchronization of data has successfully completed.

Assure MIMIX for AIX User Guide v5.2.04.00 383

 Example:
Determining Filesystems to unmount...
Unmounting /dev/lvFS_1_C1 from /FS_1_C1...
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

16. On the new production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<FailoverContextID>

17. On the new production server verify that the synchronization of data has
successfully completed.

Example:
No mounted filesystems
Sync: transferring any current LFC data to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.
Stopping scrt_lca................
Unloading Assure MIMIX DR for AIX Production Server Drivers

18. On the new recovery server execute the failback command to start the failback
process. Wait for failback to successfully complete before performing failback
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> failback

19. On the new recovery server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Production Server Drivers are already
loaded for Context ID 1.
Starting scrt_lca
fsck -fp -y /dev/rlvFS_1_C1
The current volume is: /dev/lvFS_1_C1
Primary superblock is valid.
Mounting /FS_1_C1...
--- Primary Context ID <1> is enabled. ---

20. On the new production server execute the failback command to start the
failback process. Wait for failback to successfully complete before starting your
application.
/usr/scrt/bin/rtdr -qC <Failover Context ID> failback

21. On the new production server verify that the failback process completed.

Example:

384 Assure MIMIX for AIX User Guide v5.2.04.00

 Assure MIMIX DR for AIX Recovery Server Drivers are already
loaded for Context ID 1.
Starting scrt_aba
--- Primary Context ID <1> is enabled. ---

NOTE
At this point the production and recovery servers have been returned back
to their original roles and replication is active.

22. On the production server start your application.

23. Use PowerHa Start Cluster Services to manage the resource groups.

Start now, on system restart or both select [both]

Start Cluster Services on these nodes select [both nodes]

Manage Resource Groups select [Automatically]

NOTE
This concludes the Planned Failover Operations (Failover, Resync and
Failback).

Configuring a highly available Assure MIMIX for AIX

production server in a PowerHA environment (option 2)
An Assure MIMIX for AIX Highly Available (HA) production server configuration
is supported with PowerHA (HACMP). In this setup, the production server is highly
available under PowerHA with a 2-node cluster (primary and secondary production
servers). The data from the active production server will be replicated to a single
recovery server, which is outside the PowerHA cluster. This section describes how
you configure Assure MIMIX for AIX in a HA production server environment.

In this mode:

• There are two production nodes with shared disks between them.

• Replication is to a third node that lies outside the cluster.

• A Resource Group can only be moved between the two production nodes, and
the Assure MIMIX for AIX roles of the nodes never changes.

• Multiple Assure MIMIX for AIX Replication Group configurations are

supported however they must be online on the same node.

Assure MIMIX for AIX configuration requirements

Review these guidelines before you configure Assure MIMIX for AIX:

Assure MIMIX for AIX User Guide v5.2.04.00 385

 • The file systems protected by Assure MIMIX for AIX should not be
automatically mounted at system restart.

• The file systems protected by Assure MIMIX for AIX should not be mounted or
unmounted when a Resource Group is brought online or offline. The mounting
and unmounting of the protected filesystems will be performed by Assure
MIMIX for AIX.

• Do not use the Assure MIMIX for AIX Enable Automatic Startup feature, as
documented in the User Guide.

• Assure MIMIX for AIX software must be installed on both PowerHA

production nodes and the recovery node.

• All volume groups associated with an Assure MIMIX for AIX configuration
must be enhanced concurrent mode volume groups on both PowerHA
production nodes. Use PowerHA C-SPOC to create/change the volume
group(s), selecting Fast Disk Takeover or Disk Heart Beat for the Enable Fast
Disk Takeover or Concurrent Access option.

• Assure MIMIX for AIX file containers and the Assure MIMIX for AIX
configuration file systems /usr/scrt/run/c<Primary Context ID> and
/usr/scrt/run/c<Failover ContextID> can co-exist on the same
enhanced concurrent mode volume group(s) that are part of the Assure
MIMIX for AIX configuration. The file systems need to be at least 128MB in
size and must have a separate jfslog, jfs2log, or jfs2 inline log since they will
not be part of the protected file systems.

By default the Assure MIMIX for AIX File Containers are created on a volume
group (Default VG, selected when using the Replication Group wizard), unless
otherwise specified.

• Assure MIMIX for AIX must be configured with a Service IP address (an alias
address that follows the application when it is moved between nodes) so that the
recovery server can connect to either production server. To configure a Service
IP Address, change the production servers Initial host adapter IP Address to the
Service IP address used by your application. If your application did not use a
Service IP address, create one. The /etc/hosts file on all nodes must contain the
Service IP Address and associated IP label.

• Before starting Assure MIMIX for AIX on the production server, you must stop
your application and unmount the protected file systems.

Configuring highly available production servers - Option 2

To configure Highly Available production servers:

386 Assure MIMIX for AIX User Guide v5.2.04.00

 NOTE
In the steps below, APPLICATION_RG is used as the name of the
PowerHA Resource Group that contains the application (production)
logical volumes and file systems that would be protected by Assure
MIMIX for AIX. MIMIX_COMMON_RG is used as the name of
PowerHA Resource Group, containing the Assure MIMIX for AIX
configuration. MIMIX_VG is the name of the shared volume group
containing the logical volumes of Assure MIMIX for AIX containers. You
can use any other names to suit your environment. 1 and 17 are used as the
Primary and Failover Context IDs respectively. If 1 and 17 are already
used by another Assure MIMIX for AIX Replication Group configuration,
change these values to next available unique ID values such as 2 and 18.

1. On the primary production server, the secondary production server and the
recovery server, install the Assure MIMIX for AIX software.

2. On the primary production server, use PowerHA to add Resource Group

MIMIX_COMMON_RG to the PowerHA configuration with the primary and
secondary Production Servers as its participating nodes with the following
Policies:

• Startup Policy: Online On Home Node Only

• Fallover Policy: Fallover To Next Priority Node In The List
• Fallback Policy: Never Fallback

This Resource Group will be used control the configuration required by Assure
MIMIX for AIX.

3. On the primary production server, use PowerHA C-SPOC to create a shared

enhanced concurrent mode volume group MIMIX_VG on both production
servers.

4. On the primary production server, use PowerHA C-SPOC to create file system
/usr/scrt/run/common with an inline log on volume group MIMIX_VG. The
filesystem must be at least 128 MB in size.

5. On the primary production server, use PowerHA C-SPOC to create file systems
/usr/scrt/run/c<Primary Context ID> and /usr/scrt/run/c<FailOver Context
ID> with inline logs on one of the shared enhanced concurrent mode volume
groups that contains the production server logical volumes you want protected.
The filesystem must be at least 128 MB in size.

6. On the primary production server, use PowerHA to add a Service IP

Label/Address resource to the PowerHA configuration. Also add the Service IP
Address and associated IP label to the /etc/hosts file on the primary and
secondary production servers, the recovery server and the Windows PC that will
be used to create the Assure MIMIX for AIX Replication Group configuration.

Assure MIMIX for AIX User Guide v5.2.04.00 387

 7. On the primary production server, use PowerHA to add the Service IP
Label/Address, Volume Group MIMIX_VG and Filesystem
/usr/scrt/run/common resources to Resource Group MIMIX_COMMON_RG.

8. On the primary production server, use PowerHA to verify and synchronize the
cluster configuration.

9. On the primary production server, bring Resource Group

MIMIX_COMMON_RG online.

10. On the primary production server, mount the filesystems associated with the
Assure MIMIX for AIX configuration.

• mount /usr/scrt/run/c1 <Primary Context ID>

• mount /usr/scrt/run/c17 <Failover ContextID>

As in this example, 1 and 17 are the configured Primary and Failover Context
IDs, respectively.

11. On the recovery server, create volume group MIMIX_VG, which holds the
logical volumes for the Assure MIMIX for AIX containers and the volume
group(s) that will contain the replicated data. Please specify the AUTO ON
option for the volume groups so that they are varied on automatically at system
startup.

12. Use the Replication Group wizard to create the Assure MIMIX for AIX
replication group configuration.

Refer to the section “Configuring Replication Groups” on page 107. Make sure
to add a portal connection, using the Service IP Address as the Host or IP
Address for the production server. This will allow the Assure UI portal to
connect to either the primary or secondary production server, depending on
which server is online. While configuring the replication IP addresses, select the
option to use server IP addresses for replication. This will set the Service IP
address as the replication IP address.

Also, while configuring the production server logical volumes you want
protected, do not select the logical volumes for file systems
/usr/scrt/run/c<primary context id>,
/usr/scrt/run/c<failover context id> and
/usr/scrt/run/common.

After the creation of the Assure MIMIX for AIX replication group
configuration, perform the following steps.

13. On the primary production server, verify that filesystem /usr/scrt/run/common

is mounted, then execute es_ha_production_setup, as shown below, to link the
Assure MIMIX for AIX ODMs /etc/objrepos/SCCuAttr, /etc/objrepos/SCCuObj
and /etc/objrepos/SCCuRel to /usr/scrt/run/common/ and create the required
subsystem resource controller (SRC) entries:

388 Assure MIMIX for AIX User Guide v5.2.04.00

 • es_ha_production_setup <Primary Context ID> <Failover
Context ID>

For example:

• /usr/scrt/bin/es_ha_production_setup 1 17

14. On the secondary production server, execute es_ha_production_setup, as

shown below, to link the Assure MIMIX for AIX ODMs
/etc/objrepos/SCCuAttr, /etc/objrepos/SCCuObj and /etc/objrepos/SCCuRel to
/usr/scrt/run/common/ and create the required subsystem resource controller
(SRC) entries:
• es_ha_production_setup <Primary Context ID> <Failover
Context ID>

For example:
• /usr/scrt/bin/es_ha_production_setup 1 17

15. On the primary production server, execute the following command to get the
Instance value for the Primary Context ID.
• rtattr -C<Primary Context ID> -o production -a Instance

The ObjectAttributeValue shown in the output is the Instance number.

For example when you execute:

• /usr/scrt/bin/rtattr –C1 -o production -a Instance

SCCuAttr:
ObjectName = "production"
ConfigObjectSerial = 15
ObjectType = "SCRT/info/host"
ObjectAttributeName = "Instance"
ObjectAttributeValue = "4"
ObjectAttributeType = "uint"
SerialNumber = 150011
ObjectNlsIndex = 0
SC_reserved = 0
ContextID = 1

In the above case, the Instance number for Context ID 1 is 4.

16. On the primary production server, execute the following command to obtain the
device major number used by Primary ContextID:
• es_ha_config <Primary Context ID>

For example:
• /usr/scrt/bin/es_ha_config 1
Current major number: 73

Assure MIMIX for AIX User Guide v5.2.04.00 389

 17. On the secondary production server, use lvlstmajor to obtain a list of
unused device major numbers:

NOTE
The Assure MIMIX for AIX major numbers must match on both the
primary and secondary production servers. In case of a change in the major
number on one of the production servers, the other must also be updated
with the same number to match. Otherwise, Assure MIMIX for AIX will
not function properly.

For example:
• /usr/sbin/lvlstmajor
46,50,54,57,64,67,70,73..75,82..93,95...

NOTE
If the device major number used by Primary Context ID 1 on the primary
production server is displayed in the list of unused device major numbers
on the secondary production server, move Resource Group
MIMIX_COMMON_RG to the secondary production server.

If the device major number used by the Primary Context ID on the primary
production server is not displayed in the list of unused device major numbers on
the secondary production server, use the lvlstmajor AIX command on both
production servers to find a matching unused device major number that is
unused on both production servers. Then, update the configuration on the
primary production server by running the following command before moving
Resource Group MIMIX_COMMON_RG to the secondary production server.

For example:
• /usr/scrt/bin/es_update_major <Primary Context ID>
<Instance> <New Major Number>

18. On the secondary production server, verify that resource group

MIMIX_COMMON_RG is online and filesystem /usr/scrt/run/common is
mounted, then execute the following command to update the HostId attribute in
the RecoverNow configuration.
• es_ha_update_hostid <Primary Context ID> < Failover
Context ID >

For example:
• /usr/scrt/bin/es_ha_update_hostid 1 17

19. On the secondary production server, verify that resource group

MIMIX_COMMON_RG is online and filesystem /usr/scrt/run/common is

390 Assure MIMIX for AIX User Guide v5.2.04.00

 mounted, then execute the following command to update the HostId attribute in
the RecoverNow configuration.
• es_update_major <Primary Context ID> <Instance> <Major
Number>

For example:
• /usr/scrt/bin/es_update_major 1 4 73

Note that the instance in the above command was obtained from step 15 from
the primary production server.

20. On the secondary production server, add the replication group port numbers to
/etc/services.

The port numbers to add can be found in the /etc/services file on the primary
production server.

For example, these port numbers are for primary context id 1 and failover
context id 17:

sc1aba_dchannel 5779/tcp
sc1aba_dchannel 5783/tcp
sc1lca_channel 5780/tcp
sc1lca_dchannel 5784/tcp
sc1aa_channel 5778/tcp
sc1aa_achannel 5782/tcp
sc1ra_channel 5785/tcp
sc1ca_channel 5781/tcp

sc17aba_channel 5787/tcp
sc17aba_dchannel 5791/tcp
sc17lca_channel 5788/tcp
sc17lca_dchannel 5792/tcp
sc17aa_channel 5786/tcp
sc17aa_achannel 5790/tcp
sc17ra_channel 5793/tcp
sc17ca_channel 5789/tcp
21. On the secondary production server, use PowerHA to move resource group
MIMIX_COMMON_RG to the primary production server.

22. On the primary production server, unmount the filesystems associated with the
Assure MIMIX for AIX configuration.

• unmount /usr/scrt/run/c1 <Primary Context ID>

• unmount /usr/scrt/run/c17 <Failover ContextID>

23. On the primary production server, use PowerHA to add the filesystem resources
/usr/scrt/run/c1 and /usr/scrt/run/c17 to the resource group

Assure MIMIX for AIX User Guide v5.2.04.00 391

 APPLICATION_RG, which contains the volume group and the logical volumes
you want protected.

NOTE
The PowerHA Resource Group attribute Filesystems (empty is ALL for
volume groups specified) cannot be empty, because the file systems
protected by Assure MIMIX for AIX must be mounted by Assure MIMIX
for AIX.

If there are filesystems on the volume groups specified in the PowerHA

Resource Group that are not being protected by Assure MIMIX for AIX, those
filesystems will not be mounted by Assure MIMIX for AIX; add the mount
points of those filesystems which should be mounted when the resource group is
acquired.

24. On the primary production server, use PowerHA to add or change Application
Controller Scripts. For your convenience, sample start and stop scripts are
provided in the /usr/scrt/samples directory.

Copy the sample Assure MIMIX for AIX start and stop scripts to the location of
your choice and change the values for CONTEXT_ID and
FAILOVER_CONTEXT_ID and insert your application start and stop scripts
where indicated.

For example:

Application Controller Name: App_Controller_C1

Start Script: [/scripts/es_ha_start_script_C1.ksh]
Stop Script: [/scripts/es_ha_stop_script_C1.ksh]
Application Monitor Name(s)
Application startup mode: [background]

See the sample Assure MIMIX for AIX start and stop scripts below.
25. On the primary production server, use PowerHA to Add Parent/Child
Dependency between resource groups, as follows: MIMIX_COMMON_RG as
the Parent Resource Group and the APPLICATION_RG as the Child Resource
Group.

26. On the primary production server, use PowerHA to add Online on the Same
Node Dependency between resource groups MIMIX_COMMON_RG,
APPLICATION_RG and any other resource groups associated with Assure
MIMIX for AIX.

27. On the primary production server, use PowerHA to verify and synchronize the
cluster configuration.

28. On the recovery server use rtstart –C<Primary Context ID> to

manually start the Assure MIMIX for AIX primary context ID.

392 Assure MIMIX for AIX User Guide v5.2.04.00

 For example:
• rtstart –C1

29. On the primary production server, bring resource group APPLICATION_RG

online.

Sample Assure MIMIX for AIX start script

The Assure MIMIX for AIX start script needs to be placed at the beginning of the
application server startup sequence, before applications are started.
#!/bin/ksh
#****** Modify the CONTEXT_ID (Primary ContextID) and ******
#****** FAILOVER_CONTEXT_ID (Failover ContextID) below ******
#****** to match your environment ######
CONTEXT_ID=1
FAILOVER_CONTEXT_ID=17

# Read Environment and Common Functions

. /usr/scrt/bin/sccfgd_arch

DATE_CMD=$(date +"%Y-%m-%d %T")

RTSTARTLOG=/usr/scrt/log/rtstart_c${CONTEXT_ID}.log
echo "${DATE_CMD}: Starting ${PRODUCT_NAME} ..." > ${RTSTARTLOG}

/usr/scrt/bin/rtattr -C${CONTEXT_ID} -o production -a HostId -v

$(/usr/scrt/bin/rthostid)
/usr/scrt/bin/rtattr -C${FAILOVER_CONTEXT_ID} -o backup -a HostId -v
$(/usr/scrt/bin/rthostid)

LVS=$(odmget -q"ContextID=${CONTEXT_ID} and

ObjectType=SCRT/containers/PDFC and ObjectAttributeName=FileName"
SCCuAttr | \
awk '
{
gsub(/"/,"")
if ($1=="ObjectName")
{
printf("%s\n",$3)
}
}')

for lv in $LVS
do
rm -f /dev/recd$lv
rm -f /dev/rrecd$lv
done

/usr/scrt/bin/rtstart -C${CONTEXT_ID} >> ${RTSTARTLOG} 2>&1

if [[ $? -ne 0 ]]

Assure MIMIX for AIX User Guide v5.2.04.00 393

 then
echo "${DATE_CMD}: ${PRODUCT_NAME} startup failed" >>
${RTSTARTLOG} 2>&1
exit 1
fi

echo "${DATE_CMD}: ${PRODUCT_NAME} startup successful" >>

${RTSTARTLOG} 2>&1

#****** <Insert your application start script here> ******

exit 0

Sample Assure MIMIX for AIX stop script

The Assure MIMIX for AIX stop script needs to be executed at the end of the
application server shutdown sequence, after all applications have been stopped
gracefully.
#!/bin/ksh
#****** <Insert your application stop script here> ******

#****** Modify the CONTEXT_ID (Primary ContextID) below ******

#****** to match your environment ******
CONTEXT_ID=1

# Read Environment and Common Functions

. /usr/scrt/bin/sccfgd_arch
DATE_CMD=$(date +"%Y-%m-%d %T")

RTSTOPLOG=/usr/scrt/log/rtstop_c${CONTEXT_ID}.log
echo "${DATE_CMD}: Shutting down ${PRODUCT_NAME} ..." > $RTSTOPLOG

/usr/scrt/bin/rtumnt -C${CONTEXT_ID} >> $RTSTOPLOG 2>&1

if [[ $? -eq 0 ]]
then
echo "${DATE_CMD}: rtumnt failed" >> $RTSTOPLOG 2>&1
for i in `/usr/scrt/bin/sclist -C${CONTEXT_ID} -f`
do
fuser -k $i
done
/usr/scrt/bin/rtumnt -C${CONTEXT_ID} >> $RTSTOPLOG 2>&1
if [[ $? -ne 0 ]]
then
echo "${DATE_CMD}: rtumnt failure" >> $RTSTOPLOG 2>&1
exit 1
fi
fi

/usr/scrt/bin/rtstop -C ${CONTEXT_ID} -kFv >> $RTSTOPLOG 2>&1

if [[ $? -ne 0 ]]
then
echo "${DATE_CMD}: ${PRODUCT_NAME} shutdown failed" >> $RTSTOPLOG 2>&1
exit 1
fi

394 Assure MIMIX for AIX User Guide v5.2.04.00

 echo "${DATE_CMD}: ${PRODUCT_NAME} shutdown successful" >> $RTSTOPLOG 2>&1
exit 0

Managing Assure MIMIX for AIX in a HA production server

environment
Keep in mind the following when you manage Assure MIMIX for AIX in a HA
production server environment:

• “Changing the Assure MIMIX for AIX configuration” on page 395

• “Changing the Assure MIMIX for AIX Configuration after extending a

filesystem in a PowerHA highly available production server environment” on
page 396

• “Other topics to consider before making configuration changes” on page 397

• “Managing Failover to the recovery server” on page 398

Changing the Assure MIMIX for AIX configuration

Use the Assure MIMIX for AIX portal application’s Change Replication Group
wizard to change the Assure MIMIX for AIX Replication Group configuration. To
add additional logical volumes to be protected, the Resource Groups that are
associated with the Assure MIMIX for AIX Replication Group must be online so
that the new logical volumes can be discovered. Similarly, to add additional
containers, the logical volumes containing the containers must be online and
accessible.

Refer to “Change a replication group’s configuration” on page 130 for more

information.

Note that if the Replication Group is active, the following warning message is
displayed in the Servers panel:

Replication group is currently active. Configuration changes cannot be saved

until the replication group is stopped.

You will be allowed to continue through the Change Replication Group wizard and
make changes, until the Summary panel is displayed, after which the following
warning message will be displayed:

Replication group is currently active. Configuration changes cannot be saved

until the replication group is stopped. Go to the Replication Groups portlet in
the Assure UI portal and stop the replication group. After the replication group
is stopped, return to this wizard and click Finish to save your configuration.

At this time, the Replication Group must be stopped so that the configuration
changes can be deployed to the production and recovery servers. Please do not click

Assure MIMIX for AIX User Guide v5.2.04.00 395

 the Finish button or use the Assure UI portal to stop the Replication Group. Use
PowerHA to take the Resource Group offline, as described below:

1. Use PowerHA to bring Resource Group APPLICATION_RG offline. Wait for

the Resource Group to be offline before proceeding to the next step.

2. On the recovery server execute the following command to stop the Replication
Group:

rtstop -FC <Primary ContextID>

For example:

rtstop -FC1

3. Return to the Summary panel of the Assure UI portal and click the Finish button
when the following message displayed:

The following is a summary of this replication group's configuration. To save

and initialize this configuration on the specified servers, click Finish. To cancel,
click Cancel.

4. After the configuration changes have completed, execute the following

command to start the Replication Group on the recovery server:

rtstart -C <Primary ContextID>

For example:

rtstart -C1

5. On the production server, use PowerHA to bring Resource Group

APPLICATION_RG online.

Changing the Assure MIMIX for AIX Configuration after extending a

filesystem in a PowerHA highly available production server environment
Do not use the AIX command line or the Assure UI portal to extend file systems.
The filesystem must be extended from PowerHA so that the PowerHA environment
on the secondary production server is also updated.

Changes that you make to a PowerHA Highly Available production server

environment do not automatically propagate to the Assure MIMIX for AIX
configuration.

Perform the following step to update the Assure MIMIX for AIX configuration on
the recovery server:

On the primary production server execute the extend_replica_lv command to

update the Assure MIMIX for AIX configuration on the primary production
server and the recovery server.
extend_replica_lv -C <ContextID> -L <PVS LV>

396 Assure MIMIX for AIX User Guide v5.2.04.00

 Other topics to consider before making configuration changes
• “Support for LVM commands when the Assure MIMIX for AIX drivers are
loaded” on page 153

• “Extending a protected file system beyond the limit of the region (block) size”
on page 224

Assure MIMIX for AIX User Guide v5.2.04.00 397

 Managing Failover to the recovery server
There are two scenarios for failover from a HA production server to the
recovery server:
• “Unplanned failover” on page 398

• “Planned Failover” on page 404

NOTE
Both scenarios require that you manually perform Failover operations.

Unplanned failover
In this scenario, both Highly Available Production servers are unavailable due to a
disaster. For example, an entire site is lost due to a disaster such as a flood or
hurricane.

Unplanned failover -failover operations

Do not perform a failover until you have validated the integrity of the data on the
recovery server. After performing a failover, Assure MIMIX for AIX cannot be
rolled back to a point in time before the failover. This section provides guidelines to
execute before performing your failover operations.

Validating data integrity

Validating the data integrity of the replica is critical. Prior to performing the failover
operations, validate the data integrity of the replica on the recovery server and
restore it if necessary. To validate the data, first create a snapshot of the replica and
then analyze it with the application itself.

Follow these steps to perform the Unplanned Failover/Resync/Failback operations:

1. On the recovery server, make sure all snapshot filesystems are unmounted
before trying to release the snapshot.
/usr/scrt/bin/rtumnt -C <Context ID>

2. Make sure no snapshots already exist on the recovery server.

/usr/scrt/bin/scrt_ra -C <Context ID> -W

3. On the recovery server, create a Snapshot based on the current redo log and
validate the data integrity. Enter the following command to create a snapshot
based on the current redo log:
/usr/scrt/bin/scrt_ra -C <Primary Context ID> -X

You should see output similar to the following:

Making SNAP /dev/rsnc1lif_bk_1, 66.306
Making SNAP /dev/rsnc1lif_bk_2, 66.310

398 Assure MIMIX for AIX User Guide v5.2.04.00

 Making SNAP /dev/rsnc1lif_bk_3, 66.314
Making SNAP /dev/rsnc1dbmf_bk_1, 66.318
Making SNAP /dev/rsntestlv, 66.450
Making SNAP /dev/rsnrtlog, 66.454
Making SNAP /dev/rtestlv, 66.448
Making SNAP /dev/rrtlog, 66.452
Snap Devs (read only, raw) Minor rj wj Snap level
Vdev level Vdevs (read/write, block)
------------------------------ ----- -- -- --------------
/dev/rsnc1lif_bk_1 304 ON -- 10
0 N/A
/dev/rsnc1lif_bk_2 308 ON -- 10
0 N/A
/dev/rsnc1lif_bk_3 312 ON -- 10
0 N/A
/dev/rsnc1dbmf_bk_1 316 ON -- 10
0 N/A
/dev/rsntestlv 448 ON ON 10
10 /dev/testlv
/dev/rsnrtlog 452 ON ON 10
10 /dev/rtlog

4. Mount the snapshot filesystems on the recovery server. Enter the following
command:
/usr/scrt/bin/rtmnt -C <Context ID>
You should see output similar to the following:
Determining Filesystems to mount...
fsck -fp -y /dev/rtestlv
log redo processing for /dev/rtestlv
syncpt record at 7028
end of log 7028
syncpt record at 7028
syncpt address 7028
number of log records = 1
number of do blocks = 0
number of nodo blocks = 0
/dev/rtestlv (/test): ** Unmounted cleanly - Check
suppressed
Mounting /test...

"To validate the data, analyze it with your application.

"If analysis indicates the data is valid, use rtumnt to unmount the snapshot
filesystems, use scrt_ra to remove the snapshot then proceed to step 6 to
perform a failover to the latest point in the data.
/usr/scrt/bin/rtumnt -C <Context ID>
/usr/scrt/bin/scrt_ra -C <Context ID> -W

"If analysis indicates data corruption, use rtumnt to unmount the snapshot
filesystems, use scrt_ra to remove snapshot.
/usr/scrt/bin/rtumnt -C <Context ID>
/usr/scrt/bin/scrt_ra -C <Context ID> -W

Assure MIMIX for AIX User Guide v5.2.04.00 399

 Use the following command to display the Available rollback windows:
/usr/scrt/bin/scrt_ra -C<Context ID> -vpe

then create a snapshot based on one of the following to locate and validate an
optimal restore point.

– “Creating snapshots based on a specific date and time” on page 199

– “Creating a snapshot based on a specific event mark” on page 202
– “Creating a snapshot based on a specific LFCID” on page 203

Once you have located an optimal restore point, remove the snapshot. Proceed
to step 5 to Backup the replica or to step 6 to perform a failover restore.

5. On the recovery server, if you have TSM or SysBack, backup the replica. This
provides additional data protection by keeping complete copies of the data on
archive media such as tape. Refer to Chapter 13, “Working with Archived Data”
on page 263.

6. On the recovery server, depending on the results from step 4, either rollback the
replica to the validated rollback location before executing a failover or failover
using the current redo log.

To rollback the replica to the validated rollback location from step 4, use:
scrt_ra -C <Primary Context ID> -F [-t | -S | -D].

For example, to restore the replica to a previously validated LFC:

scrt_ra -C <Primary Context ID> -F -t 70250

For example, to restore the replica to a previously validated epoch time

(1169584788 seconds from Jan. 1, 1970):
scrt_ra -C <Primary Context ID> -F -S 1169584788

For example, to restore the replica to a previously validated date and time:
scrt_ra -C <Primary Context ID> -F -D "05/15/09 09:33:40"

For example, to restore the replica to a previously validated event mark

(1389727288 which is the event mark Epoch Time):
scrt_ra -C <Primary Context ID> -F -S 1389727288

7. On the recovery server, failover the replication group, execute:

rtdr -C <Primary Context ID> failover

NOTE
At this point the configured recovery server has become the new
production server and the configured production server has become the
new recovery server.

400 Assure MIMIX for AIX User Guide v5.2.04.00

 8. On the new production server, start your application.

NOTE
At this point your application is running on the new production server and
both configured production servers are down. When one or both
configured production servers come online, Power HA will start and bring
the Resource Groups online on one of the configured production servers.

9. On the configured production server, use PowerHa Stop Cluster Services to

unmanage the resource groups.

Stop now, on system restart or both select [now]

Stop Cluster Services on these nodes select [both nodes]

Select an Action on Resource Groups select [Unmanage Resource Groups]

10. On the configured production server stop your application.

Unplanned failover -resync operation

A resync operation is required when the Production Volumes and Recovery Replica
Volumes diverge. This occurs after a failover to the recovery server.

When the application is started on the new production server the updates to the
Replica Volumes result in a divergence from the data on the new recovery server.

11. On the new recovery server, execute the resync command to start replication on
the new recovery server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

Answer “y” to the “Do you wish to” questions:

scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

12. On the new recovery server verify that the resync process completed.

Example:
-- Failover Context ID <Failover ContextID> is enabled and ready
for re-sync. ---

13. On the new production server, execute the resync command to start replication
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

Assure MIMIX for AIX User Guide v5.2.04.00 401

 14. On the new production server verify that the resync process completed.

Example:
--- System re-sync is activated. ---

NOTE
At this point your application is running on the new production server and
data is being replicated to the new recovery server.

IMPORTANT
Important: If the failover from the production server to the recovery server
was necessary because all protected data was lost on the production server,
then the data must be restored to the production server before doing a
failback.

15. On the new production server, use the scconfig command to resync all protected
data from the new production server to the new recovery server.
/usr/scrt/bin/scconfig -B -G -C <Failover Context ID>

Unplanned failover -failback operation

16. Before performing the failback operation, ensure that you stop your application
on the new production server.

17. On the new production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.
/usr/scrt/bin/rtumnt -FC<FailoverContextID>

18. On the new production server verify that the protected file systems are
unmounted and synchronization of data has successfully completed.

Example:
Determining Filesystems to unmount...
Unmounting /dev/lvFS_1_C1 from /FS_1_C1...
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

19. On the new production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<FailoverContextID>

20. On the new production server verify that the synchronization of data has
successfully completed.

Example:

402 Assure MIMIX for AIX User Guide v5.2.04.00

 No mounted filesystems
Sync: transferring any current LFC data to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.
Stopping scrt_lca................
Unloading Assure MIMIX DR for AIX Production Server Drivers

21. On the new recovery server execute the failback command to start the failback
process. Wait for failback to successfully complete before performing failback
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> failback

22. On the new recovery server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Production Server Drivers are already
loaded
for Context ID 1.
Starting scrt_lca
fsck -fp -y /dev/rlvFS_1_C1
The current volume is: /dev/lvFS_1_C1
Primary superblock is valid.
Mounting /FS_1_C1...
--- Primary Context ID <1> is enabled. ---

23. On the new production server execute the failback command to start the
failback process. Wait for failback to successfully complete before starting your
application.
/usr/scrt/bin/rtdr -C <Failover Context ID> failback

24. On the new production server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Recovery Server Drivers are already
loaded for Context ID 1.
Starting scrt_aba
--- Primary Context ID <1> is enabled. ---

NOTE
At this point the production and recovery servers have been returned back
to their original roles and replication is active.

25. On the production server start your application.

26. Use PowerHa Start Cluster Services to manage the resource groups.

Start now, on system restart or both select [both]

Start Cluster Services on these nodes select [both nodes]

Assure MIMIX for AIX User Guide v5.2.04.00 403

 Manage Resource Groups select [Automatically]

End of Unplanned Failover/Resync/Failback operations

Planned Failover
In this scenario, the administrator has a scheduled maintenance period and switches
operations that run on the production server to the designated recovery server.

Follow these steps to perform the Planned Failover/Resync/Failback operations:

Planned Failover - failover operation

Perform the following steps for a planned failover:

1. Use PowerHa Stop Cluster Services to unmanage the resource groups.

Stop now, on system restart or both select [now]

Stop Cluster Services on these nodes select [both nodes]

Select an Action on Resource Groups select [Unmanage Resource Groups]

2. On the production server stop your application.

3. On the production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.

4. On the production server verify that the synchronization of data has successfully
completed.

Example:
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

5. On the production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<PrimaryContextID>

6. On the production server verify that the synchronization of data has successfully
completed.

Example:
All data has been synchronized to the Recovery Server.
Stopping scrt_lca..............
Unloading Assure MIMIX DR for AIX Production Server Drivers

7. On the recovery server execute the failover command to initiate the failover
process:
/usr/scrt/bin/rtdr -C <Primary Context ID> failover

404 Assure MIMIX for AIX User Guide v5.2.04.00

 Answer “y” to the “Do you wish to” questions:
scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

On the recovery server verify that the failover process completed.

Example:
--- Failover Context ID <Failover ContextID> is enabled. ---

NOTE
At this point the configured recovery server has become the new
production server and the configured production server has become the
new recovery server.

8. On the new production server start your application.

NOTE
At this point your application is running on the new production server and
replication is not active. Perform the resync operation to start replication.

Planned failover - resync operation

A resync operation is required when the Production Volumes and Recovery Replica
Volumes diverge. This occurs after a failover to the recovery server.

When the application is started on the recovery server the updates to the Replica
Volumes result in a divergence from the data on the production server.

9. On the new recovery server, execute the resync command to start replication on
the new recovery server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

Answer “y” to the “Do you wish to” questions:

scsetup: You have requested failover processing.
scsetup: Do you wish to continue? [y|n]

!!! RESET WARNING !!!

You have requested an LCA reset.
All outstanding sealed LFCs will be dumped.
Do you wish to do this? [y|n]

10. On the new recovery server verify that the resync process completed.

Assure MIMIX for AIX User Guide v5.2.04.00 405

 Example:
-- Failover Context ID <Failover ContextID> is enabled and ready
for re-sync. ---

11. On the new production server, execute the resync command to start replication
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> resync

12. On the new production server verify that the resync process completed.

Example:
--- System re-sync is activated. ---

NOTE
At this point your application is running on the new production server and
data is being replicated to the new recovery server. To return the
production and recovery server back to their original roles, perform the
failback operation.

Planned failover - failback operation

13. Before performing the failback operation, ensure that you stop your application
on the new production server.

14. On the new production server, use rtumnt to unmount the protected file systems,
transfer any current LFC data to the recovery server.
/usr/scrt/bin/rtumnt -FC<FailoverContextID>

15. On the new production server verify that the protected file systems are
unmounted and synchronization of data has successfully completed.

Example:
Determining Filesystems to unmount...
Unmounting /dev/lvFS_1_C1 from /FS_1_C1...
Sync: transferring current LFC to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.

16. On the new production server, use rtstop to unmount the protected file systems,
transfer any current LFC data to the recovery server and unload the Assure
MIMIX for AIX production server drivers.
/usr/scrt/bin/rtstop -FSC<FailoverContextID>

17. On the new production server verify that the synchronization of data has
successfully completed.

Example:

406 Assure MIMIX for AIX User Guide v5.2.04.00

 No mounted filesystems
Sync: transferring any current LFC data to Recovery Server
Waiting for synchronization of data to complete.
All data has been synchronized to the Recovery Server.
Stopping scrt_lca................
Unloading Assure MIMIX DR for AIX Production Server Drivers

18. On the new recovery server execute the failback command to start the failback
process. Wait for failback to successfully complete before performing failback
on the new production server.
/usr/scrt/bin/rtdr -C <Primary Context ID> failback

19. On the new recovery server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Production Server Drivers are already
loaded
for Context ID 1.
Starting scrt_lca
fsck -fp -y /dev/rlvFS_1_C1
The current volume is: /dev/lvFS_1_C1
Primary superblock is valid.
Mounting /FS_1_C1...
--- Primary Context ID <1> is enabled. ---

20. On the new production server execute the failback command to start the
failback process. Wait for failback to successfully complete before starting your
application.
/usr/scrt/bin/rtdr -C <Failover Context ID> failback

21. On the new production server verify that the failback process completed.

Example:
Assure MIMIX DR for AIX Recovery Server Drivers are already
loaded for Context ID 1.
Starting scrt_aba
--- Primary Context ID <1> is enabled. ---

NOTE
At this point the production and recovery servers have been returned back
to their original roles and replication is active.

22. On the production server start your application.

23. Use PowerHa Start Cluster Services to manage the resource groups.

Start now, on system restart or both select [both]

Start Cluster Services on these nodes select [both nodes]

Assure MIMIX for AIX User Guide v5.2.04.00 407

 Manage Resource Groups select [Automatically]

End of Planned Failover/Resync/Failback operations

Configuring an Assure MIMIX for AIX/PowerHA production to

recovery server environment (option 3)
This section describes the following configuration:

Option 3:

• There is one production node in the cluster.

• Replication is to the second node in the cluster.
• Multiple Assure MIMIX for AIX Replication Group configurations are
supported.

This purpose of this section:

• Have PowerHA for AIX monitor an Assure MIMIX for AIX context. PowerHA
for AIX will monitor the LCA and ABA Assure MIMIX for AIX agents and
provides notification in the event of failure.

• If the Assure MIMIX for AIX production server fails, provide the ability to
failover Assure MIMIX for AIX and the users application to the recovery server
after verifying the Replica data.

• Provide the ability to control Assure MIMIX for AIX by manipulating the
location and status of the PowerHA for AIX resource groups.

Prerequisites
Before you begin, keep in mind the following:

• Assure MIMIX for AIX must be operational and configured with Primary and
Failover contexts.

• scconfigd must be running on the Assure MIMIX for AIX production and
recovery servers.

• Starting Assure MIMIX for AIX and the associated user applications in
/etc/inittab is not recommended. If the production server fails and the user
applications are brought up on the recovery server, it would not be desirable to
have them start when the production server is restored to service.

Overview of the failover process

If the Production_Server resource group fails it will not automatically move to the
recovery node because it is anti-collocated, low priority with the Recovery_Server
resource group.

408 Assure MIMIX for AIX User Guide v5.2.04.00

 Not doing a automatic Failover allows the creation of a snapshot to validate the
Replica data and to restore the Replica to a point in time if required. The
Recovery_Server resource group will have to be brought offline before the
Production_Server resource group can be brought online on the recovery server.

When the Production_Server resource group is brought online on the recovery node
it executes the rtdr -C <Primary Context ID> failover command. When the
Production_Server resource group is brought offline (on the recovery server), after
the recovery node becomes available, it will send the rtdr -C <Primary Context ID>
resync command to the recovery node before stopping.

There may be special cases where you would delay bringing the Production_Server
resource group offline on the recovery server. Normally, this would mean that no
data is being synchronized to the production server. In that case, you can manually
execute the rtdr -C <Primary Context ID> resync command on the production
server. This starts the ABA but it will not be monitored by PowerHA for AIX.

If the Recovery_Server resource group fails it will not move, because there is only
one node in the participating node list.

Ensure that you have the Recovery_Server resource group online to prevent an
automatic failover of the Production_Server resource group to the recovery server.

Sequence to manually bring the resource groups online

1. Bring the Recovery_Server resource group online on the recovery node.

2. Bring the Production_Server resource group online on the recovery node.

Sequence to manually bring the resource groups offline

1. Bring the Production_Server Resource Group offline on the recovery node.

2. Bring the Recovery_Server resource group offline on the recovery node.

Planned Failover procedure

1. Bring the Production_Server resource group offline on the recovery node.

2. Bring the Recovery_Server resource group offline on the recovery node.

3. Bring the Production_Server resource group online on the recovery node.

Unplanned Failover procedure

1. Create a snapshot to validate the Replica data and restore the Replica to a
validated point in time, if required. Refer to “Creating snapshots based on a
specific date and time” on page 199 for information on creating snapshots.

Assure MIMIX for AIX User Guide v5.2.04.00 409

 Refer to “Performing a Failover restore” on page 302 for information on how to
restore the Replica to a validated point in time.

2. Bring the Recovery_Server resource group offline on the recovery node.

3. Bring the Production_Server resource group online on the recovery node.

Failback procedure
1. Move the Production_Server resource group to the recovery node.

2. Bring the Recovery_Server resource group online on the recovery node.

PowerHA for AIX configuration

Note the following for the example Assure MIMIX for AIX configuration:

• Performed using PowerHA for AIX 6.1.0.7

• Names used such as, Cluster Nodes, resource groups are arbitrary. The
integrator can choose to use any names.

• Topology configuration for networks, communication interfaces and devices is

not shown in this example because it is environment specific.

• Notification scripts are not provided and are the responsibility of the integrator.

• The implementation of the user application in this example is a suggestion and

could be done differently at the integrator’s preference.

• Has a Primary Context ID of 85 and Failover Context ID of 850.

The following Assure MIMIX for AIX scripts are provided for the PowerHA for
AIX configuration. These scripts require parameters -C <Primary Context ID> and
for the first two scripts optionally -P if called from the Production_Server resource
group. These scripts will log to "/usr/scrt/log" if the "HACMP Log File Parameters"
have "Debug Level" set to "high".
/usr/scrt/bin/production_failback_acquire
/usr/scrt/bin/production_failover_release
/usr/scrt/bin/ABA_Monitor
/usr/scrt/bin/LCA_Monitor

410 Assure MIMIX for AIX User Guide v5.2.04.00

Sample PowerHA Configuration
Configure HACMP Nodes:
Production
Recovery

Configure Resource Groups:

Resource Group Name Production_Server
Participating Nodes Production Recovery]
Startup Policy Online On Home Node Only
Fallover Policy Fallover To Next Priority Node In The List
Fallback Policy Never Fallback

Resource Group Name Recovery_Server

Participating Nodes [Recovery]
Startup Policy Online On Home Node Only
Fallover Policy Fallover To Next Priority Node In The List
Fallback Policy Never Fallback

Configure Online on Different Nodes Dependency

High Priority Resource Group(s) [Recovery_Server]
Low Priority Resource Group(s) [Production_Server]

Configure HACMP Application Servers

Server Name Production_85
Start Script [/users_path_name/Production_Server_Start]
Stop Script [/users_path_name/Production_Server_Stop]
Application Monitor LCA_Monitor_85 Monitor_85

Server Name Recovery_85

Start Script [/usr/scrt/bin/production_failback_acquire -C <Primary Context ID>]
Stop Script [/usr/scrt/bin/production_failover_release -C <Primary Context ID>]
Application Monitor ABA_Monitor_85

Assure MIMIX for AIX User Guide v5.2.04.00 411

Example for Production_Server_Start script
#!/bin/ksh
###############################################################################
#
# Name: Production_Server_Start
#
# Arguments: None
#
# Returns: 0 - success
#
# Environment: None
###############################################################################

###############################################################################
# Main Entry Point
################################################################################

PROGNAME=${0##*/}
[[ ${VERBOSE_LOGGING} == high ]] &&
{
rm -f /tmp/${PROGNAME}.out
exec 1> /tmp/${PROGNAME}.out
exec 2>&1
PS4='[${PROGNAME}][${LINENO}]'
set -x
}
printf "$(date) ******** Begin ${PROGNAME} ********\n"
/usr/scrt/bin/production_failback_acquire -C <Primary Context ID> -P
if ((${?}!=0))
then
printf "$(date) Production Server start failed.\n"
exit 1
fi
printf "$(date) Production Server start successful.\n"

-> Insert application start script here <-

if ((${?}!=0))
then
printf "$(date) MIMIX_DR_for_AIX_85_Application_Start failed.\n"
exit 1
fi
printf "$(date) MIMIX_DR_for_AIX_85_Application_Start successful.\n"
################################################################################

412 Assure MIMIX for AIX User Guide v5.2.04.00

Example for Production_Server_Stop script
#!/bin/ksh
###############################################################################
#
# Name: Production_Server_Stop
#
# Arguments: None
#
# Returns: 0 - success
#
# Environment: None
###############################################################################

###############################################################################
# Main Entry Point
###############################################################################

PROGNAME=${0##*/}
[[ ${VERBOSE_LOGGING} == high ]] &&
{
rm -f /tmp/${PROGNAME}.out
exec 1> /tmp/${PROGNAME}.out
exec 2>&1
PS4='[${PROGNAME}][${LINENO}]'
set -x
}
printf "$(date) ******** Begin ${PROGNAME} ********\n"

-> Insert application stop script here <-

if ((${?}!=0))
then
printf "$(date) MIMIX_DR_for_AIX_85_Application_Stop failed.\n"
exit 1
fi
printf "$(date) MIMIX_DR_for_AIX_85_Application_Stop successful.\n"
/usr/scrt/bin/production_failover_release -C <Primary Context ID> -P
if ((${?}!=0))
then
printf "$(date) Production Server stop failed.\n"
exit 1
fi
printf "$(date) Production Server stop successful.\n"
###############################################################################

Assure MIMIX for AIX User Guide v5.2.04.00 413

Configure Custom Application Monitors:
Monitor Name LCA_Monitor_85
Application Server(s) to Monitor Production_85
Monitor Mode [Long-running monitoring]
Monitor Method [/usr/scrt/bin/LCA_Monitor -C <Primary Context ID>]
Monitor Interval [180]
Hung Monitor Signal [9]
Stabilization Interval [900]
Restart Count [0]
Restart Interval [0]
Action on Application Failure [notify]
Notify Method [/users_path_name/LCA_85_Notify]

Note: The value for "Stabilization Interval" depends on the time required
to reset the LFCs on Failover. This depends on the number of LFCs
on the Recovery Server and the system performance. With 20,000
LFCs it could typically take up to 15 minutes.

Monitor Name ABA_Monitor_85

Application Server(s) to Monitor Recovery_85
Monitor Mode [Long-running monitoring]
Monitor Method [/usr/scrt/bin/ABA_Monitor -C <Primary Context ID>]
Monitor Interval [180]
Hung Monitor Signal [9]
Stabilization Interval [900]
Restart Count [0]
Restart Interval [0]
Action on Application Failure [notify]
Notify Method [/users_path_name/ABA_85_Notify]

Monitor Name Monitor_85

Application Server(s) to Monitor Application_85
Monitor Mode [Long-running monitoring]
Monitor Method [/users_path_name/ MIMIX_DR_for_AIX_Application_Monitor]
Monitor Interval [60]
Hung Monitor Signal [9]
Stabilization Interval [900]
Restart Count [0]
Restart Interval [0]
Action on Application Failure [notify]
Notify Method [/users_path_name/App_85_Notify]

414 Assure MIMIX for AIX User Guide v5.2.04.00

Change/Show All Resources and Attributes for a Resource Group
Resource Group Name Production_Server
Participating Nodes (Default Node Priority) Production Recovery
Application Servers [Production_85]

Resource Group Name Recovery_Server

Participating Nodes (Default Node Priority) Recovery
Application Servers [Recovery_85]

HACMP Log File Parameters:

Node Name Production
Debug Level high
Formatting options for hacmp.out Standard

HACMP Log File Parameters:

Node Name Recovery
Debug Level high
Formatting options for hacmp.out Standard

Assure MIMIX for AIX User Guide v5.2.04.00 415

416 Assure MIMIX for AIX User Guide v5.2.04.00
Installing X11 for the Sizing Tool
B

To run the GUI version of the Sizing Tool, you need to install X11 software on
your laptop and configure the X11 software to allow access from the remote AIX
node. Actual sizing data will be collected by the backend Sizing Tool scripts on
the AIX node.

1. Install Cygwin/X. For details, refer to Chapter 2 - Setting Up Cygwin/X in the

following document: https://x.cygwin.com/docs/ug/cygwin-x-ug.pdf.

2. Download the setup-x86_64.exe file from Cygwin. Double click to launch

the installer.

3. Select X11 packages from the listing screen. Search for X11 and select
xorg-server, xinit, xlaunch, openssh and any other packages you prefer.

4. When the installation finishes, run C:\cygwin64\bin\xlaunch with the

following selections.

On the Display Settings screen, select Multiple Windows.

Assure MIMIX for AIX User Guide v5.2.04.00 417

 On the Session type screen, Select either Start no client or Start a program.

On the Start program screen, select Start program on this computer and select
xterm as the local program.

On the Extra settings screen, select Disable access control.

418 Assure MIMIX for AIX User Guide v5.2.04.00

 Click Next to complete the configuration.

5. Run the Environment Setup on the AIX backend node (which will be the
production node).

6. After installation on the laptop, define the following settings on the AIX
backend node:

• export DISPLAY = 10.22.28.43:0.0 (the IP Address of your laptop).

Assure MIMIX for AIX User Guide v5.2.04.00 419

 • export PATH = $PATH:/usr/java8_64/bin.

• Add the java location to the PATH env.

420 Assure MIMIX for AIX User Guide v5.2.04.00

PDFPrint 2