“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/start_mxws.sh
>>/var/log/EchoStream/mxws_start_stop.log 2>&1”
.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.
-
Using the cat command, determine the entry for the protected application in the /etc/inittab file.
-
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.
-
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.
Example:
Jan 03 11:18:06 sccfgd_boot
LoadingMIMIX DR for AIX context 1
MountingMIMIX DR for AIX file system /xyz1
The current volume is: /dev/l
vxyz1Primary superblock is valid.
MountingMIMIX 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.
LoadingMIMIX DR for AIX context 4
ERROR: Filesystem /xyz3 is mounted, cannot start!!!
Context 4 initialization failure !!!