Re: do locked nodes participate in expiration?

BTW, when you DECOMM a node, after purging the inactive copies and marking remaining active backups as inactive, it LOCKs the node. On Wed, Nov 14, 2018 at 3:40 PM Marc Lanteigne wrote: > Locked or not locked, it's not a determining factor for expiration. > > You could also de

Re: do locked nodes participate in expiration?

Locked or not locked, it's not a determining factor for expiration. You could also decommission the nodes after you move them to a new server. That will do a few things for you: - prevent the node to perform any new backups/archives, but can still connect to restore older data, if you lo

do locked nodes participate in expiration?

we trying to lock out clients from a server we're moving off of but we also want data to expire for the locked out clients maybe we need to rename the nodes instead

Re: Scalability problems with expiration?

Not sure if I see any improvement going from 7.1.3 to 7.1.7.1. Expiration has lasted 4 days processing the last "problematic" node with 50 mill objects deleted so far. DB is on all flash so hardware performance should not be an issue. Hans Chr, On Wed, Oct 11, 2017 at 3:01 PM, Hans

Re: Scalability problems with expiration?

higher) and 7.1.3 (or higher) > expiration might "hang" on a node while expiring backup data only. > Expiration is not actually hung it is still processing but very slowly due > to a non-optimized* > *SQL/Select. A change to this SQL/Select occurred between 6.3.5

Re: Scalability problems with expiration?

We hit the problem at 6.3.6 per this document <http://www-01.ibm.com/support/docview.wss?uid=swg1IT17642> which says: *After upgrading the server to 6.3.6.000 (or higher) and 7.1.3 (or higher) expiration might "hang" on a node while expiring backup data only. Expiration is not

Scalability problems with expiration?

I have noticed that expiration suddenly takes a lot more time. The first million objects are expired/deleted very quickly but it slows down to an almost hang with the last 10%. The DB has reached 2 TB and server is 7.1.3.100. Any performance enhancements in later levels? Hans Chr.

Re: SAP HANA backup expiration

OPT3) - KLM" > To: ADSM-L@VM.MARIST.EDU > Date: 06/21/2017 04:28 AM > Subject: Re: SAP HANA backup expiration > Sent by: "ADSM: Dist Stor Manager" > > Hi Del! > Thank you very much for your explanation. I discovered that the > delete through HANA studio

Re: SAP HANA backup expiration

Engineering -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Del Hoobler Sent: maandag 19 juni 2017 15:48 To: ADSM-L@VM.MARIST.EDU Subject: Re: SAP HANA backup expiration Hi Eric, Once the backups have been deleted in HANA Studio, then HANA will delay

Re: SAP HANA backup expiration

/SYS/global/hdb/backint/2016_09_20_databackup_3_1" BKI2003I: File R26___A0HZTF1HWY_RZ_TSM_SERVER@MC_DISK#130698 0 /usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_1_1 deleted. #DELETED "R26___A0HZTF1HWY" "/usr/sap/R26/SYS/global/hdb/backint/2016_09_20_databackup_1_1"

SAP HANA backup expiration

ccessful new backup version so we do not currently offer expiration of backups based on version limit. However, we do plan to provide that capability once SAP implements the enhancement to the backup API we have requested (to indicate whether or not all the data was streamed successfully). SA

Re: File expiration in schedule log

: Wednesday, January 20, 2016 12:12 PM To: ADSM-L@VM.MARIST.EDU Subject: File expiration in schedule log I've never had to deal much with the client schedule log. But, do the statements below (from dsmsched.log) mean that a file was marked to be expired, and that a subsequent EXPIRE INVENTORY o

File expiration in schedule log

I've never had to deal much with the client schedule log. But, do the statements below (from dsmsched.log) mean that a file was marked to be expired, and that a subsequent EXPIRE INVENTORY on the TSM server would have removed the file? 01/19/2016 19:23:14 Expiring-->5,898,240 \\\d$

expiration errors, now what

I have recently started having 1,698 errors during expiration. In tsm 5, you would audit the database. Now not sure how to go about determining then fixing the errors. Recently audited the disk pool, after having to rebuild the server from scratch. That took 72 hours. No errors were found at

Inventory expiration failure

The inventory expiration process on one of our TSM servers was reported as failed this morning, but I couldn't find any message reporting a reason for the failure. The output from the "dsmadmc" command used to execute the "expire inventory" command was captured to a f

Expiration nodes processed larger than number of nodes

If I have 32 nodes (SELECT COUNT(*) FROM NODES) why does EXPIRE INVENTORY show more than that being processed? Curious. Steve STEPHEN STACKWICK | Senior Consultant | 301.518.6352 (m) | stephen.stackw...@icfi.com | icfi.com ICF INTERNATIONAL | 4

SV: Help with NDMP dump & diff expiration

Help with NDMP dump & diff expiration Another option, the one we use, is to use the NAS to snap a copy and keep that snap for some number of days and only make full dumps once a week. Andy Huebner -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Beha

Re: Help with NDMP dump & diff expiration

, December 27, 2012 4:41 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Help with NDMP dump & diff expiration Exactly what I needed to know. Thanks Remco. ( and saves me the trouble of putting in another RFE!) -Original Message- From: ADSM: Dist Stor Manager [mailto:AD

Re: Help with NDMP dump & diff expiration

: Re: [ADSM-L] Help with NDMP dump & diff expiration Hi, I once raised an RFE for managing diffs separately from the fulls. Unfortunately the answer is NO. workaround: use multiple nodenames and make fulls on both nodenames and diffs only with one yes a pita and a waste of tapes... if only

Re: Help with NDMP dump & diff expiration

Hi, I once raised an RFE for managing diffs separately from the fulls. Unfortunately the answer is NO. workaround: use multiple nodenames and make fulls on both nodenames and diffs only with one yes a pita and a waste of tapes... if only IBM could think of something better ;-) On 27 dec.

Help with NDMP dump & diff expiration

Need some help from folks doing "external" NDMP dumps, where TSM triggers the dump but it's done by the NAS device across the fibre to pool defined as TYPE=NDMPDUMP, not a standard TSM storage pool. Have a customer installing an EMC (VNX) NAS which will store multiple millions of .pdf files.

Expiration performance TSM 5.5 (request)

We are still running TSM 5.5.3 and are an IBM shop with DS8300, XIV Gen3 and XIV Gen2 behind SVC 8G4's servicing the I/O. We run a Windows 2003 Enterprise MSCS with 7 instances across the two nodes. Our expiration runs straight after we've completed a full database backup to tape, f

Re: Expiration performance TSM 5.5 (request)

questions when I'm back. Please keep your expiration performance figures coming. TSM Support said that more that more than 1000 object/sec is probably not possible, but you proved otherwise. It should be possible to at least make it run 8 times as fast. Kind regards, Eric van Loon -O

Re: Expiration performance TSM 5.5 (request)

ba and hdisks.  We find the hba default often to be too low for large I/O processing. - Are your luns on FASTVP in the vmax?  If you have a sata tier/pool, expiration could be reading lots of little used blocks that have fallen to the lowest tier.  You would see very slow reads in this case for t

Re: Expiration performance TSM 5.5 (request)

ing a list of expiration candidates, which is added overhead. Whereas expiration involves database updates, and thus locking, it may run into lock conflicts with other processes operating in the same area. The expiration of System Objects used to involve a huge, grouped transaction, but was chang

Re: Expiration performance TSM 5.5 (request)

I'm pretty sure we can agree that expiration should be alot higher than 100 objects / sec. The question is more WHY he's getting 100 objects / sec. According to previous information, disks should be in order, so the next questions would be: a) What platform are you on? b) How lon

Re: Expiration performance TSM 5.5 (request)

On 02/16/2012 09:02 AM, Loon, EJ van - SPLXO wrote: select activity, cast((end_time) as date) as "Date", (examined/cast((end_time-start_time) seconds as decimal(18,13))*3600) "Objects Examined/Hr" from summary where activity='EXPIRATION' and days(end_time)-da

Re: Expiration performance TSM 5.5 (request)

ow that the AIX defaults can be very low. Steven On 16 February 2012 14:02, Loon, EJ van - SPLXO wrote: > Hi TSM-ers! > I'm struggling with the performance of our expiration process. I can't > get it any faster than 100 object/second max. We tried everything, like > using mo

Re: Expiration performance TSM 5.5 (request)

Hi Eric Out of curiosity, how long has the TSM server existed, and how long has it been since you did an unload/load database? Fragmentation could also be the root cause to expiration taking to long. Regards Daniel Daniel Sparrman Exist i Stockholm AB Växel: 08-754 98 00 Fax: 08-754 97 30

Re: Expiration performance TSM 5.5 (request)

To: ADSM-L@VM.MARIST.EDU Subject: Ang: Expiration performance TSM 5.5 (request) Hi To begin with, the guidelines for database setup is something similiar to: a) 8-12 primary database volumes (since you're on 5.x you can still use TSM mirroring). Each volume should be in it's own filesystem,

Re: Expiration performance TSM 5.5 (request)

Hi Gary! I know about the Windows 2008 system state performance issue which will never be resolved in 5.5, but expiration performance is similar on another server, which only contains 3 Windows 2008 nodes... Thanks! Kind regards, Eric van Loon -Original Message- From: ADSM: Dist Stor

Re: Expiration performance TSM 5.5 (request)

Well, since you have multi-threaded expiration in TSM v6 (basically 1 thread per volume) expiration is alot faster. That could be an easy way of handling your expiration problems, going to v6, but if your databasevolumes are located on the same arrays, you'll still get lousy performance,

Re: Expiration performance TSM 5.5 (request)

Do you have many win 2008 and win 7 clients with client version 6.2.2? For some reason (forget the apar), expiration is very slow with these clients. I am going to 6.3 soon, and hope to solve this with that move. I have a 6.2 server, can't get your script to run, but observation tells me

Ang: Expiration performance TSM 5.5 (request)

;surprised if your db volumes are located (some of them or all of them) within >the same array. What operating system are you using? If you're on AIX, try checking I/O statistics during expiration to see if your queues are getting full (as in 100% utilization of the disks using iostat

Expiration performance TSM 5.5 (request)

Hi TSM-ers! I'm struggling with the performance of our expiration process. I can't get it any faster than 100 object/second max. We tried everything, like using more or less database volumes, multiple volumes per filesystem, mirroring, unmirroring, but nothing seems to have any positive

Re: expiration

This has been one of my gripes for a while. The main problem with this is the vocabulary that the client uses. A TSM client just "deactivates" a file, it doesn't expire anything despite what the client log says. The Server expiration process will then analyze the inactive files

Re: expiration

" To: ADSM-L@VM.MARIST.EDU Date: 10/20/2011 10:47 AM Subject: Re: [ADSM-L] expiration Sent by:"ADSM: Dist Stor Manager" On 10/20/2011 09:00 AM, Tim Brown wrote: > If I have a client that I need to not run a backup on for specific > DR reasons since it

Re: expiration

xpire inventory process on the server and not the client backup the missing files on the server wont expire and will remain active. An important distinction here: older "Inactive" file versions will continue to age away and be discarded by successive expiration processes. But if the file

expiration

As a client performs a backup it expires files and this is evident in the logs. Later the expiration inventory process runs on the server. Are the files just marked for expiration by the client and the expiration process actually updates the database. If I have a client that I need to not

Re: DB backup expiration

case it'd be easiest to just do the del volhist on a daily basis... Sent from my iPhone On Aug 1, 2011, at 2:22 PM, Erwann SIMON wrote: > Hi Thomas, > > Virtual volumes are considered "remote" by DRM as soon as they're created, so > the expiration of "DB ba

Re: DB backup expiration

Hi Thomas, Virtual volumes are considered "remote" by DRM as soon as they're created, so the expiration of "DB backup series expiration days" is immediatly taken into account whereas "real" volumes (tapes or files) needs to be in a "vault" state

DB backup expiration

We have two TSM 6.2.2.0 servers running under mainframe Linux. Both report 'DB Backup Series Expiration Days: 3 Day(s)' when I execute 'query drmstat' commands. One of the systems is configured as a library manager. It performs a database snapshot and a full database bac

Problem with expiration and log volume filling up.

Hi all Running TSM 5.5.2.0 on Solaris 9 I have started to see a problem now where the expiration process seems to get caught in some kind of loop where the log volume starts to fill up. At this point if I cancel the process it can sit there for over an hour with the log getting more and more

Re: Expiration causes backups to hang

pr 25, 2011 at 8:19 AM, David E Ehresman > wrote: > > > Where might one find the 6.2.2.30 patch? > > > > >>> Zoltan Forray 4/24/2011 7:46 AM >>> > > 6.2.2.30 is out as an official patch. > > On Apr 24, 2011 7:33 AM, "Hans Christian R

Re: Expiration causes backups to hang

an official patch. > > On Apr 24, 2011 7:33 AM, "Hans Christian Riksheim" > > > wrote: > > > Problem is resolved. > > > > > > We upgraded from 6.2.2.0 to 6.2.2.25(6.2.2.2 patch + efix) and > > expiration > > > rates are 5-10 times hi

Re: Expiration causes backups to hang

as an official patch. > On Apr 24, 2011 7:33 AM, "Hans Christian Riksheim" > wrote: > > Problem is resolved. > > > > We upgraded from 6.2.2.0 to 6.2.2.25(6.2.2.2 patch + efix) and > expiration > > rates are 5-10 times higher and no hangs yet. We observe

Re: Expiration causes backups to hang

the 6.2.2.30 patch? > > >>> Zoltan Forray 4/24/2011 7:46 AM >>> > 6.2.2.30 is out as an official patch. > On Apr 24, 2011 7:33 AM, "Hans Christian Riksheim" > wrote: > > Problem is resolved. > > > > We upgraded from 6.2.2.0 to 6.2.2.25

Re: Expiration causes backups to hang

Where might one find the 6.2.2.30 patch? >>> Zoltan Forray 4/24/2011 7:46 AM >>> 6.2.2.30 is out as an official patch. On Apr 24, 2011 7:33 AM, "Hans Christian Riksheim" wrote: > Problem is resolved. > > We upgraded from 6.2.2.0 to 6.2.2.25(6.2.2.2 patch +

Re: Expiration causes backups to hang

6.2.2.30 is out as an official patch. On Apr 24, 2011 7:33 AM, "Hans Christian Riksheim" wrote: > Problem is resolved. > > We upgraded from 6.2.2.0 to 6.2.2.25(6.2.2.2 patch + efix) and expiration > rates are 5-10 times higher and no hangs yet. We observe that System State &

Re: Expiration causes backups to hang

Problem is resolved. We upgraded from 6.2.2.0 to 6.2.2.25(6.2.2.2 patch + efix) and expiration rates are 5-10 times higher and no hangs yet. We observe that System State expirations from 2008 servers are much faster now. Hans Chr. On Wed, Apr 13, 2011 at 10:17 AM, Hans Christian Riksheim wrote

Re: Expiration causes backups to hang

clients were upgraded to 6.2.1.0 (now I'd use 6.2.2.0). - Margaret Clark -Original Message- From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of Hans Christian Riksheim Sent: Wednesday, April 13, 2011 1:18 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiration c

Re: Expiration causes backups to hang

Hi Hans, We are still having problem with the expiration on some filesystem node but instead of hanging, the DB is growing at an incredible pace then TSM crashes. This is with 6.1.3 and cancel expiration command would not respond. We identified some Windows 2008 servers (Systemstate

Expiration causes backups to hang

Hi, anyone else have this problem? Running 6.2.2 on AIX 6.1. Submitting a PMR on this in parallell. When I say hang I mean a complete hang. All incoming backups stops. Traffic is resumed when we cancel expiration. Hans Chr.

Re: Ang: TSM for DB password expiration

ohn 3:16! > > > -Original Message- > From: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of > David E Ehresman > Sent: Friday, March 25, 2011 10:34 AM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Ang: TSM for DB password expiration > &g

Re: Ang: TSM for DB password expiration

Howard Coles > Sent: Friday, March 25, 2011 5:11 PM > To: ADSM-L@VM.MARIST.EDU > Subject: Re: [ADSM-L] Ang: TSM for DB password expiration > > No, it's not different, Oracle TDP works the same on Linux and AIX. > The only TDP I'm not sure of is the Windows version, but

Re: Ang: TSM for DB password expiration

rom: ADSM: Dist Stor Manager [mailto:ADSM-L@VM.MARIST.EDU] On Behalf Of David E Ehresman Sent: Friday, March 25, 2011 10:34 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Ang: TSM for DB password expiration And is Oracle TDP on Linux different than on AIX? Does password generate on linux? Dav

Re: Ang: TSM for DB password expiration

here is to set the password expiration to 0 on both the node, and the admin owner (if you have it) of the node. However, what Daniel said is correct unless you run "update node server-oracle passexp=0" AND "update admin server-oracle passexp=0", then it will just keep on usi

Re: Ang: TSM for DB password expiration

For the Oracle TDP on AIX you have to set the passwordaccess option to prompt, as the TDP will NOT update the password. The best option here is to set the password expiration to 0 on both the node, and the admin owner (if you have it) of the node. However, what Daniel said is correct unless

Re: Ang: TSM for DB password expiration

Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with passw

Ang: TSM for DB password expiration

ds Daniel Sparrman -"ADSM: Dist Stor Manager" skrev: - Till: ADSM-L@VM.MARIST.EDU Från: David E Ehresman Sänt av: "ADSM: Dist Stor Manager" Datum: 03/25/2011 15:41 Ärende: TSM for DB password expiration Has anyone had problems with TSM for DB (Oracle), aka TDPO, and passwo

TSM for DB password expiration

Has anyone had problems with TSM for DB (Oracle), aka TDPO, and password expiration? We are running TSM for DB v5.5.1.0 with TSM api 6.2.2.0 on AIX 5.3 to a TSM server at 6.2.2.0 also on AIX 5.3. We are running with password generate. Last night we got two ANR0425W password has expired messages

Re: Expiration processing

Technically correct, Just make sure you disable the auto expiration (q opt EXPINTERVAL) If I were confronted with a temporary need like this (as I have been in the past), I'd rather just change the RETE and RETO until you can resume expiration. I think that is much safer. You won'

Expiration processing

I have a copygroup with VERE and VERD set to NOLIMIT and RETE and RETO set to 30 days. If I do NOT do expiration processing (expire inventory), will inactive backups remain accessible longer than 30 days until expiration processing resumes? David

Re: Expiration and Delete Filespace causing TSM DB to grow and crash

Québec 514-254-6000 x 6559 -Message d'origine- De : ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] De la part de Prather, Wanda Envoyé : 23 novembre 2010 15:40 À : ADSM-L@VM.MARIST.EDU Objet : Re: [ADSM-L] Expiration and Delete Filespace causing TSM DB to grow and crash Also,

Re: Expiration and Delete Filespace causing TSM DB to grow and crash

or Manager [mailto:ads...@vm.marist.edu] On Behalf Of Richard Sims Sent: Tuesday, November 23, 2010 2:46 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Expiration and Delete Filespace causing TSM DB to grow and crash It is often the case that such backups are segregated on their own volumes, where t

Re: Expiration and Delete Filespace causing TSM DB to grow and crash

It is often the case that such backups are segregated on their own volumes, where that allows you to perform a Delete Volume to dispose of the stuff in a meta manner. Richard Sims

Expiration and Delete Filespace causing TSM DB to grow and crash

Hi TSMers, Our TSM 6.1.3.3. has a Windows 2008 (R2 64bits) client node that contains over 14 millions files (95% being SystemState backup files) and when either the expiration process or a delete filespace command is run against it, TSM DB is growing at the rate of 1 gb/hour until

Expiration question

ously it can only run > one-at-a-time. > > > > From: > "Clark, Margaret" SDDPC.ORG> > To: > ADSM-L < at > VM.MARIST.EDU > Date: > 08/25/2010 02:50 PM > Subject: > Re: [ADSM-L] Expiration question > Sent by: > "ADSM: Dist Stor Manager&

Re: Expiration question

There is Cancel Expiration, and then there is Cancel Process on that process number, to different effect. ;-)

Re: Expiration question

08/25/2010 02:50 PM Subject: Re: [ADSM-L] Expiration question Sent by: "ADSM: Dist Stor Manager" A bit late, but I don't recall any previous responses to this... It will do no good to cancel a running expiration process. When you start again, expiration picks up exactly where it

Re: Expiration question

A bit late, but I don't recall any previous responses to this... It will do no good to cancel a running expiration process. When you start again, expiration picks up exactly where it left off. Trying to cancel it just prolongs the agony. No idea about the retries, sorry. - Margaret

Expiration question

I have 2-issues with expiration processing. First, on my 5.5.4.2 server - we stopped expiration for more than a week, to perform recovery of a large SAN failure. Now, expiration has been running since 08/17 and still running. Expired over 24M objects out of 29M examined. Didn't know

Re: TSM Exclude/Expiration

de.FS preclude entry into the specified areas when the backup is by file system: other forms of Exclude involve entry and scanning and attendant overhead. However, expiration effect rules for the two are different (see the manual). You may want to commit to the elimination of the 1/3 from t

TSM Exclude/Expiration

Good Afternoon. We have a TSM AIX server running TSM 5.4 and a Windows 2008 running TSM client 5.5 We currently have 53 million files on a single partition and plan to break it up into 3 partitions to help with backup times, etc.. The plan was to move about 1/3 of the data to the other partition,

Re: Expiration Questions

This would suggest to me that any inactive objects (modified or deleted) bound to this management class will be expired/removed from TSM-managed storage 30 days from their inactivation date (subject to expiration processing). >From the TSM Server, the only way I can think of checking this wo

Re: Expiration Questions

On Mar 23, 2010, at 9:22 AM, Jones, Eric J wrote: > Is there a way to see how many files will expire in the next day and/or week > for a particular server/workstation? You would have to trawl through the enormous Backups table, matching on CLASS_NAME and operating on the DEACTIVATE_DATE field i

Re: Expiration Questions

Sent: Friday, March 19, 2010 10:07 AM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Expiration Questions Hi Eric, When you say, "We have a 30 day policy", could you send the output of a `Q COPYGROUP` for the relevant management class? Cheers, David McClelland London, UK -Origin

Re: Expiration Questions

: 19 March 2010 13:04 To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Expiration Questions We are running TSM 5.4 server on an AIX machine with our clients(Windows 2003/2008) running also running TSM 5.4. My question is we changed permissions on all our files on 1 of our servers 32 days ago which cause

Antwort: [ADSM-L] Expiration Questions

Hi Eric, do you keep more than n versions of a file? Have a look at your config of "Versions data exists" regards, Dierk Von: "Jones, Eric J" An: ADSM-L@VM.MARIST.EDU Datum: 19.03.2010 14:05 Betreff: [ADSM-L] Expiration Questions Gesendet von: "ADSM: Dist Stor Ma

Expiration Questions

so I had expected a large expiration to take place 2 days ago but it hasn't taken place yet. Is there a way to tell 1: When these files will expire? 2: How many versions of the files are currently on the server and how many days until they expire? Thanks Eric

Re: Question on Expiration

.*). Don't run heavy selects during busy periods, like during Expiration. If you don't have a comfortable buffer of recovery log and db space, be very wary of the following message: "ANR2963W This SQL query may produce a very large result table, or may require a significant amount of

Re: Question on Expiration

On Feb 26, 2010, at 10:40 AM, Jones, Eric J wrote: > Thanks everyone. Got exactly what I wanted. > 1 other question is, is there a way to tell how many objects were added to > the DB a day/week by server. > The best harvest point for that is the TSM accounting records. The Summary table may

Re: Question on Expiration

: Thursday, February 25, 2010 5:07 PM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] FW: [ADSM-L] Question on Expiration Eric, That only shows and object count, not bytes. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebschman, George J. Sent

Re: FW: [ADSM-L] Question on Expiration

, George J. Sent: Thursday, February 25, 2010 5:30 PM To: ADSM-L@vm.marist.edu Subject: [ADSM-L] FW: [ADSM-L] FW: [ADSM-L] Question on Expiration Eric, I believe that Remco is correct. The only way I see to do this is by doing a before/after query of occupancy: select * from occupancy where

FW: [ADSM-L] FW: [ADSM-L] Question on Expiration

uestion on Expiration expiration only deals in objects, reclamation deals in objects and bytes. I don't believe there is any way for you to find out. I fail to see why this is operationally important. On 25 feb 2010, at 23:07, Huebschman, George J. wrote: > Eric, > That only shows

Re: FW: [ADSM-L] Question on Expiration

expiration only deals in objects, reclamation deals in objects and bytes. I don't believe there is any way for you to find out. I fail to see why this is operationally important. On 25 feb 2010, at 23:07, Huebschman, George J. wrote: > Eric, > That only shows and object count

FW: [ADSM-L] Question on Expiration

Eric, That only shows and object count, not bytes. -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Huebschman, George J. Sent: Thursday, February 25, 2010 5:05 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Question on Expiration

Re: Question on Expiration

, 2010 4:23 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Question on Expiration Bill: I can see a total on the TSM server for all the machines that have objects to expire but cannot see for a particular machine. Is there any way to tell how many have expired on 1 machine since we are backing u

Re: Question on Expiration

x27;s expiring, not the amount of space. Thanks -Original Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Evans, Bill Sent: Thursday, February 25, 2010 3:21 PM To: ADSM-L@vm.marist.edu Subject: Re: [ADSM-L] Question on Expiration query actl begind=-1 se=&qu

Re: Question on Expiration

Sent: Thursday, February 25, 2010 11:55 AM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Question on Expiration Good Afternoon. I was wondering if there was a way to generate a report or see it in the server logs how many files had expired each day for a particular server by day for a week then 2 week

Re: Question on Expiration

, February 25, 2010 2:55 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Question on Expiration Good Afternoon. I was wondering if there was a way to generate a report or see it in the server logs how many files had expired each day for a particular server by day for a week then 2 weeks, etc. We run

Question on Expiration

Good Afternoon. I was wondering if there was a way to generate a report or see it in the server logs how many files had expired each day for a particular server by day for a week then 2 weeks, etc. We run expiration each day at 4:00 and the logs show the total expiration but not by machine

Re: Long Expiration

On Thu, Jan 21, 2010 at 01:03:52PM -0500, Richard Rhodes wrote: > We are always fighting expiration problems. > > We've found is that it's highly dependent on: >- number of files for the node > - number of inactive files for the node (ibm has a note about

Re: Long Expiration

We are always fighting expiration problems. We've found is that it's highly dependent on: - number of files for the node - number of inactive files for the node (ibm has a note about this) - random access performance of your disk system - what else the tsm server is

Long Expiration

Hello List, I'am facing a long expiration Time on my TSM Server: OS: AIX 5.3 TL 07 HW: Power6 4 CPU, 32 GB Mem TSM Server 5.4.5 TSM Database 105 GB on SAN (DS8k) 2x4 Gbit Fiber Attached TSM Log 13 GB on SAN (DS8k) 2x4 Gbit Fiber Attached I wrote a small script which looks for Entrys in actl

Re: Bug report - backupsets and expiration hanging - just helping out

al Message- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Conway, Timothy Sent: Friday, November 27, 2009 12:25 PM To: ADSM-L@VM.MARIST.EDU Subject: [ADSM-L] Bug report - backupsets and expiration hanging - just helping out We are off maintenance, so I can't turn t

Bug report - backupsets and expiration hanging - just helping out

We are off maintenance, so I can't turn this in directly to IBM, but I know some of their best and brightest watch this list. I've got a consistent case where a backupset being generated hangs if an expiration starts during it, after which neither process will finish cancelling

Re: Expiration of Exchange

o:ads...@vm.marist.edu] On Behalf Of Del Hoobler Sent: Thursday, October 08, 2009 6:05 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Expiration of Exchange Hi Fred, All files backed up in an Exchange VSS backup are part of a "group". The files in a "group" are all managed togethe

Re: Expiration of Exchange

ote on 10/07/2009 09:33:19 PM: > [image removed] > > Expiration of Exchange > > Fred Johanson > > to: > > ADSM-L > > 10/07/2009 09:34 PM > > Sent by: > > "ADSM: Dist Stor Manager" > > Please respond to "ADSM: Dist Stor Manager&quo

Re: Expiration of Exchange

Sent: Wednesday, October 07, 2009 8:53 PM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Expiration of Exchange My guess is that you are mounting up the filesystem, and backing up the files directly. The log files in Exchange are probably getting a new name as they are truncated, which means that

  1   2   3   4   5   6   7   >