ADSM-L

Re: [ADSM-L] Backup of share will not work with schedule

2008-12-05 17:23:40
Subject: Re: [ADSM-L] Backup of share will not work with schedule
From: "Schneider, John" <John.Schneider AT MERCY DOT NET>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Fri, 5 Dec 2008 16:21:55 -0600
 Tim,   
        In the world of healthcare, it is not unusual for the
application vendor to provide the server and application and support the
whole shootin' match themselves.  Sometimes the customer can talk the
vendor into allowing modifications to "their" server, as in a TSM
client, but sometimes they won't do it.  Sometimes they won't even let
you log in to "their" server. So the vendor will configure shares or
some such method to allow you access from outside, and you have to roll
your own solution. 


Best Regards,

John D. Schneider 
Cell: 314-750-8721 


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Friday, December 05, 2008 3:55 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backup of share will not work with schedule

Usually a tsm service running with local system account
cant access remote resources. You can try having each
system use the same account and password, or change the
share to everyone read which is dangerous.

When you mean the vendor owns it does it just own the
application on it or everything including the hardware.

It is our corporate policy to use TSM on all servers, We
havent had any issues as of yet.

Tim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Schneider, John
Sent: Friday, December 05, 2008 4:48 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Backup of share will not work with schedule


Tim,
        Thanks for your email.  There is not a Windows domain involved
here; I think the two clients' security is a workgroup.  I am logged in
to the local Administrator account, and I presume the TSM Client
Acceptor is running as the local System account as usual.
        So you think the problem here has something to do with Windows
security, not with how I set up the TSM client or schedule?


Best Regards,

John D. Schneider
Phone: 314-364-3150
Cell: 314-750-8721
Email:  John.Schneider AT Mercy DOT net


-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of
Tim Brown
Sent: Friday, December 05, 2008 3:35 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Backup of share will not work with schedule

If the TSM service is using a local system account try  it with  a
domain
id

Tim

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Schneider, John
Sent: Friday, December 05, 2008 4:27 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Backup of share will not work with schedule


Greetings,
    I have a server that I can't install the TSM client on because the
vendor who owns it won't permit it.   One alternative seemed to be to
share the directory that must be backed up, and acces that share from
another server to back it up explicitely as an object.   We created a
share on that server that we can access from another server.
    I can log in to the other server, bring up the TSM line mode client,
and back it up with:

dsmc inc \\172.17.16.101\archive2\ -subdir=yes

And that backs up fine.  But when I build a schedule with the
\\172.17.16.101\archive2\ <file://172.17.16.101/archive2/>  as the
object, it fails.  The dsmsched.log is below.  Does anyone know the
scheduler won't backup a filesystem that the linemode client backs up
fine?

12/04/2008 13:00:11 --- SCHEDULEREC QUERY BEGIN
12/04/2008 13:00:11 --- SCHEDULEREC QUERY END
12/04/2008 13:00:11 Next operation scheduled:
12/04/2008 13:00:11
------------------------------------------------------------
12/04/2008 13:00:11 Schedule Name:         EXCELLERA_ARCHIVE2
12/04/2008 13:00:11 Action:                Incremental
12/04/2008 13:00:11 Objects:               \\172.17.16.101\archive2\
<file://172.17.16.101/archive2/>
12/04/2008 13:00:11 Options:               -subdir=yes
12/04/2008 13:00:11 Server Window Start:   13:00:00 on 12/04/2008
12/04/2008 13:00:11
------------------------------------------------------------
12/04/2008 13:00:11
Executing scheduled command now.
12/04/2008 13:00:11 --- SCHEDULEREC OBJECT BEGIN EXCELLERA_ARCHIVE2
12/04/2008 13:00:00
12/04/2008 13:00:11 Incremental backup of volume
'\\172.17.16.101\archive2\'
12/04/2008 13:00:13 ANS1228E Sending of object
'\\172.17.16.101\archive2\*' failed
12/04/2008 13:00:13 ANS1063E The specified path is not a valid file
system or logical volume name.
12/04/2008 13:00:13 --- SCHEDULEREC STATUS BEGIN
12/04/2008 13:00:13 --- SCHEDULEREC OBJECT END EXCELLERA_ARCHIVE2
12/04/2008 13:00:00
12/04/2008 13:00:13 ANS1512E Scheduled event 'EXCELLERA_ARCHIVE2'
failed.  Return code = 12.
12/04/2008 13:00:13 Sending results for scheduled event
'EXCELLERA_ARCHIVE2'.
12/04/2008 13:00:13 Results sent to server for scheduled event
'EXCELLERA_ARCHIVE2'.


Best Regards,

John D. Schneider

This e-mail contains information which (a) may be PROPRIETARY IN NATURE
OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for
the
use of the addressee(s) named above. If you are not the addressee, or
the
person responsible for delivering this to the addressee(s), you are
notified
that reading, copying or distributing this e-mail is prohibited. If you
have
received this e-mail in error, please contact the sender immediately.
This e-mail contains information which (a) may be PROPRIETARY IN NATURE
OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for
the
use of the addressee(s) named above. If you are not the addressee, or
the
person responsible for delivering this to the addressee(s), you are
notified
that reading, copying or distributing this e-mail is prohibited. If you
have
received this e-mail in error, please contact the sender immediately.
This e-mail contains information which (a) may be PROPRIETARY IN NATURE OR
OTHERWISE PROTECTED BY LAW FROM DISCLOSURE, and (b) is intended only for the
use of the addressee(s) named above. If you are not the addressee, or the
person responsible for delivering this to the addressee(s), you are notified
that reading, copying or distributing this e-mail is prohibited. If you have
received this e-mail in error, please contact the sender immediately.