1 - Identifier le serveur de sauvegarde du client (=su0294) su0294:root/# more /var/adm/sw/swinstall.log … distribution_source_directory su0350svg:/catalog/socle/ste6/depot/product/base/B.11.11_SX00 use_alternate_source false verbose 1 write_remote_files false * Source: su0350svg:/catalog/socle/ste6/depot/product/base/B.11.11_SX00 * Targets: su0294svg:/ * Software selections: CEGCTLMA,r=A.6.1.03,a=HP-UX_B.1X.XX_700/800,v=CEG … On déduit que le serveur de sauvegarde est su0350svg ------------------------------------------------------------------------------------------------ 2 - Identifier la dernière sauvegarde sur le serveur de sauvegarde su0350:root /var/opt/ignite/recovery/archives/su0294 # ls -lrt total 1642144 -rw------- 1 nobody sys 420313764 Dec 2 13:02 2008-12-02,12:56 -rw------- 1 nobody sys 420444598 Feb 19 10:09 2009-02-19,10:03 On constate que la dernière sauvegarde système a été faite le 19 février 2009 ------------------------------------------------------------------------------------------------ 3 - Lancer la sauvegarde système à partir du serveur client su0294:root/var/adm/sw# make_net_recovery -x inc_entire=/dev/vg00 -s su0350svg * Creating NFS mount directories for configuration files. ======= 04/11/09 15:23:36 METDST Started make_net_recovery. (Sat Apr 11 15:23:36 METDST 2009) @(#) Ignite-UX Revision C.6.7.79 @(#) net_recovery (opt) $Revision: 10.778 $ * Testing for necessary pax patch. * Passed pax tests. * Checking Versions of Recovery Tools WARNING: The version of the tools used for system recovery on "su0294" is older than the version found on the server system "su0350svg2". It is recommended that you update Ignite-UX to the same version. You can do this by using the command: /usr/sbin/swinstall -x mount_all_filesystems=false -s su0350svg2:/var/opt/ignite/depots/recovery_cmds "*" * Creating System Configuration. * /opt/ignite/bin/save_config -f /var/opt/ignite/recovery/client_mnt/0x0 012799E74DC/recovery/2009-04-11,15:23/system_cfg vg00 * Backing Up Volume Group /dev/vg00 * /usr/sbin/vgcfgbackup /dev/vg00 * Creating Map Files for Volume Group /dev/vg00 * /usr/sbin/vgexport -s -p -m /etc/lvmconf/vg00.mapfile /dev/vg00 * Backing Up Volume Group /dev/sharevg * /usr/sbin/vgcfgbackup /dev/sharevg * Creating Map Files for Volume Group /dev/sharevg * /usr/sbin/vgexport -s -p -m /etc/lvmconf/sharevg.mapfile /dev/sharevg * Backing Up Volume Group /dev/sharevg1 * /usr/sbin/vgcfgbackup /dev/sharevg1 * Creating Map Files for Volume Group /dev/sharevg1 * /usr/sbin/vgexport -s -p -m /etc/lvmconf/sharevg1.mapfile /dev/sharevg1 * Creating Control Configuration. * Creating Archive File List * Creating Archive Configuration * /opt/ignite/lbin/make_arch_config -c /var/opt/ignite/recovery/client_m nt/0x0012799E74DC/recovery/2009-04-11,15:23/archive_cfg -g /var/opt/ig nite/recovery/client_mnt/0x0012799E74DC/recovery/2009-04-11,15:23/flis t -n 2009-04-11,15:23 -r pa -b 64 -d Recovery\ Archive -L /var/opt/ignite/recovery/arch_mnt -l su0350svg2:/var/opt/ignite/recovery/archives/su0294 -i 1 -m t * Saving the information about archive t /var/opt/ignite/recovery/previews * Creating The Networking Archive * /opt/ignite/data/scripts/make_sys_image -d /var/opt/ignite/recovery/arch_mnt -t n -s local -n 2009-04-11,15:23 -m t -w /var/opt/ignite/recovery/client_mnt/0x0012799E74DC/recovery/2009- 04-11,15:23/recovery.log -u -R -g /var/opt/ignite/recovery/client_mnt/ 0x0012799E74DC/recovery/2009-04-11,15:23/flist -a 5162610 * Preparing to create a system archive. * The archive is estimated to reach 2581305 kbytes. * Free space on /var/opt/ignite/recovery/arch_mnt after archive should be about 22956319 kbytes. * Archiving contents of su0294 via tar to /var/opt/ignite/recovery/arch_mnt/2009-04-11,15:23. * Creation of system archive complete. NOTE: diskinfo failed for device at: /dev/rdsk/c14t15d0 NOTE: diskinfo failed for device at: /dev/rdsk/c12t15d0 NOTE: diskinfo failed for device at: /dev/rdsk/c4t15d0 NOTE: diskinfo failed for device at: /dev/rdsk/c8t15d0 * Creating CINDEX Configuration File * /opt/ignite/bin/manage_index -q -c 2009-04-11,15:23\ Recovery\ Archive -i /var/opt/ignite/recovery/client_mnt/0x0012799E74DC/CINDEX Recovery\ Archive * Cleaning up Archives NOTE: Archive: 2008-12-02,12:56 is being deleted * /opt/ignite/bin/manage_index -d -c 2008-12-02,12:56\ Recovery\ Archive -i /var/opt/ignite/recovery/client_mnt/0x0012799E74DC/CINDEX ======= 04/11/09 15:38:54 METDST make_net_recovery completed with warnings su0294:root/var/adm/sw# La sauvegarde système s’est bien passée. ------------------------------------------------------------------------------------------------------- 4 – Confirmer que la dernière sauvegarde système du client est présente sur le serveur su0350 su0350:root /var/opt/ignite/recovery/archives/su0294 # ls -lrt total 4098528 -rw------- 1 nobody sys 420444598 Feb 19 10:09 2009-02-19,10:03 -rw------- 1 nobody sys 1677979827 Apr 11 15:39 2009-04-11,15:23 => dernière sauvegarde ######################################################################################################################################################### ######################################################################################################################################################### UNE AUTRE FACON: ####################################### Voici les éléments pour effectuer la sauvegarde systeme hpux. Le répertoire client est : /var/adm/sw Le fichier a regardé depuis la fin est swinstall.log pour rechercher le serveur de sauvegarde. Le repertoire coté serveur est : /var/opt/ignite/clients/ Attention le nom peut être su0896, su0896adm ou su0896svg La commade de sauvegarde est : make_net_recovery -s deschute -x inc_entire=vg00 deschute = serveur de sauvegarde Christophe LE CLAIRE ################################################################################################################# UNE AUTRE FACON ############################## De source sure, Christophe , voic le modop pour faire une sauvegarde Sous HP avant reboot du serveur : Identifier le serveur de sauvegarde : Aller sous le fichier / var/adm/sw/swinstall.log su0391:root/var/adm/sw# vi swinstall.log ======= 03/24/06 07:05:41 EST BEGIN swinstall SESSION (non-interactive) (jobid=su0391-0001) * Session started for user "root@su0391". * Beginning Selection * "su0391:/": This target does not exist and will be created. * Source connection succeeded for "10.42.145.4:/catalog/socle/ste6/depot/core/B.11.11_SX00". NOTE: The patch fileset "PHKL_31241.CORE-KRN,fa=HP-UX_B.11.11_32/64" supersedes another patch fileset that has already been selected. The superseded patch fileset, "PHKL_23291.CORE-KRN,fa=HP-UX_B.11.11_32/64", will be deselected. NOTE: The patch fileset "PHKL_30510.C-INC,fa=HP-UX_B.11.11_32/64" supersedes another patch fileset that has already been selected. The superseded patch fileset, "PHKL_23313.C-INC,fa=HP-UX_B.11.11_32/64", will be deselected. NOTE: The patch fileset "PHKL_26743.LVM-KRN,fa=HP-UX_B.11.11_64" supersedes another patch fileset that has already been selected. The superseded patch fileset, "PHKL_25778.LVM-KRN,fa=HP-UX_B.11.11_64", will be deselected. :$ write_remote_files false * Source: su0350svg:/catalog/socle/STE042006/product/patches/B.11.11_SX00 * Targets: su0391:/ * Software selections: MQSERIES.U802131,r=B.11.530.11,a=HP-UX_B.11_700/800 * Beginning Analysis * "su0391:/": 1 check scripts had warnings. * Ending Analysis * Beginning Task Execution * Proceeding with Task Execution on the following targets: * su0391:/ * The execution phase succeeded for "su0391:/". * Ending Task Execution ======= 07/09/07 12:23:09 METDST END swinstall SESSION (interactive) ======= 07/09/07 12:23:09 METDST BEGIN swinstall SESSION (interactive) Puis lancer la commande en vous inspirant de l’exemple ci-dessous sur su0391 : su0391:root/var/adm/sw# make_net_recovery -x inc_entire=/dev/vg00 -s su0350svg Si probleme lors du lancement de la sauvegarde : Par exemple dans notre cas on a eu le message d’erreur ci-dessous : Permission denied ERROR: Unable to mount or write su0350svg:/var/opt/ignite/recovery/archives/su0391 On su0350svg you may need to: mkdir -p /var/opt/ignite/recovery/archives/su0391 chown bin:bin /var/opt/ignite/recovery/archives/su0391 vi /etc/exports (add or modify an entry). The /etc/exports file on "su0350svg" should contain the entry: /var/opt/ignite/recovery/archives/su0391 After editing the /etc/exports file, run exportfs –av (ou un exportfs –ua suivi d’un exportfs –av ) If you need to change the owner of the directory, you will also need to re-export the directory. Hugues de la Motte ######################################################################################### UNE AUTRE FACON ####################### Pour info à garder sous le coude : Pour vérifier le bon déroulement d'une sauvegarde IGNITE il faut se connecter au serveur de sauvegarde IGNITE . Ensuite il faut se placer dans le répertoire /var/opt/ignite/clients/nom_du_client_sauvegardé/recovery/latest Il faut consuler le fichier recovery.log. En fin de fichier il y a un message indiquant le bon ou mauvais déroulement de la sauvegarde ignite . Par exemple Configuration : Serveur de sauvegarde IGNITE : su0350 Client à sauvegarder : su0002 On se connecte sur su0350 et on se place sous le répertoire citée précédement : su0350:root /var/opt/ignite/clients/su0002/recovery/latest # ll total 17856 -rw-r--r-- 1 bin sys 28395 Apr 21 16:08 archive_cfg -rw-r--r-- 1 bin sys 16 Apr 21 16:04 archive_content -rw-r--r-- 1 bin sys 9986 Apr 21 16:06 control_cfg -rw-r--r-- 1 bin sys 8812635 Apr 21 16:08 flist -rw-r--r-- 1 bin sys 146341 Apr 21 16:28 manifest -rw-r--r-- 1 bin sys 24597 Apr 21 16:28 recovery.log -rw-r--r-- 1 bin sys 88227 Apr 21 16:05 system_cfg su0350:root /var/opt/ignite/clients/su0002/recovery/latest # cat recovery.log Et la ligne la plus interessante est la dernière : ======= 04/21/08 16:28:33 METDST make_net_recovery completed successfully! Sami ZAOUECH