HP B6960-90078 manual HP-UX Example, Solaris Example, Tru64, 508

Disaster Recovery

Disk Delivery Disaster Recovery of an UNIX Client

•If the system that will be backed up has application processes active at low run levels, establish a state of minimal activity (modified init 1 run level) and enter the single user mode to prevent errors after recovery (see “Consistent and Relevant Backup” on page 444). Consult your operating system documentation for details.

HP-UX Example	1.	Move some kill links from /sbin/rc1.d to /sbin/rc0.d and
		complement the changes for the boot-up section. The kill links
		include the basic services that would otherwise be suspended by
		moving to run level 1, and they are needed for the backup. For an
		example, see Appendix A, “Disaster Recovery: Move Kill Links on
		HP-UX 11.x,” on page A-25.
	2.	Ensure that rpcd is configured on the system (configure the
		variable RPCD=1 within the file /etc/rc.config.d/dce).
		This prepares the system so that it enters the state of minimal
		activity. The state can be characterized as follows:
		— Init-1 (FS_mounted, hostname_set, date_set,
		syncer_running)
		— Network must be running
		— The following processes should also be running: inetd, rpcd,
		swagentd
Solaris Example	1.	Move the rpc kill link from /etc/rc1.d to /etc/rc0.d and
		complement the change for the boot-up section. The kill links
		include the basic services that would otherwise be suspended by
		moving to run level 1, and they are needed for the backup.
	2.	Ensure that rpcbind is configured on the system.
		This prepares the system so that it enters the state of minimal
		activity. The state can be characterized as follows:
		— Init 1
		— Network must be running
		— The following processes should also be running: inetd,
		rpcbind.
Tru64	—	If the system is powered down, boot up the system and enter the
		System Reference Manual (SRM) console (the firmware console).
		Execute the following command from the SRM console to enter the

508 Chapter 10