I concur. You can't ignore the "server out of storage space" message,
because that seems to have prevented the backup from completing. The stats
won't get updated unless the file system is successfully processed by TSM.
The ending stats show 230 objects inspected, but nothing backed up.
Coupled with the "server out of storage space" message, it seems to me
that the file systems were not successfully processed, and that is why the
stats don't get updated.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
Mahesh Prasad <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
04/10/2002 02:17
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Date question
Richard,
Output of your dsmsched.log says your scheduled event 'B18' was failed. I
believe this is the reason the date of last backup in filespace is not
updated.
09-04-02 21:00:59 ANS1329S Server out of data storage space
09-04-02 21:00:59 --- SCHEDULEREC OBJECT END B18 09-04-02 18:00:00
09-04-02 21:00:59 ANS1512E Scheduled event 'B18' failed. Return code =
4
Mahesh Prasad
DCM Data Systems Limited
New Delhi, India
"Denzel, Richard van"
<Richard.vanDenzel@GETR To:
[EMAIL PROTECTED]
ONICS.COM> cc:
Sent by: "ADSM: Dist Subject: Re: Date
question
Stor Manager"
<[EMAIL PROTECTED]>
04/10/2002 02:26 PM
Please respond to
"ADSM: Dist Stor
Manager"
No, because there was a unicode problem with the client, and we had to
delete the data from TSM.
Here are the other items you requested (see attachments):
Server: AIX 5.1 ML1
TSM 4.2.1.13
Client: AIX 5.1 ML1
TSM 4.2.1.25
You can ignore the out of serverspace messages, because we have a problem
with our tape drive, which can't mount any tapes anymore (PMR 91056).
Richard.
-----Original Message-----
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 5:06 PM
To: [EMAIL PROTECTED]
Subject: Re: Date question
Can't you provide the info from last night's backup?
The only reason that I can think of (off-hand) that would explain what you
are seeing is if your schedule definition has an OBJECTS setting for
specific files and/or directories. In such a case, the backup is not
considered to be for the entire volume, so the timestamp would not get
updated.
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Denzel, Richard van" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
04/09/2002 07:34
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Date question
Andrew,
My schedule is running again at 18:00 (GMT+1), I will let you know
tomorrow.
Richard.
-----Original Message-----
From: Andrew Raibeck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 4:10 PM
To: [EMAIL PROTECTED]
Subject: Re: Date question
It would help to have additional detail about your problem, including (but
not necessarily limited to):
- Operating system name and version of the client
- TSM client and server version
- Complete definition of schedule (Q SCH domain schedname F=D)
- Output from Q FI nodename F=D
- Parts of dsmsched.log that show the scheduled backup starting and ending
- Any messages in dsmerror.log that coincide with the time the backup ran
Regards,
Andy
Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: [EMAIL PROTECTED]
The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.
"Denzel, Richard van" <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
04/09/2002 07:00
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject: Re: Date question
No, the schedules are started at the correct date/time. After the schedule
completes the date on the clients filespaces doesn't get updated to the
date the last schedule ran.
Richard.
-----Original Message-----
From: Elenara Geraldo [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, April 09, 2002 3:42 PM
To: [EMAIL PROTECTED]
Subject: Re: Date question
Hi,
Verify the status/scheduler it's finished with sucess.
With the command below:
q even * *
Maybe, appear an error.
---
Regards,
Elenara Geraldo
Analyst Support
MML Systems
Phone: 55 41-342-7864
E-mail: [EMAIL PROTECTED]
On Tue, 9 Apr 2002 15:28:37
Denzel, Richard van wrote:
>Hi All,
>
>I have a question about the backup dates. I've seen the following
behaviour which I can't explain:
>
>When I make a manual backup of a client, the dat on the filespace gets
set. When the next day a backup is made through a schedule, the filespace
date doesn't get updated.
>Has anyone seen this?
>Is it normal behaviour? If so, what's the reason?
>
>Richard.
>
>-------------------------------------------------
>Richard van Denzel
>High Availability & Storage Solutions
>Senior Technical Consultant
>
>Infrastructure Consulting & Integration
>[EMAIL PROTECTED]
>
>Getronics Infrastructure Solutions
>Wiltonstraat 42
>Postbus 1005
>3900 BA Veenendaal
>tel.: 0318 - 567 100
>fax: 0318 - 567 633
>
>mobiel: 06 - 212 78 569
>
> Building Futures on <<http://www.getronics.com/>>
>
See Dave Matthews Band live or win a signed guitar
http://r.lycos.com/r/bmgfly_mail_dmb/http://win.ipromotions.com/lycos_020201
/splash.asp
(See attached file: dsmsched.log)
(See attached file: node.out)
(See attached file: sched.out)
#### dsmsched.log has been removed from this note on April 10 2002 by
Andrew Raibeck
#### node.out has been removed from this note on April 10 2002 by Andrew
Raibeck
#### sched.out has been removed from this note on April 10 2002 by Andrew
Raibeck
