I have an Admin schedule to backup the TSM database that has missed it's
schedule start window twice this week. Environment is 3466-C00, AIX 4.3.2,
TSM 3.7.2 and a q schedule shows this:
tsm: FSPHNSM1q sched backup_db t=a f=d
Schedule Name: BACKUP_DB
Well what do you know?!? Another ADMIN schedule to manage storage pools was
running. When it finished, the BACKUP_DB admin schedule started. But, does
this mean that only one (1) admin schedule can be active at any given time?
TIA,
John G. Talafous IS Technical Principal
The Timken
The ADMIN schedule that processing storage pools contained a "backup stg
blahpool blahpool wait=yes". When the wait completed, another backup stg
command was issued and the ADMIN schedule ended. Then, the ADMIN schedule to
do the database backup kicked off.
Does this mean only one ADMIN
The issue here would seem to be the "wait=yes" option you have specified for
the backup command. Doing so causes the server to process the command in the
foreground. This, in turn, requires that you must wait for the command to
complete before performing any other tasks. Indeed, in such an
Yes, the compelling reason is to have the backups of storage pools complete,
hopefully, by 9:00AM. Then the scheduled launch of a database backup at
10:00AM would coincide nicely with DRM processing and the resultant ejection
of tapes from an ATL.
But, if clients send more data than
You can simulate having an EVENT driven scheduler by changing the database
backup event from a straight command to a script. See, for example, the
Tivoli-supplied script BKUP_STG_DB that is shipped with the product. In the
supplied sample, they show doing a storage pool backup, followed by a
Hello All,
Please provide me your suggestions and comments regarding my proposed
configurations. Please help me.
I am planning to upgrade Adsm server both hardware and software due to
tremedous increase of a heterogeneous clients and the to upgrade ADSM
software into a latest version. The
