ADSM-L

Re: Priorities

2004-07-12 08:54:09
Subject: Re: Priorities
From: "Bos, Karel" <Karel.Bos AT ATOSORIGIN DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Mon, 12 Jul 2004 14:53:09 +0200
Hi,

If you start reclamation from an admin schedule defined with prio >5 then the 
manual started processes (default=5) should preempt the space recl.

Regards,

Karel

-----Original Message-----
From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU]On Behalf Of
Copper, Steve
Sent: maandag 12 juli 2004 14:46
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Priorities


All,

Sorry to keep on at this, but I am not seeing the predicted situations as
per the Admin guide, (or at least my interpretation of it)

In the guide it says 
The following are defined as high priority operations for mount point
access:

- Backup database
- Restore
- Retrieve
- HSM recall
- Export
- Import

Any of which will preempt, in decreasing order of priority:
1. Move data
2. Migration from disk to sequential media
3. Backup, archive, or HSM migration
4. Migration from sequential media to sequential media
5. Reclamation


I understand the top list preempting the lower list, but what if there are 2
processes in the lower list running at the same time. Does it still have the
decreasing order of priority?

>From what I am seeing there is no order of priority between options 1 to 5.
For example I have a space rec and a move node data running as per the
example below.

7,662     Space Reclamation   Offsite Volume(s) (storage pool OFFSITE1),
Moved
                                        Files: 33801, Moved Bytes:
6,043,874,172,
                              Unreadable Files: 0, Unreadable Bytes: 0.

                              Current Physical File (bytes): 2,147,615,593
Current input volume:         000039.
Current output volume:          000117.

7,663     Move Node Data        Storage Pool LTO_POOL, Target Pool LTO_POOL
Files
                              Moved: 0, Bytes Moved: 0, Unreadable Files: 0,

                              Unreadable Bytes: 0. Current Physical File

                              (bytes): 293,560

Waiting for access to input volume 000039 (426 seconds).
Current output                  volume: 000116.

The space rec process has volume 000039 mounted on which the move node data
process is waiting on. Therefore indicating that there is no priority
between these 2 operations.

Is there anyway that I can get the move node data command to take priority
over the space rec process?

TSM Server 5.1.8.0

Thanks in advance

Steve

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________

<Prev in Thread] Current Thread [Next in Thread>