Eric, it is a problem, I guess we all know that. And the same happens, when you have only 2 mount points and Reclamation is running, or something else and the Migration cannot clean up the Diskpool by migrating to tape, because of the missing mount point. We solved the problem by 1) defining 3 mountpoints. When Reclamation, Backup Stg and so on is using 2 mount points, we have one left 2) Because our diskpool has 20 Gb Storage and our clients are used to backup about 80 Gb per night, we are running Backup Diskpool->Copypool each hour and after 1 pm, we are running Backup Primarypool->Copypool to backup the missing data (which was migrated between the hourly Diskpool Backup) Regards Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 11:42:53 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema: Re: Antwort: Preemption not working Hi Gerhard! You are right, the backup stgpool command is not on the priority list. If this means that a backup stgpool will never be canceled, I think this is a really serious problem. What if a client, or several (new) clients are generation a lot of backup data. In this case your backups stgpool processes will run a lot longer than normally. If you haven't got a very large diskpool you will probably run in a full diskpool before the backup stgpool is finished. Some backups (like TDP backups) can't handle this and will hang. Could someone from development confirm that the backup stgpool will never be preempted? Kindest regards, Eric van Loon KLM Royal Dutch Airlines -----Original Message----- From: Gerhard Wolkerstorfer [mailto:[EMAIL PROTECTED]] Sent: Wednesday, July 18, 2001 10:15 To: [EMAIL PROTECTED] Subject: Antwort: Preemption not working Eric, it really is a deep s***, and you could report it, but the answer would be: "Works as designed" When you read the Preemption section of the Admin Guide, you'll see, that only the following actions would cause TSM to cancel another process when needing mount-points => Backup database, Restore, Retrieve, HSM recall, Export and Import So, TSM would never cancel another process, because your migration process needs a Mount Point. The following list (from the manual) only describes the Priority-sequence, which process TSM would cancel, when e.g. a Restore Process needs a mount point => 1. Move data 2. Migration from disk to sequential media 3. Backup, archive, or HSM migration 4. Migration from sequential media to sequential media 5. Reclamation So TSM would first cancel Reclamation. If Reclamation doesn't exist, he would try to cancel the Migration Seq to Seq Media, and so on, and at last he would cancel a Move Data Process. If none of them is running, the Process would hang with "waiting for mount point ..... bla bla" Gerhard Wolkerstorfer [EMAIL PROTECTED] (Loon. E.J. van - SPLXM) am 18.07.2001 09:20:07 Bitte antworten an [EMAIL PROTECTED] An: [EMAIL PROTECTED] Kopie: (Blindkopie: Gerhard Wolkerstorfer/DEBIS/EDVG/AT) Thema: Preemption not working Hi *SM-ers! Today, again all my client backups were hanging. Again I encountered a 100% full diskpool, but this time it was caused by a very long running backup stgpool. Migration was running, but waiting for mountpoints. According to the Admin Guide, migration processing has a higher priority than a backup stgpool, so the backup should be canceled due to mountpoint preemption, but it didn't!!!! So again I'm in deep s***! Should I report this as a bug to Tivoli? I'm running 3.7.4.0 on AIX 4.3.3. Kindest regards, Eric van Loon KLM Royal Dutch Airlines ********************************************************************** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **********************************************************************
