Re: expire inventory question
Expiration is finishing successfully. I takes about an hour to run, the DB is 20 Gig at 50% util. The reclamation threshold is 50% already. What should be noted is that the files are not expiring. The volumes say full and the used percentage is 100%. Rob Schroeder Roger Deschner <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Sent by: "ADSM: cc: Dist StorSubject: Re: expire inventory question Manager" <[EMAIL PROTECTED] .EDU> 07/24/2002 01:46 AM Please respond to "ADSM: Dist Stor Manager" How long does expiration take? Is it finishing? If not, you are in big trouble. What is your reclamation threshold? A good rule of thumb is to simply set it to 50%, which is the default. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] ( ) ASCII ribbon campaign X against HTML e-mail / \ On Tue, 23 Jul 2002, Rob Schroeder wrote: >When I run inventory expiration, I can look in the activity log and see the >process going through each of my file spaces. I see it hitting the TSM >clients as well as the TDP for SQL clients, however I do not see the >messages for the TDP for Oracle clients. I have used RMAN to expire and >delete the backups that are older than 10 days, but are still not getting >any tape storage back. My TSM server is Win2k Sp2 4.1.6 and my client is >Win2k Sp2 TDP 2.2 TSM 4.2.1.20. I have double checked the settings for >verdeleted and retonly and both are set to 0. > >Am I missing something here. > >Help > >Rob Schroeder >Famous Footwear >
Re: expire inventory question
How long does expiration take? Is it finishing? If not, you are in big trouble. What is your reclamation threshold? A good rule of thumb is to simply set it to 50%, which is the default. Roger Deschner University of Illinois at Chicago [EMAIL PROTECTED] ( ) ASCII ribbon campaign X against HTML e-mail / \ On Tue, 23 Jul 2002, Rob Schroeder wrote: >When I run inventory expiration, I can look in the activity log and see the >process going through each of my file spaces. I see it hitting the TSM >clients as well as the TDP for SQL clients, however I do not see the >messages for the TDP for Oracle clients. I have used RMAN to expire and >delete the backups that are older than 10 days, but are still not getting >any tape storage back. My TSM server is Win2k Sp2 4.1.6 and my client is >Win2k Sp2 TDP 2.2 TSM 4.2.1.20. I have double checked the settings for >verdeleted and retonly and both are set to 0. > >Am I missing something here. > >Help > >Rob Schroeder >Famous Footwear >
Re: expire inventory question
What about retv for t=a. I know that on TDP for SAP is it does everything as archives so it may actually be your archives that aren't going away. You do need to make sure that retv is greater then or equal to how long you keep them in TDP. Becky -Original Message- From: Rob Schroeder [mailto:[EMAIL PROTECTED]] Sent: Tuesday, July 23, 2002 10:55 AM To: [EMAIL PROTECTED] Subject: expire inventory question When I run inventory expiration, I can look in the activity log and see the process going through each of my file spaces. I see it hitting the TSM clients as well as the TDP for SQL clients, however I do not see the messages for the TDP for Oracle clients. I have used RMAN to expire and delete the backups that are older than 10 days, but are still not getting any tape storage back. My TSM server is Win2k Sp2 4.1.6 and my client is Win2k Sp2 TDP 2.2 TSM 4.2.1.20. I have double checked the settings for verdeleted and retonly and both are set to 0. Am I missing something here. Help Rob Schroeder Famous Footwear
expire inventory question
When I run inventory expiration, I can look in the activity log and see the process going through each of my file spaces. I see it hitting the TSM clients as well as the TDP for SQL clients, however I do not see the messages for the TDP for Oracle clients. I have used RMAN to expire and delete the backups that are older than 10 days, but are still not getting any tape storage back. My TSM server is Win2k Sp2 4.1.6 and my client is Win2k Sp2 TDP 2.2 TSM 4.2.1.20. I have double checked the settings for verdeleted and retonly and both are set to 0. Am I missing something here. Help Rob Schroeder Famous Footwear
expire inventory question
Hi All Everyday I run the following command line : expire inventory skipdir=no duration=300 and the result is : ANR0812I Inventory file expiration process 582 completed:examined 229248 objects, deleting 1004 backup objects, 756 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. I woul like to know exactly what does it means ? What the real difference between skpdir=yes and skpdir=no and what is the best choice ? Thanks in advanced !
Re: expire inventory - question on number of objects examined
what if you marked a volume as detroyed? I mean if there are active files on the volume, will the inventory expiration update the database so those were-active files get picked up during the next backup? Jie > -Original Message- > From: Thomas Denier [SMTP:[EMAIL PROTECTED]] > Sent: Wednesday, September 13, 2000 10:19 AM > To: [EMAIL PROTECTED] > Subject: Re: expire inventory - question on number of objects > examined > > > What does the number of objects examined during inventory expiration > > include? > > ADSM differentiates between active and inactive backup files. A backup > file is > always active when it first arrives from a client. A backup file changes > to > inactive when the ADSM server finds out that the corresponding client file > has > been updated or deleted. An inactive backup file is retained until > inventory > expiration processing discovers that it no longer meets the retention > criteria > for its management class. Earlier postings to this list indicate that > information about active and inactive backup files is stored in different > parts of the ADSM database, with different trade-offs between compactness > and > fast access. As far as I can tell, inventory expiration does not look at > the > portion of the database used for active backup files. On our system, the > number of objects examined by inventory expiration is in good agreement > with > estimates of the number of inactive backup files. I am not sure how > archived > and space-managed files fit into this scheme of things. We currently have > no > space-managed files, and very few archived files in comparison to the > number > of inactive backup files.
Re: expire inventory - question on number of objects examined
> What does the number of objects examined during inventory expiration > include? ADSM differentiates between active and inactive backup files. A backup file is always active when it first arrives from a client. A backup file changes to inactive when the ADSM server finds out that the corresponding client file has been updated or deleted. An inactive backup file is retained until inventory expiration processing discovers that it no longer meets the retention criteria for its management class. Earlier postings to this list indicate that information about active and inactive backup files is stored in different parts of the ADSM database, with different trade-offs between compactness and fast access. As far as I can tell, inventory expiration does not look at the portion of the database used for active backup files. On our system, the number of objects examined by inventory expiration is in good agreement with estimates of the number of inactive backup files. I am not sure how archived and space-managed files fit into this scheme of things. We currently have no space-managed files, and very few archived files in comparison to the number of inactive backup files.
expire inventory - question on number of objects examined
What does the number of objects examined during inventory expiration include? The following is a sample of the messages I received today when inventory expiration completed: 09/12/2000 13:39:57 ANR0812I Inventory file expiration process 121 completed: examined 40702 objects, deleting 573 backup objects, 0 archive objects, 0 DB backup volumes, and 0 recovery plan files. 0 errors were encountered. 09/12/2000 13:39:57 ANR0987I Process 121 for EXPIRE INVENTORY running in the BACKGROUND processed 573 items with a completion state of SUCCESS at 13:39:57. I am concerned because "examined 40702 objects" is such a low number if "objects" is the same thing referenced to at the completion of a node backup. For example, a single node backup alone last night completed with the following messages: Date/TimeMessage -- 09/12/2000 02:47:00 ANR0403I Session 411 ended for node E011CNCROOKS (NetWare). 09/12/2000 02:47:02 ANE4952I (Session: 429, Node: E011CNCROOKS) Total number of objects inspected: 20,698 09/12/2000 02:47:02 ANE4954I (Session: 429, Node: E011CNCROOKS) Total number of objects backed up: 20,651 09/12/2000 02:47:02 ANE4958I (Session: 429, Node: E011CNCROOKS) Total number of objects updated: 0 09/12/2000 02:47:02 ANE4960I (Session: 429, Node: E011CNCROOKS) Total number of objects rebound: 0 09/12/2000 02:47:02 ANE4957I (Session: 429, Node: E011CNCROOKS) Total number of objects deleted: 0 09/12/2000 02:47:02 ANE4970I (Session: 429, Node: E011CNCROOKS) Total number of objects expired: 0 09/12/2000 02:47:02 ANE4959I (Session: 429, Node: E011CNCROOKS) Total number of objects failed: 0 09/12/2000 02:47:02 ANE4961I (Session: 429, Node: E011CNCROOKS) Total number of bytes transferred: 4.20 GB 09/12/2000 02:47:02 ANE4963I (Session: 429, Node: E011CNCROOKS) Data transfer time:15,673.13 sec 09/12/2000 02:47:02 ANE4966I (Session: 429, Node: E011CNCROOKS) Network data transfer rate: 281.31 KB/sec 09/12/2000 02:47:02 ANE4967I (Session: 429, Node: E011CNCROOKS) Aggregate data transfer rate:256.04 KB/sec 09/12/2000 02:47:02 ANE4968I (Session: 429, Node: E011CNCROOKS) Objects compressed by:0% 09/12/2000 02:47:02 ANE4964I (Session: 429, Node: E011CNCROOKS) Elapsed processing time:04:46:59 09/12/2000 02:47:02 ANR0403I Session 429 ended for node E011CNCROOKS (NetWare). 09/12/2000 02:47:04 ANR0406I Session 430 started for node E011CNCROOKS (NetWare) (BPX-Tcp/Ip 168.169.92.29(1125)). 09/12/2000 02:47:04 ANR0403I Session 430 ended for node E011CNCROOKS (NetWare). The number of "objects backed up" for this node alone is over 20,000. I know that many more files have been backed up for other nodes as indicated by the following portion of output for one volume of a particular node using the QUERY OCCUPANCY command: Node NameType Filespace StorageNumber of Physical Logical Name Pool Name Files Space Space Occupied Occupied (MB) (MB) -- -- - - - E011ERIE1Bkup E011ERIE1- BACKUP-TA-66,795 4,017.34 3,190.26 \VOL1: PEPOOL How can I be sure everything in my TSM database is being examined for possible need of expiration?
