I've never done this, so you'll have to test it for yourself to see how practical these suggestions are:
1) If the machine is a UNIX variant, and you specify VIRTUALMOUNTPOINT for each of the users' directories, doesn't TSM store it as though it is a separate filespace? Then does Q OCC filespacename give you what you want? 2) If that doesn't work, consider just giving each user a script that invokes archiving using an options file with his own NODENAME. Allow OS backups to run under the host NODENAME as usual, but force archives to be stored under separate NODENAMEs. Then for sure you can get the amount of GB that person has backed up. Wanda Prather "I/O, I/O, It's all about I/O" -(me) -----Original Message----- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of Jim Zajkowski Sent: Tuesday, August 01, 2006 11:17 AM To: [email protected] Subject: Determining archive sizes for recharge? Hi folks, Right now we only backup servers to TSM. We are considering allowing individuals to use TSM as an archive repository, and the first question that came up was how to figure out how much space a particular client or person is using in the archive, so we can send them a bill. The caveat: one of the machines that people will archive from is used by more than one billable group (specifically, more than one research lab). I will need to be able to figure out which person has archived however much they did. While the idea of having more than one management class with different tape pools seems like a sound idea, I cannot necessarily rely on the users choosing the right class. Each user's directory has their name on it, so we can probably figure it out from a q arch on the client. Has anyone done this? I know how much we all love recharging, but that is out of my control. Thanks! --Jim
