Professional Documents
Culture Documents
1
Server, Client, Operation Center, HSM & FB4W
Tricia Jiang
GA 9/12/14
TSM for VE
Provide initial TSM for VE solution for Microsoft Hyper-V
Integrate simplified mount solution for file-level recovery in DP for VMwar
UI; "Help Desk"
FCM & DP for VMware - integrated vSphere Web Client user interface
(Adobe Flex)
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 800-131a compliance
Application consistent FlashCopies from target of a metro/global mirror
Polices graphics
Expiration
Traffic Graphics
Customizable Traffic view
Usage of
DB & Log
Space
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 email address associated
update admin {admin_name} emailaddress={userid@domain}
Email message:
Sent in HTML format
Viewable in email clients that support HTML format
Lotus Notes, Outlook, Apple Mail, Gmail and others
Might not be shown correctly in email clients that convert HTML to another format
For example, if HTML email is converted to Rich Text Format (RTF)
Attached detailed HTML report
Download report and then open the HTML file with web browser
Email client preview feature not supported
Report will open but because of security features report may not display or function correctly
Wizard
Different prompts for schedule type
and subtype
Followed by client association
Benefit
Administrator can better control the scheduling of client and administrative tasks
Server Support
10
11
Last Activated
Will display
Migration
Destination
here if set
14
16
17
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
Silent Install Steps (approx 2 minutes after file created & edited)
18
Description
Estimated count of reclaimable volumes can be retrieved from the server by the Operation Center.
Benefit
OCs 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)
19
Can add custom login text that will be shown on the login screen
20
Benefit
Allows the OC to display more up to date information without waiting for status refresh interval
Server Support
21
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 email notifications for administrators
Does not configure hub server and spoke servers for email notification
Click Configure to
change alert settings for
the Hub and any Spoke
servers
22
Benefit
Administrators dont 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 OCs 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
SELECT output
tsm: FUSION>select TOTALSUROCC_TB,SUROCC_DATE from status
TOTALSUROCC_TB
----------------------4.56000000000000E+000
23
tsm: FUSION>
SUROCC_DATE
--------------------------2014-08-10 14:21:32.000000
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
24
versionhistory
Date (GMT)
-------------------2013/11/09 23:46:08
2013/11/09 23:57:31
2013/11/10 00:15:56
Version
-------------------7.1.1.0
7.2.0.0
7.2.0.0
Pre-release Driver
-------------------0300
25
26
27
28
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
Benefit
No need to issue multiple commands against each librarys 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
30
Benefit
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
>show adminsql
Table Name
Syntax
.-Format--=--Standard--->>-SHOW ADMINSQL---+--------------------+---><
'-Format--=--+-Standard-+-'
'-Detailed-
DB2 Name
ACTLOG
14 No
ADMIN_SCHEDULES ADMIN_SCHEDULES
21 Yes
ADMINS
ADMINS
20 Yes
Q ADMIN F=D
AR_COPYGROUPS
AR_COPYGROUPS
12 No
ARCHIVES
ARCHIVES
11 No
...
>show adminsql f=d
Table Name
DB2 Name
ACTLOG
14 No
Type
Length Null
31
0 DATE_TIME
TIMESTAMP
10 N
1 MSGNO
INTEGER
2 SEVERITY
VARCHAR
1 Y
3 MESSAGE
VARCHAR
2001 N
4 ORIGINATOR
VARCHAR
6 Y
5 NODENAME
VARCHAR
65 Y
6 OWNERNAME
VARCHAR
65 Y
4 N
Benefit
In 7.1.1 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 7.1.0 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
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
https://publib.boulder.ibm.com/tividd/td/TSMM/SC32-9103-01/en_US/HTML/tsmdiag.html
33
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 7.1.1- Examines entire list of files in a file space (much like pre 7.1.1)
Once reconcile completes, change tracking processing takes over during the next replication
Change Tracking in TSM 7.1.1 eliminates need to query target server for its list of files
New and change files are assigned a change identifier: when its stored & when meta data is updated
34
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
35
If disabled, the serves will act as they do today and honor the source servers policy
On source server SET DISSIMILARPOLICIES server on
VEREXIST, VERDELETED, RETEXTRA, RETONLY, RETVER, RETMIN will impact what is kept
Expiration then runs independently on each server target server runs expiration
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>
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
QUERY REPLSERVER
New field added to tell you if Dissimilar Policies is enabled for target replication server or not
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
36
Done at server level the first time a replication is run after upgrading to 7.1.1
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
37
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
If dissimilar Policies is not enabled, the data's state is copied from the source serve
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
Replaces damaged files with good copies that have been replicated
Includes files on volumes that have been updated as destroyed
Scenario:
1)
2)
3)
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
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
Groups are repaired with the new object IDs during recovery
Deduplication
39
Server must encounter damage through data movement (reclamation, client restore, move data, etc.)
Or volume must be marked as destroyed
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
Update Volume
40
If server crashes/restarted during an outstanding update, not all bitfiles marked damaged
Solution: Mark volume read-only, then back again to damaged
AES-128
DES-56
AES-256 (NEW)
41
Information security standard of the National Institute of Standards and Technology (NIST)
Requires longer key lengths and stronger cryptography than other standards
Benefit:
Server Support:
Product options to require use of TLS 1.2 or higher ( when SSL is in use )
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
42
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)
Enforces the rejection of SSL connection attempts that use levels earlier than TLS 1.2
During Install of OC 7.1.1 option for which type of secure connection (or none at
all) that the browser will use to connect to OC
43
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
DB2 10 introduced the ability to compress log files as they are archived
In TSM 7.1.1
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:
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
45
7.1.1 updates the Solaris x86 build to the most current Backup-Archive client version
46
Currency
47
When more than 50 rows are present, sliders appear on the graph for better usability
48
Results in fewer full backups, since block level is used mostly for very large files, like email
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
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
49
Enablement Resources
Youtube short demos: http://www.youtube.com/watch?v=el_se-m8QoI&list=PL1c3vkFzmhec0xvPtplZD_yNpaPNfRHh0
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 Email:
Tivoli Storage Manager Node Replication dissimilar polices and damaged file recovery:
Tivoli Storage Manager for VE 7.1.1 - Data Protection for Hyper-V - Protecting Hyper-V Virtual
Machines
Tivoli Storage Manager for VE 7.1.1 - Data Protection for Hyper-V - Individual File Restore
50
Thank You
51