Hi, Bill. I believe the migration destination you're talking about is the
destination for HSM migrated files. I think the following might accomplish
your goal.
upd stgpool diskpool next=""
(run your backup)
upd stgpool diskpool next=tapepool
upd mig thresholds to start migration
Thanks,
Alex
-----Original Message-----
From: Bill Robb [mailto:[EMAIL PROTECTED]]
Sent: Thursday, June 14, 2001 7:09 PM
To: [EMAIL PROTECTED]
Subject: Full Disk Buffer Stopping a Backup.
Folks...
I have an instance where I want to backup an entire Sybase database to its
own disk buffer. However, for DRP purposes I need the entire database, so
if the buffer reaches it high threshold, I want the backup to fail. I'll
then increase the size of the disk buffer, and restart the backup. What
I'm trying to prevent is having the backup spill to a sequential, or copy
pool.
Later in the day though, I will want to empty the buffer by migrating it to
a sequential pool - I'll do this via command to reset the thresholds.
I think I can do this by not specifying a 'next' pool when I define the disk
buffer, and by specifying a destination on the management class (for the
migration).
Is my thinking correct?
Thanks...
Bill Robb
