We have on occasion created a batch job that runs on the TSM servers that users 
can feed a few parameters to then have our operations group run it through the 
enterprise scheduler.  This allows a user to run a command of higher privilege 
but still be under control.  Also the users may have the job run at a time of 
their choosing and not bother us with details.
As long as you build in good error checking it should be relatively safe.

Hope that helps and I send my condolences.


Andy Huebner


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of 
Paul Zarnowski
Sent: Thursday, June 02, 2011 12:52 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: [ADSM-L] TSM & client machine renames

Hello all,

We are contemplating a massive Active Domain reorganization which would involve 
renaming hundreds of Windows machines that we backup into TSM.  We forsee a few 
problems with this, and I am looking to see if any other TSM sites have faced a 
similar problem and what they did to address it.

The problems:
1. Renaming a Windows system will result in TSM making a fresh backups for the 
volumes on that system (because the system name is part of the filespace name). 
 Renaming the filespace on the TSM server will address this, but timing is a 
problem.  If you rename the filespace a day early or a day late, you will still 
end up with extra backups.

2. TSM likes to replace DOMAIN C: statements with DOMAIN \\systemname\C$.  If 
the systemname changes, then the TSM backup will fail, because it won't be able 
to find the old systemname (unless and until the DOMAIN statement is updated).  
Again, with so many machines, updating all those DSM.OPT files will be 
problematic.

3. If we have a large number of unintended extra backups, TSM server resources 
(database size and stgpool capacity) will be stretched.


Having a tool that would allow our customers to rename their TSM filespaces 
on-demand would be a big help.  As we do not give out policy domain privileges, 
we cannot use dsmadmc to do this.  I am looking for other solutions that any of 
you might have developed, or even just thought about.  If the TSM BA client 
allowed a user to rename their filespace, that would be a great solution.  But 
it's not there.

Thanks for any help (or condolences).

..Paul


--
Paul Zarnowski                            Ph: 607-255-4757
Manager, Storage Services                 Fx: 607-255-8521
719 Rhodes Hall, Ithaca, NY 14853-3801    Em: psz1 AT cornell DOT edu

This e-mail (including any attachments) is confidential and may be legally 
privileged. If you are not an intended recipient or an authorized 
representative of an intended recipient, you are prohibited from using, copying 
or distributing the information in this e-mail or its attachments. If you have 
received this e-mail in error, please notify the sender immediately by return 
e-mail and delete all copies of this message and any attachments.

Thank you.