What messages did you get in the activity log? It could be a number of problems. Are the session limit parameters correct? Are there tapes in the primary tape pool that you are sending to (is it a primary pool). I presume when you say copy pool you mean next storage pool which is a tape (sequential) primary storage pool. Usually when I have this problem it is something dumb that I just forgot to key in.
The other piece is the database estimated element support did not come into play until recently which will be needed if you want to cause it to fail over to the tape pool if it is too large for the disk pool. Did you set a maximum threshold on the primary disk pool? -----Original Message----- From: Joe Cascanette [mailto:[EMAIL PROTECTED]] Sent: Monday, November 26, 2001 2:16 PM To: [EMAIL PROTECTED] Subject: Re: data to tapepools. If the databases are large, you can set a value in the pool to say anything over 500megs is size (or any size) to go directly to tape. Joe Cascanette -----Original Message----- From: Pothula S Paparao [mailto:[EMAIL PROTECTED]] Sent: Saturday, November 24, 2001 1:39 AM To: [EMAIL PROTECTED] Subject: data to tapepools. Importance: High Hi tsmers, can any one suggest me how to backup up data directly to tape pool. instead going through tradiitional setup of backing up to disk first and then migrating to tape pool. im using 3575 tape pool with 6 drives . i need to backup around 80gb of db2 database using 4 sessoins. when i created a management class and copy group specifying copy destination as 3575_bkup (which is tape pool) and node mount points to 4 (which uses 4 tapes to be mounted for 4 sessions opened). But it ran for few MB and terminated. i dont understand why is not happening ? can anybody help me to findout a way to backup directly to tape instead of backing up fist to disk and then migrating it to tapepool. help in this regard is highly appriciated. regards sree.,
