Results 1 to 18 of 18
  1. #1
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default x on file object when doing a restore

    Hi Folks

    I have wanted to restore some files on a client server using the backup-archive gui on the client server. When opening the restore option and expanding the tree to file level let x's appear on some of the objects. What do they mean?

    Thanls

  2. #2
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Those are inactive files. Still available for restore based on your retention policies...
    and all that could have been...

  3. #3
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Thanks Stephen...i'm very new to TSM (Hence the nic)...I dont believe we have any pol's but sort of condition(s) in the pols would prevent these from being recovered?

  4. #4
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,931
    Thanks
    4
    Thanked 233 Times in 228 Posts

    Default

    Quote Originally Posted by Noob View Post
    I dont believe we have any pol's but sort of condition(s) in the pols would prevent these from being recovered?
    The inactive files means that there are/were newer files in its place. You can recover these files by doing a restore should you need to get back information from the "older" files.
    Last edited by moon-buddy; 02-25-2009 at 10:31 AM.
    Ed

  5. #5
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    moon-buddy...so does this mean that the new file hasnt been backedup or are you saying that there are multiple versions?

  6. #6
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Technically, you can recover those files just fine since TSM still has them, but they are not considered the active version of that file. Either the file was deleted a while ago and TSM is retaining it until it officially expires or that file is the 2nd or 3rd or whatever version of the active file on the server still...As mentioned, this all depends on the Retention policies that your node falls under. If you can't recover the file, check the activity log on the TSM server
    and all that could have been...

  7. #7
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    How can I check the policy\expiration values?

  8. #8
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    On the TSM server, you can check what domain your node belongs to and its associated management classes which have the retention policies.

    Check the option files on your nodes to see if you bind a specific backup to a management class and you could also, using the command line (or gui) check the associated domain and MCs. for example, on a AIX box, start the command line client with dsmc. Then at the prompt issue a query mgmtclass

    You can also see what MC your backup are bound to by issuing a query backup "path you want to see" and look at the MC it was bound to.
    and all that could have been...

  9. #9
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Query node - to list the nodes on your TSM server.
    query domain - to list the domains.

    This will list you all the retentions on the TSM server...
    select class_name,destination,verexists,retextra,verdelet ed,retonly,serialization from bu_copygroups
    and all that could have been...

  10. #10
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Hey Stephan...thanks a million

    The returned values for verdelete is 2 and ret only 60 so I am assuming that means that the mgmt class keeps 2 versions of the file...i'm not sure about retonly...would that be rentention for 60 days?

  11. #11
    Senior Member Stephan's Avatar
    Join Date
    Jun 2004
    Location
    Great White North
    Posts
    645
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Yep.

    Here is a little webpage (Lascon) that explains tons of stuff about TSM. Here is the link to the retention. Check it out. It helped me out quite a bit "in the beginning" !

    http://www.lascon.co.uk/d005102.htm#bretain
    and all that could have been...

  12. #12
    Member
    Join Date
    Oct 2008
    Posts
    23
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Excellent thanks stephan. I read the link you sent and I think I understand whats going on

    2 versions of the file is kept for 60 days and then if there are no new versions the file file is expired and so we get a little x on the object in the gui. In our enviroment data is written to disk and then to tape so as long we dont loose the TSM DB we are still able to recover the file from tape provided the tape hasnt been overwritten.

  13. #13
    Member
    Join Date
    Feb 2009
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    That little blue x confused me today. Here's the scenario:

    File x backed up on monday
    Fille x deleted tuesday

    On thursday I look to do a point in time restore to wednesday and I do not see x in the tree. Expected behavior.

    I reinstall the app later thursday and file x is back in place.

    Friday I again look to do a point in time restore to wednesday and now file x appears with a blue x. Unexpected behavior. Did this on two servers to confirm the behavior.

    What am I missing?

    Thanks.

    DW

  14. #14
    Moderator moon-buddy's Avatar
    Join Date
    Aug 2005
    Location
    Somewhere in the US
    Posts
    5,931
    Thanks
    4
    Thanked 233 Times in 228 Posts

    Default

    This means that the file is not part of the new FSID since you reinstalled the APP and had done a new backup (I am assuming that you did).
    Ed

  15. #15
    Member
    Join Date
    Feb 2009
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    True. After the app was reinstalled the file x was backed up. So why does it appear at all for the point in time restore for the day it didnt exist on the system? Thats the confusing part.

    Thanks for your help.

    DW

  16. #16
    Moderator BBB's Avatar
    Join Date
    Feb 2007
    Location
    Brisbane, Australia
    Posts
    2,075
    Thanks
    0
    Thanked 5 Times in 5 Posts

    Default

    Quote Originally Posted by Noob View Post
    2 versions of the file is kept for 60 days and then if there are no new versions the file file is expired and so we get a little x on the object in the gui.
    Hmm to clarify, they might be kept for up to 60 days. If you back up a new version every day, each version will only be kept for 2 days, because you can only store 2 versions.

  17. #17
    Moderator BBB's Avatar
    Join Date
    Feb 2007
    Location
    Brisbane, Australia
    Posts
    2,075
    Thanks
    0
    Thanked 5 Times in 5 Posts

    Default

    Quote Originally Posted by dxw View Post
    On thursday I look to do a point in time restore to wednesday and I do not see x in the tree.
    I presume you were enabling the display of INACTIVE files in the GUI? By default it won't show you files that have been deleted from the server (and are hence inactive). You need to enable this.

  18. #18
    Member
    Join Date
    Feb 2009
    Posts
    25
    Thanks
    0
    Thanked 0 Times in 0 Posts

    Default

    Nope. The view only active files is selected. I'm starting to think it is a bug with the gui.

    DW

Similar Threads

  1. ANS5280E Object enumeration from a file set or file list failed
    By cfhoffmann in forum Backup / Archive Discussion
    Replies: 10
    Last Post: 08-27-2013, 04:48 AM
  2. System Object Restore
    By m*a*s*h in forum Restore / Recovery Discussion
    Replies: 2
    Last Post: 09-14-2007, 01:45 PM
  3. How to restore System Object
    By Robert_Cody in forum Restore / Recovery Discussion
    Replies: 3
    Last Post: 04-26-2007, 08:49 AM
  4. Replies: 1
    Last Post: 12-28-2006, 02:27 PM
  5. AD Object Restore
    By huntinginvt in forum Restore / Recovery Discussion
    Replies: 0
    Last Post: 03-15-2006, 03:12 PM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •