What we do :
- We set retention to the max of all our policies
- We set version to NOLIMIT

It's the only manner to not have problem during restore process with GUI.

Andrew Raibeck a écrit :

I would need more information. For example, I can understand how this can happen if it is, say, a point-in-time restore. In that case, if the management class with the longest retention period happens to have a lower VEREXISTS or VERDELETED than the management class to which the directory's files are bound, you can have a situation where files exist for a given date, but not the parent directory. Or if DIRMC points to a directory with a lower RETONLY setting.

Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Product Development
Level 3 Team Lead
Internal Notes e-mail: Andrew Raibeck/Tucson/IBM@IBMUS
Internet e-mail: storman AT us.ibm DOT com

IBM Tivoli Storage Manager support web page: http://www.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> wrote on 05/06/2008 02:57:52 PM:

No, directories get bound to the management class with the longest retention, not the shortest. I can't quite figure how a file in a directory wouldn't expire before the directory it was in expired. The directory would have been backed up when the file was touched last so I would think that directory would go no sooner than the file went. If you move a directory to a new class, don't they get rebound? Maybe not. I'm counting on Andy jumping in here when he has a chance and straightening us all out...

Kelly Lipp
CTO
STORServer, Inc.
485-B Elkton Drive
Colorado Springs, CO 80907
719-266-8777
www.storserver.com


-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Joe Crnjanski

Sent: Tuesday, May 06, 2008 3:43 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: [ADSM-L] Directory Structure Expires

We had same problem. GUI behavior is by design. You need to add command in your dsm.opt

DIRMC      longretentionmgmtclass

If you don't have this command directories get bind to management class that has shortest retention time (or something like this); I always need to look at manual when I need to understand this command. If you go in gui, click on directory, than click on info button, it will show you to which mgmt class that directory is bound.

If you know your path you can use command line to restore required file.

Joe Crnjanski
Infinity Network Solutions Inc.
Phone: 416-235-0931 x226
Fax:     416-235-0265
Web: www.infinitynetwork.com


-----Original Message-----

From: ADSM: Dist Stor Manager [mailto:ADSM-L AT VM.MARIST DOT EDU] On Behalf Of Laurent Bendavid

Sent: Tuesday, May 06, 2008 5:11 PM
To: ADSM-L AT VM.MARIST DOT EDU
Subject: Re: Directory Structure Expires

You have to specify a different Management Class for directory (MC_DIR parameter) with NOLIMIT for retention (or a time greater than all other policies).

Now, to do your restore, you could use dsmc query backup -filesonly to show your files backed up and use it in dsmc restore.

Lepre, James a écrit :

Hello Everyone,



 I placed a call with TSM support regarding the Client GUI not showing
the directory structure and they told me that when the directory

structure expires you can no longer use the GUI for restores. An

option

is to selectively backup the node again which will refresh the

directory

structure.  Has anyone encounter this problem and does anyone have
procedures in place to avoid this?





Any help or Suggestions are appreciated

Thank you

James

---------------------------------------------------------------

Confidentiality Notice: The information in this e-mail and any

attachments thereto is intended for the named recipient(s) only. This e-mail, including any attachments, may contain information that is privileged and confidential and subject to legal restrictions and penalties regarding its unauthorized disclosure or other use. If you are not the intended recipient, you are hereby notified that any disclosure, copying, distribution, or the taking of any action or inaction in reliance on the contents of this e-mail and any of its attachments is STRICTLY PROHIBITED. If you have received this e-mail in error, please immediately notify the sender via return e- mail; delete this e-mail and all attachments from your e-mail system and your computer system and network; and destroy any paper copies you may have in your possession. Thank you for your cooperation.