Thanks, Joerg, for reminding me that the accounting records contain this info! I was hoping that there was, in addition, something that I could spot check (using 'q act', for example) a bit more easily (accounting is currently turned off - too much data).
-----Original Message----- From: ADSM: Dist Stor Manager [mailto:[email protected]] On Behalf Of Joerg Pohlmann Sent: Thursday, September 24, 2009 11:17 AM To: [email protected] Subject: Re: [ADSM-L] GPFS, HSM and backups Gretchen, I don't know about the first part, but as to information about recall activity, use the accounting records (set accounting on) - fields 26-29 relate to migration and recall activity. Joerg Pohlmann 250-245-9863 ----- Original Message ----- From: "Gretchen L. Thiele" <[email protected]> Date: Thursday, September 24, 2009 7:56 am Subject: [ADSM-L] GPFS, HSM and backups To: [email protected] > We've been using GPFS-directed HSM for a while now, working quite well > (with a few bugs, but they're being worked on). > > The 'problem' I'm seeing is the mounting of HSM media (tapes, in > particular) during the running of an incremental backup. Since we have > the requirement that nothing can be migrated without a backup in > place, this just doesn't make sense to me. > > It's also frustrating that I don't see any type of info on the server > after a recall as to the size of the file being recalled, etc. - much > like you would see after a backup, restore, archive or retrieve > (separate from the issue above). > > Server and client (BA and HSM) all at 5.5.1.1 (upgrade to 5.5.3.x when > I can get downtime in a month or so) on SLES 10. > > Any ideas? > > Gretchen Thiele > Princeton University >
