1. Course title
Tivoli Storage Manager Server, Client, Operation Center, HSM & FB4W
Tricia Jiang
© Copyright IBM Corporation 2013

2. TSM 7.1.1 –New Features GA 9/12/14 Operations Center
Daily Reports – executive summary
Alert Configuration
Client, Admin and Server Maintenance schedule
Storage Pools details
Bookmarks
Services (Policies) Details
SUR Occupancy
Client Management Services
TSM Server
Replication: Scale Enhancements
Replication: Dissimilar Policies
Replication: Repair/recover files for source server from replication target
Compress DB2 backups & archive logs
TSM Client
256-bit AES encryption
Conformance to NIST SP a
Windows 2012 R2 support
Solaris x86 BA client (64-bit)
HSM for Windows
Backup Performance Enhancement
TSM for Space Management
GPFS User Exit Based Failover
UNIX: Enhanced Recall
Fastback for Workstations
Central admin console Websphere Liberty Profile
Graphing in the reporting tables in Central admin console
New block level backup strategy
Help system upgrade
TSM for VE
Provide initial TSM for VE solution for Microsoft Hyper-V
Integrate simplified mount solution for file-level recovery in DP for VMware UI; "Help Desk"
FCM & DP for VMware - integrated vSphere Web Client user interface (Adobe Flex)
TSM for ERP (shipped July 25th)
Performance Enchantements
DB /10.5 support
Support BRTools 7.4
Windows 2012 Support
Solaris 11 support
TDP (Currency)
Windows 2012 R2 - Exchange, SQL, Oracle,
SQL 2014 support
TDP Exchange
Windows 2012 R2 support
Reduced authority for Exchange IMR – Roll Based Access Control support
IMR Usability and Performance enhancements
Exchange config wizard to validate permissions
FCM for Windows:
SQL Server 2014 Support, Windows Server 2012 R2 Support
Exchange – IMR Browser Usability & Performance see WI 3304 above
FCM for VMware:
GUI integrated with vSphere Web Client
Configuration Wizard
NIST SP a compliance
Application consistent FlashCopies from target of a metro/global mirror
One: TSM / 7.1.1
Three: :
Extending Virtualization protection -- More operational and resource efficiency with 70% reduction in help desk processes and up to 95% reduction in backup space requirements for Hyper-V protection.
Simplifying Disaster Recovery -- Building resiliency through efficient replication for higher availability of data
Visualizing and Controlling Data Protection -- Operations Center: Advancing client visibility and control across your data protection environment
Nine: The specifics: Who - What - Wow (the gorp):
Virtualization
VM Administrators can perform even more efficient backups for Microsoft Hyper-V environments with incremental forever and deduplication support and reduce backup space requirements by up to 95%.
Don't worry, be happy. You don't have to backup full Hyper-V VMs all the time now. Backup just the data that's changed...forever. Now you can meet your backup windows and accomplish more with less.
VMware Administrators can now be more operationally efficient for meeting SLAs in supporting file, software/application (dbas), platform (server admins) owners with a 70% reduction in their help desk processes for file level restores
Think about admins supporting 1000s of users and they have to deal with 3-5 file level restores a week (the apparent market average). Probably not all users are doing 3-5 restores a week but even if just 10% required support, that's up to 500 recoveries a week. We just made it easier. Instead of or so manual steps to provide help desk service for file level restore, it's now just a coupla clicks in a wizard and you're done. Easy peasy.
VMware Administrators can easily perform VM data protection recovery operations powered by TSM with a single, familiar web-based interface -- the vSphere web client.
No more launching our plug-in/different administrative tool just to restore a VM. While admins are in their vSphere web-client, they can easily kick off our recovery actions with with a right-click or button-click and be launched into an integrated wizard and can check status in VMware's native views.
Disaster Recovery -- sleep well at night knowing you're reliably protected
Infrastructure admins (backup/VM/storage) now have advanced control of their replication/DR environments through flexible retention policies for source and targets without performing multiple backs of the same data
Don't have space but still want longer data retention? with our replication keep 2 copies for less time at resource-constrained remote site, keep 7 copies for longer of the same data at the DR site that has more resources
Infrastructure admins (backup/VM/storage) can repair volumes on TSM source servers using replicated data with minimal effort to ensure high availability of data for recovery.
Instead of going through a complicated, sometimes lengthy TSM DR scenario to fix damaged volumes, there is now a simple process to kick off an auto-repair using replicas.
Infrastructure admins (backup/VM/storage) can meet backup windows and ensure higher availabilty of more data with up to 3X performance improvement in TSM native replication rates
We made our native replication performance faster.
Visibility and Control --
Infrastructure admins (backup/VM/storage) can see and manage all TSM client schedules across the data protection environment from a single, intuitive interface.
Efficiently manage tens to hundreds to thousands of schedules from one place -- the TSM Operations Center. Reduce headaches and operational inefficiency by doing away with logins to multiple servers and centralize your management processes.
Infrastructure admins (backup/VM/storage) can respond to backup and restore failures more quickly through an intelligent log analytics.
Don't know which log to look at? Don't know what the errors mean? Worse yet, don't know what to do? Take the guesswork out with log analysis through TSM Operations Center's Client Managed Services. Admins now have centralized views of the client log files, clear error/warning descriptions and recommended actions for troubleshooting.
Infrastructure admins (backup/VM/storage) can be conveniently updated on the overall health of their data protection from a single page, executive-level summary report.
TSM OC is great for those who can access the information, look and take action when logged in. But many administrators have to provide operational reports to other consumers and upline managers regarding data protection environment health. summaries allow admins the ability to see what's going on in the environment without having to log in to the interface -- giving them the choice of needing to do some administrative work in OC only if there's a critical issue. They can also use the same report for departments, execs, etc. and can spend less time on preparing reports and more on higher value work.
Then there's all the extras like the blueprints, entry, front-end, partner resell, etc. -- That too is all around simplifying from licensing (entry, front-end) to deployment (blueprints) to access and management (front-safe, servergraph) for data protection.

3. TSM Operation Center - Dashboard or Overview Changes3
TSM Operation Center - Dashboard or Overview Changes
What’s new in 7.11
Multiple videos on what is new
Shows each time OC started
Can Click “Don’t show again”
Usage of DB & Log Space
Polices graphics
Expiration
Task info
Traffic Graphics
The Operations Center dashboard areas of change :
Traffic Graphics
Customizable Traffic view 3

4. TSM Operations Center – Daily Email Report
Daily Reports
Summary: Backup Success, Server & Storage availability, Client Protection
HTML detailed report: Summary, At Risk Clients, TSM Servers, Storage Pools, Storage Devices
Works with most s & browsers
Configurable
Recipient (TSM admin or )
Time of day sent
Executive summary of over health and client coverage

5. TSM Operations Center - Daily Email Report
Daily that summarize the basic health of your TSM environment:
High level summary: Backup success, Server and storage availability, Client protection
Attached detailed report: Summary & Details: At Risk Clients, TSM Servers, Storage Pools, Storage Devices
Requirements:
Setup a SMTP server that allows open mail relay
No authentication, No SSL, OC must have access to
SMTP server address and port
TSM administrator with address associated
update admin {admin_name}
message:
Sent in HTML format
Viewable in clients that support HTML format
Lotus Notes, Outlook, Apple Mail, Gmail and others
Might not be shown correctly in clients that convert HTML to another format
For example, if HTML is converted to Rich Text Format (RTF)
Attached detailed HTML report
Download report and then open the HTML file with web browser
client preview feature not supported
Report will open but because of security features report may not display or function correctly

6. TSM Operations Center – Client Schedules
View all client schedules across servers
Create New Schedules
Edit existing schedules
See client associations
Visualize and Create Client Schedules

7. TSM Operations Center – Create New Client Schedules
Wizard
Different prompts for schedule type and subtype
Followed by client association
Visualize and Create Client Schedules

8. TSM Operations Center – Client Schedules Details
View schedule start window
Visualize start window, duration…
Modify schedule attributes
View and mange client associations to schedules
The number of anticipated clients determines the start window parameters:
minutes
hour
hours
Visualize and Create Client Schedules

9. TSM Operations Center – Maintenance Schedule
View Maintenance activities for servers
Read only
2 week history
“Initiated by” = how task started
Automatic Tasks
Commands
TSM Schedule
External
New “end time” for admin schedules
MAXRUNTIME parameter in DEF SCHE
Server processes still running past this time are cancelled by the server
For TSM Schedules and scripts
BACKUP DB
BACKUP STGPOOL
CHECKIN LIBVOLUME
CHECKOUT LIBVOLUME
COPY ACTIVEDATA
EXPIRE INVENTORY
IDENTIFY DUPLICATES
MIGRATE STGPOOL
MOVE DRMEDIA
MOVE MEDIA
RECLAIM STGPOOL
REPLICATE NODE
RUN
Visualize and Create TSM Maintenance Schedules

10. Maximum Run Time on Client & Administrative Schedules
1010
Maximum Run Time on Client & Administrative Schedules
Description
For client schedules
TSM Admin can specify the max amount of time a schedule runs before getting a warning message
For administrative schedules
TSM Admin can specify the maximum amount of time the schedule can run
If the schedule has reached the maximum time, it will get cancelled
Benefit
Administrator can better control the scheduling of client and administrative tasks
Server Support
MAXRUNTIME is a new parameter added to DEFINE SCHEDULE command
Default is 0: no maximum run time 10

11. TSM Operations Center - Storage Pool
Storage Pool Configuration
Capacity, Next Pool, Start / Stop Migration, Start Reclamation, # of Volumes
2 week storage pool activity History
Activity Graph + daily Backup/Reclaim/Migrate operation completion
Edit storage pool properties
View storage pool volumes
Capacity, Access, Online/Offline or Status, Reclaimable Space capacity
Visibility for Reclaimable Space
All STGpool Table: Reclaimable Volumes added as hidden table
Volumes Level: % Reclaimable Space & Reclaimable Space Capacity
Storage Pool Visibility already available in 7.1.0
All Storage Pools Table
Quick Looks visibility to storage pool properties
Destination storage pools for Services ( Policy Domains)
Backup Storage Pool Action
What’s New in 7.1.1
Storage Pool Configuration
Capacity, Next Pool, Start and Stop Migration, Start Reclamation, Number of Volumes
2 week storage pool activity History
Activity Graph + daily Backup/Reclaim/Migrate operation completion
Edit storage pool properties
View storage pool Volumes
Capacity, Access, Online/Offline or Status, Reclaimable Space capacity and %
Visibility for Reclaimable Space
All Storage Pools Table: Reclaimable Volumes added as hidden table
Based on the current pool setup for reclamation
Volumes Level: % Reclaimable Space and Reclaimable Space Capacity
2 week storagepool history
View and update properties
Volumes assigned to a pool
Next pool (if assigned)
Reclaimable space
Visibility to reclaimable space

12. TSM Operations Center - Services Policy Details
2 week expiration history
Policy Attributes
Retention Settings
Versions settings
Pool destination
Activation
Last Activated
Will display Migration Destination here if set
View when policy domain was activated in the last 2 weeks
servers ONLY
Visual information on Storage Pools

13. TSM Operation Center - Reclaim Storage Pool Action
Ability to manually kick off Reclamation directly from the OC
Underneath the More button in Storage Pools
Volumes number might change as you slide the Start Reclamation threshold
Kick off Reclamation from the OC

14. TSM Operation Center - Migrate Storage Pool Action
Ability to manually kick of migration directly from OC
Underneath More button in Storage Pools
Kick off Migration from the OC

15. TSM Operations Center - Advanced Filtering
Magnifying glass icon opens advanced filter
Build a custom search of one or more search terms
Column Name - Condition - Content
Use “+” “-” buttons to add and remove terms
Use “And” “Or” buttons to switch between joining operators
When an advanced filter is applied
Reset button appears
Basic filter displays “Advanced Filter ON”
Column headers being searched are shown as depressed
Customize items being viewed

16. TSM Operation Center - Global Shared Links
Description: List of shared links that can be used by all OC users
Benefits: Share commonly used links or sorts
OC Specifics:
Admin Authority
System Admin: add, delete, update, view & open links
Non-system admin: viewing and opening links
To control entries, click enabled save button
Add
10 entries in maximum can be added
Delete
Any existing entries can be deleted
Update
Both Name and URL entries can be updated
Opening the links
OC internal links will be opened in the current tab
Others will be opened in a new tab
Dropdown list in banner
Open the existing shared links
OC internal links will be opened in the current tab; others will be opened in a new tab
Launch the shared links tab of global settings dialog

17. TSM Operations Center - Client Management Services
View and understand client problems directly from OC
SW runs on the client machine
Retrieves errors from client’s DSMERROR.log DSMSCHED.log
Visual information on Storage Pools

18. TSM Operations Center - Client Management Services
Benefit
Enables TSM admin to view & understand client problems directly in OC
No need to log into the client machine and manually viewing log files
Client Specifics
Client Management Service (CMS) is software that runs on the client machine itself
Supports TSM Backup-archive client system at version 6 or 7 (not tested on TDPs)
Supports TSM client OS: Windows 32 & 64 bit & Linux 64 bit
In OC, TSM admin needs to have: System, Policy, Client Owner or Client Access authority
Need to make sure firewalls are configured for all initiated connections
Can process up to about 500 MB combined dsmsched.log and dsmerror.log
GUI Install Steps (approx 5 minutes)
Obtain installation package from product DVD or IBM download site
TIV-TSMCMS-Linuxx64.bin
TIV-TSMCMS-Windows32.exe
TIV-TSMCMS-Windows64.exe
Run the install package in a directory; this will extract the installation files.
Run the install.bat (Windows) or install.sh (Linux) to initiate installation
Silent Install Steps (approx 2 minutes after file created & edited)
Copy the install_response_sample.xml to install_response.xml
To change port install_response.xml file line: <variable name='port' value='9028' />
On Linux./install.sh -s input input/install_response.xml -acceptLicense
On Windows install.bat -s input input\install_response.xml -acceptLicense

19. TSM Operation Center - Count of Reclaimable Volumes
1919
TSM Operation Center - Count of Reclaimable Volumes
Description
Estimated count of reclaimable volumes can be retrieved from the server by the Operation Center.
Benefit
OC’s storage pool view shows the number of reclaimable volumes for each sequential type storage pool
Server Support
The count includes volumes that meet the following criteria
Volume has a percent reclaimable value that is equal to or greater than the pool's reclaim threshold
Volume access is READWRITE, READONLY, or OFFSITE
For spoke servers that are unavailable at the time of status monitor collection
The number of reclaimable volumes will not be available and will show zero value for that server
For spoke servers that are downlevel (prior to 711)
The NUM_RCLMVOLS value is blank (null)
The number of reclaimable volumes is an *Estimate*
The reclamation process itself has a lot of different criteria to determine which volumes should be reclaimed. The monitor status collection will not follow all the steps as the reclamation process to determine which volumes are to be reclaimed.  For the TSMGUI_ALLSTG_GRID the number is an estimate to give the user an idea of the count. 19

20. TSM Operation Center – Customizable Logon Screen
2020
TSM Operation Center – Customizable Logon Screen
Customize the TSM OC logon to highlight information important to your users
Custom Login Text
Create or Update <install dir>/ui/Liberty/usr/servers/guiServer/loginText.html
Can add custom login text that will be shown on the login screen
Can add html tags
Normal –vs- Customized 20

21. TSM Operation Center - Automatic Refresh of the GUI Data
2121
TSM Operation Center - Automatic Refresh of the GUI Data
Description
Prior to V7.1.1, the server refreshed data in the GUI table at the status refresh interval (default 5 mins)
Starting with V7.1.1, the server will immediately refresh the data on server tables used by the OC
Benefit
Allows the OC to display more up to date information without waiting for status refresh interval
Server Support
Applied to all status monitor table( TSMGUI_nnnn_GRID tables )
Currently does not apply to Alerts table – it has it’s own update and refresh handling
Does not apply to TSMGUI_STATUS_DATA
Table used by OC “Overview” page
Refresh is still done only at status refresh interval due to constant changing nature of the data
Full refresh of data in all OC related tables ( TSMGUI_xxxx_xxxx) are done at status refresh
No auto refresh if status refresh interval is set to 3 minutes or less
Avoids conflict between the two refresh cycles
There’s minimal delay, for example if a node is added to the schedule in the OC
Update is made on the server; Server pushes the update to the OC; OC table gets refreshed
Status Retention is changed from 48 hours to 24 hours 21

22. TSM Operation Center - Alert Updates
Alerts were introduced in the TSM server
7.1.1 Operations Center
Define new alert trigger on Hub server and on any Spoke servers for which alert trigger is valid
Change category of alert triggers on Hub server and on any Spoke servers on which alert triggers exist
Remove alert triggers from Hub server and from any Spoke servers on which alert triggers exist
Configure alert notifications for administrators
Does not configure hub server and spoke servers for notification
Click Configure to change alert settings for the Hub and any Spoke servers
Can change the category the alert belongs to

23. TSM Server and OC SUR Occupancy
2323
TSM Server and OC SUR Occupancy
Description
TSM server collects the space occupancy of primary storage pools for the purposes of SUR licensing
Keeps a record of the space occupied by primary pool storage pools supports TSM SUR
Suite for Unified Recovery is licensing based on the amount of data being managed
Benefit
Administrators don’t have to run a long SQL statement to get the SUR information
Server Support
Collected once a week
Logged to the Activity Summary table as ACTIVITY=SUR_OCCUPANCY – in TB or PB
QUERY STATUS is updated to display the value and time when it was last collected
SELECT * from STATUS will also display the value and time
Can view in OC’s Server view by adding in the SUR Occupancy and SUR Collected columns
QUERY STATUS output
tsm: FUSION>q status
Storage Management Server for AIX - Version 7, Release 1, Level 1.0
Server Name: FUSION …
SUR Occupancy (TB): 4.56
SUR Occupancy Date/Time: 08/10/ :21:32
SELECT output
tsm: FUSION>select TOTALSUROCC_TB,SUROCC_DATE from status
TOTALSUROCC_TB SUROCC_DATE
E :21:
tsm: FUSION>
SUR Occupancy
QUERY STATUS output
tsm: FUSION>q status
Storage Management Server for AIX - Version 7, Release 1, Level 1.0
Server Name: FUSION …
SUR Occupancy (TB): 4.56
SUR Occupancy Date/Time: 08/10/ :21:32
SELECT output
tsm: FUSION>select TOTALSUROCC_TB,SUROCC_DATE from status
TOTALSUROCC_TB SUROCC_DATE
E :21:
tsm: FUSION> 23

24. TSM Server Scratch Pad Description Benefit Server Support Scratch pad
2424
TSM Server Scratch Pad
Description
New commands allows a user to enter data on a new line in the scratch pad
Scratch pad is a database table that the TSM server hosts
Can use the scratch pad to store diverse information in table format
Benefit
Allows the OC (or other TSM components like clients, or even end users) to store a wide range of data
Currently OC use of scratchpad is not exposed
Using internally to save some settings, filter information and link info
Admins can use it to save some notes to themselves or for their team
Server Support
New commands introduced
DEFINE SCRATCHPADENTRY - create a new line entry in the scratch pad
DELETE SCRATCHPADENTRY – delete an entry from the scratch pad
QUERY SCRATCHPADENTRY – query entries in the scratch pad
UPDATE SCRATCHPADENTRY – update an entry in the scratch pad
SET SCRATCHPADRETENTION – set how long to keep an entry in the scratch pad
Modified command
QUERY STATUS – new output field added to show the scratch pad retention setting
Data input
- can be up to 1000 chars
- use double quotes if data has one or more blanks
- data is case sensitive
Scratch pad
DEFINE SCRATCHPADENTRY
Syntax
DEFine SCRATCHPadentry <major category> <minor category> <subject> Line=<number> Data=<data>
Example
Enter the vacation dates of an administrator, Jane, in a table that stores information about the location of all administrators.
define scratchpadentry admin_info location jane line=2 data="Out of the office from 1-15 Nov."
DELETE SCRATCHPADENTRY
DELete SCRATCHPadentry <major category> <minor category> <subject> Line=< *|number >
Example: Delete all lines of data about the location of an administrator, Jane
Delete scratchpadentry admin_info location jane
QUERY SCRATCHPADENTRY
Query SCRATCHPadentry < * | major category > < * | minor category > < * | subject > Line=< * | number >
Example:
Query all the entries under major category ‘admin_info’ and minor category ‘location’
query scratchpadentry admin_info location
Scratchpad major category: admin_info
Sratchpad minor category: location
Scratchpad subject: jane
Scratchpad line number: 2
Scratchpad data: Out of the office from 1-15 Nov.
Date/time of creation: , 14:30:05
Last Update Date/Time: , 16:55:52
Last Update by (administrator): JANE_W
UPDATE SCRATCHPADENTRY
UPDate SCRATCHPadentry <major category> <minor category> <subject> Line=<number> Data=<data>
Update the vacation contact details of an administrator, Jane
update scratchpadentry admin_info location jane line=2 data=“Out of the office until 18 Nov.“
SET SCRATCHPADRETENTION
SET SCRATCHPADRETention <days>
Retain scratch pad entries for 367 days after last update.
set scratchpadretention 367
QUERY STATUS
QUERY STATUS output is updated to display scratchpad retention 24

25. TSM OC - Visualization of Down Level & Unavailable Servers
2525
TSM OC - Visualization of Down Level & Unavailable Servers
Unavailable server in table of servers
Server status is shown with unavailable icon
Last known data for server is presented, e.g. Used and Free Space for Database
Unavailable server in other tables
Last known data for server is presented, e.g. Capacity and Access
The row of an unavailable server is grayed out & no actions can be performed
7.1.1 adds checks for beta code
Will remember code levels used with a particular database
If any level was pre-release, then ANR4901E issued at startup and on 24-hour loop:
ANR4901E The server database has been used with a pre-release server_version Tivoli Storage Manager server (driver driver_number, build build_id). The server is not supported for commercial or production use.
Only able to detect pre-release use after 7.1.1
New SHOW VERSIONHISTORY command implemented to display version history
>show versionhistory
Date (GMT) Version Pre-release Driver
2013/11/09 23:46:
2013/11/09 23:57:
2013/11/10 00:15:
Included in output for QUERY SYSTEM
Can be issued by any administrator regardless of authority
If non-NULL value in 'Pre-release Driver' column, the server instance is not supported for production use 25

26. TSM Operation Center - Updates to Logging/Tracing
2626
TSM Operation Center - Updates to Logging/Tracing
User can control logging from a panel in the Operations Center
Logs are centralized in same file as Admin API 26

27. TSM Operation Center - Updates to Progress Dialog
2727
TSM Operation Center - Updates to Progress Dialog
Task is in-progress
Progress bar blue
Can Hide and Show details (Details are hidden by default)
Check mark icon next to successful steps
Spinner icon next to in-flight step
Task is still in-progress, but a step has failed
Error icon next to failed steps
Successful completion, summarizes the results of the task
Progress bar green
Succeeded text and icon 27

28. TSM Operation Center - Additional Changes in 7.1.1
2828
TSM Operation Center - Additional Changes in 7.1.1
The Java Level has been upgraded
To: Java(TM) SE Runtime Environment (pwa6470sr6fp _01 (SR6 FP1))
The Liberty Web server has been upgraded
To: WebSphere Application Server (wlp cl )
The Knowledge Center upgraded to Customer Installable 1.5
Fully supported
Supports newer versions of FireFox, Chrome and Internet Explorer
The Operations Center requires the Hub to be a TSM server 
Spoke servers are permitted to be at version through version 7.1.1
Spoke server can not be at a higher version (any part of V.R.L) than the Hub server
Down level Spoke servers are reflected as such in the Operations Center
If a user attempts to use less than a server as the Hub for a Operations Center
Following just an upgrade of the Operations Center, the login will fail with an error indicating the Hub server must be or higher
If the user attempts to Configure the Hub server for the Operations Center, the Configuration login will fail with an error indicating the Hub server must be or higher
Neither the TSM server install nor the Operations Center install prevent the user from upgrading one and not the other
Story – auto refresh 28

29. Activity Summary Record – ACTIVATE POLICYSET
2929
Activity Summary Record – ACTIVATE POLICYSET
Description
New record logged to activity summary table for ACTIVATE POLICYSET command
Benefit
Allows the OC to inform the user of when the active policy set was activated
Server Support
Activity summary record logged when ACTIVATE POLICYSET command completes successfully
Purpose of this record is for use by OC
The following fields of the activity summary record are used
START_TIME/END_TIME   <-- Timestamp of when the policy set was activated. ACTIVITY            <----  for ACTIVATE POLICYSET this will be "POLICYSET ACTIVATION" ENTITY               <----  Name of the domain 29

30. PERFORM LIBACTION – New ACTION Values
3030
PERFORM LIBACTION – New ACTION Values
Description
New action values, RESET and QUIESCE introduced to PERFORM LIBACTION
Update all drive paths and all drives online in a specific library with one command
New DRIVESONLY parameter allowed when ACTION=RESET
Benefit
No need to issue multiple commands against each library’s drive & path to make them all online or offline
In the future this may be utilized by the OC and allow the user to reset their drives and paths
Server Support
Syntax
PERform LIBAction <library name> Action=<DEFine| DELete | RESet | QUIesce DRIVEsonly = <No|Yes>
Action
Reset update all drive paths and drives online
Quiesce update all the drives to offline; drive paths not updated only the drives themselves
DRIVESOnly
This new parm allowed only if ‘Action=RESET’ specified.
Yes vary drives online without updating any paths
No vary drives and paths online
Before this enhancement, the user has to issue UPDATE DRIVE
and UPDATE PATH for each library’s drive and path to make them online or offline. The command allows the Admin to make all of them offline or online in one swoop.
In regards to QUIESCE,
The QUIESCE action will update all drives offline to stop action to the library.  Drives can be updated offline without affecting current I/O to the drive and in that case the offline setting prevents the next operation from using the drive (not preempting any current operation using the drive).  The drive paths will not be updated offline, only the drives themselves. 30

31. Querying DB2 Directly Description Benefit Server Support Syntax
As of 6.1, TSM no longer provides ODBC interface for Admin SQL
Management Applications / Report Engines were told to use DB2 ODBC/JDBC
TSM DB2 Schema is not documented
In particular, there's no way to distinguish between operational and reporting tables
Benefit
Have the ability to identify TSM DB2 Schema
Server Support
SHOW ADMINSQL identifies which DB2 views correspond to tables supported by Admin SQL interface
Publish technote to document usage and to discuss limitations
Syntax
.-Format--=--Standard----
>>-SHOW ADMINSQL ><
'-Format--=--+-Standard-+-'
'-Detailed-‘
>show adminsql
Table Name DB2 Name Cols Staged Query
ACTLOG ACTLOG No
ADMIN_SCHEDULES ADMIN_SCHEDULES 21 Yes QUERY SCHED F=GUI TYPE=ADMIN
ADMINS ADMINS Yes Q ADMIN F=D
AR_COPYGROUPS AR_COPYGROUPS No
ARCHIVES ARCHIVES No
...
>show adminsql f=d
Col# Column Name Type Length Null
0 DATE_TIME TIMESTAMP N
1 MSGNO INTEGER N
2 SEVERITY VARCHAR Y
3 MESSAGE VARCHAR N
4 ORIGINATOR VARCHAR Y
5 NODENAME VARCHAR Y
6 OWNERNAME VARCHAR Y
7 SCHEDNAME VARCHAR Y
8 DOMAINNAME VARCHAR Y
9 SESSID INTEGER Y
10 SERVERNAME VARCHAR Y
11 SESSION INTEGER Y
12 PROCESS INTEGER Y
13 UNIQUE INTEGER N
If it is staged, would have to run TSM admin SQL command to first populate. 31

32. New Maximum Size for Active Logs
Description
TSM increased maximum value allowed for ACTIVELOGSIZE
Increased 4X from to
Not documented or announced
Benefit
In announcing the new limit
Decision was too late for pubs update – 7.2 books will show the new limit
Techdoc will be published to announce the higher maximum
New max allows active logs to grow to 512GB
Server Support
Larger logs can be enabled in even though announcing in 7.1.1
Things to watch out for
Need to provision more space for logs
Larger logs can lead to longer restart times if DB2 crash recovery is required 32

33. TSMDIAG - New Fields Description Benefit Server Support
3333
TSMDIAG - New Fields
Description
New fields for tsmdiag
Benefit
Help expedite & ease the gathering of appropriate doc to help resolve problemes
Server Support
-servername is now required field on UNIX
-dbalias – creates alias
tsmdiag –dbgrowth –id admin –pa xxx –dbalias tsmdb5
-crash – collects core files and runs platform tools
-dbgrowth – runs dedupAudit.pl
-dbalias (NEW) automated version
Takes given input and adds it in DBGROWTH scripts; serverReorgInfo.pl, tsmdiag_servermonv6.pl, tsm_dedup_stats.pl
Alias specified cannot be longer than 8 characters
Anything other than TSMDB1 for a DB name should be specified on the command line
Example. tsmdiag -dbgrowth -id admin -pa xxx -dbalias tsmdb5
-dbgrowth now runs dedupAudit.pl
-crash collects core file and runs platform tools
LINUX, runs getcoreinfo script on the core file
Output file from getcoreinfo, getcoreinfo-shlibs.tar.gz in the results/SERVER dir
AIX, snapcore on core file, output file is snapcore_xxx.pax in results/SERVER dir
WINDOWS, captures .dmp, no output, just gathered and placed in the results\ dir 33

34. TSM 7.1.1 Performance Enhancements – Node Replication’s Reconciliation
Prior to TSM 7.1.1, replication has always done a reconcile
Compares complete list of files between the source and target server
Used to synchronize the source and target servers / Makes target server look just like the source server
Reconcile in TSM Examines entire list of files in a file space (much like pre 7.1.1)
Used during the initial replication between servers
Once reconcile completes, change tracking processing takes over during the next replication
Automatically runs following a database restore on the source or target server
Can run manually using REPLICATE NODE FORCERECONCILE=NO|YES
Synchronize source/targert files - used like an audit
Resynchronize source/target files if the db is regressed (other than DSMSERV RESTORE DB)
Restartable – remembers where it left off if cancelled or after some catastrophic server event
Change Tracking in TSM eliminates need to query target server for its list of files
New and change files are assigned a change identifier: when it’s stored & when meta data is updated
Replication only processes files with a change identifier – incremental replication
Replication picks up where the last replication left off
Improves performance for fs with lots of files
New Replication rule that enables replication based upon Domain
In addition to current replication by Server, Node and Filespace
Prior 7.1 built replicating.tables object table and filled it with objects needing replication
In 7.1 only created list in memory, except for files on tape and files needing retry of failed replicatied files

35. TSM 7.1.1 - Node Replication with Dissimilar Policies
Description:
Decouple target from source server policy, allowing target server to manage replicated files via its own policy
Benefits:
Maintain more or fewer versions of replicated backup files between the source and target replication servers
Retain replicated archive files for more or less time on the target replication server
If fewer versions of files are kept or retained for less time on the target server, the amount of target server storage required can be reduced
Server Support:
Different policy for retention time & number versions can exist on primary & target server
On source server first run VALIDATE REPLPOLICY
Default is to disable dissimilar policies
If disabled, the serves will act as they do today and honor the source server’s policy
On source server SET DISSIMILARPOLICIES server on
Once enabled, target server is notified during the next replication
VEREXIST, VERDELETED, RETEXTRA, RETONLY, RETVER, RETMIN – will impact what is kept
Expiration then runs independently on each server – target server runs expiration
Archive files checked before sent, backup files sent regardlessly
If you delete filespace from the source, you have to manually delete the filespace from the target too.
In 7.1 & before source server policy determined the versions & retention on the target
Dissimilar policy in will:
Allow different versions & retention of files to be maintained on the source & target server
Cause versions & retention of replicated files on the target server to be managed based on its policy
Prevents the source server from sending deletes for expired target server files
Stills sends deletes for files deleted by the client or administrator
Dissimilar policies is enabled from the source server
Default in TSM would disable dissimilar policies
Once enabled, target server is notified during the next replication
Files marked for immediate deletion can not be deleted by expiration until they have been replicated
May be needed by target server based on its policy
Eliminates the ACTIVE_DATA and ACTIVE_DATA_HIGH_PRIORITY replicationrules
All active data rules must be removed or replication will skip the file spaces
Administrators must configure the policy on the target server
Could use EXPORT or Enterprise Configuration
Administrators can no longer prime target server using active only replication
Prior to enabling dissimilar policies
Administrators will need to validate the target servers policy
VALIDATE REPLPOLICY (or something like that)
Attempting to enable dissimilar policies without running VALIDATE
REPLPOLICY will fail
–ACTIVE_DATA and ACTIVE_DATA_HIGH_PRIORITY rules must be removed prior to dissimilar policies being enabled
VALIDATE REPLPOLICY
Checks all nodes and file spaces enabled for replication
Generates a report to indicate the side effects of enabling dissimilar policies
Show difference between source server's policy and target server's policy
Especially important if the target server's policy would retain fewer versions that what was needed
Indicates where any ACTIVE_DATA replication rules are still in effect

36. TSM 7.1.1 - Node Replication with Dissimilar Policies
Backup data: VEREXIST, VERDEL, RETONLY, RETEXTRA control when a backup is deleted
Archive Data: Only RETVER controls the length of time a file is retained for
Space Management Data: Retains the same behavior with or without dissimilar policies enabled
VALIDATE REPLPOLICY <server>
Must be ran prior to enabling dissimilar policies
Displays differences in policy settings for all nodes that exist on both source and target servers
Can be used to validate policy settings are correct, or to debug policy related issues
If no server is specified, defaults to current replication target server
SET DISSIMILARPOLICIES <server> <on|off>
Issued on source server to enable dissimilar policies for a specific target server
Must run VALIDATE REPLPOLICY for the given target server before this can be enabled
QUERY REPLSERVER
New field added to tell you if Dissimilar Policies is enabled for target replication server or not
Rebinding of Files on the Target Replication Server
In <=, files bound to STANDARD on target server if the mgmtclass didn’t exist at the time of replication
With Dissimilar Policies, the mgmtclass that a file is bound to on the target server is now important
During Reconcile Replication, files will be rebound to the correct mgmtclass if it exists on the target server
Done at server level the first time a replication is run after upgrading to 7.1.1
Done at node level when REPLICATE NODE forcereconcile=yes

37. TSM 7.1.1 - Node Replication with Dissimilar Policies
Changes for Expiration
Source server
If dissimilar policies enabled, source server holds onto a file until it has been replicated to the target
Files that have not yet been replicated, must be replicated before they can expire on the source
Files that have been updated ( active → inactive or inactive → expire immediately ) must be replicated (updated) before they can expire
Bypass this requirement temporarily by updating the node or filespace replication rule to NONE
Target Server
All files are now deleted by expiration on the target server
Replication process no longer directly deletes files, instead deferred until expiration processing on the target server
The exceptions are group data and hsm data: These are still deleted during replication processing
If dissimilar Policies is enabled, the targets policy take affect as data is ingested into the server
This is exactly the same way a client backup is handled
As a file comes in, if there is an extra version, it is set to be expired
If dissimilar Policies is not enabled, the data's state is copied from the source serve
If it is active on the source, it will be active on the target
If it is inactive on the source, it will be inactive on the target
When expiration runs, it will delete files as it always has
Files that are expired will be removed whether dissimilar policies is on or off
Dissimilar Policies just dictates how files are set to expired during the ingest of the data
ARCHIVE data that has passed its retention data is only expired on the target if dissimilar policies is enabled 37

38. TSM 7.1.1 - Node Replication with Recovery of Damaged Files
Description: Retrieve files that have been damaged on the source server from replication target server
Benefit: Assist with local recovery of files that have been damaged on the source server
Replaces damaged files with good copies that have been replicated
Includes files on volumes that have been updated as destroyed
Scenario:
Server A replicates data to Server B
Storage pool volume or files on Server A is lost or data is otherwise inaccessible
Storage pool volume or files is restored from Server B to Server A
Server Support:
Must enable: SET replrecoverdamaged on
Additional step in replication process, if source server has damaged files in a file space being replicated
Notifies the target server to resend them at the end of the replication
When source replication ends, the target would start process to resend the damaged files
Damaged files are deleted and replaced with new copies, retaining original insertion date
New parameter on REPLICATE NODE command: RECOVERDAMAGED=YES|NO|ONLY
RECOVERDAMAGED=ONLY will not do replication, it will only recover damaged files
RECOVERDAMAGED=YES|NO|ONLY
YES, include recovery of damaged files as part of this replication
No, do not include recovery of damaged files as part of this replication
Only, only perform the recovery of damaged files during this replication
Recovered files sill maintain original insertion date
TSM knows files are damaged, due to results of audit, or failure to retrieve object. We track these objectes all ready in the db. We would look at this table to get list of damaged files or aggregrate of files

39. TSM 7.1.1 - Node Replication with Recovery of Damaged Files
New column in Replicated_Objects tracks damaged files
Valid values are currently 0 (not damaged) and 1 (damaged on source)
Worker thread periodically re-synchronizes the Damaged column
Thread wakes every 30 mins, only syncs if count of damaged changed
Source server initiates recovery, target server controls
At the end of a replication process, the source server will decide if a recovery is needed
If so, it will build up the recovery command and send it to the target for processing
Target starts modified replication process & corresponding replication recovery process on the source
The source & target will talk, with the target requesting damaged files and the source supplying them
Grouped objects
Requires special consideration, object ID cannot be reused
Groups are repaired with the new object IDs during recovery
Deduplication
Reuses existing replication code to only send needed chunks 39

40. TSM 7.1.1 - Node Replication with Recovery of Damaged Files
Does not seek out damage
Server must encounter damage through data movement (reclamation, client restore, move data, etc.)
Or volume must be marked as destroyed
Deduplication (Largest area of limitation)
When a base chunk becomes damaged, links to it are not automatically made invalid
Example:
Node Bob backs up coolstuff.txt, which is split into 5 base chunks, stored on VOLA.BFS
Node Jason backs up files, which links to all five chunks created by coolstuff.txt, stored on VOLB.BFS
Administrator replicates node Jason, but not Bob
Administrator marks VOLA.BFS as destroyed
Replication recovery will not recover node Jason's damaged files
Solution - run audit VOLB.BFS
Audit Volume marks all damaged files on the volume, if the base chunks are damaged
Client restore marks individual files as damaged, but not all files sharing the same chunks
What if Node Bob was replicated?
No additional action is necessary
Chunks come back, links repaired throughout pool
Relinking limitations
One relink thread for all replication recovery requests
If server crashed/restarted, potential for many outstanding invalid links
Solution, run Audit Volume on all volumes potentially with replaced damaged chunks & run Validate Extents
Update Volume
If server crashes/restarted during an outstanding update, not all bitfiles marked damaged
Solution: Mark volume read-only, then back again to damaged 40

41. TSM 7.1.1 256-bit EAS Backup Archive API encryption
TSM now supports 3 algorithms of encryption
AES-128
DES-56
AES-256 (NEW)
TSM introduced AES-256
Backup-Archive Client , API and DPs that use the API
Use ENCRYPTIONTYPE AES256 in dsm.opt or dsm.sys
Then rebackup already backed up and encrypted items
Data deduplication is not supported with encryption
“query backup” shows encryption being used
Client GUI will have new option
Special Publication a (SP a) is an information security standard of the National Institute of Standards and Technology (NIST). SP a requires longer key lengths and stronger cryptography than other standards.
You can run SP a in two modes: transition and strict. Use the transition mode to move gradually towards a strict enforcement of SP a. The transition mode allows the use of weaker keys and algorithms than strict enforcement allows. The transition mode also allows the use of Transport Layer Security (TLS) v1.0 and v1.1.
A strict enforcement of SP a of the Security Access Manager Base components requires the following configuration: TLS v1.2 protocol for the Secure Sockets Layer (SSL) context
Certificates must have a minimum length of 2048
Elliptical Curve (EC) certificates must have a minimum size of 244-bit curves
Certificates must be signed with a signature algorithm of SHA256, SHA384, or SHA512. Valid signature algorithms include:
SHA256withRSA
SHA384withRSA
SHA512withRSA
SHA256withECDSA
SHA384withECDSA
SHA512withECDSA
SP a approved cipher suites
The Security Access Manager Base component communication uses certificates generated by the policy server. The policy server uses the same key strength and algorithms to create certificates for both the transition and strict versions of the SP a security mode. As a result, you can convert between the transition and strict modes without completely regenerating all Security Access Manager certificates.
The SP a certificates are not compatible with previous releases of Security Access Manager. Previous release Security Access Manager clients cannot communicate with the Security Access Manager 7.0 policy server in SP a mode.
Meet National Standards

42. TSM 7.1.1 and FCM Conformance to NIST SP800-131a
Description: Special Publication a
Information security standard of the National Institute of Standards and Technology (NIST)
Requires longer key lengths and stronger cryptography than other standards
Ability to enforce use of TLS 1.2 or higher when SSL is used
Benefit: Stronger cryptography when using SSL
Server Support:
Product options to require use of TLS 1.2 or higher ( when SSL is in use )
Server / Storage agent option: SSLTLS12
Default is No (specifies that the server uses TLS 1.1 for SSL sessions)
YES (causes the server and storage agent to prefer TLS 1.2 )
Client, server & storage agent check that the session has been setup with protocol TLS 1.2 or higher
They will break the connection if TLS 1.2 or higher is not in use
SSLDISABLELEGACYTLS
Defaults to NO (SSL session processing works as in prior releases, client and server negotiate TLS level)
YES (SSL session setup is terminated if TLS 1.2 or higher is not used)
Overrides the SSLTLS12=NO option
Enforces the rejection of SSL connection attempts that use levels earlier than TLS 1.2
No compliance with certificates for FCM on VMware
Compliance for the CIMOM device adapter with FCM on Unix/Linux
Unencrypted TCP protocols are still allowed .
Certificates must have a minimum length of 2048
Elliptical Curve (EC) certificates must have a minimum size of 244-bit curves
Certificates must be signed with a signature algorithm of SHA256, SHA384, or SHA512
Valid signature algorithms include:
SHA256withRSA
SHA384withRSA
SHA512withRSA
SHA256withECDSA
SHA384withECDSA
SHA512withECDSA
Special Publication a (SP a) is an information security standard of the National Institute of Standards and Technology (NIST). SP a requires longer key lengths and stronger cryptography than other standards.
You can run SP a in two modes: transition and strict. Use the transition mode to move gradually towards a strict enforcement of SP a. The transition mode allows the use of weaker keys and algorithms than strict enforcement allows. The transition mode also allows the use of Transport Layer Security (TLS) v1.0 and v1.1.
A strict enforcement of SP a of the Security Access Manager Base components requires the following configuration: TLS v1.2 protocol for the Secure Sockets Layer (SSL) context
Certificates must be signed with a signature algorithm of SHA256, SHA384, or SHA512. Valid signature algorithms include:
SP a approved cipher suites
The Security Access Manager Base component communication uses certificates generated by the policy server. The policy server uses the same key strength and algorithms to create certificates for both the transition and strict versions of the SP a security mode. As a result, you can convert between the transition and strict modes without completely regenerating all Security Access Manager certificates.
The SP a certificates are not compatible with previous releases of Security Access Manager. Previous release Security Access Manager clients cannot communicate with the Security Access Manager 7.0 policy server in SP a mode.
Meet National Standards

43. TSM Operation Center - Conformance to NIST SP800-131a
Secure browser to OC connection
During Install of OC option for which type of secure connection (or none at all) that the browser will use to connect to OC
Secure OC to TSM Hub Server connection
To use the Secure Sockets Layer (SSL) protocol to secure communications between the Operations Center and the hub server, you must add the SSL certificate of the hub server to the truststore file of the Operations Center. You can use the below URL to configure TSM Server as well as Operations Center.
The default is to use no secure connection.
If you set to SSL, it will try TLS 1.2 first, but if it fails it will try the TLS 1.1 and then TLS 1.1.
If you set TLS12Only, then it will try TLS 1.2, but it will not try the next lowest protocol if it fails.
Off – The connection will not be secure.
Transition – The connection will use TLS 1.0
Strict – The connection will use TLS 1.2 43

44. TSM 7.1.1 Compress Database Backups
Description: Selectively choose which TSM database backups are compressed
Benefits:
TSM deduplication increases size of the TSM database
The space requirements have also increased when backing up the TSM database
DB backup to local media: compression doesn't add much, compression overhead can be too much
DB backup to remote media: reduced amount of data sent compensates for compression’s overhead
Server Support:
What can be configured
Can specify a "compress" parameter on the BACKUP DB and SET DBRECOVERY commands
SET DBRECOVERY sets the compress defaults for the BACKUP DB command
Impact of configuration decisions
Processor usage and duration increased
Increases varied based on database size, and hardware configuration
Database backup compression decreases the size of the backed up database files
Backup file sizes: For a brand new database “sample” (backed up and compressed shortly after DSMS
CPU usage: Testing showed “non-compression” CPU usage of approximately 10% during database backup, while “database compression” CPU usage ranged from 20% to 90% during database backup.
Backup duration: In general, backup duration increased when database compression was enabled. For smaller databases (sample sizes of 9,330 MB and 26,528 MB), the backup duration sometimes increased and sometimes decreased. In these cases, the duration differed by only a couple of minutes. However, for larger databases (sample sizes of 1,356,706 MB and 1,573,978 MB), the backup duration was much more apparent and increased by approximately 400% (sample durations went from about 1 hour to just over 4 hrs for the first database, and increased from approximately 1.5 hours to nearly 6 hours 50 minutes for the second database).

45. TSM 7.1.1 Compress Archive Logs
4545
TSM Compress Archive Logs
Description:
Compress DB2 archive logs
DB2 10 introduced the ability to compress log files as they are archived
In TSM 7.1.1
Default to compress archive log is set to “NO”
Known DB2 active log problem that occurs when the DB2 archive log compression flag is set to YES
Only seen the DB2 active log problem on our large appliance CET test systems when they are under sustained high volume usage and heavy workloads
Benefits:
Consume less space and reduce the time required to back up the archive logs
Potentially reduces the frequency of back ups that are initiated just to clear the archive logs
Server Support:
Default ARCHLOGCOMPress value is No (do not compress archive logs)
ARCHLOGCOMPress option set in the dsmserv.opt file and by the SETOPT command
dsmserv.opt: server must be started or restarted for the option to take effect
SETOPT command: can be used when the server is up and running
Updates the server option immediately and appends the option and value to the dsmserv.opt file
Current setting of the server option displayed with:
Q LOG F=D
Q OPT
Q OPT ARCHLOGCOMPress 45

46. TSM 7.1.1 Solaris x86 native 64-bit B/A Client
Solaris x86 (32-bit) package was last updated in TSM V6.2
Solaris x86 continues to be a popular customer request
7.1.1 updates the Solaris x86 build to the most current Backup-Archive client version
64-bit native package will be updated as well
Solaris 10 and 11 supported
Currency

47. TSM for Space Management 7.1.1
TSM GPFS User Exit based HSM FAILOVER
Replaces legacy HSM failover method
HSM uses GPFS user exit callback function to register for failover modes
HSM uses GPFS user exit callback function to identify a cluster node as HSM node
Simple functionality to improve servicability
New failover modes to improve usability (Enabled, TakeOver, HandOver, Disabled)
The scout daemon (if used) stores the port number in file /etc/adsm/SpaceMan/config/DSMSCOUTPort
Enhanced Recall provides more granular recall
dsmmigfs, dsmmigrate, dsmattr commands enhaced with more granularity for recalls
PREVIEWSIZE option added to prevent file explorer preview icons from causing recall
PRE TSM HSM FAILOVER
Propritary node to node communication to identify node and HSM service failures (Responsivness service, soap based)
Usage of legacy GPFS function to register and unregister HSM nodes for failover function (mmdsm)
Local copy of DSMNodeset on all HSM nodes to identify failover partner nodes in the cluster
The scout daemon (if used) stores the port number inside DSMNodeSet
File system wide settings (new with WI 3060)
The dsmmigfs command allows the specification of the option readstartsrecall (RSR). Once it was set to yes RSR is enabled for all subsequent migrations.
The dsmmigfs command was enhanced with the option previewsize (PS). The PS must be less or equal to the stub size enabled for the file system. A value greater than stubsize won't be accepted. Once PS was set to a value it is enabled for all subsequent migrations. A new argument was introduced for this (previewsize=( ))
File specific settings (new with WI 3060)
The dsmattr command was enhanced to read and update the IBMObj attribute.
The dsmattr command was enhanced to read and list the settings for RSR and PS for a migrated file.
The dsmattr command was enhanced to update the settings for RSR and PS for a migrated file.
The dsmmigrate command was enhanced to set the values for RSR and PS while the file is migrated. New arguments were introduced for this (-previewsize=( |undef) -readstartsrecall=[yes|no] -STubsize=( ))
Hierarchy
dsmmigfs : apply setting for all subsequent migrations
dsmmigrate : apply setting for current migration
dsmattr : apply settings for migrated files
HSM for Windows is a fix pack:
FIX PACK
IC97262 HSM FOR WINDOWS DOES NOT WORK WITH CHINESE INSTALLATION OF TSM BACKUP/ARCHIVE CLIENT
IC97770 HSM FOR WINDOWS RECALL SERVICE DOES NOT WORK FOR SOME STUB FILES
IC99948 BACKUP/ARCHIVE CLIENT ERRONEOUSLY PRINTS HSM ERROR MESSAGE
IT00799 HSM FOR WINDOWS CLIENT DOES NOT ASSIGN MANAGEMENT CLASS AS DOCUMENTED.
IT00822 HSM FOR WINDOWS RECALL AND MOVE OF OLD STUB FILES MAY FAIL
IT02715 HSM FOR WINDOWS RE-MIGRATION OF STUB RESTORES FILE CONTENT IF IN STATE 'DELETION' ON TSM SERVER
IT03497 HSM FOR WINDOWS DOES NOT MIGRATE THE FIRST FILE OF A MIGRATION LIST FILE

48. FastBack For Workstations 7.1.1 – Admin Console
Moving central admin console from TIP to Websphere Liberty Profile
User interface basically unchanged
Smaller package, around 80% smaller
Install in 10 minutes instead of an hour
Provides greater flexibility for future releases
Adding graphing to the reporting tables in Central admin console
Easier to understand data
Every report will have a button to display a graph of the data
When more than 50 rows are present, sliders appear on the graph for better usability
Support for Windows Servers 2012 and 2012 R2

49. FastBack For Workstations 7.1.1 – Client
New block level backup strategy
Results in fewer full backups, since block level is used mostly for very large files, like
New block level will be fully backward compatible with no changes to the configuration
Help system will be upgraded and a link to the IBM Knowledge Center will be added
Product integrated help for the client is now created by using Eclipse tools
Runs on all modern browsers
Encryption has been strengthened to 256 bit
Files backed up with native file encryption may use 256 bit encryption
Set option by running command from install directory: fpa config-set Encryption Type=2
Support for Windows 8.1 and 2012 R2

50. Enablement Resources
Youtube short demos:
Tivoli Storage Manager Operation Center scheduling:
Tivoli Storage Manager Operation Center storage pool and policies:
Tivoli Storage Manager Operation Center Client Management Services:
Tivoli Storage Manager Operation Center Advanced Filtering:
Tivoli Storage Manager Operation Center Executive
Tivoli Storage Manager Node Replication dissimilar polices and damaged file recovery:
Tivoli Storage Manager for VE Data Protection for Hyper-V - Protecting Hyper-V Virtual Machines
Tivoli Storage Manager for VE Data Protection for Hyper-V - Individual File Restore

51. Thank You 51 51