ADSM-L

Re: Question - Migration

2006-05-23 12:06:14
Subject: Re: Question - Migration
From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Tue, 23 May 2006 18:05:13 +0200
Hi,

Short answer, I don't think that there is such a setting. But:
- Change your admin script to do - Backup stg disk -> copy (all data is
send to copy stg before migration);
                                         - backup stg tape -> copy (any
data in tape pool that isn't in copy will be copied)
                                           - Back-up ITSM database
                        now your DRM tapes are there     
                                           - migrate disk -> tape
- implement maxsize on the diskpools so that large files are send to
tape instead of disk during the back-up. This will reduce the amount of
data moved from disk to tape and reduce the time needed for creating the
DRM status.

And, using system tools?, find the bottlenecks causing the time problem
and if possible solve them too.

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Nancy L Backhaus
Sent: dinsdag 23 mei 2006 17:40
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Question - Migration

Problem:   TSM doesn't have enough time during the day to drain all of
the
diskpools down to 0% before client backups start in the afternoon.
So,
on our declared disaster day, one of our critical small DB2 databases
was
still on disk never going to tape.   Because migration selects the
largest
client with the largest amont of data, that small database is stuck in
disk for multiple days never going to tape.    I could seperate the
critical servers into smaller disk pools as one solution, or collocate
by group node data.

Question>   Is there a way  to force all of a client nodes data in a
diskpool to migrate to tape even though it falls below the low migration
setting?     I see settings in update stgpool to keep data longer in
disk,
but I want any data that is left over from yesterday to migrate first
before starting with the largest client again.



Background:

TSM Server  Extended Edition 5.3.2.2
AIX Operating System 5.3



Our clients all back up to disk pools first , then we backup the
diskpools to onsite tape pools, then do a backup of the onsite tapepools
for disaster recovery and send those tapes to an offsite location.


Nancy Backhaus
Enterprise Systems
HealthNow, NY
716-887-7979

CONFIDENTIALITY NOTICE: This email message and any attachments are for
the sole use of the intended recipient(s) and may contain proprietary,
confidential, trade secret or privileged information.  Any unauthorized
review, use, disclosure or distribution is prohibited and may be a
violation of law.  If you are not the intended recipient or a person
responsible for delivering this message to an intended recipient, please
contact the sender by reply email and destroy all copies of the original
message.

Attachment: Disclaimer.txt
Description: Text document

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