Re: Sysback
Latest I heard and is recent... https://www.cristie.com/news/take-over-development-ibm-sysback-software/ Thanks -Dave -Original Message- From: ADSM: Dist Stor Manager On Behalf Of Richard van Denzel Sent: Friday, September 21, 2018 09:17 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Sysback Hi All, Does anyone know if Sysback/6000 (sending AIX mksysb to TSM) is still around for Spectrum Protect 7 or 8 and what's it called now? Richard
Re: Sysback
Yes, it sends its backup images to TSM. This is true for all of SysBack's backup types (system, volume group, filesystem, local volume and file/directory) Its called IBM Tivoli Storage Manager for System Backup and Recovery (SysBack). Recently the product was sold to Christie. But IBM is still honoring all existing SysBack contracts with Tech support and maintenance. Lee Miller IBM Spectrum Protect Server Development Phone: 817-874-7484 From: Richard van Denzel To: ADSM-L@VM.MARIST.EDU Date: 09/21/2018 08:19 AM Subject:[ADSM-L] Sysback Sent by:"ADSM: Dist Stor Manager" Hi All, Does anyone know if Sysback/6000 (sending AIX mksysb to TSM) is still around for Spectrum Protect 7 or 8 and what's it called now? Richard
Re: sysback help needed !
Perhaps I am reading this wrong, but here are some hints that I have learned over the years: 1) The bootp server must be at or above the oslevel of the restored server: AIX 5.3 can be used as a bootp server for AIX 5.2 AIX 5.2 cannot be used as a bootp server for AIX 5.3 This sounds like a show stopper till you are able to upgrade the NIM/bootp server. 2) In order for sysback to restore on different hardware, the sysback image must include all the device drivers for the restored machine. I was sure they fixed that during the upgrade to AIX 5.3 by loading ALL device drivers during installation. Just to be sure, you might try the following steps: a) install devices.* from the install media b) recreate your sysback image c) re-run your sysback restore Question: What is the LED shown for your 505 server? The LED might also indicate the problem. goc [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU 04/03/2006 02:21 AM Please respond to ADSM: Dist Stor Manager ADSM-L@VM.MARIST.EDU To ADSM-L@VM.MARIST.EDU cc Subject sysback help needed ! hi all, i'm doing an test restore of rootvg from TSM via classic network boot the communication is fine and everything seems okay except this ... it simply hangs on following ... --- Type menu item number and press Enter or select Navigation key:1 IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM STARTING SOFTWARE IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBMPLEASE WAIT... IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM IBM BOOTP: chosen-network-type = ethernet,auto,rj45,auto BOOTP: server IP =10.243.122.10 BOOTP: requested filename = BOOTP: client IP =10.243.166.9 BOOTP: client HW addr = 0 11 25 7e 4 4e BOOTP: gateway IP =10.243.166.1 BOOTP: device/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] BOOTP: loc-code U789A.001.AAA1094-P1-T1 BOOTP: wait 60 seconds for Spanning Tree ... BOOTP R = 1 BOOTP S = 2 FILE: /tftpboot/axtprov2 BOOTP: chosen-network-type = ethernet,auto,rj45,auto BOOTP: server IP =10.243.122.10 BOOTP: requested filename = BOOTP: client IP =10.243.166.9 BOOTP: client HW addr = 0 11 25 7e 4 4e BOOTP: gateway IP =10.243.166.1 BOOTP: device/[EMAIL PROTECTED]/[EMAIL PROTECTED]/[EMAIL PROTECTED] BOOTP: loc-code U789A.001.AAA1094-P1-T1 BOOTP: wait 60 seconds for Spanning Tree ... BOOTP R = 1 BOOTP S = 2 FILE: /tftpboot/axtprov2 FINAL Packet Count = 16673 FINAL File Size = 8536286 bytes. load-base=0x4000 real-base=0xc0 Elapsed time since release of system processors: 16 mins 27 secs --- Welcome to AIX.
Re: sysback backup procedure on TSM and client server
hi, what do you mean it doesnt work ? you have to give us some clues, error messages and so on ... i'm doing over 60 sysbacks to TSM via crontab scripts goran - Original Message - From: Dksh Cssc [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, August 24, 2005 11:24 AM Subject: sysback backup procedure on TSM and client server Dear all, I manage to get OS backup via sysback done successfully for the first time(manually using sysback).However when I try to arrange a schedule to backup a sysback script, it doesn't work. Is there any recommended advice to backup the OS using TSM scheduler rather than cron job? Any good procedure to do a sysback backup? I Thanks and Warmest Regards,
Re: sysback backup procedure on TSM and client server
Yeah, I haven't found the TSM integrated features of SYSBACK very useful. We do cron scheduled SYSBACKS to a common area on the sysback server, then do a TSM scheduled archive delete of the area. We stagger our sysbacks for our nodes over the days of the week to get all of them done weekly. [EMAIL PROTECTED] 08/24/2005 9:22:08 AM hi, what do you mean it doesnt work ? you have to give us some clues, error messages and so on ... i'm doing over 60 sysbacks to TSM via crontab scripts goran - Original Message - From: Dksh Cssc [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, August 24, 2005 11:24 AM Subject: sysback backup procedure on TSM and client server Dear all, I manage to get OS backup via sysback done successfully for the first time(manually using sysback).However when I try to arrange a schedule to backup a sysback script, it doesn't work. Is there any recommended advice to backup the OS using TSM scheduler rather than cron job? Any good procedure to do a sysback backup? I Thanks and Warmest Regards,
Re: sysback backup procedure on TSM and client server
well, i do ... :-) it's simple and works very very good directly to tape ... :-) peace, goran - Original Message - From: Lawrence Clark [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, August 24, 2005 3:31 PM Subject: Re: sysback backup procedure on TSM and client server Yeah, I haven't found the TSM integrated features of SYSBACK very useful. We do cron scheduled SYSBACKS to a common area on the sysback server, then do a TSM scheduled archive delete of the area. We stagger our sysbacks for our nodes over the days of the week to get all of them done weekly. [EMAIL PROTECTED] 08/24/2005 9:22:08 AM hi, what do you mean it doesnt work ? you have to give us some clues, error messages and so on ... i'm doing over 60 sysbacks to TSM via crontab scripts goran - Original Message - From: Dksh Cssc [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Wednesday, August 24, 2005 11:24 AM Subject: sysback backup procedure on TSM and client server Dear all, I manage to get OS backup via sysback done successfully for the first time(manually using sysback).However when I try to arrange a schedule to backup a sysback script, it doesn't work. Is there any recommended advice to backup the OS using TSM scheduler rather than cron job? Any good procedure to do a sysback backup? I Thanks and Warmest Regards,
Re: sysback interaging to tsm restore question
afaik this is okay , you have to choose network adapter which will be active during restore, another words the net. adapter which was used when sysbackup was made, after choosing the right net. adapter you will have option to choose virtual tsm device goran - Original Message - From: liming [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, July 11, 2005 12:16 PM Subject: sysback interaging to tsm restore question Hi all,TSM server is 5.2.4(OS is aix 5.3 ml02,it's the instserver and bootserver also),TSM client is 5.2.4(OS is aix 5.3 ml02 too,sysback is 5.6.6).I can boot this to sysback boot menu ,but from change installation device option I can see all the ethernet adapters but can't see the virtual TSM devices.I can't access change volume group logical volume information and install the system with current settiongs options,the error message is No install options on the server are available for the rootvg volume group. You must select an install device or file for the rootvg before continuing.The content of debug.out is: # more /debug.out [sysinstall setupfiles: Mon Jul 11 14:58:11 2005] -- + typeset -i numpvs + rm -f /tmp/inst_error + MAXPPS=1016 + KSH=/bin/ksh + set -x + cd / + [ -z ] + [ ! -f /usr/lib/methods/devices.cat -a 5 != 5 -a -z ] + [ 5 = 3 -a ! -f /tmp/cd.extract ] + [[ ! -f /usr/sbin/umount ]] + [[ ! -f /usr/sbin/unmount ]] + [[ -n ]] + 1 /tmp/pvinfo + getlvminfo -PN + VGname= + getlvminfo -VN + [ -z ] + VGname=(free) + + getlvminfo -P hdisk0 -iI PVid=00c41efe5b293c99 + + getlvminfo -P hdisk0 -iX Location=0B-08-00-4,0 + [ -z 0B-08-00-4,0 ] + + lsdev -Cl hdisk0 -F description desc=16 Bit LVD SCSI Disk Drive + print hdisk0 (free) 00c41efe5b293c99 0B-08-00-4,0 16 Bit LVD SCSI Disk Drive + VGname= + getlvminfo -VN + [ -z ] + VGname=(free) + + getlvminfo -P hdisk1 -iI PVid=00c41efef44dfbe3 + + getlvminfo -P hdisk1 -iX Location=0B-08-00-5,0 + [ -z 0B-08-00-5,0 ] + + lsdev -Cl hdisk1 -F description desc=16 Bit LVD SCSI Disk Drive + print hdisk1 (free) 00c41efef44dfbe3 0B-08-00-5,0 16 Bit LVD SCSI Disk Drive + [ ! -z ] + [ ! -f /tmp/instdev ] + [ ! -z ] + [ ! -z ] + print /dev/ent0 + 1 /tmp/instdev + + cat /tmp/instdev INSTDEV=/dev/ent0 + setdevdesc + + cat /tmp/instdev DEVLIST=/dev/ent0 + basename /dev/ent0 + print Network [ent0] + 1 /tmp/instdevdesc + grep ^sbnet /etc/services + 1 /dev/null 2 1 + test 1 -ne 0 + print sbnet\t\t1239/tcp\t\t\t# Sysback Remote Backup/Install + 1 /etc/services + 1 /tmp/..buffer4 + grep rmt + lsdev -Cctape -S Available + LANG=C + grep ^cd + lsdev -Cccdrom -S Available + LANG=C + grep ^tok + lsdev -Ccadapter + LANG=C + grep ^ent + lsdev -Ccadapter + LANG=C + grep ^fdd + lsdev -Ccadapter + LANG=C + exec + 4 /tmp/..buffer4 + 1 /tmp/instdevinfo + read -u4 dev status loc desc + iscfg rmt0 + device=rmt0 + odmget CuDv + grep -p rmt0 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt0 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt1 + device=rmt1 + odmget CuDv + grep -p rmt1 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt1 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt2 + device=rmt2 + odmget CuDv + grep -p rmt2 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt2 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt3 + device=rmt3 + odmget CuDv + grep -p rmt3 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt3 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg cd0 + device=cd0 + odmget CuDv + grep -p cd0 + read x x uniquetype + grep
Re: sysback interaging to tsm restore question
Thank goran,the network adapter for sysback is en0,but in sysback boot menu all the adapters are inactive,and I didn't find a way to make it active. - Original Message - From: goc [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, July 11, 2005 8:07 PM Subject: Re: [ADSM-L] sysback interaging to tsm restore question afaik this is okay , you have to choose network adapter which will be active during restore, another words the net. adapter which was used when sysbackup was made, after choosing the right net. adapter you will have option to choose virtual tsm device goran - Original Message - From: liming [EMAIL PROTECTED] To: ADSM-L@VM.MARIST.EDU Sent: Monday, July 11, 2005 12:16 PM Subject: sysback interaging to tsm restore question Hi all,TSM server is 5.2.4(OS is aix 5.3 ml02,it's the instserver and bootserver also),TSM client is 5.2.4(OS is aix 5.3 ml02 too,sysback is 5.6.6).I can boot this to sysback boot menu ,but from change installation device option I can see all the ethernet adapters but can't see the virtual TSM devices.I can't access change volume group logical volume information and install the system with current settiongs options,the error message is No install options on the server are available for the rootvg volume group. You must select an install device or file for the rootvg before continuing.The content of debug.out is: # more /debug.out [sysinstall setupfiles: Mon Jul 11 14:58:11 2005] -- + typeset -i numpvs + rm -f /tmp/inst_error + MAXPPS=1016 + KSH=/bin/ksh + set -x + cd / + [ -z ] + [ ! -f /usr/lib/methods/devices.cat -a 5 != 5 -a -z ] + [ 5 = 3 -a ! -f /tmp/cd.extract ] + [[ ! -f /usr/sbin/umount ]] + [[ ! -f /usr/sbin/unmount ]] + [[ -n ]] + 1 /tmp/pvinfo + getlvminfo -PN + VGname= + getlvminfo -VN + [ -z ] + VGname=(free) + + getlvminfo -P hdisk0 -iI PVid=00c41efe5b293c99 + + getlvminfo -P hdisk0 -iX Location=0B-08-00-4,0 + [ -z 0B-08-00-4,0 ] + + lsdev -Cl hdisk0 -F description desc=16 Bit LVD SCSI Disk Drive + print hdisk0 (free) 00c41efe5b293c99 0B-08-00-4,0 16 Bit LVD SCSI Disk Drive + VGname= + getlvminfo -VN + [ -z ] + VGname=(free) + + getlvminfo -P hdisk1 -iI PVid=00c41efef44dfbe3 + + getlvminfo -P hdisk1 -iX Location=0B-08-00-5,0 + [ -z 0B-08-00-5,0 ] + + lsdev -Cl hdisk1 -F description desc=16 Bit LVD SCSI Disk Drive + print hdisk1 (free) 00c41efef44dfbe3 0B-08-00-5,0 16 Bit LVD SCSI Disk Drive + [ ! -z ] + [ ! -f /tmp/instdev ] + [ ! -z ] + [ ! -z ] + print /dev/ent0 + 1 /tmp/instdev + + cat /tmp/instdev INSTDEV=/dev/ent0 + setdevdesc + + cat /tmp/instdev DEVLIST=/dev/ent0 + basename /dev/ent0 + print Network [ent0] + 1 /tmp/instdevdesc + grep ^sbnet /etc/services + 1 /dev/null 2 1 + test 1 -ne 0 + print sbnet\t\t1239/tcp\t\t\t# Sysback Remote Backup/Install + 1 /etc/services + 1 /tmp/..buffer4 + grep rmt + lsdev -Cctape -S Available + LANG=C + grep ^cd + lsdev -Cccdrom -S Available + LANG=C + grep ^tok + lsdev -Ccadapter + LANG=C + grep ^ent + lsdev -Ccadapter + LANG=C + grep ^fdd + lsdev -Ccadapter + LANG=C + exec + 4 /tmp/..buffer4 + 1 /tmp/instdevinfo + read -u4 dev status loc desc + iscfg rmt0 + device=rmt0 + odmget CuDv + grep -p rmt0 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt0 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt1 + device=rmt1 + odmget CuDv + grep -p rmt1 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt1 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt2 + device=rmt2 + odmget CuDv + grep -p rmt2 + read x x uniquetype + grep PdDvLn + [ -z tape/fcp/ost ] + + sed s///g + print tape/fcp/ost uniquetype=tape/fcp/ost + odmget PdDv + grep -p tape/fcp/ost + read x x cfgfile + grep [ ]*Configure + [ -z /etc/methods/cfgscsitape ] + + sed s///g + print /etc/methods/cfgscsitape cfgfile=/etc/methods/cfgscsitape + [ ! -f /etc/methods/cfgscsitape ] + return 0 + printf /dev/%-8.8s %-35.35s %s\n rmt2 Other FC SCSI Tape Drive 0E-08-02 + read -u4 dev status loc desc + iscfg rmt3 + device=rmt3 + odmget CuDv + grep -p rmt3 + read x x uniquetype + grep PdDvLn + [ -z
Re: Sysback version 5.6.5
Paul, You want IBM Tivoli Storage Manager for System Backup and Recovery, GC32-9076-02. Sysback is installed on the system that you want to run it on and then you tie into the TSM api to store the backup to TSM. The book above explains the how to. Bill Sherrill
Re: Sysback version 5.6.5
I don't see the link. However if I get this correct You say to install the product onto the client not the TSM server correct? Then configure it through smit as unusual -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of William Sherrill Sent: Monday, June 13, 2005 12:01 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Sysback version 5.6.5 Paul, You want IBM Tivoli Storage Manager for System Backup and Recovery, GC32-9076-02. Sysback is installed on the system that you want to run it on and then you tie into the TSM api to store the backup to TSM. The book above explains the how to. Bill Sherrill - Music from EMI This e-mail including any attachments is confidential and may be legally privileged. If you have received it in error please advise the sender immediately by return email and then delete it from your system. The unauthorised use, distribution, copying or alteration of this email is strictly forbidden. If you need assistance please contact us on +44 20 7795 7000. This email is from a unit or subsidiary of EMI Group plc. Registered Office: 27 Wrights Lane, London W8 5SW Registered in England No 229231. -
Re: Sysback and 32-bit client
From my experience, the whole 32 bit vs 64 bit thing on AIX comes down to what the process is doing. For Oracle, 64 bit makes sense on a large memory system, since you can then throw heaps of RAM at its SGA, and hopefully experience a higher cache hit ratio. For something like TSM client, the performance difference between 32 and 64 bit should be fairly minimal. Even for the AIX kernel, IBM recommends running 32 bit unless you have more than 16 GB of RAM (not sure where the reference is for that). Indeed, some processes will even slow down going from 32 bit to 64 bit. Also, 64 bit applications are often about 30% larger than their 32 bit counterparts, which, in itself, means a performance hit. On Friday, Jan 30, 2004, at 04:30 Australia/Sydney, David E Ehresman wrote: I don't disagree with any of what you wrote in your latest note but that is hardly the same as Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api which is what you orginially wrote. The 32 bit api does work. But today the choice is using the TSM integration with all its benefits via the 32 bit api or not using the TSM integration because the api isn't 64. The later seems to me a choice of making ones life more difficult than it needs to be just to prove a point to a large organization which could care less about your individual stand. I am confident that as the Sysback TSM integration matures, it will support the then current api. David [EMAIL PROTECTED] 1/29/2004 12:16:56 PM Hi, I would assume that the 64-bit client is faster, smaller, better (otherwise why create a 64-bit client) and as almost all of my systems are 64-bit, that is the client that is loaded on them. To me, running a 32-bit client on a 64-bit OS/Hardware is like running the 32-bit version of Oracle on a 64-bit OS/Hardware (ie. It is gimping yourself some). Also the future (whether IBM likes to admit it or not) is 64-bit computing (Alpha's have been there for 10 years now..). By only supporting the 32-bit client, it seems that IBM is saying that we kind of support your bare metal solution. I was just wondering if anyone has seen any kind of timetable regarding changes to this feature. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Thursday, January 29, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Sysback and 32-bit client Why does the 32-bit TSM api prevent you from using the feature? the 32-bit api does run on 64 bit machines and will work with servers running in 64 bit mode. David [EMAIL PROTECTED] 1/29/2004 11:13:28 AM Hi, We use sysback as our bare metal solution for our AIX servers. Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api. Does anyone know what IBM's plans for changing this requirement are? The solution isn't horrible currently, but could I would really like to take advantage of some of the expiration features, etc in TSM. Michael This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). -- Paul Ripke Unix/OpenVMS/TSM/DBA I love deadlines. I like the whooshing sound they make as they fly by. -- Douglas Adams
Re: Sysback and 32-bit client
Why does the 32-bit TSM api prevent you from using the feature? the 32-bit api does run on 64 bit machines and will work with servers running in 64 bit mode. David [EMAIL PROTECTED] 1/29/2004 11:13:28 AM Hi, We use sysback as our bare metal solution for our AIX servers. Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api. Does anyone know what IBM's plans for changing this requirement are? The solution isn't horrible currently, but could I would really like to take advantage of some of the expiration features, etc in TSM. Michael This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Sysback and 32-bit client
Hi, I would assume that the 64-bit client is faster, smaller, better (otherwise why create a 64-bit client) and as almost all of my systems are 64-bit, that is the client that is loaded on them. To me, running a 32-bit client on a 64-bit OS/Hardware is like running the 32-bit version of Oracle on a 64-bit OS/Hardware (ie. It is gimping yourself some). Also the future (whether IBM likes to admit it or not) is 64-bit computing (Alpha's have been there for 10 years now..). By only supporting the 32-bit client, it seems that IBM is saying that we kind of support your bare metal solution. I was just wondering if anyone has seen any kind of timetable regarding changes to this feature. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Thursday, January 29, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Sysback and 32-bit client Why does the 32-bit TSM api prevent you from using the feature? the 32-bit api does run on 64 bit machines and will work with servers running in 64 bit mode. David [EMAIL PROTECTED] 1/29/2004 11:13:28 AM Hi, We use sysback as our bare metal solution for our AIX servers. Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api. Does anyone know what IBM's plans for changing this requirement are? The solution isn't horrible currently, but could I would really like to take advantage of some of the expiration features, etc in TSM. Michael This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Sysback and 32-bit client
I don't disagree with any of what you wrote in your latest note but that is hardly the same as Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api which is what you orginially wrote. The 32 bit api does work. But today the choice is using the TSM integration with all its benefits via the 32 bit api or not using the TSM integration because the api isn't 64. The later seems to me a choice of making ones life more difficult than it needs to be just to prove a point to a large organization which could care less about your individual stand. I am confident that as the Sysback TSM integration matures, it will support the then current api. David [EMAIL PROTECTED] 1/29/2004 12:16:56 PM Hi, I would assume that the 64-bit client is faster, smaller, better (otherwise why create a 64-bit client) and as almost all of my systems are 64-bit, that is the client that is loaded on them. To me, running a 32-bit client on a 64-bit OS/Hardware is like running the 32-bit version of Oracle on a 64-bit OS/Hardware (ie. It is gimping yourself some). Also the future (whether IBM likes to admit it or not) is 64-bit computing (Alpha's have been there for 10 years now..). By only supporting the 32-bit client, it seems that IBM is saying that we kind of support your bare metal solution. I was just wondering if anyone has seen any kind of timetable regarding changes to this feature. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of David E Ehresman Sent: Thursday, January 29, 2004 10:49 AM To: [EMAIL PROTECTED] Subject: Re: Sysback and 32-bit client Why does the 32-bit TSM api prevent you from using the feature? the 32-bit api does run on 64 bit machines and will work with servers running in 64 bit mode. David [EMAIL PROTECTED] 1/29/2004 11:13:28 AM Hi, We use sysback as our bare metal solution for our AIX servers. Currently we are forced to use the sysback remote server utilities instead of the TSM integration feature as it only supports the 32-bit TSM api. Does anyone know what IBM's plans for changing this requirement are? The solution isn't horrible currently, but could I would really like to take advantage of some of the expiration features, etc in TSM. Michael This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply). This e-mail may contain identifiable health information that is subject to protection under state and federal law. This information is intended to be for the use of the individual named above. If you are not the intended recipient, be aware that any disclosure, copying, distribution or use of the contents of this information is prohibited and may be punishable by law. If you have received this electronic transmission in error, please notify us immediately by electronic mail (reply).
Re: Sysback
There's a nice redbook IBM Tivoli Storage Manager: Bare Machine Recovery for AIX with SYSBACK. Go to http://www.rebooks.ibm.com and search on sysback. Right now it's just a redpiece, but dated 10/30/03. Bill Boyer DSS, Inc. -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Behalf Of Valeriano Bassi Sent: Tuesday, December 30, 2003 6:00 AM To: [EMAIL PROTECTED] Subject: Sysback Hi there, we are evaluating the use of Sysback to do Bare Metal Restore of our AIX boxes. I have two questions for you: 1) will Sysback work with an S/390 TSM Server? 2) do I need to use NIM or may I start recovery operations booting from a CD, for example? Your help will be very appreciated TIA Valeriano Bassi [EMAIL PROTECTED]
Re: Sysback/6000 vs. mksysb for TSM DR restore
One quick thought, just install the needed drivers on the H70. Miles [EMAIL PROTECTED] 07-Mar-02 11:19:12 AM Hi, We have been using Sysback/6000 for years as our backup recovery tool for our AIX systems. We are now merging many of those servers, and the collection of non-AIX systems is proliferating so we are migrating to a TSM backup/recovery mechanism. The TSM server is an AIX based NSM box. I am in the process of learning the ins and outs of DR with a TSM and the first step is to restore the TSM server itself. The first method tried was the IBM standard mksysb. Because the box I am restoring onto is a different model, size and slightly newer architecture with newer cards and I/O subsystems, it took a while to figure out the right combination of CD's, mksysb tape, and procedures to get the DR test system working. For example, the boot disk requires drivers that do not exist on the H70, and they have to be installed after the mksysb restore, but before we can actually use the restored system. Once I got the restored system into a usable state, I still faced the task of cleaning up and recreating the storage pool volume group and it's associated logical volumes and filesystems. The DR test box also has a very different set of hdisks onto which to restore the disk storage pools. It occurred to me, and has been mentioned on this mailing list, that using Sysback/6000 would afford me the option of having the Sysback restore rebuild those other LVM objects in a familiar way. The questions I have have to do with the disparate hardware and driver requirements: Would the extra driver restore procedures be required? Assuming they would, would I need more of them or does the Sysback restore pull some of that from the AIX install disks the way mksysb is supposed to? Then, if I need them, would they work? I should be able to test this next month some time, but any help or gotcha's would be appreciated. Werner Kliewer Manitoba Public Insurance
