Thanks, Wanda. I think you answered my question. I just want to make sure
there are no issues. So, to clarify...
I have had management classes setup to handle these files for a long time,
and they are pointing to either a diskpool or a tapepool. I want all of
the files in these management classes to eventually be stored in a
different disk and tape pool. It sounds like the best way to do this is
(very simply) to just change the copy-to destination of the existing
management classes for these files to point to the new storage pools. I
will still maintain the original storage pools for other management classes
still in use.
I just wasn't sure of any negative aspects of this change. Do you see any
gotchas? anything in particular of which I should be aware?
Thanks again,
Todd
|--------+-------------------------->
| | "Prather, Wanda"|
| | <Wanda.Prather@J|
| | HUAPL.EDU> |
| | Sent by: "ADSM: |
| | Dist Stor |
| | Manager" |
| | <[EMAIL PROTECTED]|
| | T.EDU> |
| | |
| | |
| | 07/02/02 11:50 |
| | AM |
| | Please respond |
| | to "ADSM: Dist |
| | Stor Manager" |
| | |
|--------+-------------------------->
>--------------------------------------------------------------------------------------------------------------------|
|
|
| To: [EMAIL PROTECTED]
|
| cc:
|
| Subject: Re: Changing Storage Pools/Management Classes
|
>--------------------------------------------------------------------------------------------------------------------|
If you want some files in a different tape storage pool, you will need a
new
management class for them.
If you are backing up direct to tape, just point the new management class
to
the new tape storage pool. Use INCLUDE statements in dsm.opt to bind just
the files you want to the new management class.
If you are backing up to disk first, you will need to create a new disk
pool
for these files as well as a separate tape pool. (You can't have one
primary disk pool that migrates to two different tape pools.) Make the new
management class point to the new disk pool and have the disk pool point to
the new tape pool.
When you backup files to the new management class, the NEW backup versions
will go to the new pool(s).
Nothing happens to older/existing backup versions of those files. They
stay
on whatever media they were on originally. Nothing triggers them to move
or relocate. They aren't hurt, you can still restore from them if you need
to. The best thing to do is just leave them where they sit, and let them
expire when they normally would.
-----Original Message-----
From: Todd Lundstedt [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, July 02, 2002 11:48 AM
To: [EMAIL PROTECTED]
Subject: Changing Storage Pools/Management Classes
I sent this out just over a month ago, and received no responses. Trying
again to see if anyone can help.... Thanks..
Currently, we backup everything either to DISKPOOL (which migrates to
LTOTAPE), or directly to LTOTAPE. Files (backup/archive client), databases
(TDP for Domino, and TDP for SQL), everything is eventually stored into
LTOTAPE. The databases get backed up FULL every time. The largest
database we have is ~75GB. The TDP SQL databases are in a different set of
management classes from the other files (TDP Domino databases have their
own management class, as well).
Soon, we will be creating an application that will have a 500GB database.
FULL backups for SQL databases will be changing over to FULL with DIFFs
(for the larger databases, FULLs on the smaller ones). I would like to
segregate the SQL databases into their own tape storage pool. There will
be no reclamation on the tapes in this storage pool, and collocation will
be turned on, because I will be doing some striped backups. (I don't see
the sense in reclaiming tapes when the major databases range in size from
10% to 400% of a tape, but give me a reason to consider it, and I will)
What is the best way to handle moving/changing the storage location of my
SQL databases from the LTOTAPE storage pool to the LTOSQLTAPE storage pool
(I just made that name up).
Should I modify the existing management classes to start using the new
storage pool? If so, what happens to the files in the current storage
pool?
Should I create a new management class pointing to the new storage pool and
change the INCLUDE statements to point to the new management class? If so,
what happens to the files in the current storage pool and the current
management class?
Is there another way to do this?
Thanks in advance for your help.
Todd Lundstedt
Technical Specialist
Via Christi Information Management Services
[EMAIL PROTECTED]
ps FYI. Since the first time I sent this note out, I have done some
testing. After working with TSM support on an issue that came up in my
testing, I find out that a management class cannot be changed if you are
backing up LANFREE. You must back up the file across the LAN in order to
change the management class. Once the active version of the file is in the
new management class, LANFREE backups can resume. However, I am still
getting occasional errors when I do this, and then try to perform striped
backups.
