It could be but is a very rare situation. And you do not have the
reusedelay parameter for diskpools, do you.
Zlatko Krastev
IT Consultant
Sam Sheppard <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
22.02.2003 01:03
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Order of daily admini
---------------------------- Top of message ----------------------------
>>--> 02-21-03 14:59 S.SHEPPARD (SHS) Re: Order of daily admini
I had the opportunity to have to restore a database a while back from a
backup created after disk pool backup and before migration. After
finishing, it appeared that the disk pool was in the same state as
before the migration. Audit showed no inconsistencies and migrations
kicked off and migrated the data that had already been migrated.
Looks like migration doesn't really affect the data on the pool, just
moves it to tape and updates the database.
Sam Sheppard
San Diego Data Processing Corp.
(858)-581-9668
-----------------------------------------------------------------------`
---------------------------- Top of message ----------------------------
>>--> 02-21-03 13:21 ..NETMAIL () Re: Order of daily admini
Date: Fri, 21 Feb 2003 16:17:42 -0500
From: "Steve Roder" <[EMAIL PROTECTED]>
Subject: Re: Order of daily administrative events
To: [EMAIL PROTECTED]
_________________________________Top_of_Message_________________________________
> Backups
> Creation of copypool volumes from disk
> Creation of copypool volumes from primary tape
> DB backup
> Remove offsite tapes
> Migration from disk to cartridge
> Expiration
> Reclamation
I like to clear my disk cache before backing up the DB, so that if I
restore that DB, I don't have a problem with what is in the disk storage
pools, as they certainly will not reflect what the DB thinks is in there.
It may then be a situtation where the only copy of some of your data is in
your copypool.
>
>
>
> --
> Phillip Ford
> Senior Software Specialist
> Corporate Computer Center
> Schering-Plough Corp.
> (901) 320-4462
> (901) 320-4856 FAX
> [EMAIL PROTECTED]
>
>
>
>
> -----Original Message-----
> From: Lawrence Clark [mailto:[EMAIL PROTECTED]
> Sent: Thursday, February 20, 2003 10:36 AM
> To: [EMAIL PROTECTED]
> Subject: Re: Order of daily administrative events
>
>
> Backups
> creation of copypool volumes
> Migration from disk to cartridge
> DB backup
> Expiration (which triggers reclamation)
>
> >>> [EMAIL PROTECTED] 02/20/03 11:28AM >>>
> I was just wondering what order that most TSM users have their daily
> processes running (IE: Migration, Expiration, Reclaim etc). It seems
that
> those process times were set up wrong when our TSM server was first
> installed. Our process schedule looks this way right now. I know its way
off
> base from what it should be. Any suggestions? I know I need to put
> EXPIRATION first.
>
> thanks,
>
> Tommy Templeton
> Senior System Administrator
> DFA-MMRS
> 601-359-3106
> e-mail - [EMAIL PROTECTED]
>
> Scheduled Start Actual Start Schedule Name
> Status
> -------------------- -------------------- -------------
> ---------
> 02/19/03 06:00:00 02/19/03 06:00:16 BACKUPSTG_D-
> Completed Backup disk storagepool
> ISK
>
> 02/19/03 06:15:00 02/19/03 06:15:17 BACKUPSTG_T-
> Completed Backup tape storagepool
> 02/19/03 07:30:00 02/19/03 07:30:18 BACKUPSTG_O-
> Failed Backup tape offsitepool FFSITE
> 02/19/03 09:00:00 02/19/03 09:00:19 RESET_MIGR_-
> Completed Reset threshold for migrate to tape pool low
> LOW
>
> 02/19/03 11:00:00 02/19/03 11:00:20 RESET_RECLA-
> Completed Reset threshold for reclamation of offsitepool1 low
>
> IM_OFFSITE-
>
> _LOW
>
> 02/19/03 13:00:00 02/19/03 13:03:50 DBBACKUP_FULL
> Completed TSM database backup
> 02/18/03 14:00:00 02/18/03 14:00:11 EXPIRE_INVE-
> Completed Expire inventory
> NTORY
>
>
> 02/19/03 14:00:00 02/19/03 14:00:21 RESET_MIGR_-
> Completed Reset threshold for migrate to tape pool high
> HIGH
>
> 02/19/03 14:00:00 02/19/03 14:00:21 RESET_RECLA-
> Completed Reset threshold for reclamation of tapepool low
> IM_LOW
>
> 02/19/03 17:00:00 02/19/03 17:00:21 DELETE_VOL_-
> Completed Delete volume history file
> HIST
>
> 02/19/03 17:00:00 02/19/03 17:00:21 DEL_DBVOL_H-
> Completed Delete database volume history
> IST
>
> 02/19/03 17:15:00 02/19/03 17:15:21 DEL_DBSNAP_-
> Completed delete dbsnapshot volume history
> HIST
>
> 02/19/03 18:00:00 02/19/03 18:00:22 RESET_RECLA-
> Completed Reset threshold for reclamation of tapepool high
> IM_HIGH
>
> 02/19/03 18:30:00 02/19/03 18:30:22 RESET_RECL_-
> Completed Reset threshold for reclaim of copy pool high
> COPY_HIGH
>
> 02/19/03 19:00:00 02/19/03 19:00:22 RESET_RECLA-
> Completed Reset threshold for reclamation of
> offsitepool1high
> IM_OFFSITE-
>
> _HIGH
>
>
>
>
> *********************************************************************
> This message and any attachments is solely for the intended recipient.
If you
are not the intended recipient, disclosure, copying, use or distribution
of the
information included in this message is prohibited -- Please immediately
and per
manently delete.
>
>
Steve Roder, University at Buffalo
HOD Service Coordinator
VM Systems Programmer
UNIX Systems Administrator (Solaris and AIX)
TSM/ADSM Administrator
([EMAIL PROTECTED] | (716)645-3564)
-----------------------------------------------------------------------`
