|
Re: [Networker] Tracking NetWorker license codes
2006-02-06 21:13:51
We have done this for several years now. We keep a file (:-
separated) with the client name, e-mail addresses and a University
Account Code, and some extra flags for other purposes.
We charge a fixed amount per month for each active client and for
each BSM (Exchange only at this stage). I have not worked out how to
clusters properly yet. We also charge for tape usage by volume.
We buy our client connection licences in bulk (usually 25 at a
time). We compute a monthly charge to recover the capital and
maintenance costs.
Each month I run a script that processes "mminfo" output and computes
charges based on the volumes written to each pool. Since we are
really only doing cost recovery, we charge different rates depending
on how long we retain the save sets on tape. For short retention
times users pay less, as the tape will be reused by other save sets.
This script generates a file that our accounting people can use to
bill our internal "customers".
I also use this file to send my save-group completions to the system
owners. I know that you can now do this within Legato, but I suspect
it sends multiple e-mails to users who control multiple clients. Our
system runs as a save-group completion notification, combines all the
completion messages for a user and sends one e-mail.
On 07/02/2006, at 10:32 AM, Stan Horwitz wrote:
We're at the early stages of charging other departments to do
backups of their servers to our central site NetWorker server.
Right now, the only charge is for the cost of a client connection
and any optional modules they may need. I am wondering if others
are in this situation. I assume so. How do you keep track of which
department owns which auth code? I am using 7.2.1 so I have set up
an Excel spread sheet with the details on it and I fill in the
comment field on each auth code I register for an outside
department, but this is going to get too confusing, esp. since
NetWorker doesn't know who owns which license.
At some point, we will also charge for tape resources, but that
hasn't happened yet. This idea is not mine; I think it is not cost-
effective to buy individual client connections each time we need to
add a new server onto our nightly backup schedule, but that's the
way management wants it here.
If anyone has any suggestions on how to manage this stuff so that
you don't accidentally use one department's license for another
group's server, please let me know.
Thanks,
Stan
To sign off this list, send email to listserv AT listserv.temple DOT edu
and type "signoff networker" in the
body of the email. Please write to networker-
request AT listserv.temple DOT edu if you have any problems
wit this list. You can access the archives at http://
listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
To sign off this list, send email to listserv AT listserv.temple DOT edu and type
"signoff networker" in the
body of the email. Please write to networker-request AT listserv.temple DOT edu
if you have any problems
wit this list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
|
|
