On the server (10.10.10.4):
mkdir -p /var/opt/ignite/recovery/archives/client_host
chown bin:bin /var/opt/ignite/recovery/archives/client_host
/etc/exports:
/var/opt/ignite/clients -anon=2
/var/opt/ignite/recovery/archives/client_host -anon=2,access=client_host
#exportfs -av
/etc/hosts:
10.10.10.2 client_host
#time /opt/ignite/bin/make_net_recovery -x inc_entire=vg00 -x exclude=/var/DAILY_SAVED -s 10.10.10.4
SHELL>dbprofile -dn test -sip <Server_IP_Address> -cip <Client_IP_address> -gip <Gateway_IP_address> -m <subnet_mask> -b /opt/ignite/boot/nbp.efi
SHELL>dbprofile — this lists the boot profiles.
SHELL>lanboot -dn test
kill -9 `ps -aef | grep 'processname' | grep -v grep | awk '{print $2}'`
Probably files being deleted but still opened by some application.
lsof -P -n +L1
lsof -P -n | grep -E -e "(path inode|deleted)"
$ mysqldump -u root -p dbname >~/db_name.sql
$ mysql -u root -pmypassword
Welcome to the MySQL monitor. Commands end with ; or g.
Your MySQL connection id is 812
Server version: 5.1.20-beta-log FreeBSD port: mysql-server-5.1.20
Type ‘help;’ or ‘h’ for help. Type ‘c’ to clear the buffer.
mysql> create database dbname_copy
mysql> use dbname_copy
mysql> source ~/db_name.sql
crontab -l | sed -e "s/^\([^ ]*\) [0-9]* \(.*#change-enabled\)/\1`/home/user/slow-hour` \2/" | crontab -
source
#! /bin/ksh
#
# oracle Startup script for start oracle database server
#
case $1 in
‘start’)
echo -n $”Starting oracle”
su – oracle -c “ORACLE_SID=SID lsnrctl start”
su – oracle -c “ORACLE_SID=SID sqlplus ‘/as sysdba’ @/etc/startsid.sql”
;;
‘stop’)
echo -n $”Stopping oracle”
su – oracle -c “ORACLE_SID=SID sqlplus ‘/as sysdba’ @/etc/stopsid.sql”
su – oracle -c “ORACLE_SID=SID lsnrctl stop”
;;
*)
echo “oracleSID start|stop”
exit
;;
esac
exit
/etc/startsid.sql:
startup open;
exit
/etc/stopsid.sql:
shutdown immediate;
exit
Spacewalk is an open source (GPLv2) Linux systems management solution. It is the upstream community project from which the Red Hat Network Satellite product is derived.
01. Create the system recovery image of the system to be cloned using “make_net_recovery” command
02. The recovery configurations and archives created by make_net_recovery are stored in a separate directory on Ignite-UX server for each client. If the client to be installed does not currently have a directory in /var/opt/ignite/clients but is up and running, create the directory using “Add new Client for Recovery” from Actions menu on Ignite-UX GUI (From server). Alternatively, we can also run add_new_client -s <ignite-ux_server_name> from the client. If the client is not running, you will have to boot the system from the Ignite-UX server to get the directory created.
03. Copy the CINDEX and recovery directory from the source client to the target client directory. If the CINDEX file already exits, either create a backup copy of the CINDEX or edit the CINDEX file to add the desired entries from the source client.
cd /var/opt/ignite/clients/src_client_name find CINDEX recovery | cpio -pdvma ../target_client_name
04. Give the target client NFS access to recovery image of the source system
05. From the Ignite GUI select
Actions + Boot client…
Actions + Install Client + New Install…
06. Change the system networking parameters for the client during installation
For more information, refer Cloning Using Ignite-UX.PDF