Hi Zoltan

We've been told the 3592 announcement is this coming Thursday, whether that's US or 
Australian time I'm not sure, but our reseller is very keen to sell them to us unstead 
of the H upgrade we'd been planning.  I won't steal their thunder by giving away any 
details.

I just looked up the doc and I'm surprised to see that TSM 5.1 supports an image 
backup without mounting read only, with the advice to run an fsck after restore.  I'd 
have to test the heck out of it before I'd trust that.

You don't say what type of client you are backing up, but I'd be inclined to take some 
sort of shapshot if that was possible. A five minute outage to get a clean backup is 
worth it, considering the investment that has been made.

In AIX and Solaris it is possible to run  a snapshot filesystem - but I don't think 
you can run an image backup on it.
It is also possible to split a mirror and with some fiddling mount it on a different 
mount point.
The third alternative would be to take an image at the disk array level e.g. EMC 
Timefinder, IBM  FlashCopy or similar and then back that up.  One advantage here is 
that the copy volumes could be mounted on thenew TSM server and thus backup directly 
across the SAN rather that via ethernet.

Management probably won't like it, but that's the cost of a clean image.

Regards

Steve Harris
AIX and TSM Admin
Queensland Health, Brisbane Australia




>>> [EMAIL PROTECTED] 19/08/2003 5:45:37 >>>
I think that I have asked a similar question, so I apologize if this
sounds like a repeat.....

We are trying to implement IMAGE backups for our larger systems (1TB
plus).  We have purchased a new AIX system just for this purpose. Our
experience with IMAGE backups, is pretty much nil !

We are still trying to figure out what type of tape drive/library to buy.
We are leaning towards an LTO2 system (I have been trying to convince them
to look at the new 3592 but it is so new there is no information on
IBM.COM about them. Probably too expensive, anyway !!).

My boss wants to dedicate this TSM server to *JUST* IMAGE BACKUPS. The
INCREMENTALs would still go to the existing TSM server that handles it
right now.  This way, we wouldn't have to do much, if any, administrative
processes (reclaims, copypools, etc).  (Is this even do-able ? )

However, my concerns are the elapsed times and synchronization.

Lets say the IMAGE backup takes 24-hours or more.  Since this is an active
email system, there are tens-of-thousands of files being created / edited
/ received / deleted / sent, daily (when the server was down for 2-days,
the NAV email scanners had over 90K messages backed up, awaiting to be
received).

Would we continue to run INCREMENTALS to server-A, while the IMAGE backup
is running to server-B  or do we have to wait until after the IMAGE
finishes ?

How about the restore/syncing processes. How would it figure out what to
restore ?  Would we just guess on a PIT set to the time the IMAGE backup
started ?

What about files "in flight" during the IMAGE backup and/or from the time
the IMAGE started and the INCREMENTAL started ?  Are they just considered
"collateral damage" and not recoverable ?

Any thoughts on this would be helpfull.



***********************************************************************************
This email, including any attachments sent with it, is confidential and for the sole 
use of the intended recipients(s).  This confidentiality is not waived or lost, if you 
receive it and you are not the intended recipient(s), or if it is transmitted/received 
in error.

Any unauthorised use, alteration, disclosure, distribution or review of this email is 
prohibited.  It may be subject to a statutory duty of confidentiality if it relates to 
health service matters.

If you are not the intended recipients(s), or if you have received this e-mail in 
error, you are asked to immediately notify the sender by telephone or by return 
e-mail.  You should also delete this e-mail message and destroy any hard copies 
produced.
***********************************************************************************

Reply via email to