Re: volhist file
"ba volh" just creates another copy in a file you choose. The volhistory
file is created on any sequential volume operation (and is not affected by
diskpool/random access volume operations).
Zlatko Krastev
IT Consultant
Mark Stapleton <[EMAIL PROTECTED]>
Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]>
27.11.2002 15:59
Please respond to "ADSM: Dist Stor Manager"
To: [EMAIL PROTECTED]
cc:
Subject:Re: volhist file
On Wed, 2002-11-27 at 07:43, Hussein Abdirahman wrote:
> Perhaps a tough question to a newbie, but I would like
> to know "when does the volume history file get created/updated"
As often as you back it up with
backup volhist
--
--
Mark Stapleton ([EMAIL PROTECTED])
Certified TSM consultant
Certified AIX system engineer
MCSE
Re: volhist file
File is created if does not exist or overwritten whenever sequential volume operation is done - define a scratch to pool, empty volume returning to scratch and deleted from pool, creation of objects tracked through volhistory (DB backups, DB snapshots, backupsets,etc.), deletion of objects in the volhistory. volhist is just a plain-text export of internal TSM DB volume history table. Zlatko Krastev IT Consultant Hussein Abdirahman <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> 27.11.2002 15:43 Please respond to "ADSM: Dist Stor Manager" To: [EMAIL PROTECTED] cc: Subject:volhist file Hi TSMers; Perhaps a tough question to a newbie, but I would like to know "when does the volume history file get created/updated" thanks in advance Hussein M. Abdirahman AIX administrator IrwinToy Canada
Re: volhist file
the internal copy in the data base gets updated/created on the fly (as a volume's status changes) BUT to cut the external file use the "backup volhist" command from either an admin session or an admin schedule. The "backup volhist" command will write the internal table to the file specified in the dsmserv.opt (or to a file or files specified via the optional parameter of the backup volhist command) How often/when it gets written to the external file automatically, I don't know off the top of my head. Dwight E. Cook Software Application Engineer III Science Applications International Corporation 509 S. Boston Ave. Suite 220 Tulsa, Oklahoma 74103-4606 Office (918) 732-7109 -Original Message- From: Hussein Abdirahman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 7:43 AM To: [EMAIL PROTECTED] Subject: volhist file Hi TSMers; Perhaps a tough question to a newbie, but I would like to know "when does the volume history file get created/updated" thanks in advance Hussein M. Abdirahman AIX administrator IrwinToy Canada
Re: volhist file
On Wed, 2002-11-27 at 07:43, Hussein Abdirahman wrote: > Perhaps a tough question to a newbie, but I would like > to know "when does the volume history file get created/updated" As often as you back it up with backup volhist -- -- Mark Stapleton ([EMAIL PROTECTED]) Certified TSM consultant Certified AIX system engineer MCSE
Re: volhist file
This file is updated dynamically by the Server. Anytime a volume is added for database or storage pool usage or deleted from storage pool usage, an entry is placed in the VOLHIST file. Hence, the name of the file. Old information is removed by the DELETE VOLHIST command. Try HELP DELETE VOLHIST from an ADMIN Command prompt or refer to the Reference Manual for this command. Happy Holiday! John G. Talafous IS Technical Principal The Timken CompanyGlobal Software Support P.O. Box 6927 Data Management 1835 Dueber Ave. S.W. Phone: (330)-471-3390 Canton, Ohio USA 44706-0927 Fax : (330)-471-4034 [EMAIL PROTECTED] http://www.timken.com -Original Message- From: Hussein Abdirahman [mailto:[EMAIL PROTECTED]] Sent: Wednesday, November 27, 2002 8:43 AM To: [EMAIL PROTECTED] Subject: volhist file Hi TSMers; Perhaps a tough question to a newbie, but I would like to know "when does the volume history file get created/updated" thanks in advance Hussein M. Abdirahman AIX administrator IrwinToy Canada ** This message and any attachments are intended for the individual or entity named above. If you are not the intended recipient, please do not forward, copy, print, use or disclose this communication to others; also please notify the sender by replying to this message, and then delete it from your system. The Timken Company **
volhist file
Hi TSMers; Perhaps a tough question to a newbie, but I would like to know "when does the volume history file get created/updated" thanks in advance Hussein M. Abdirahman AIX administrator IrwinToy Canada
Re: Volhist file
Del volh type=dbb todate=xxx bob On Thu, Oct 17, 2002 at 03:01:41PM -0400, Peppers, Holly wrote: > Hello All!!! > > I have a issue/question that I'm hoping someone out there knows the answer > to... > We just discoverd that our volhistory file is maintaining copies of > full/incr db backups since February 2002. As most of you may have guessed, > we don't want it to do this...:-) > Isn't there a parm that can be set somewhere to tell TSM how many versions > of this to keep? Where is it? How does one do this?? > > Please respond. Thanks a bunch. > > Holly L. Peppers > BCBSFL > Technical Services > > > > > Blue Cross Blue Shield of Florida, Inc., and its subsidiary and > affiliate companies are not responsible for errors or omissions in this e-mail >message. Any personal comments made in this e-mail do not reflect the views of Blue >Cross Blue Shield of Florida, Inc.
Re: Volhist file
The delete volume history command (del volh) allows you to specify the number of days to keep. If you have Disaster Recovery (DRM), that also has settings to control volume history. You can run the del volh command daily from an administrative script. Douglas C. Nelson Distributed Computing Consultant Alltel Information Services Chittenden Data Center 2 Burlington Square Burlington, Vt. 05401 802-660-2336 -Original Message- From: Peppers, Holly [mailto:Holly.Peppers@;BCBSFL.COM] Sent: Thursday, October 17, 2002 3:02 PM To: [EMAIL PROTECTED] Subject: Volhist file Hello All!!! I have a issue/question that I'm hoping someone out there knows the answer to... We just discoverd that our volhistory file is maintaining copies of full/incr db backups since February 2002. As most of you may have guessed, we don't want it to do this...:-) Isn't there a parm that can be set somewhere to tell TSM how many versions of this to keep? Where is it? How does one do this?? Please respond. Thanks a bunch. Holly L. Peppers BCBSFL Technical Services Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.
Volhist file
Hello All!!! I have a issue/question that I'm hoping someone out there knows the answer to... We just discoverd that our volhistory file is maintaining copies of full/incr db backups since February 2002. As most of you may have guessed, we don't want it to do this...:-) Isn't there a parm that can be set somewhere to tell TSM how many versions of this to keep? Where is it? How does one do this?? Please respond. Thanks a bunch. Holly L. Peppers BCBSFL Technical Services Blue Cross Blue Shield of Florida, Inc., and its subsidiary and affiliate companies are not responsible for errors or omissions in this e-mail message. Any personal comments made in this e-mail do not reflect the views of Blue Cross Blue Shield of Florida, Inc.
Re: volhist file extremely large
>Would this also be applicable if all data was going directly to tape? and >data is being archived for >3 and 8 years? Bill, I think what the consensus is here, is the tapes that are legitimate data tapes will not be deleted from the volhist file. Only DB backups, exports and volumes that have been rewritten to are going to be removed. Obviously then, the rewrite is when the volume is marked as STGNEW the most recent time in the file. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/
Re: volhist file extremely large
Sure you have data on those volumes, but you would never use the volhist file to do anything with them. The current wisdom suggests keeping these entries for as long as you keep your db backups. I'm with you, that seemed extreme so I use 30 days. Wanda Prather also had input on this and suggests that 30 days is good as well. ( I love quoting her. And I'm probably wrong about her numbers but who will check?) Delete away. That large file is a pain the arse. Especially when you have DRM. Kelly J. Lipp Storage Solutions Specialists, Inc. PO Box 51313 Colorado Springs CO 80949-1313 (719) 531-5926 Fax: (240) 539-7175 Email: [EMAIL PROTECTED] or [EMAIL PROTECTED] www.storsol.com www.storserver.com -Original Message- From: ADSM: Dist Stor Manager [mailto:[EMAIL PROTECTED]]On Behalf Of Matthew A. Bacchi Sent: Wednesday, October 03, 2001 7:39 AM To: [EMAIL PROTECTED] Subject: volhist file extremely large Folks, I have seen some posts concerning this in the past, but I don't have a good feeling about my options. I have a volumeshistory file that is around 5 megs, and entries that go back to 1997. What I want to know is, how do I know for sure that I can delete a particular entry? Kelly mentioned that he does a "delete volhist type=all todate=today-30" but that seems a little extreme to me. I believe that I have volumes that have data on them for much longer than 30 days. I am pretty sure they haven't had data on them for 4 years, but I'll bet it is closer to 6 months. What do you guys do to verify that the volumehistory entry can be deleted? I suppose I can write a script, but wanted some input first. Thanks in advance. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/
Re: volhist file extremely large
Would this also be applicable if all data was going directly to tape? and data is being archived for 3 and 8 years? -Original Message- From: Maurice van 't Loo [mailto:[EMAIL PROTECTED]] Sent: Wednesday, October 03, 2001 11:03 AM To: [EMAIL PROTECTED] Subject: Re: volhist file extremely large Matthew, We use a "delete volhist type=all todate=today-14", the tapes that contains data will not be deleted from the volhist. The onlyest concern is the database backups and exports. As i know, if you keep the database backups only for 2 days and no exports, you can even use 3 days for the volhist. Greetings, Maurice van 't Loo Compare Computers The Netherlands - Original Message - From: "Matthew A. Bacchi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 03, 2001 3:39 PM Subject: volhist file extremely large Folks, I have seen some posts concerning this in the past, but I don't have a good feeling about my options. I have a volumeshistory file that is around 5 megs, and entries that go back to 1997. What I want to know is, how do I know for sure that I can delete a particular entry? Kelly mentioned that he does a "delete volhist type=all todate=today-30" but that seems a little extreme to me. I believe that I have volumes that have data on them for much longer than 30 days. I am pretty sure they haven't had data on them for 4 years, but I'll bet it is closer to 6 months. What do you guys do to verify that the volumehistory entry can be deleted? I suppose I can write a script, but wanted some input first. Thanks in advance. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/
Re: volhist file extremely large
Matt, In mine opinion an delete volhistory todate=today-7 type=all is good. The file vlolumehistory only give information when an tape changed from scratch to private or dbbackup and what the location is off the dbbackup tapes. You don't need the file in an total disaster. Then you need the file created whit the command prepare. -Original Message- From: Matthew A. Bacchi [mailto:[EMAIL PROTECTED]] Sent: woensdag 3 oktober 2001 15:39 To: [EMAIL PROTECTED] Subject: volhist file extremely large Folks, I have seen some posts concerning this in the past, but I don't have a good feeling about my options. I have a volumeshistory file that is around 5 megs, and entries that go back to 1997. What I want to know is, how do I know for sure that I can delete a particular entry? Kelly mentioned that he does a "delete volhist type=all todate=today-30" but that seems a little extreme to me. I believe that I have volumes that have data on them for much longer than 30 days. I am pretty sure they haven't had data on them for 4 years, but I'll bet it is closer to 6 months. What do you guys do to verify that the volumehistory entry can be deleted? I suppose I can write a script, but wanted some input first. Thanks in advance. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/ ***DISCLAIMER*** Deze e-mail is uitsluitend bestemd voor de geadresseerde(n). Verstrekking aan en gebruik door anderen is niet toegestaan. Fortis sluit iedere aansprakelijkheid uit die voortvloeit uit electronische verzending. This e-mail is intended exclusively for the addressee(s), and may not be passed on to, or made available for use by any person other than the addressee(s). Fortis rules out any and every liability resulting from any electronic transmission.
Re: volhist file extremely large
Matthew, We use a "delete volhist type=all todate=today-14", the tapes that contains data will not be deleted from the volhist. The onlyest concern is the database backups and exports. As i know, if you keep the database backups only for 2 days and no exports, you can even use 3 days for the volhist. Greetings, Maurice van 't Loo Compare Computers The Netherlands - Original Message - From: "Matthew A. Bacchi" <[EMAIL PROTECTED]> To: <[EMAIL PROTECTED]> Sent: Wednesday, October 03, 2001 3:39 PM Subject: volhist file extremely large Folks, I have seen some posts concerning this in the past, but I don't have a good feeling about my options. I have a volumeshistory file that is around 5 megs, and entries that go back to 1997. What I want to know is, how do I know for sure that I can delete a particular entry? Kelly mentioned that he does a "delete volhist type=all todate=today-30" but that seems a little extreme to me. I believe that I have volumes that have data on them for much longer than 30 days. I am pretty sure they haven't had data on them for 4 years, but I'll bet it is closer to 6 months. What do you guys do to verify that the volumehistory entry can be deleted? I suppose I can write a script, but wanted some input first. Thanks in advance. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/
volhist file extremely large
Folks, I have seen some posts concerning this in the past, but I don't have a good feeling about my options. I have a volumeshistory file that is around 5 megs, and entries that go back to 1997. What I want to know is, how do I know for sure that I can delete a particular entry? Kelly mentioned that he does a "delete volhist type=all todate=today-30" but that seems a little extreme to me. I believe that I have volumes that have data on them for much longer than 30 days. I am pretty sure they haven't had data on them for 4 years, but I'll bet it is closer to 6 months. What do you guys do to verify that the volumehistory entry can be deleted? I suppose I can write a script, but wanted some input first. Thanks in advance. -Matt /** **Matt Bacchi [EMAIL PROTECTED] **IBM Global ServicesSDC Northeast **F6TG; MD Filesystems/Internet (802) 769-4072 **ADSM & AFS/DFS Backup (tie) 446-4072 **/
Re: volhist file
Hi Ray! Checkout the DELETE VOLHIST command. Kindest regards, Eric van Loon -Original Message- From: Ray Baughman [mailto:[EMAIL PROTECTED]] Sent: Monday, January 15, 2001 14:21 To: [EMAIL PROTECTED] Subject: volhist file Hello all, I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file I noticed it is rather large. After further inspection I see that all the volume history is stored in this file back to the day when we first turned ADSM. Most of this data is useless. Is there a setting or a way to clear this file? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED] ** This e-mail and any attachment may contain confidential and privileged material intended for the addressee only. If you are not the addressee, you are notified that no part of the e-mail or any attachment may be disclosed, copied or distributed, and that any other action related to this e-mail or attachment is strictly prohibited, and may be unlawful. If you have received this e-mail by error, please notify the sender immediately by return e-mail, and delete this message. Koninklijke Luchtvaart Maatschappij NV (KLM), its subsidiaries and/or its employees shall not be liable for the incorrect or incomplete transmission of this e-mail or any attachments, nor responsible for any delay in receipt. **
Re: volhist file
Ray Use 'del volhist' command I hope that this helps > -Original Message- > From: Ray Baughman [SMTP:[EMAIL PROTECTED]] > Sent: Monday, January 15, 2001 1:21 PM > To: [EMAIL PROTECTED] > Subject: volhist file > > Hello all, > > I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file > I > noticed it is rather large. After further inspection I see that all the > volume history is stored in this file back to the day when we first turned > ADSM. Most of this data is useless. Is there a setting or a way to > clear > this file? > > Thanks in advance. > > Ray Baughman > Engineering Systems Administrator > TSM Administrator > National Machinery Co. > Phone: 419-443-2257 > Fax: 419-443-2376 > Email: [EMAIL PROTECTED]
volhist file
Hello all, I am running TSM 3.7.3.8 on AIX 4.3.3. In looking at my volhist.txt file I noticed it is rather large. After further inspection I see that all the volume history is stored in this file back to the day when we first turned ADSM. Most of this data is useless. Is there a setting or a way to clear this file? Thanks in advance. Ray Baughman Engineering Systems Administrator TSM Administrator National Machinery Co. Phone: 419-443-2257 Fax: 419-443-2376 Email: [EMAIL PROTECTED]
