ADSM-L

Re: [ADSM-L] managing space

2007-04-10 00:17:45
Subject: Re: [ADSM-L] managing space
From: "bogdan.stoica AT clicknet DOT ro" <bogdan.stoica AT CLICKNET DOT RO>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 10 Apr 2007 07:17:12 +0300
One of my biggest problem is that I have 2 mailstore to backup and that's a
lot of data. With ultrium2 I need a lot of tape....
Data changed in 2 days is about 800 -1000 Gb. So, I need a full backup once
at 1'th date of the month that will be keepd 2 years and rest a rewritable
backup at 1st ,3th and 5th day of week.


Roger Deschner a scris:

Hello. This is not the way that TSM works. You need to understand the
TSM system of "progressive backups", where a file is backed up only
once. If it never changes, it is never backed up again. Every day, only
the files that change get backed up. The TSM Database keeps track of all
this, and allows you to do a complete restore if you need to, getting
each file from the tape it was written to. I suggest looking in the
manual "TSM Administrator's Guide" which you may be able to find in your
own language for easier reading. There is an English copy at
http://publib.boulder.ibm.com/infocenter/tivihelp/v1r1/index.jsp.

You have two separate backup requirements. One is the normal working
backups. Instead of weekly overwrite and so on, you need to set these up
with 7 inactive copies, keep inactive copies for one month, and use
normal TSM progressive backups. You will find that normal TSM
progressive backups are MUCH faster than overwriting a full backup every
2 or 7 days, use a LOT less tape, and that it gives you better
protection. For fastest restore, these should probably be set up with
TSM collocation.

Your monthly archive is a separate problem. This should be a TSM archive
process, set to be kept for 2 years. This would be a full archive copy.

Multiple backups will be written to the same tape, until it is full. The
same tape can have backups from different dates on it. This is normal,
and it saves tape. The tape will be reused and overwritten automatically
when enough of its files have expired that it can be copied to a new
one. The default is when it becomes 50% empty.

Do not forget that you also need to back up the TSM Database to tape.

Hope this helps get you started. It is a different way of working in
TSM. You do not have the usual cycle of weekly full backups and daily
incremental backups. TSM is very different - you never do a full backup
after the first day, because you do not need to. This confuses a lot of
people, but once you understand how progressive backups work and how the
TSM database keeps track of everything for you, then you will understand
how it is really better.

Contact your local IBM office and have them order a copy of the TSM
Concepts Poster for you. It is free, and it makes of these concepts a
lot easier to understand. The poster is IBM publication number
SC32-9464-00.

Roger Deschner      University of Illinois at Chicago     rogerd AT uic DOT edu



On Sat, 7 Apr 2007, bogdan.stoica AT clicknet DOT ro wrote:

I want to make the following configuration:

1. on 1 server i want to have all data on one or two tape, with backup full
once at 2 days, with overwrite all data at the second day. At 1'th in the
month I want to have a full backup that i need to keep 2 years separately
(about 500Gb uncompressed)

2. on 1 server i want to have backup on another one or two tape, with weekly
full backup and daily incremental with overwrite data at the end of week. At
1'th in the month I want to have a full backup that i need to keep 2 years
separately (about 300Gb uncompressed)

3. on 2 servers i want to have a daily incremental backup on separately tape

4. rest servers will use the rest of tapes...

I have a ibm lto 8192 with more than 20 slots, used 10 slots now.

Thanks for helping me





<Prev in Thread] Current Thread [Next in Thread>