Hi Richard (and others)!
Thank you very much for your reply!
I forgot that the volume history file is generated by the BAckup
VOLHistory command and thought it was a file which was continuously
updated by TSM.
Thank you very much for the update!
Kindest regards,
Eric van Loon
KLM Royal Dutch
Backup volhist make a copy of VOLHISTORY table in a sequential file.
Do "Backup volhist filename=x" it make a new volume history file ..
On Fri, Jul 4, 2008 at 9:29 AM, Loon, E.J. van - SPLXM <
[EMAIL PROTECTED]> wrote:
> Hi!
> I don't understand your reply.
>
On Jul 4, 2008, at 8:29 AM, Loon, E.J. van - SPLXM wrote:
Hi!
I don't understand your reply.
A BAckup VOLHistory just makes a backup of the currently incomplete
volume history file. How would that help me?
Hi, Eric -
The file is a copy of the information in the TSM database, generated
b
- SPLXM
Sent: den 4 juli 2008 14:29
To: ADSM-L@VM.MARIST.EDU
Subject: Re: [ADSM-L] Rebuilding a volume history file
Hi!
I don't understand your reply.
A BAckup VOLHistory just makes a backup of the currently incomplete volume
history file. How would that help me?
Kindest regards,
Eric van Loo
Hi!
I don't understand your reply.
A BAckup VOLHistory just makes a backup of the currently incomplete
volume history file. How would that help me?
Kindest regards,
Eric van Loon
KLM Royal Dutch Airlines
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On B
BAckup VOLHistory
On Fri, Jul 4, 2008 at 8:02 AM, Loon, E.J. van - SPLXM <
[EMAIL PROTECTED]> wrote:
> Hi *SM-ers!
> The filesystem which contains my volume history file was filled to 100%
> last night, so TSM reported I/O errors while writing to it. I have had
> the filesystem
Hi *SM-ers!
The filesystem which contains my volume history file was filled to 100%
last night, so TSM reported I/O errors while writing to it. I have had
the filesystem enlarged, but now I have a volume history file which is
missing data.
Is there a way to rebuild a volume history file?
Thank you
Two possibilities Thomas.
Is /tmp symlinked to /var/tmp? The problem may not be where you think
it is.
I have known for AIX filesystems to fill up but there be no file or
files big enough to cause the problem. In Unix, if a file that is open
is deleted, the directory entry pointing to the file
513E A database lock conflict was
encountered in
processing sequential volume history
information.
05-03-2007 14:03:02 ANRD icvolhst.c(4060): ThreadId<37> Lock
Conflict
encountered in updating volume his
Some time ago (years), that error message would appear when a deadlock
of some kind prevented the volume history table from being accessed
during the write attempt.
One GB scratch volumes? At what rate do you create/delete these during
the night? A high rate would increase the chance of a
x109
Cell: 952-221-6938
Fax: 763-417-0554
[EMAIL PROTECTED]
http://www.us.logicalis.com
Thomas Denier <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager"
03/20/2007 03:26 PM
Please respond to
"ADSM: Dist Stor Manager"
To
ADSM-L@VM.MARIST.EDU
cc
Subject
R
-Tom Kauffman wrote: -
>What filesystem type? (reiser, ext3, etc.) Could you be running out
>of inodes at times?
It is an ext3 file system. We are using about 20,000 out of 300,960
inodes. I can't think of anything running on the system that would
create several hundred thousand files in
-Bill Kelly wrote: -
>Is it not possible that the /var filesystem *sometimes* has too
>little space available? After all, didn't you say that this only
>fails roughly every one to two weeks? Perhaps the failures coincide
>with some other activity (possibly unrelated to TSM) that
>temporari
: Error writing volume history file
We are seeing the following pair of messages occasionally:
ANRD icvolhst.c(5267): ThreadId <47> Error Writing to output File.
ANR4510E Server could not write sequential volume history information
to /var/tsm_automation/volumehistory.
Successive occuran
-Richard Sims wrote: -
>One possible, but less likely cause could be a volume history set of
>such size that it exceeds the "filesize" Unix Resource Limit under
>which the TSM server was started: if yours is a large set, try
>pruning and see if the problem goes a
On Mar 20, 2007, at 1:56 PM, Thomas Denier wrote:
We are seeing the following pair of messages occasionally:
ANRD icvolhst.c(5267): ThreadId <47> Error Writing to output File.
ANR4510E Server could not write sequential volume history information
to /var/tsm_automation/volumehistory
esystem?
The file system has about 240 megabytes of free space. Our volume
history file is a little under one megabyte.
>Does the service running dsmserv have sufficient privilege to write
>to the directory?
The server code runs as root, which can write to any file in any
directory, regardl
-Mark Stapleton wrote: -
>Does the directory exist?
Yes.
>Is there room in the /var filesystem?
The file system has about 240 megabytes of free space. Our volume
history file is a little under one megabyte.
>Does the service running dsmserv have sufficient privilege to writ
From: ADSM: Dist Stor Manager on behalf of Thomas Denier
We are seeing the following pair of messages occasionally:
ANRD icvolhst.c(5267): ThreadId <47> Error Writing to output File.
ANR4510E Server could not write sequential volume history information
to /var/tsm_automation/volumeh
We are seeing the following pair of messages occasionally:
ANRD icvolhst.c(5267): ThreadId <47> Error Writing to output File.
ANR4510E Server could not write sequential volume history information
to /var/tsm_automation/volumehistory.
Successive occurances of this pair of messag
Depends.
If all you are managing is your DB backups, you are correct.
However, remember that if somebody creates EXPORT or BACKUPSET tapes,
they are also tracked in volume history. If you delete those records,
TSM loses track of them and they could get overwritten.
Wanda Prather
"I/O
|
Sir:
Depends on what you want to have available. I let my volume history
grow. This is because I occasionally need
Sir:
Depends on what you want to have available. I let my volume history
grow. This is because I occasionally need to know the history of a
particular tape cartridge.
After it goes back to scratch, tsm loses its error information. I can
use the volhist to see how many times it has cycled
Good morning people
This is such an old question but I have just been thinking about something
and want to make sure that my understanding is correct.
When I want to delete volume history information, am I right in assuming
that I can delete anything older than my oldest database backup.
For
[EMAIL PROTECTED] On Behalf Of
Ken Chamberlain
Sent: Wednesday, March 07, 2007 11:39 AM
To: ADSM-L@VM.MARIST.EDU
Subject: volume history file
I've been running TSM for over a decade now. During this time the only
deletions from volhist happen by way of a daily schedule:
"del volhist tod
Create a Server
Command
Script and define an Administrative command schedule to run it.
HTH
Thomas Rupp
-Ursprüngliche Nachricht-
Von: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] Im Auftrag von Ken
Chamberlain
Gesendet: Mittwoch, 07. März 2007 17:39
An: ADSM-L@VM.MARIST.EDU
Betreff:
3/7/2007 10:38 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] volume history file
I've been running TSM for over a decade now. During this time the only
deletions from volhist happen by way of a daily schedule:
"del volhist todate=today-9 type=dbb"
My volhist file is getting HUGE.
I've been running TSM for over a decade now. During this time the only
deletions from volhist happen by way of a daily schedule:
"del volhist todate=today-9 type=dbb"
My volhist file is getting HUGE. There must be more I can delete. What do
other shops do?
How do you find the oldest inuse volum
>> On Thu, 30 Mar 2006 14:56:31 -0500, Joni Moyer <[EMAIL PROTECTED]> said:
> I am trying to figure out how long to keep my volume history for
> I had been keeping it for 30 days, but is there any reason to keep
> it longer than that? Thanks!
"How long do I keep v
he message. Thank you."
*
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Joni Moyer
Sent: Friday, March 31, 2006 1:27 AM
To: ADSM-L@VM.MARIST.EDU
Subject: [ADSM-L] Retention of the Volume History
Hello everyone,
I am trying to figu
Hello everyone,
I am trying to figure out how long to keep my volume history for I had
been keeping it for 30 days, but is there any reason to keep it longer than
that? Thanks!
This is the job I had been running: delete volhist tod=today-31 type=all
Joni
don't see any reason to keep this
info for any longer.
Regards,
Karel
-Original Message-
From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED] On Behalf Of
Richard Sims
Sent: woensdag 30 november 2005 15:29
To: ADSM-L@VM.MARIST.EDU
Subject: Re: Volume history question
If yo
If you are referring to the file system file which TSM maintains with
volume history information, it is a waste of time to make any changes
to the file, as it is a generated copy of the volume history info
maintained in the TSM database.
You may housekeep the volume history information, by age
Just looked at the volume history file again.
Redoing the disaster recovery plans for tsm.
Is there any reason to keep the "STGNEW" entries that build up in this file?
Been removing the "STGDEL" entries during daily processing.
Didn't see anything in the manuals abo
Hello,
I was wondering when most sites do a delete volume history to clean out
your volume history file? I only keep backupsets for 30 days and I can't
think of anything else that I may need to keep this info. for more than 35
days. I just thought I would get a consensus of a general id
EMAIL PROTECTED] Im Auftrag von Joni Moyer
Gesendet: Dienstag, 04. Jänner 2005 14:53
An: ADSM-L@VM.MARIST.EDU
Betreff: Volume History
Hello All!
I am setting up a new TSM environment and I am using DRM for the first
time. I have a couple of questions concerning volume history maintenance:
1.
Hello All!
I am setting up a new TSM environment and I am using DRM for the first
time. I have a couple of questions concerning volume history maintenance:
1. I had been doing delete volh type=dbb todate=today-15, but I have
realized that if you set drmdbbackupexpiredays to 14 this should be
With VOLUMEHistory in your server options file, there is no need to
execute
that command - the history backup file is updated automatically.
(See notes in http://people.bu.edu/rbs/ADSM.QuickFacts)
Richard Sims.
On Sep 22, 2004, at 11:13 AM, Luc Beaudoin wrote:
Hi all
Little question about the co
Hi all
Little question about the command BACKUP VOLHIST
- Is there a best practice saying how often shoul I run it
- My file VOLHIST.OUT is updating every day but I dont figure why ... or
witch other command or task is running it ..
thanks
Luc
Command:
I tried to label libvol but would not let me because It has a entry of this
tapes barcode (label) in the volume history.
I can't use the delete volhist command for this because its not a db backup
tape or export/import volume.
Can't use delete volume because its not a volume in a
We are running v4.2.2.12, on OS/390 v2.10.
We had this problem with an earlier version of TSM, but it seems, that it
is back!
I have several (hundred) backupset tapes, that have been deleted from the
database, but not from the volume history.
IBM has a PTF for v4.2.1 (UQ65585), but I am on
them.
-Original Message-
From: Leijnse, Finn F SITI-ITDSES31 [mailto:[EMAIL PROTECTED]]
Sent: Friday, February 01, 2002 9:14 AM
To: [EMAIL PROTECTED]
Subject: volume history file
Hi,
We have just taken control of a TSM server on AIX rs/6000 with TSM V3.7 and
4x drives in a LIB_3575. The first thing
Hi,
We have just taken control of a TSM server on AIX rs/6000 with TSM V3.7 and
4x drives in a LIB_3575. The first thing that struck us was that the library
had run out of tape slots to put more scratch tapes.
We found out that there was never a delete set-up for the volume history
file and by
43 matches
Mail list logo
