You are mostly correct in your understanding of our configuration.  Let see
if this helps.

We have a server called TSMCIFS3.  It has access/mount points to numerous
CIFS and now DFS storage/directories/mount points/shares, whatever you want
to call them.
The TSM software on this server is used to backup everything but the local
box since it/the local boxes has nothing on it worth backing up.  It is
purely a service machine.
Each TSM node configured on this box (>30) has its own configuration files
(dsmsched, dsm.opt, etc) which includes unique http ports for each node.
User/admins access their backups for their nodes via dsmcad/http.
Each node has a unique set of services and yes those services are
configured to use specific domain accounts to perform the backups for each
node.
The backup schedules for each of these nodes has the OBJECT value set to
determine which mount point/share/filesystem/directory is backed up.

Yes I agree I think it is an authority issue.  However, our confusion is if
the ID associated with the node can see and backup what it needs to
see/access, why can't the restore function see the same?


On Thu, Nov 17, 2016 at 10:24 AM, Robert Talda <r...@cornell.edu> wrote:

> Zoltan:
>   Okay, I’m getting mixed messages from your post.  So my answer may be of
> limited value.
>
>   “Signing in via browser” implies to me you are using the Web client - am
> I correct?
>
>   Assuming so,
> - BACKUP is looking at the local filesystems - not the information from
> the TSM Server
> - RESTORE would be looking at the information from the TSM Server.
>
>   Based on that, I suspect it may be the id you are using to sign on via
> the Web client.
>
> FWIW,
> Bob T
>
>
> Robert Talda
> EZ-Backup Systems Engineer
> Cornell University
> +1 607-255-8280
> r...@cornell.edu
>
>
> > On Nov 16, 2016, at 2:19 PM, Zoltan Forray <zfor...@vcu.edu> wrote:
> >
> > I have an interesting situation when attempting to perform a restore on a
> > node that performs backups of CIFS/DFS mounts.
> >
> > The client is accessed via http / dsmcad since this server is setup to
> > backup multiple CIFS shares and now moving to DFS.
> >
> > After signing in via browser, I can bring up BACKUP and see lots and lots
> > of file shares/directories, etc.
> >
> > But when I bring up RESTORE, I don't see any of that.  Just three
> > higher-level directories.
> >
> > Occupancy shows 4.7-million files backed up and yes I tried toggling
> > active/inactive.  Checking the dsmsched log shows it scanning 4.7 million
> > files and backed up 1300 just last night.
> >
> > Both the client and server are 7.1.6.3 so I can't go any higher.
> >
> > Recently rebooted everything.  Nothing out of the ordinary in
> > dsmwebcl.log.  Just shows sessions starting and there was a password
> issue
> > for the user who contacted me about this.  Even shows idle-timeouts.
> >
> > So what gives?  Why can't restore/see anything?  Obviously, I am a full
> > system admin so that's not be an issue.
> >
> >
> >
> >
> >
> > --
> > *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
> > zfor...@vcu.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
zfor...@vcu.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

Reply via email to