Hi Robert
I usually handle this by having a schedule that runs every hour, and two
subsidiary admin schedules. One sets the hourly schedule to
expiration=N to start it running. the second sets the hourly schedule
expiration to a date in the past to stop it from running.
Regards
Steve
Steven
I just have an admin schedule that runs after the last hourly log job and
before the dif/full backup job that updates the log backup schedule to a
STARTDATE/STARTTIME= to however many hours the diff/full backup runs.
Bill
-Original Message-
From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.
Hi,
you can created different dsm.opt files an present SQL server as two
different nodes, also create two different
management classes: one for transaction logs (every hour) and one for
diff/full backup,
Use these dsm.opt file witn dsmcutil to create two schedules, and
TCPCLIENTPORT to specify di
Ray,
We are on our 3rd E-fix for node replication. 6.3.1.009. There appears
to be a lot of high level DB locking in the 6.3.0 code. IBM has made
several code fixes for us and is working on a few more issues. Below is
what we have on.
tsm: TSM02FM>show banner
**
Hi All
Like a lot of us, I'm contemplating a TSM 5.5 to 6.3 move for one of my
customers.
Most clients are not a problem, point the client at the new server,
take the first backup, and then after an appropriate length of time
either delete the data on the old server or export/import whatever is
- Original Message -
> From: "Steve Harris"
>
> Hi All
>
> Like a lot of us, I'm contemplating a TSM 5.5 to 6.3 move for one of
> my
> customers.
>
> Most clients are not a problem, point the client at the new server,
> take the first backup, and then after an appropriate length of time
>
