OK, regarding "

We can't help you much if you don't supply enough information. Any
diagnosis based on what you've said so far will be nothing but WAGs."

Here is a bit more info.

TSM Server 4.2.2.12 running on Solaris 2.7
TSM Client 3.7.2.0 running on Solaris 2.6

All client options are defined on the TSM server (not in the client dsm.sys
file) �and consist of a few other exludes of files / dir's etc. Nothing at
all in releation to /mnt file system.

The /mnt/stats mount point is temporary while an administrator moves some
files (quite a lot in fact). When done, the moint point will be removed
again, but I just want to exclude it for tonights backup.

The way I check to see if files, file systems, dir's etc will be backed up
is to load up the ba client on the gui and see if said dir etc appears in
the backup list. If they do, I assume that they are not being excluded.

Here is an output of df -k on the client machine if that helps at all.

Filesystem � � � � � �kbytes � �used � avail capacity �Mounted on
/dev/dsk/c0t0d0s0 � � 248287 �184258 � 39201 � �83% � �/
/dev/dsk/c0t0d0s6 � �7597873 3082770 4439125 � �41% � �/usr
/proc � � � � � � � � � � �0 � � � 0 � � � 0 � � 0% � �/proc
fd � � � � � � � � � � � � 0 � � � 0 � � � 0 � � 0% � �/dev/fd
/dev/dsk/c0t0d0s1 � � 248287 � 26268 �197191 � �12% � �/var
/dev/dsk/c0t1d0s7 � �17413250 5850417 11388701 � �34% � �/wispers/opt
/dev/dsk/c0t0d0s5 � �1018191 �116779 �840321 � �13% � �/opt
swap � � � � � � � � 2344720 �100400 2244320 � � 5% � �/tmp
/dev/osa/dev/dsk/c3t2d0s1
� � � � � � � � � � �10326524 1730926 8492333 � �17% � �/wispers/tmp
/dev/osa/dev/dsk/c3t2d0s3
� � � � � � � � � � �5163254 �471305 4640317 � �10% � �/wispers/repository
/dev/osa/dev/dsk/c3t2d0s5
� � � � � � � � � � �51634919 6970365 44148205 � �14% � �/wispers/data
/dev/osa/dev/dsk/c3t2d0s0
� � � � � � � � � � �20653809 11074016 9373255 � �55% � �/wispers/home
/dev/osa/dev/dsk/c3t2d0s6
� � � � � � � � � � �210404916 88624696 119676171 � �43% � �/wispers/users
/dev/osa/dev/dsk/c3t2d0s4
� � � � � � � � � � �51634919 5117175 46001395 � �11% � �/wispers/content
/dev/osa/dev/dsk/c2t0d0s1
� � � � � � � � � � �94348822 �666755 92738579 � � 1% � �/mnt/stats

Many thanks for any help with this.

Farren Minns - John Wiley & Sons Ltd





Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

Sent by: � � � �"ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>

To: � � � �[EMAIL PROTECTED]
cc:
Subject: � � � �Re: Exclude filesystem on Solaris


On Tue, 2003-01-21 at 08:33, Farren Minns wrote:
> How do I just exclude a file system on a Solaris client.
>
> I was to exclude the /mnt/stats file system, so I figure exclude.fs
> /mnt/stats but when I go to the backup/archive gui, I can see that it's
> still going to get backed up. What am I doing wrong?

Let's take this a step back.

What is your TSM server level? client level? What do the relevant
portions of your client option file say? How do you know the /mnt/stats
filesystem is being backed up?

We can't help you much if you don't supply enough information. Any
diagnosis based on what you've said so far will be nothing but WAGs.

Please review the monthly TSM faq on how to post sufficient information
to describe your problem.

--
Mark Stapleton ([EMAIL PROTECTED])



Reply via email to