Re: Backup of Sun OS
You could also take a look at Bare Metal Restore - from VERITAS. It was formerly a TKG product, but TKG was aquired by and megerd into VERITAS. You can still get BMR for TSM from IBM channels. Remco Post wrote: Hi, Jumpstart is free, and is more like the AIX nim. ufsdump/restore are ok tools, but they don't make a bootable image. The angian, if your happy with 'boot net -s' or 'boot cdrom -s' mount the nsf fs the ufsdump is on and then restoreing maulally, you'll probably be ok using usfdump. If you want to do these things automatically with one command, you'll probably need a very customized junpstart (not entierly impossible, if you have the time), or a third party non-free (as in beer ;) tool. SUN's equivalent to AIX's 'mksysb' is: ufsdump (backup OS) and ufsrestore (restore filesystems). Sorry, I don't have sample scripts, however, you can go to SUN's website, www.sun.com, and do a search of ufsdump to get the online command reference. PS. It's free. Jack -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Wouter V Sent: Friday, January 25, 2002 4:18 PM To: [EMAIL PROTECTED] Subject: Re: Backup of Sun OS MessageThere is a separate product that has the same functionality as mksysb on AIX, it is called 'JUMPSTART'.Contrary to mksysb, it is not a free product. I think you can by it at Sun. Regards, Wouter Verschaeve Unix Sys. Engineer -Oorspronkelijk bericht- Van: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]Namens MacMurray, Andrea (CC-ETS Ent Storage Svcs) Verzonden: vrijdag 25 januari 2002 20:59 Aan: [EMAIL PROTECTED] Onderwerp: Backup of Sun OS HI everybody, The first thing I have to say to this is that I am NOT a UNIX guru, so I greatly would appreciate all the help I can get. The problem is that our Unix team wants to backup a running Sun OS and then later on restore this backed up OS backup and boot the machine from there, which of course did not work. I know AIX has the make sysb solution for this, does anybody know of a solution for SUN. TSM version 4.2.1.9 on AIX 4.3.3 Thanks Andrea Mac Murray Sen. Systems Administrator ConAgra Foods, Inc. 7300 World Communication Drive Omaha,NE 68122 Tel: (402) 577-3603 [EMAIL PROTECTED] -- Met vriendelijke groeten, Remco Post SARA - Stichting Academisch Rekencentrum Amsterdam High Performance Computing Tel. +31 20 592 8008Fax. +31 20 668 3167 I really didn't foresee the Internet. But then, neither did the computer industry. Not that that tells us very much of course - the computer industry didn't even foresee that the century was going to end. -- Douglas Adams -- Ray Schafer VERITAS Software www.veritas.com Field Sales Strategy[EMAIL PROTECTED] +1 512 433 3300
Re: BMR product
Ron, The three BMR Servers required are best described as logical components. All three (Main, File, and Boot Server) can be co-located on one machine - this machine can also be the TSM server. The server components have to run on a UNIX machine - either AIX, Solaris, or HP UX. If the components are separated, only the Main server must also run a TSM (or ADSM) client. BMR clients - machines to be protected - must have both TSM BA Client (ADSM version 3.1.0.20 or higher or TSM version 3.7, 4.1, or 4.2) and BMR Client. Hope that helps... cc52 wrote: I was looking thru the BMR (Bare Metal Restore) documents on the Kernal Groups web site. Since the BMR architecture (three of its own servers) seems to be external to the TSM server, is there something that makes TSM 4.2 a required level to use BMR? Ron Greve SDSU Computing Services -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive messages for addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this message in error, please advise the sender by reply email and delete the message. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300
Re: BMR for Win2k: Use of NTBACKUP
Yes, I do think the TCO is dependent on the number of machines you have to protect, and to some extent the way you administer them. For example, if you build all your machines the same way, with the drives and partitions clearly defined (i.e. disk0 is 18 GB and it is divided into a 4 GB C: FAT32 partition and a 14 GB D: NTFS partition, then clearly it is easier to know how the machines are partitioned when you start the recovery process. As you deviate from this rigidity, both the administrative costs of keeping track of the machine configurations and the potential for human error becomes greater. On the other hand, BMR saves this information automatically and uses it to re-partition and format the drives for you and then restore the data from TSM automatically. This is nice because now you are no longer bound by recovery constraints. You have complete freedom to partition drives according to the needs of the applications. Also, during a BMR recovery, one person can initiate multiple restores and sit back to watch it all happen. If you have a multiple server recovery, the more manual methods - however minimal they may be - will gate the number of simultaneous restores because they require an administrator to perform manual steps at various points in the process (and hopefully an administrator who knows this information is available for the restoration). Salak Juraj wrote: Hello Ray, You are absolutely right we have to think in TCO (Total Costs of Ownership) terms. On the other side, the initial investment counts to TCO as well. Generally speaking, the prices of each product, will determinate the market share as well as other product attributes. I had a look at your solution, found it great, but its price limited its suitability for my business needs substantially. There really are disadvantages coming aling with simple solutions but the extent is not necessarily as high as you mentioned. The simpler solutions like those with NTBACKUP or PcBax - to name only two - are automatisable to a fair extent. Typically you will have to create a set of boot media (floppy) for each node, and schedule the simple tool to backup system state to a local file, which is backed-up by TSM in turn. Obviously, both backup and restore procedures will require at least one step more than OTG, but there is neither need for repeated manual tasks nor for usage of local media. If I had a w2k server farm I would, no doubt, prefer to use your tool. For not so critical business with workstations there are even manual fresh W2K installations cheaper for me. Facit: it depends :) best regards Juraj Salak Asamer Familienholding -Original Message- From: Ray Schafer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 21, 2001 2:05 AM To: [EMAIL PROTECTED] Subject: Re: BMR for Win2k: Use of NTBACKUP Michael Bartl wrote: In a standard Win2k environment bare metal recovery using TSM doesn't work. Of course, the Kernel Group BMR is a great tool, but expensive. I think if you take into consideration all of the costs, TKG's BMR gives a return on investment rather quickly. With this solution, after the initial installation, there is nothing to do except run your incremental backups the way you do now. All of the point solutions you have to perform Bare Metal Restores are no longer needed. No more local tape drives or monitoring the processes, no more administrators time tracking the backups, dealing with the media, wondering if you remembered everything. And we're not even talking about the time saved when you actually have to use it for a Bare Metal Restore. It is automated in both daily operations and during the restoration. That's where the value comes in. Weigh the entire solution: what it costs you before you implement BMR and after. Most companies get back their investment within the first 6 months of use. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive messages for addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this message in error, please advise the sender by reply email and delete the message. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300 -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive messages for addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this message in error, please advise the sender by reply email and delete the message
Re: BMR for Win2k: Use of NTBACKUP
Michael Bartl wrote: In a standard Win2k environment bare metal recovery using TSM doesn't work. Of course, the Kernel Group BMR is a great tool, but expensive. I think if you take into consideration all of the costs, TKG's BMR gives a return on investment rather quickly. With this solution, after the initial installation, there is nothing to do except run your incremental backups the way you do now. All of the point solutions you have to perform Bare Metal Restores are no longer needed. No more local tape drives or monitoring the processes, no more administrators time tracking the backups, dealing with the media, wondering if you remembered everything. And we're not even talking about the time saved when you actually have to use it for a Bare Metal Restore. It is automated in both daily operations and during the restoration. That's where the value comes in. Weigh the entire solution: what it costs you before you implement BMR and after. Most companies get back their investment within the first 6 months of use. -- -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= This message contains information which may be confidential and privileged. Unless you are the addressee (or authorized to receive messages for addressee), you may not use, copy or disclose to anyone the message or any information contained in the message. If you have received this message in error, please advise the sender by reply email and delete the message. -=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-=-= -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300
Re: restoring client as a full OS install?
Alex, As far as I know, TKG's Bare Metal Restore is the only product (commercial or otherwise) to restore an NT, 2000, AIX, Solaris, or HP UX machine from bare metal. It is also a fully automated restore, using only the data in TSM to restore the system. The web link is http://www.tkg.com/bmr/tsm. Hope that helps. Alexander Lazarevich wrote: I'd like to know if anyone has restored a client to a blank/new drive in order to fully bring back the OS. What I mean is this: If a client disk drive fails, and I need bring that client machine back up ASAP, it would be quicker if I could restore every single file that was backed up for the client. If all system/install/data files on the client were backed up, then the restore should work, right? This would be quicker than reinstalling all apps, because we have a lot of apps... I already tried this. But it didn't work because I was trying to restore to a drive that was the currently running OS client, and I think ADSM was unable to restore files that were running processes. So now I'm going to try and restore to a second clean drive that I installed in the machine. I also installed a base OS on the second drive, rather than keeping it a clean drive with a formated filesystem of the OS type. I'm not sure if one was is better than another. I read the ADSM manual, thinking that the section called Disaster Recovery would be just what I'm doing, and it's not. I already know what my machine specs are, I just need to know if I can trully restore the OS. Cause everything on a computer is a file, right? If that's true then this should work, right? Anyone done this before? Thanks in advance, Alex ~ Alex Lazarevich Systems Administrator Imaging Technology Group, http://www.itg.uiuc.edu Beckman Institute, http://www.beckman.uiuc.edu 405 N. Mathews, Urbana IL 61801 USA Ph: (217)244-1565 e-mail: [EMAIL PROTECTED] _ -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300
Re: Bare Metal Restore sizing.
A noteworthy point. You can use the AIX 433 install CD to create the AIX 4.3 SRT. It can then handle AIX 4.3.1, 4.3.2, or 4.3.3. Generally, you want to use the latest relese of the level of the OS to build the SRT. Zlatko Krastev/ACIT wrote: Ray, let me point small and very rare but important issue: If you update AIX 4.3(.1) to 4.3.2 or 4.3.3 you have the ability to change a volume group to big volume group using chlv -B If you make a mistake to change to rootvg to big vg AIX 4.3 and 4.3.1 are completely uncapable to handle it. I am not yet familiar with details of TKG's BMR products and didn't read their docs. But even on an pure AIX complex (no TSM, no BMR) if and only if we do have an administrator (if I do this I would be very silly) which extended rootvg beyond limits of normal vg he will have to be sure that boot image is created from 4.3.[23]. Just some thoughts for something I hope will never happen. Girls and guys, has someone already done it ;-) Zlatko Krastev IT Consultant How often are the boot images refreshed? How BMR is going to realize that a client has upgraded its OS, when others have not? BMR does not currently validate the boot images. You will need to update the boot image when the client has a major OS level change (For AIX that would mean if the machine is upgraded from 4.1 to 4.2, but not from 4.3.2 to 4.3.3. ). The boot image creation does not take a long time, and it can be done regardless of the state of the client. The BMR database holds enough information about the client to help you build the correct boot image. -- Ray Schafer The Kernel Group www.tkg.com http://www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]+1 512 433 3300 -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300
Re: Bare Metal Restore sizing.
Eduardo, My comments are interspersed. Eduardo Martinez wrote: Hi All. Has anyone of you ever sized an BMR solution? I have several doubts about it. A) Space requirements for BMR software installation TKG says the following: The BMR server requires 4 megabytes of disk space plus approximately 1 KB of disk space for every 2 clients. Each Boot image on the Boot Server will require 100 to 800 KB of disk space. How much space am I going to need for each boot image? AIX Boot images are about 6 to 8 megabytes each. They are stored in /tftpboot on the Boot server. Is a boot image created for each of my clients? if so, am BMR is going to backup a boot image each time the client is backed up? in this case I have to calculate the space on disk according the backup policies for each one of my clients. or am I going to create ONLY one boot image per platform I 'm going to backup (one image for SUN, another for NT, another for AIX)? This way I'm going to use much less space than the above scenario. AIX boot images are are built using 3 parameters: Architecture, Processors, and Network type. The possible architectures are rspc, rs6k, or chrp. The possible processor types are up or mp, the possible Network types are ent or tok. So there are 12 possible boot images for each AIX SRT. There are currently 4 different AIX SRT's you can have on a File Server. (AIX 4.1, 4.2, 4.3, and 5.1). Solaris Boot Images are very small (200 KB) and you only need one for each SRT. NT boot images are just BMR database place holders. They take up no space, BMR does not use network boot for NT. NT is always booted from a BMR Floppy. How often are the boot images refreshed? How BMR is going to realize that a client has upgraded its OS, when others have not? BMR does not currently validate the boot images. You will need to update the boot image when the client has a major OS level change (For AIX that would mean if the machine is upgraded from 4.1 to 4.2, but not from 4.3.2 to 4.3.3. ). The boot image creation does not take a long time, and it can be done regardless of the state of the client. The BMR database holds enough information about the client to help you build the correct boot image. B) Shared Root Tree For the SRT TKG states: Each Shared Root Tree (SRT) on the File server will require 200 to 400 MB of disk space. The same questions as above. Is a SRT created each time a client is backed up? No. Once an SRT is created, it is shared among many clients. I've calculated the space Im going to need considering I have 6 clients (2 sun, 2 aix and 2 NTs), also that I only need one boot image per platform (3 in this case), and also one SRT per platform too. This makes a total of 606 MB. Are this calculations right? Your calculations are about right. You will need 3 SRT's, one for NT, one for AIX, and one Solaris. The SRT's will total about 600 MB. Each platform varies in the amount of disk space required for the SRT, and it depends on the OEM drivers and utilities that are added to the SRT to support the clients. So 200 MB is an average. NT takes about 100 MB, AIX takes about 300 MB, and Solaris takes about 200 MB. BMR Server BMR Server 1 4MB BMR Client 6 3.0Kb Boot Server Boot image 3 2MB File Server Shared Root Tree (SRT) 3 600 MB Total 606MB Thanks in advance. = Do or Do Not, there is no try -Yoda. The Empire Strikes Back ___ Do You Yahoo!? Yahoo! Messenger: Comunicacisn instantanea gratis con tu gente - http://messenger.yahoo.es -- Ray Schafer The Kernel Group www.tkg.com http://www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]+1 512 433 3300
Re: Desaster Recovery for Win2K Clients
Volker, Here is a link to a posting by Wanda Prather to this list made about a year ago. It describes a manual process of doing a Bare Metal Restore for Win2k Professional: http://msgs.adsm.org/cgi-bin/get/adsm0009/304.html The Kernel Group has a commercial product called Bare Metal Restore that completely automates the recovery of a system using the data from TSM. The current release works for AIX, Solaris, HP-UX, and NT. Windows 2000 server is currently in Beta and should be released in mid September. Here is a link to TKG's BMR: http://www.tkg.com/products/bmr/tsm Volker Reinen wrote: Moin, Does anybody have a description like a Cookbook to make a successfull desaster recovery on Win2K clients? Mit freundlichen Gruessen - Yours sincerely Volker Reinen System Engineering GE CompuNet Essen Severinstrasse 42, 45127 Essen, Germany Phone: +49-(0)201-2012-650, Fax: +49-(0)201-2012-7963, Mobile: +49-(0)173-3507643 E-Mail : Volker.Reinen @ gecits-eu.com Visit us on the Internet: http://www.gecits-eu.com This email is confidential. If you are not the intended recipient, you must not disclose or use the information contained in it. If you have received this mail in error, please tell us immediately by return email and delete the document. -- Ray Schafer The Kernel Group www.tkg.com Sr. Sales Engineer [EMAIL PROTECTED]+1 512 433 3300
Re: AIX 4.3.3 list of excludable files filesystems
The Bare Metal Restore product from The Kernel Group (http://www.tkg.com/products/bmr/tsm) has the ability to use the backup data in TSM to recover your server. The prepare to restore operation can be issued with a single command and will create a customized restore procedure that will automatically recover the entire machine, or if you prefer, just the rootvg. The prepare to restore operation will also allocate the BMR file and boot server components so they will answer the network boot and NFS requests of the server being recovered. It works well, and the restore is automated: prepare to restore and network boot. That's it. Lisa Cabanas wrote: Thanks for your reply, Herfried. It brings to mind some other questions regarding other volume groups. Say you have all your Oracle stuff on one or two different vgs. Would you need to have done a savevg sometime in the past to get the vg back, or at bare metal time would you need to manually create the volume group and lvs and fss associated with it, and then fill it with the data from TSM? I went and looked for a bare metal Redbook for AIX and found the one from 1997 that deals with AIX 4.1-- is it still pretty applicable to 4.3.3? I wonder if TSM still supports a bare metal for AIX, or if it is now unsupported like Win2K is? thanks lisa Herfried Abel [EMAIL PROTECTED] 08/09/2001 01:52 AM Please respond to ADSM: Dist Stor Manager To: [EMAIL PROTECTED] cc: (bcc: Lisa Cabanas/SC/MODOT) Subject:Re: AIX 4.3.3 list of excludable files filesystems Lisa, All the filesystems within the rootvg are backed up with a mksysb as long as they are not explicit excluded from rthe mksysb. In general AIX does not delete (major) files on reboot as other UNIX's do ( eg /tmp ). This is how we do the restore of an AIX machine : 1) restore mksysb 2) restore OS-definitions via TSM ( rootvg filesystems eg. /etc ) ( TSM Client already restored by mksysb ) 3) restore filesystems (non rootvg) via TSM 4) restore application-data ( DBs eg. ORACLE,SAPDB, MSSQL etc ) via TDP Agents in necessary. Step 2) depends on the time-difference between the mksysb and the last config changes of AIX. Should not be necessary if you make a mksysb after every config change , as all of the sysadmins do :-) So what we do, we dont exclude files from the rootvg in the TSM backup ( AIX-OS is not really need much space ) but we exclude lots of temporary application files. We think that at this point we can find a lot of temporary data (eg. SAP rollfiles ).Of cause you have to know your application / Datebase very well, so that you dont exclude a file by mistake. herfried Lisa Cabanas [EMAIL PROTECTED]@VM.MARIST.EDU on 08.08.2001 18:20:26 Please respond to ADSM: Dist Stor Manager [EMAIL PROTECTED] Sent by: ADSM: Dist Stor Manager [EMAIL PROTECTED] To: [EMAIL PROTECTED] cc: Subject: AIX 4.3.3 list of excludable files filesystems Has anyone ever compiled a list of files and/or file systems that can be excluded from backup either because they are dynamically created by the OS at reboot/syncvg etc or because they are included in a mksysb? The information contained in this transmission, which may be confidential and proprietary, is only for the intended recipients. Unauthorized use is strictly prohibited. If you receive this transmission in error, please notify me immediately by telephone or electronic mail and confirm that you deleted this transmission and the reply from your electronic mail system.
Re: bare metal restore for NT...
Walker, Thomas wrote: Also in the FAQ, I noticed that is does not *yet* support restoring to dissimiliar hardware. Considering that a true Disaster Recovery will probably take place in slightly different systems, I find it a little odd the BMR still doesn't support that yet. The hardest thing to do is restore NT machines because it's impossible to get an exact copy of the hardware at the DR site. So restoring the registry is useless. BMR looks promising, but only for NT. Mksysb's are still very useful and less of a hassle than setting up a BMR boot server. Our FAQ needs to be updated. The first phase of dissmililar machine restore is done. Release 3.1 is out and will support restore to dissimilar disks. This is phase one. More to come. I would like to point out that TKG's BMR is the only product that can do this on AIX, Solaris, HP-UX, and NT. I have set up many BMR Boot Servers. In my opinion, it is just as easy as doing a mksysb, but it is a one time effort. Mksysb's have to be done over and over again. begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: bare metal restore for NT...
Stephen A. Cochran wrote: Someone pointed TKG's product out a few months ago to me, and I looked at their site. If you read the FAQ carefully, you'll see that you will need one server for every type of system you need to restore. So if want BMR capability for both Solaris, AIX, and NT, then you'll need a Solaris, AIX, and NT server for their product to work. Each of those servers will need to run the BMR File Server and BMR Netboot Server.From the sound of it, I worry that if you had some servers running Solaris 6 and some Solaris 7, that you might need a different File/Boot server for each of those. The BMR File and Boot Servers do not have to be dedicated servers. They can be doing work while they are sitting there waiting to serve up boot images or satisfy NFS requests. A lot can change in a few months. Now, with the 3.1 release, BMR allows you to create CD's that can be used in place of File Servers and Boot Servers. This also allows you to circumvent the use of bootp, bootparams, tftp, and NFS during a TKG Bare Metal Restore if you desire. After taking over the TSM admin for our site, I've been looking in to BMR options. The best I've come up with so far is the following: I bought some big bit buckets for inside the TSM (RS6000 h50 AIX) server. Nothing too fast, just decent. For my AIX servers, I'm running makesysb and dumping the data onto a NFS share. If you are using TSM, wouldn't it be nice to just back everything up to TSM and then use the data in TSM to restore the machine? BMR allows you to do that. The mksysb's back up data that is also being backed up (more efficiently) by TSM. For Solaris and Linux, I'm using the hostdump.sh script from backupcentral.com (run by the Orielly backup book author) to dump to the NFS share. I manually dump the OS only after the change log is modified (we keep a change log on the boot system so that any admin that makes a change logs it in case there are problems). This way it's fairly automated. I also run it manually before/after patching or upgrading. I also run SysAudit and Sysinfo every night and dump those locally and to the same NFS share, so I have up to date info on the system in case I loose the disk configurations. TKG's BMR will capture the machine configuration using a fully automated process. To restore, I use the install CD to boot, get the networking up and running, mount the NFS share, and restore. I'm still rolling this out, but so far it's worked well. I restored a solaris 7 server as a test, and it was flawless. If you use Veritas Volume Manager on Solaris, how would you restore the machine with this methodology? It is a very manual process, but BMR handles it with no extra steps or reboots. begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: BRM Question
Mike, The BMR Server currently will not run on an NT machine. There are inexpensive UNIX boxes on the market that will easily hold a BMR Server, so this might be a vaible option yet. While porting the BMR Server to Windows NT (or 2000) is in our product plan, we have not yet set a release date for it. The requirements of our customers and potential customers are always important to us. Mike Glassman - Admin wrote: Ray, The terminolagy then is wrong as per what they explained, but I am still left in a situation when I need an additional UNIX based machine for the BMR main server. Do you have plans to bring out a version that sits on an NT machine, so that I will not need to include another OS in my backup server cluster ? I really can't go to management and sell this to them. Mike -Original Message- From: Ray Schafer [SMTP:[EMAIL PROTECTED]] Sent: b n`i 22 2001 15:24 To: [EMAIL PROTECTED] Subject: Re: BRM Question Mike, This is NOT true. While it is true that the Bare Metal Restore Main Server must sit on a UNIX machine (AIX, Solaris, or HP), it does not matter to BMR what type of platform is used for the TSM server - so long as TCP/IP communications are used between the BMR Server and the TSM server, and the TSM Clients and the TSM server. There is a FAQ available for BMR, as well as other documentation on the TKG website: http://www.tkg.com/bmr/tsm. Mike Glassman - Admin wrote: All, We just had a meeting with our support people for TSM, regarding finishing the project we have. To cut things short, one of the options we required was Bare Metal Restore of NT and Unix servers. Our TSM server sits on an NT server. We were just informed (and this is what I want to ask about) that the BRM server (TSM) module, does not operate if the TSM server is on an NT server. (As I understand from their explanation, there is the TSM server side module and the client module). So in effect, we cannot impliment BRM due to this factor. Does anyone know if this is true ? Mike Glassman System Security Admin Israeli Airports Authority Ben-Gurion Airport http://www.ben-gurion-airport.co.il Tel : 972-3-9710785 Fax : 972-3-9710939 Email : [EMAIL PROTECTED] Usage of this email address or any email address at iaa.gov.il for the purpose of sales pitches, SPAM or any other such unwanted garbage, is illegal, and any person, whether corporate or alone doing so, will be prosecuted to the fullest possible extent. File: Card for Ray Schafer begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: BRM Question
Mike, This is NOT true. While it is true that the Bare Metal Restore Main Server must sit on a UNIX machine (AIX, Solaris, or HP), it does not matter to BMR what type of platform is used for the TSM server - so long as TCP/IP communications are used between the BMR Server and the TSM server, and the TSM Clients and the TSM server. There is a FAQ available for BMR, as well as other documentation on the TKG website: http://www.tkg.com/bmr/tsm. Mike Glassman - Admin wrote: All, We just had a meeting with our support people for TSM, regarding finishing the project we have. To cut things short, one of the options we required was Bare Metal Restore of NT and Unix servers. Our TSM server sits on an NT server. We were just informed (and this is what I want to ask about) that the BRM server (TSM) module, does not operate if the TSM server is on an NT server. (As I understand from their explanation, there is the TSM server side module and the client module). So in effect, we cannot impliment BRM due to this factor. Does anyone know if this is true ? Mike Glassman System Security Admin Israeli Airports Authority Ben-Gurion Airport http://www.ben-gurion-airport.co.il Tel : 972-3-9710785 Fax : 972-3-9710939 Email : [EMAIL PROTECTED] Usage of this email address or any email address at iaa.gov.il for the purpose of sales pitches, SPAM or any other such unwanted garbage, is illegal, and any person, whether corporate or alone doing so, will be prosecuted to the fullest possible extent. begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: BRM Question
It will - in early August the next version of BMR will be released and will support Windows 2000. Rob Schroeder wrote: Does BMR support Win2000? Rob Famous Footwear begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: bare metal restore for NT...
The BMR Server should work just fine on the Sun Blade. Palmadesso Jack wrote: If you are speaking about budgets then I hear you. Then again I am wondering what the minimum requirements are. Sun makes these new machines called Blades. Some are as cheap as 1300usd and perform similar an Ultra60. We are trying a few of them out now. That wouldn't be such a large investment. Otherwise there is always next years budget. -Original Message- From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 22, 2001 11:18 AM To: [EMAIL PROTECTED] Subject: Re: bare metal restore for NT... Yes, so I understood, but with the amount of money we have already invested in the system, and with the fact that our dealers and integrators forgot to explain this issue untill yesterday (3 months after the initiall installation etc), I cannot now go and explain that I need a second server for BMR, as much as I would like to. So I am stuck. Mike -Original Message- From: Palmadesso Jack [SMTP:[EMAIL PROTECTED]] Sent: b n`i 22 2001 15:54 To: [EMAIL PROTECTED] Subject: Re: bare metal restore for NT... The wording is a bit hard to understand but I believe that the BMR server itself is a separate server and requires Unix. BMR does not care what the TSM server is itself. Check the FAQ out on their site. http://www.tkg.com/bmr/tsm This looks promising! -Original Message- From: Mike Glassman - Admin [mailto:[EMAIL PROTECTED]] Sent: Tuesday, May 22, 2001 10:37 AM To: [EMAIL PROTECTED] Subject: Re: bare metal restore for NT... Ray, Do you have some idea when you will have BRM that will work when the TSM server is an NT server ? Mike -Original Message- From: Ray Schafer [SMTP:[EMAIL PROTECTED]] Sent: b n`i 22 2001 15:13 To: [EMAIL PROTECTED] Subject: Re: bare metal restore for NT... Thank you, Jack. While we do offer BMR, The Kernel Group is an independent software vendor that has numerous relationships with IBM/Tivoli. In this particular case, our Bare Metal Restore product is re-marketed by IBM/Tivoli to extend the recovery capabilities TSM currently has with the system recovery that we provide. Palmadesso Jack wrote: You may want to look at the Kernel Groups Bare Metal Recovery tool. We are planning on bringing them in here. Supposedly its a one button recovery that interacts with TSM. By the way the Kernel Group is part of IBM. Jack -Original Message- From: Zosimo Noriega (ADNOC IST) [mailto:[EMAIL PROTECTED]] Sent: Monday, May 21, 2001 6:08 AM To: [EMAIL PROTECTED] Subject: bare metal restore for NT... I'm looking a tool or agent that i can use for complete disaster recovery for NT. I heard this tool, can you please provide me enough information. thanks a lot. Zosi Noriega ADNOC P.O. Box 898 AUH - AUE File: Card for Ray Schafer begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: Where are the solaris bare metal restore procedures for TSM4.x ?????!!!!!!
I admit I am biased. I work for The Kernel Group (TKG) and I am proud of our Bare Metal Restore (BMR) product and of the capabilities that BMR has provided to TSM. TKG's BMR generates restoration procedures during the Prepare to Restore operation. These procedures are customized for the particular machine being restored and are executed by BMR to drive the unattended recovery of this machine. In other words, not only does BMR generate system recovery procedures, it does so automatically at any time you choose to perform the BMR Prepare to Restore function (before or after machine failure). All configuration changes made to the machine are captured automatically (at TSM backup time) or manually (any time you choose) and are automatically incorporated into the custom restoration procedure at the time Prepare to Restore is run. So the restoration procedure is based on the machine configuration that existed when the TSM backup was done. The configuration present at the time of the last incremental describes exactly how you want to rebuild the machine before you restore this data, right? The Kernel Group's Bare Metal Restore for Solaris has several advantages over doing it by hand after booting from a jumpstart image: 1. You don't have to remember how the drive was formatted before, BMR will automate the format to the way it was at the last incremental backup. 2. You don't have to worry about making an error in the procedure. Human error is eliminated by the automated procedure generated and executed by BMR. 3. If you have a Volume Manager, BMR handles that as well. For example it can automatically re-partition, re-mirror and re-encapsulate a Veritas-encapsulated mirrored root drive, and then use TSM to restore the data. Automatically, unattended, in one fell swoop. 4. You can restore just the drives containing the operating system, or all the drives. 5. You can use the dissimilar disk restore feature to re-map filesystems to other drives, decrease or increase the file system size, or eliminate some filesystems if desired. 6. Because BMR's restoration process is automated, there is no manual intervention other than the initial network boot, so a large number of machines can be recovered by a small number of administrators and/or operators. 7. While BMR does support network boot, it also gives the option to create bootable CDs (this feature is referred to as Media Boot) in the event that network boot is not suitable for a given environment. Media Boot eliminates the requirement for NFS, bootp, bootparams, and tftp for UNIX, and DOS network drivers for NT. 8. BMR supports restoration from a TSM backupset. It is possible to do a complete LAN free restore of an NT server using both the TSM backupset and the BMR Media Boot options. 9. Because you can use the same tool for four major OS platforms (Solaris, HP-UX, AIX, NT), Bare Metal Restore eliminates the need to manage multiple backup and restore methods. Think about how much time you spend administering mksysb, jumpstart, sysback, Ghost images or mkrecovery. With BMR there's no need to perform redundant system backups or maintain client configuration definitions. So long as the normal TSM backups are taken, any BMR client can be completely recovered without additional effort. This alone represents a substantial savings in administrator time. We keep piling on functionality to BMR as we expand the breadth to other OS's. Your feedback is valuable to us. Keith Kwiatek wrote: Yes, and it seems rather expensive we have 750+ nodes and they are talking $200-300K for an enterprise license or somewhere between $400 and $900 per node for an individual license Our solaris clients were fine until we went to TSM 4.x now we can't use the tried and true method of boot off cd, and run dsmc to completely restore.With TSM4.x it seems solaris jumpstart doesn't provide libraries that TSM4.x needs to even provide a command line prompt Kernel Group gets around this with bootp+NFS, --as far as I can tell, all they really add is some scripts to automate the process of formatting and partitioning the drives (is this a good thing?). I think we could do the same if we can give our customers access to bootp and NFS (which is FREE), then they would just have to format+partitition, and run dsmc restore At least, that is the theory we might go with with Kernel Group's BMR yet Any other ideas? Keith - Original Message - From: Mark Stapleton [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Saturday, May 06, 2000 10:01 PM Subject: Re: Where are the solaris bare metal restore procedures for TSM 4.x ?!! Kevin M Wisneski wrote: When you get them (if you get them) can you foward them to meI am in the same boat as far as creating Solaris BMR
Re: AIX Help
Another trick is to use the at command to run things unassociated with the terminal: print dsmc sched 21 /dev/null | at now Robert Clark wrote: inittab shouldn't have the problem in the first place. And a way to work around the nohup problem is to not use ksh to run dsmc. (while in ksh) $bsh $nohup dsmc sched 21 /dev/null $exit (now back in ksh) (Seems to work well.) [RC] On Wed, May 09, 2001 at 05:23:48PM -0700, Joe Faracchio wrote: DING DING DING DING DING DING DING DING DING DING DING DING DING! thanks Frank McClean , This worked! (now can I get it into INITTAB) As you said I did: %vi strtsched strtsched [New file] #!/bin/ksh start_sched O dsmc sched /dev/null 21 trap start_sched O exit ~ strtsched [New file] 5 lines, 79 characters root@ucbackup2-on-[/] %chmod +x strtsched root@ucbackup2-on-[/] %strtsched strtsched[2]: start_sched: not found. root@ucbackup2-on-[/] %ps -ef|grep dsmc root 17296 1 0 17:20:51 pts/1 0:00 dsmc sched root 20032 18642 2 17:20:57 pts/1 0:00 grep dsmc Joseph A Faracchio, Systems Programmer, UC Berkeley Private mail on any topic should be directed to : [EMAIL PROTECTED] On Wed, 9 May 2001, McClean, Frank wrote: Put this in a file and execute the file as root: #!/bin/ksh start_sched O dsmc sched /dev/null 21 trap start_sched O exit This is from Curt Schriever at IBM support. IC26843 for AIX4.3.3 You may get a false error stating that start_sched not found, but the scheduler will stay running when you exit. -Original Message- From: Dearman, Richard [mailto:[EMAIL PROTECTED]] Sent: Wednesday, May 09, 2001 3:14 PM To: [EMAIL PROTECTED] Subject: AIX Help I am trying to run the nohup dsmc sched 2 /dev/null command on my AIX 4.3.3 machine and it works but every time I exit. It says There are jobs running so I exit again and whe I check the dsmc sched process is not running. I thought the nohup command was suppose to let process run even after you logout. What am I doing wrong. Thanks ***EMAIL DISCLAIMER** This e-mail and any files transmitted with it may be confidential and are intended solely for the use of the individual or entity to whom they are addressed. If you are not the intended recipient or the individual responsible for delivering the e-mail to the intended recipient, any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it, is strictly prohibited. If you have received this e-mail in error, please delete it and notify the sender or contact Health Information Management (312) 996-3941. begin:vcard n:Schafer;Ray tel;cell:+1 (512) 426-3188 tel;fax:+1 (512) 433-3200 tel;work:+1 (512) 433-3345 x-mozilla-html:FALSE url:http://www.tkg.com org:The Kernel Group;Sales and Services version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3, Ste. 601;Austin;TX;78746;United States fn:Ray Schafer end:vcard
Re: Restoring AIX (was Restoring Linux and Solaris)
Steve, I work for The Kernel Group, and we have a product that will allow you to to a Bare Metal Restore of AIX, Solaris, HP, and NT using the data in ADSM/TSM. The recovery is highly automated. We have solved the issues you found and more. You can check out our web site: http://www.tkg.com/bmr/tsm Steve Harris wrote: I've got a similar query to those restoring Solaris and Linux but re AIX. It annoys me that while I have a full TSM backup of the AIX rootVG I can't use it. The bare metal redbook is no use, it just says to use mksysb I've come up with a process which almost works assuming two bootable disks are available 1. Restore a standard mksysb image, which includes the TSM client to one disk 2. Run the alt_disk_install command phases 1 2 to set up an alternate rootvg and restore the most recent mksysb for the box (this is just to get filesystem sizes). 3. Use standard TSM commands to restore the / /usr /var /home filesystems on the alternate disk to the latest TSM backup 4. run alt_disk_install phase 3 to setup the restored system for boot 5. boot from alternate. 6. clean up bootstrap disk 7. remirror rootvg Unfortunately step 4 fails as the alt_disk_install command plays with the alternate ODM in phases 1 2, but I revert to the original ODM in 3. I need to restore the original ODM because minor details like software installations are kept there. I really think that this process can be made to work if I could just save the appropriate bits of the ODM at 2.1 and put them back at 3.1. The question is what are the appropriate bits? Any AIX experts with good ODM knowledge out there? Regards Steve Harris AIX and ADSM Admin Queensland Health, Brisbane Australia
Re: BMR Software
My name is Ray Schafer. I work at The Kernel Group (TKG) and have been a member of the Bare Metal Restore development team, and am currently a Sales Engineer specializing in the BMR product. I would like to respond to the list about some of the points that Richard Sims brought up. It is encouraging that The Kernel Group is the BMR vendor, given their track record in supporting AIX in conjunction with IBM. But I'm not encouraged by how far behind the curve TKG is in keeping BMR current. The product FAQ on the web site outlines all the basic things that BMR does not support; and that they still don't have Windows 2000 support, for this major OS, indicates that they are not devoting substantial resources to the product. (I get the impression that they're late on this because they've been a Unix company primarily.) You must realize that BMR is a complex piece of software. It automatically performs the tasks required to rebuild a machine from scratch. These tasks are obviously different on the different platforms, and each platform presents challenges for us to handle different types of devices (network and storage). Our focus on development has been to expand the breadth of BMR by porting it to the major platforms, and the depth of BMR by handling different types of devices per platform. We carefully analyzed the market to understand which platforms were the most important to support, and performed the work required to support those platforms in a relatively short period of time by anyone's standard. Far from being UNIX oriented, we recognize that NT support is important to our customers, and are focusing even more energy on that platform. Platform support is market driven. We focus on what customers need now. We found that Windows 2000 was not as much a priority for our customers, or potential customers. Right now, our customers are telling us that Windows 2000 is a small part of their production environment. Most people are planning on having more Win2k in production by mid year which is when we intend to have it available. Perhaps not surprisingly, we have more requests for NetWare than for Win2k. We are currently aggressively working on support for Windows 2000, and NetWare, and expect that work to be released some time in the second quarter this year. We have a huge commitment to BMR. We have a large team of talented developers that work hard on this product. As part owners of the company, we are committed to it's success. -- Ray Schafer |[EMAIL PROTECTED] |http://www.tkg.com The Kernel Group =-=-=-=-=-=-=-=-=- Core Confidence for E-Business TKG's Bare Metal Restore can re-build your machine from the ground up with a single command - using the data stored in TSM (ADSM) begin:vcard n:Schafer;Ray tel;cell:+1 512 426 3188 tel;fax:+1 512 433 3200 tel;work:+1 512 433 3300 x-mozilla-html:FALSE url:www.tkg.com org:The Kernel Group;Serices version:2.1 email;internet:[EMAIL PROTECTED] title:Senior Sales Engineer adr;quoted-printable:;;1250 South Capital of Texas Highway=0D=0ABldg 3 Suite 601;Austin;Texas;78746;United States of America x-mozilla-cpt:;0 fn:Ray Schafer end:vcard
Re: Bare Metal Restore Product fro the Kernel Group
"Kovacs, Mark" wrote: Shawn, He have both UNIX and NT servers running in our shop. We have both NT and HP-UX TSM servers, so it should not be a problem. I would like to get a contact that can give us some good technical insight into the product and how well it works. I was even wondering if you can use it to quickly create a recovery partition, load a basic OS and TSM clients, and then run a normal full TSM recovery. Since you asked: TKG's BMR does this automatically. There is a link to a document about how BMR works with NT. See http://www.tkg.com/bmr/bmr-nt.pdf. Other documents are in: http://www.tkg.com/bmr/docs.html. And another link for contact information: http://www.tkg.com/contact.html. -- Ray Schafer |[EMAIL PROTECTED] |http://www.tkg.com The Kernel Group =-=-=-=-=-=-=-=-=- Core Confidence for E-Business TKG's Bare Metal Restore can re-build your machine from the ground up with a single command - using the data stored in TSM (ADSM)
Re: AW: Tivoli TMS (ADSM) vs Veritas Netbackup
"Klatt, Michael" wrote: http://www.keylabs.com/results/veritas/veritas.html Intersting... The test doesn't seem to test real world scenarios. I wonder why they didn't test network backup and restore. I wonder why they tested client and server on the same machine - how many people do that? Only one test went to a disk cache, the rest were directly to tape. Did they use client side compression on TSM? That would affect CPU and througput - especially on the same machine. I would like to see a test of the products in a scenario that matches how the products are used on a daily basis over time. For example, after measuring backup times each day for a month in a controlled environment, how do they compare? -- Ray Schafer |[EMAIL PROTECTED] |http://www.tkg.com The Kernel Group =-=-=-=-=-=-=-=-=- Core Confidence for E-Business TKG's Bare Metal Restore can re-build your machine from the ground up with a single command - using the data stored in TSM (ADSM)
Re: ADSM SP Client Install
Daoud Shariff wrote: ADSM Guru's: We are in the process of rebuilding a Wide Node in an 8 WN/2F SP. The SP is already an ADSM Client, with one Node being the ADSM Server. I believe the install images are on the ADSM Server, but they do not coincide with the 'Installing the Clients' manual. What would be the best way to rebuild this Node? Should we use the CD's or the ADSM 3.1 Server images? What images should we look for? Are there preferred directives and preferred Publication info that can be shared? Or will the 'Installing the Clients' manual have to suffice? Any otherwise pitfalls, that we have to look out for? So the node you need to rebuild is an ADSM client? If you do "splstdata -b" on the control workstation, what image name do you see for the node to be restored? This image is the name of the image on the boot/install server (usually node 1 but not always). It can be an image created by mksysb. If it is, than use that image to restore. You will have to set the machine to install. You can do that in smit or on the command line (check your SP manual for more details). It will then set things up (allocate NIM resources, and configure PSSP) then you can reboot the node. It should then restore the image using NIM. If it is a recent mksysb, you are almost home - you just have to do an ADSM restoration after you come up. If it's not a mksysb image or if it's way out of date, then you may have some more work on your hands. You may have to install the ADSM client software, and then do a restore, hopefully you'll come up to a stable state. Good luck! -- Ray Schafer |[EMAIL PROTECTED] |http://www.tkg.com The Kernel Group =-=-=-=-=-=-=-=-=- Core Confidence for E-Business TKG's Bare Metal Restore can re-build your machine from the ground up with a single command - using the data stored in TSM (ADSM)
