| Deployment | Configuration | Recovery | Troubleshooting | FAQs |
|
No. You don't need 1-Touch Server to perform the 1-Touch Recovery. You need to install File System iDataAgent on the client computer and then enable 1-Touch feature. For more information, refer to Enable 1-Touch.
You must perform atleast one full backup before performing the 1-Touch recovery of the client computer. It is recommended to perform the backup of default subclient periodically. This will capture any changes in the client configuration. For more information, refer to Perform A Backup.
No. Use the 1-Touch Linux Live CD provided as DVD4 or You can also download the 1-Touch ISO image with the latest updates and use it for each of your clients. For more information, see Prepare for Recovery.
No. In general, all the below listed operating system utilities are distributed along with standard operating system distributions.
| Operating System Utilities | ||||
| arch | e2image | last | mv | swapon |
| awk | echo | ldd | netstat | sync |
| basename | egrep | ln | openvt | tail |
| bash | eject | locale | passwd | tar |
| cat | env | ls | pidof | tee |
| chgrp | expr | lsmod | ping | test |
| chmod | false | lspci | ping6 | time |
| chown | fdisk | lvcreate | ps | top |
| chroot | fgrep | lvdisplay | pvcreate | touch |
| chvt | file | lvm | pvdisplay | tr |
| cksum | find | lvmdiskscan | pvs | true |
| clear | fsck | lvscan | pvscan | tset |
| cp | fsck.ext2 | mkdir | pvs | tty |
| cpio | fsck.ext3 | mke2fs | pvscan | umount |
| cut | fuser | mkfifo | pwd | uname |
| date | gawk | mkfs | reboot | uptime |
| dd | getopt | mkfs.ext2 | rm | usleep |
| ddate | grep | mkfs.ext3 | rmdir | vgcfgbackup |
| depmod | gunzip | mkinitrd | rmmod | vgcfgrestore |
| df | gzip | mkswap | route | vgchange |
| diff | head | modinfo | sdiff | vgcreate |
| dir | host | modprobe | sed | vgdisplay |
| dirname | hostname | mknod | sleep | vi |
| dmesg | ifconfig | mktemp | stty | whereis |
| du | insmod | more | su | which |
| e2fsck | kill | mount | swapoff | zcat |
For example: Create a dhcp configuration file(/etc/dhcpd.conf) as follows:
authoritative;
ddns-update-style none;
allow bootp;
allow booting;
subnet 172.16.64.0 netmask 255.255.252.0
{
option routers 172.16.64.1;
option subnet-mask 255.255.252.0;
option domain-name-servers 172.19.59.6;
option domain-name-servers 172.19.59.7;
option ip-forwarding off;
default-lease-time 21600;
max-lease-time 43200;
host garuda5 {
hardware ethernet 00:0c:29:c8:bf:11;
fixed-address 172.16.65.165;
next-server 172.16.66.167;
filename "linux-install/pxelinux.0";
}
}
The hostname of the client that needs to be assigned the IP address is garuda5
MAC address of the client that needs to be assigned IP is 00:0c:29:c8:bf:11
IP that will be assigned to the client being booted through dhcp is 172.16.65.165
IP address of the tftp server is 172.16.65.167
The location on the tftp server where pxelinux.0 boot loader is located: linux-install/pxelinux.0
A prefix of /tftpboot will automatically be added to the filename provided in the /etc/dhcpd.conf file. So the actual location on the tftp server where pxelinux.0 is located is "/tftpboot/linux-install/pxelinux.0".
The file should have a name like 01-00-0c-29-c8-bf-11 (MAC address of the client that is being booted through TFTP) or AC1041A5 (IP address that is being assigned to client in the hex notation.) The configuration file contents can be as below:
default onetouch
label onetouch
kernel onetouch/vmlinuz
append initrd=onetouch/initrd.img crashkernel=32M@0 ramdisk_blocksize=1024 ramdisk_size=1024M root=/dev/ram rw method=nfs:172.16.65.167:/mnt/netboot ip=dhcp
The kernel and initrd locations are relative to the location mentioned in dhcpd.conf file. For example: When you create the dhcpd.conf file as mentioned above, the kernel and initrd will be located /tftpboot/linux-install/onetouch.
disable=no
The kernel and initrd will be extracted from the 1Touch boot cd. The network boot will access the contents of boot cd through NFS.
For example: If you have created the above configuration file @ /tftpboot/linux-install/pxelinux.cfg/01-00-0c-29-c8-bf-11, the NFS location that will be used for network boot is 172.16.65.167:/mnt/netboot.
Copy the bootcd.iso to the TFTP server.
mkdir -p /mnt/cdrom
mount -t iso9660 bootcd.iso /mnt/cdrom -o loop
cp -f /mnt/cdrom/isolinux/initrd.img /tftpboot/linux-install/onetouch
cp -f /mnt/cdrom/isolinux/vmlinuz-2.6.27.29-0.1-default /tftpboot/linux-install/onetouch/vmlinuz
The above commands will create the kernel and initrd required for Network boot.
cp -rf /mnt/cdrom/* /mnt/netboot
Here /mnt/netboot is a NFS mount point which can be accessed by the restored system through NFS.
| 1. |
|
|
| 2. | Click CD/DVD Drive 1 | Connect to ISO Image on Local Disk. |
 |
| 3. | Click Edit virtual machine settings. |
 |
| 4. |
|
 |
| 5. |
Power Off the virtual machine. Power On the virtual machine. Select CD-ROM Drive from the Boot menu. |
 |
During 1-Touch Recovery, a driver missing error shows up when the 1-Touch DVD4 cannot locate and load some specific hardware driver/s. In such cases,
1-Touch Recovery and VirtualizeME processes are carried out in two phases.
It is recommended to report any driver missing error messages via Technical Support. If it is critical to proceed without delay, the specific drivers may be compiled for the following kernel version:
2.6.27.29-0.1-default
The kernel module is compiled for x86 (32-bit).
Missing storage driver error messages during the first phase may be ignored as only the networking and keyboard/display drivers are required in this phase.
Copy the required drivers to a USB removable disk, partitioned such that the first partition is a vfat/ext2/ext3 file system.
# ls -l /dev/sdb*
- lists device names like sdb, sdb1 etc.,
# mknod /dev/sdb b 8 16
- the minor number should be as per the device naming convention followed in Linux
# mknod /dev/sdb1 b 8 17
# mkdir /mnt
# mount /dev/sdb1 /mnt
# cp /mnt/<driver>.ko /lib/modules/`uname -r`/<path>
# modprobe -f <driver>
Ensure that you use the modprobe -f option to load the custom built drivers.
# killall y2base
# cd /
# /usr/lib/YaST2/bin/y2base /1touch.ycp ncurses
# chroot /chroot /launchyast.sh
Otherwise, you can create the lost system mount point on a logical volume or a partition in the recovered disk.
Yes. . Follow the steps given below to perform the remore recovery:
Depending on the error message that was prompted, you may try to fix the problem as follows:
You can change the client host name during the 1-Touch recovery. For more information, see Change the Client Configuration during Interactive Restore or Change the Client Configuration during Non-Interactive Restore.
You can not change the client name during the 1-Touch recovery.
Yes. For more information, see Change the Client Configuration during Interactive Restore or Change the Client Configuration during Non-Interactive Restore.
Yes. For more information, see Change the Client Configuration during Interactive Restore or Change the Client Configuration during Non-Interactive Restore.
No. Software RAID is currently not supported.
|
|