Skip to Main Content
IBM System Storage Ideas Portal


This portal is to open public enhancement requests against IBM System Storage products. To view all of your ideas submitted to IBM, create and manage groups of Ideas, or create an idea explicitly set to be either visible by all (public) or visible only to you and IBM (private), use the IBM Unified Ideas Portal (https://ideas.ibm.com).


Shape the future of IBM!

We invite you to shape the future of IBM, including product roadmaps, by submitting ideas that matter to you the most. Here's how it works:

Search existing ideas

Start by searching and reviewing ideas and requests to enhance a product or service. Take a look at ideas others have posted, and add a comment, vote, or subscribe to updates on them if they matter to you. If you can't find what you are looking for,

Post your ideas
  1. Post an idea.

  2. Get feedback from the IBM team and other customers to refine your idea.

  3. Follow the idea through the IBM Ideas process.


Specific links you will want to bookmark for future use

Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.

IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.

ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Not under consideration
Created by Guest
Created on Jul 15, 2011

On W2008R2 TSM doesn't provide same functionality as Microsoft WBAdmin utility to restore specific file from Systemstate BCK.

When using TSM V6.2 on W2008R2, *.exe files are backup as part of System State Backup.
With TSM V6.2, it is not possible to perfrom RESTORE of specif file/s from the System State Backup.
Using Microsoft utility WBAdmin to perform the Backup, it is possible to perfrom RESTORE of selective file.
With TSM V6.2, we can only RESTORE the whole SYSTEM State backup only. Selective RESTORE is not possible.

I approached Microsoft Support to investigate the problem we are experiencing with BACKUP & RESTORE of EXE files.
Here are the findings of the testing that were conducted.

1. The "*.exe" files is part of the SYSTEM STATE Backup.
2. Using TSM, the "*.exe" files is part of the SYSTEM STATE Backup.
3. Using TSM, the "*.exe" files cannot be Backup or Restore from a FILE or FOLDER Backup.
4. Using TSM, the "*.exe" files cannot be RESTORE selectively from the System State Backup.
5. Using MS WBAdmin, the "*.exe" files is part of the SYSTEM STATE Backup.
6. Using MS WBAdmin, the "*.exe" files can be Backup or Restore from a FILE or FOLDER Backup.
7. Using MS WBAdmin, the "*.exe" files can be RESTORE selectively from the System State Backup.

As the functionality is available at an OS level using MS WbAdmin, we require the same functionality with TSM.
It is not possible to implement a VMWARE solution for RESTORE, as per your recommendation.

We require the same functionality that Microsoft have already tested for us using MS WBAdmin, in TSM.

Idea priority High
  • Guest
    Reply
    |
    Jun 12, 2015

    Due to processing by IBM, this request was reassigned to have the following updated attributes:
    Brand - Servers and Systems Software
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

    For recording keeping, the previous attributes were:
    Brand - Tivoli
    Product family - Storage
    Product - Tivoli Storage Manager (TSM) Family

  • Guest
    Reply
    |
    Aug 10, 2011

    Thank you for submitting this enhancement request, unfortunately, we currently do not plan to implement this enhancement request, there are multiple reasons for this decision and i'll try to describe some of the major points
    - Microsoft's MSDN site gives a brief outline of backing up and restoring system state here:
    http://msdn.microsoft.com/en-us/library/bb968830%28v=VS.85%29.aspx
    The pertinent text is: the Windows system state is defined as being a collection of several key operating system elements and their files. These elements should always be treated as a unit by backup and restore operations.

    So Microsoft did not intend that system state be restorable on an individual file basis, doing so (Restoring individual files from a system state backup) may result in unexpected behavior of the OS

    - Users can do something like this from the TSM client command line interface (dsmc) prompt: by restoring the system state to a separate location and use Microsoft tools to extract the file

    restore "{MACHINE_NAME\SystemState\NULL\System State\SystemState}\*" X:\targetrestoredir\ -pick -subdir=yes
    once you have the target directory restored you can use the WBAdmin to extract individual files from it
    (http://technet.microsoft.com/en-us/library/cc742070(WS.10).aspx), however, if you intend to use this method to restore or repair an OS, it would be outside the boundaries of our support, the supported way to restore or repair an OS is by restoring the system state in its entirety.

    - I would appreciate if you can clarify further what is it that you're trying to achieve (from a business perspective), what's the problem that you're trying to solve?