Greetings, We are running ADSM 3.1.2.20 on a Solaris 2.6 system, with a BreeceHill Q47 DLT library. Previously we had NT and Novell clients backing up data directly to DLT tape drives, but that was n
Author: "Bernd Finger - Sun SAP Walldorf SAP Eng. Technical Solution Center" <Bernd.Finger AT GERMANY.SUN DOT COM>
Date: Mon, 23 Aug 1999 16:59:57 +0200
. . . . . . Always set hi high enough to ensure all nodes can complete their backup to disk. I always had problems when the migration started during backup (this was under AIX, but I'm sure the beha
Author: Adam Slesinger <aslesinger AT US.BNSMC DOT COM>
Date: Mon, 23 Aug 1999 11:12:19 -0400
John, Do you have the option to Cache Migrated Files set to "yes" for the disk pool? If so, the disk pool will continue to look as though it is full even after the data has been migrated to your tape
Author: "Viswanathan, Ramesh (CNA)" <ramesh AT SCR.SIEMENS DOT COM>
Date: Mon, 23 Aug 1999 11:56:24 -0400
Hi, Some of the stuff that I had learnt during ISS: 1. It is a bad idea to have migration take place while backups are running. This will really slow down everything. 2. Spooling to disk is single th
Also, migration will often get ahead of client data arriving so the migration process will start and stop a bunch when doing it this way. Not unusual at all. As Adam pointed out, there are two number
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:40:32 -0500
John, Do you have the option to Cache Migrated Files set to "yes" for the disk pool? If so, the disk pool will continue to look as though it is full even after the data has been migrated to your tape
To John Schneider et al, Back on 6/23/99 I wrote the following: "Our storage migration thresholds for our diskpool are set to 25 and 10 with numpr=3. We do not use colocation. When migration (disk to
I'm reposting the following message as I never saw it appear in the digest version of ADSM-L when originally submitted on 8/24/99: To John Schneider et al, Back on 6/23/99 I wrote the following: "Our
Bob - I went to the APARs database and searched on MIGPRocess, which turned up IX77884 talking of a single tape mount handling one node's migration data, and a design change necessary to do better.
Author: Roger Hohmann <Roger_Hohmann AT WESTLB DOT DE>
Date: Thu, 26 Aug 1999 15:53:30 +0200
As far as I know, migration is processed as follows: ADSM migrates by nodes. At first, the node with the largest amount of storage in the disk pool, then second, etc etc. Each node one process. If th
How big is diskpool? Is it the default pool? If so, it's only 4 MB. That would explain what you are seeing... Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949
Author: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Date: Sun, 04 Oct 2015 17:40:33 -0500
As far as I know, migration is processed as follows: ADSM migrates by nodes. At first, the node with the largest amount of storage in the disk pool, then second, etc etc. Each node one process. If th
Author: Joel Fuhrman <joelf AT CAC.WASHINGTON DOT EDU>
Date: Thu, 26 Aug 1999 17:03:12 -0700
Since 3.1.2.20 has a bug which prevents it from expiring some file, you should move up to 3.1.2.40. Maybe as a side benefit, your problem will go away. One other thought, when you installed 3.1.2.20,