Upload
phungthu
View
233
Download
0
Embed Size (px)
NEUIGKEITEN ZUM THEMA
DATENSICHERUNG
Stefan Savoric
Senior Systemingenieur
Diplom-Geophysiker
TSM 7.1.1 –NEW FEATURES 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 VMware UI; "Help Desk"
FCM & DP for VMware - integrated vSphere Web Client user interface (Adobe Flex)
TSM for ERP 6.4.2 (shipped July 25th)
Performance Enchantements
DB2 10.1 /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 800-131a compliance
Application consistent FlashCopies from target of a metro/global mirror
TSM Front-End Licensing
Operations Center
Daily Email 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 SP800-131a
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 7.1.1 PERFORMANCE ENHANCEMENTS – NODE REPLICATION’S
RECONCILIATION
3
● Prior to TSM 7.1.1, replication has always done a reconcile (Abgleich)
– Compares complete list of files between the source and target server
– Used to synchronize the source and target servers
● Reconcile in TSM 7.1.1- Examines entire list of files in a file space (much like pre 7.1.1)
– Used during the initial replication between 7.1.1 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/target 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
TSM 7.1.1 PERFORMANCE ENHANCEMENTS – NODE REPLICATION’S
RECONCILIATION
4
● 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 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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
5
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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
6
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
7
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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
8
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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
9
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 7.1.0 <=, 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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
10
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
TSM 7.1.1 - NODE REPLICATION WITH DISSIMILAR POLICIES
11
Changes for Expiration
• 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
TSM 7.1.1 - NODE REPLICATION WITH RECOVERY OF DAMAGED FILES
12
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
TSM 7.1.1 - NODE REPLICATION WITH RECOVERY OF DAMAGED FILES
Scenario:1) Server A replicates data to Server B2) Storage pool volume or files on Server A is lost or data is otherwise inaccessible3) 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
TSM 7.1.1 - NODE REPLICATION WITH RECOVERY OF DAMAGED FILES
14
• 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
15
New Maximum Size for Active Logs
Description
TSM 7.1.0 increased maximum value allowed for ACTIVELOGSIZE
• Increased 4X from 131072 to 524288
• Not documented or announced
Benefit
In 7.1.1 announcing the new limit
• Decision was too late for pubs update – 7.2 books will show the new limit
• 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
16
TSM 7.1.1 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
17
TSM 7.1.1 COMPRESS ARCHIVE LOGS
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
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
TSM 7.1.1 Compress Database Backups
Backup file sizes: For a brand new database “sample” (backed up and compressed)
TSM 7.1.1 Compress Database Backups
TSM 7.1.1 256-BIT EAS BACKUP ARCHIVE API ENCRYPTION
20
● TSM now supports 3 algorithms of encryption
– AES-128
– DES-56
– AES-256 (NEW)
● TSM 7.1.1 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
21
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 SupportSyntax
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
22
ACTIVITY SUMMARY RECORD – ACTIVATE POLICYSET
•New record logged to activity summary table for ACTIVATE POLICYSET command
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
23
Querying DB2 Directly
Description• 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
Syntax.-Format--=--Standard----
>>-SHOW ADMINSQL---+--------------------+---><
'-Format--=--+-Standard-+-'
'-Detailed-‘
>show adminsql
Table Name DB2 Name Cols Staged Query
--------------- --------------- ---- ------ ---------------------
ACTLOG ACTLOG 14 No
ADMIN_SCHEDULES ADMIN_SCHEDULES 21 Yes QUERY SCHED F=GUI
TYPE=ADMIN
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 Cols Staged Query
--------------- --------------- ---- ------ ---------------------
ACTLOG ACTLOG 14 No
Col# Column Name Type Length Null
---- ------------------------------ ---------- ------ ----
0 DATE_TIME TIMESTAMP 10 N
1 MSGNO INTEGER 4 N
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
7 SCHEDNAME VARCHAR 31 Y
8 DOMAINNAME VARCHAR 31 Y
9 SESSID INTEGER 4 Y
10 SERVERNAME VARCHAR 65 Y
TSM 7.1.1 SOLARIS X86 NATIVE 64-BIT B/A CLIENT
24
● 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
TSM FOR VIRTUAL ENVIRONMENT
TSM for VE:
- Expand single-pass hypervisor support to include Hyper-V with
incremental forever backup, restore of full virtual machines
and individual files from image backup, and auto discovery of VMs
- Simplified individual file level recovery for VMware including fully automated
VM mount to enable help desk file level recovery models
- New GUI (TSMVMWARE UI) integrated with vSphere Web Client to enable
VMware administrators to use the same UI for VMware management and data
protection, as well as role-based access control to limit access by Data Center
TSM 7.1.1 –NEW FEATURES GA 9/12/14
27
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 6.4.2 (shipped July 25th)
Performance Enchantements
DB2 10.1 /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 800-131a compliance
Application consistent FlashCopies from target of a metro/global mirror
TSM Front-End licensing
Operations Center
Daily Email 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 SP800-131a
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
3592 GENERATION 5 – TS115010 TB GB Kapazität (JD) -> + 150%
Media Re-Use mit JC 4 TB -> 7 TB -> + 75%
360 MB/sec native Datenrate -> + 44%
Dual-active 8 Gbit FC Bis zu 700 MB/sec Durchsatz
2 GB Datenbuffer
Verbesserte „Virtual Backhitch“
Verbesserte Read-ahead
Speedmatching mit 14 Geschwindigkeiten
Verbesserte Kompression +25%
Sehr schneller Datenzugriff durch
Schnellere Locate-Geschwindigkeit
Schnellerer Ladezeit Verbesserte High Resolution Tape
Directory
Upgrademöglichkeit von TS1140 auf TS1150!
Schnellstes Tapedrive im Markt!
NEUES DRIVE 3592 (JAGUAR) GENERATION 5
Any statements regarding IBM's future direction and intent are subject to change or withdrawal without notice, and represent goals and objectives only.
LTO
Generations
LTO-3 LTO-4 LTO-5 LTO-6* LTO-7 LTO-8 LTO-9 LTO-10
Max Native
Capacity
400 GB (L3) 800 GB
(L4)
1.5 TB
(L5)2.5 TB (L6) Up to 6.4
TB (L7)
Up to
12.8 TB
(L8)
Up to 25
TB (L9)
Up to 48
TB (L10)
Other Native
Capacities
200 GB L2100 GB L1 R/O
400 GB
L3200 GB L2 R/O
800 GB
L4400 GB L3 R/O
1.5 TB L5800 GB L4 R/O
2.5 TB L61.5 TB L5
R/O
6.4 TB L72.5 TB L6
R/O
2.5 TB L61.5 TB L5 R/O
6.4 TB L72.5 TB L6 R/O
Native Data
Rate
80 MB/s 120 MB/s 140 MB/s 160 MB/s Up to 315
MB/s
Up to 472
MB/s
Up to 708
MB/s
Up to 1100
MB/s
* Data Compression engine enhancement from 2:1 to 2.5:1
TS1100
Generations
Gen-1
3592 J1A
Gen-2
TS1120
Gen-3
TS1130
Gen-4
TS1140
Gen-5 Gen-6
Max Native
Capacity
300 GB (JA) 700 GB (JB) 1.0 TB (JB) 4.0 TB (JC) 10 TB
(JD)
15-20 TB
(JD)
Other Native
Capacities with
Media Reuse
500 GB JA 640 GB JA 1.6 TB JB640 GB JA R/O
7 TB JC 7 TB JC
Native Data Rate 40 MB/s 100 MB/s 160 MB/s 250 MB/s Up to 360
MB/s
Up to 540 MB/s
IBM Tape Drive Roadmaps
2003
20052007 2009 2012
2006 2008 2011 2014
IBM TAPE DRIVE ROADMAPS
NOCH FRAGEN??
VIELEN DANK FÜR IHRE
AUFMERKSAMKEIT
Stefan Savoric
Senior Systemingenieur
Diplom-Geophysiker