Re: [ADSM-L] How to exclude bad Linux mountpoint

Thanks for the suggestions.  I forgot about the EXCLUDE.FS which seems to
have done the trick since it is a filesystem (see df below).  Now to roll
this out to all of my Linux servers.

[zforray@processor ~]$ df -m
Filesystem           1M-blocks    Used Available Use% Mounted on
/dev/mapper/vg_processr_sys-lv_root
                         20031    7123     11885  38% /
tmpfs                    48339       1     48339   1% /dev/shm
/dev/sdb2                  477     108       344  24% /boot
/dev/sdb1                  100       1       100   1% /boot/efi
/dev/mapper/vg_processr_sys-lv_home
                         50269   10818     36891  23% /home
/dev/mapper/vg_processr_sys-lv_tsmarchlog
                        302380     480    301901   1% /tsmdb2
/dev/mapper/vg_processr_sys-lv_tsmarchlog2
                        151190     348    150843   1% /tsmarchlog2
/dev/mapper/vg_processr_sys-lv_tsmdb
                        403174  364843     38331  91% /tsmdb
/dev/mapper/vg_processr_sys-lv_tsmlog
                        129016  120165      2298  99% /tsmlog
/dev/mapper/vg_processr_pool-lv_tsmpool
                      10133861 9618741       344 100% /tsmpool
/dev/mapper/vg_processr_sys-lv_var
                         14991     878     13346   7% /var
/dev/sdd                     2       0         2   0% /tmp/SECUPD
/dev/sde                     2       0         2   0% /tmp/SECUPD


On Tue, Feb 7, 2017 at 3:05 PM, Andrew Raibeck <storman AT us.ibm DOT com> 
wrote:

> Hi Zoltan,
>
> It could be the simple act of enumerating file systems or mount points that
> causes a problem. What kinds of problems, specifically, are you seeing?
>
> A couple of thoughts (not sure these will help):
>
> - Does this show up as a separate file system, such as when you do df -m?
> If yes, you could try exclude.fs /tmp/SECUPD
>
> - Another possibility is to define it as a virtual mount point using the
> VIRTUALMOUNTPOINT option, then using exclude.fs.
>
> Finally, a total "shot in the dark", but try searching the internet for
> this directory name. One discussion I found indicates that /tmp/SECUPD is
> causing other issues, too:
>
> http://en.community.dell.com/support-forums/servers/f/956/t/19996605
>
> Regards,
>
> Andy
>
> ____________________________________________________________
> ________________
>
> Andrew Raibeck | IBM Spectrum Protect Level 3 | storman AT us.ibm DOT com
>
> IBM Tivoli Storage Manager links:
> Product support:
> https://www.ibm.com/support/entry/portal/product/tivoli/
> tivoli_storage_manager
>
> Online documentation:
> http://www.ibm.com/support/knowledgecenter/SSGSG7/
> landing/welcome_ssgsg7.html
>
> Product Wiki:
> https://www.ibm.com/developerworks/community/wikis/home/wiki/Tivoli%
> 20Storage%20Manager
>
> "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 2017-02-07
> 14:45:50:
>
> > From: Zoltan Forray <zforray AT VCU DOT EDU>
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Date: 2017-02-07 14:46
> > Subject: How to exclude bad Linux mountpoint
> > Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
> >
> > Ever since a certain Dell update, a ghost mountpoint of /tmp/SECUPD is
> left
> > hanging after iDRAC/OpenManage updates.  This is now causing heartburn
> for
> > TSM backups.
> >
> > I have tried pushing down via CLOPTSET to
> >
> > exclude.dir /tmp/SECUPD
> > exclude /tmp/SECUPD
> >
> > but neither work - TSM still tries to access/back it up.
> >
> > Any suggestions on how to get TSM to stop trying to access this mount?
> >
> >
> >
> >
> >
> > --
> > *Zoltan Forray*
> > Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
> > Xymon Monitor Administrator
> > VMware Administrator (in training)
> > Virginia Commonwealth University
> > UCC/Office of Technology Services
> > www.ucc.vcu.edu
> > zforray AT vcu DOT edu - 804-828-4807
> > Don't be a phishing victim - VCU and other reputable organizations will
> > never use email to request that you reply with your password, social
> > security number or confidential personal information. For more details
> > visit http://infosecurity.vcu.edu/phishing.html
> >
>



--
*Zoltan Forray*
Spectrum Protect (p.k.a. TSM) Software & Hardware Administrator
Xymon Monitor Administrator
VMware Administrator (in training)
Virginia Commonwealth University
UCC/Office of Technology Services
www.ucc.vcu.edu
zforray AT vcu DOT edu - 804-828-4807
Don't be a phishing victim - VCU and other reputable organizations will
never use email to request that you reply with your password, social
security number or confidential personal information. For more details
visit http://infosecurity.vcu.edu/phishing.html