|
Title: Bare Machine Recovery Post by: Maarten Visser on April 01, 2008, 02:06:58 PM Hello all!
I'm searching for a fast and simple bare machine recovery solution. We use TSM for the oracle online backups, and NIM for the mksysb images, and we make a Incremental system backup with TSM also. When I need to do a bare machine restore, first I need to load the mksysb from the NIM server. Then do a incremental restore from the TSM server and then put my databases back. Isn't there a way so that my TSM server can do it all? Title: Re: Bare Machine Recovery Post by: Michael on April 01, 2008, 08:46:53 PM When you said incremental restore I thought you meant of the other volume groups, but on second reading I wonder if you mean incremental restore of rootvg.
What I have heard of as a solution is to use regular mysysb images (i.e. complete rather than incremental) of rootvtg to the nim server - and the nim server is also a client of TSM - to aid with the management of the individual mksysb's rather than a single 'clone' image that is a initial starting point for all systems. The is nothing magical about booting using tftp. The magic of NIM is that is a system for managing installable images. AFAIK it is not an original IBM product, but something that IBM licenses, and has perhaps modified to make it suitable for both AIX and Linux installations and updates. I have practically no knowledge of Tivoli products, solutions, or system management architecture. But from students what I hear that seems to be the most practicle solution is to have the NIM server be a TSM client - storing the rootvg mksysb images. What this also requires is that applications (data) are not part of rootvg. Then the changes to rootvg are relatively few. Title: Re: Bare Machine Recovery Post by: Maarten Visser on April 04, 2008, 02:48:22 PM When you said incremental restore I thought you meant of the other volume groups, but on second reading I wonder if you mean incremental restore of rootvg. What I have heard of as a solution is to use regular mysysb images (i.e. complete rather than incremental) of rootvtg to the nim server - and the nim server is also a client of TSM - to aid with the management of the individual mksysb's rather than a single 'clone' image that is a initial starting point for all systems. The is nothing magical about booting using tftp. The magic of NIM is that is a system for managing installable images. AFAIK it is not an original IBM product, but something that IBM licenses, and has perhaps modified to make it suitable for both AIX and Linux installations and updates. I have practically no knowledge of Tivoli products, solutions, or system management architecture. But from students what I hear that seems to be the most practicle solution is to have the NIM server be a TSM client - storing the rootvg mksysb images. What this also requires is that applications (data) are not part of rootvg. Then the changes to rootvg are relatively few. My bad, I do a incremental backup of the other volume groups on my system. Rootvg isn't changing(much) so one mksysb every friday for rootvg is enough. The one thing I hoped was that TSM could do it all. TSM cannot make an mksysb image from a node, so now I have 3 different tasks to do a restore. Thanks :) |