The default domain is ALL-LOCAL. If you add a drive our mountpoint the TSM
client should automaticlly include that on the next backup. On the Unix's
that's all mounted filesystems except /tmp. On Winders it's all locally
attached drives. Now on Windows if the security for the drive does not
include the account that the TSM Scheduler service is running under, then
TSM won't back it up. It won't even show up in the filespaces. That is why
after the first successful backup of a node I compare the filespaces with
the actual drives on the node. I've run into these issues before on Windows
and it is almost always an argument with the administrator of the box to get
it set right. On Unix's, if the filesystem isn't mounted, you won't get a
backup and if it's not mounted the first time you run a backup, it's not in
the filespace report either. AFter every first backup of a new node, I send
the list of filespaces to the admin of the box for comparison. If the admin
adds a drive or mountpoint later and doesn't notify us via change control,
there's not much I can do about that. I've been concidering an audit of each
node periodically just to make sure everything is included.
I also have a daily report from the TSM OPerational Reporter that lists all
filespaces that haven't had a successful backup in >2 days.
Bill Boyer
"My problem was caused by a loose screw at the keyboard" - ??
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Kovarski, Mark
Sent: Thursday, November 11, 2004 3:20 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Utility/reporting tool to list filesystems/drives not
backed up
On the note of missing filesystems/mount points. Is there a way to setup
TSM to pick everything and exclusively exclude when required? This would
somewhat eliminate the issue (but might cause more disk/tape
consumption) somewhat so that the backups will occur if someone creates
a new fs but forgets to add it to the TSM backup schedule.
Mark
-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Richard Sims
Sent: Thursday, November 11, 2004 10:20 AM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Utility/reporting tool to list filesystems/drives not
backed up
Quoting "Kovarski, Mark" <Mark.Kovarski AT BMONB DOT COM>:
> Has anyone a utility (commercial or freeware) that can produce a
> report of which filesystems (HPUX, Solaris, Windows directories or
> drive
> letters) are not backed up? Essentially it would have to do a
> directly/drive listing, compare it to what the dsm.sys or TSM has in
> its database and list the differences. This would avoid missing
> complete filesystems or drive letters (in Windows) all together.
>
> So far I was unable to find such an item but it seems like this is a
> very common problem especially when you deal with hundreds of servers
> and a lot of changes (drive, directory, filesystem adds in particular)
> that can occur.
>
> Any help is appreciated.
>
> Mark
The absence of such a utility is, I think, largely due to static file
system complements and the relatively trivial nature of the check, in
comparing 'dsmc Query Filespace' output to 'lsfs -v jfs' output in AIX,
for example. Good client monitoring does Query Filespace checks anyway,
so comparing against the file systems complement is a minor extension.
Richard Sims
<FONT SIZE =
1>**************************************************************************
**
This e-mail and any attachments may contain confidential and privileged
information. If you are not the intended recipient, please notify the sender
immediately by return e-mail, delete this e-mail and destroy any copies. Any
dissemination or use of this information by a person other than the intended
recipient is unauthorized and may be illegal. Unless otherwise stated,
opinions expressed in this e-mail are those of the author and are not
endorsed by the author's employer.</FONT>
|
