Presentasi TSM New

IBM TIVOLI STORAGE MANAGER

SELLING STORAGE SMARTER

FEATURES

Backup and recoveryArchiving and retrievalOnline database and application protectionData reductionBare-machine recoverySpace managementBuilt-in reporting and monitoring


IBM DB2Write - to Log and DBsRead - from either DBRecovery Log & MirrorsDatabase & MirrorsCATALOGS TSM database tracks every file Mirrored "two-phase commit" dynamically expand or contract "point-in-time" recovery of TSM DBBe secure that even IF something happens to TSM, it can be recovered quickly and easily


POLICY MANAGEMENT*Domain 2TSM ServerDomain 1PoliciesA set of rules that definesWhat data to protectWhere to store the dataHow long to keep it

BenefitsFlexible policies meet business needs Policies can change as needs changeChanges retroactively applied to existing data


BACKUP / RESTOREBenefitsAutomatically recover files or fs quicklyAutomated off-site copy creationSet policies to optimize backup granularityStore backups in tiered storageSingle point of controlData ProtectionProgressive incrementalAdaptive subfile differencingVolume levelMultiple versions keptPolicy managedSystem assisted restoreAutomated scheduling


LONG-TERM DATA ARCHIVAL AND RETRIEVALLong Term RetentionLong-term storagePoint in time copyRetention periodBenefitsSpeed file-server recoveryRecover only active dataReduce backup times & resource usage Focus on active files onlyExpedite locating historical information Index archives with descriptive metadata


TIVOLI STORAGE FOR SPACE MANAGEMENTTIVOLI STORAGE HSM FOR WINDOWShttp://www.ibm.com/software/tivoli/products/storage-mgr-space/Lifecycle ManagementMigrates inactive dataTransparent recallPolicy managedIntegrated with backupBenefitsImprove response times of file servers by off-loading inactive dataMove low-activity or inactive files to a hierarchy of lower-cost storageUse existing storage assets more efficientlyReduce backup times and resource usage by focusing on active files onlyEliminate manual file system clean-up activities


TRADITIONAL LAN ARCHITECTURETSM ClientTSM ClientTSM ClientTCP/IP LANTSMDBStgpoolTSM SrvAll traffic via LANData & Meta DataData sent To storageMeta DataUpdates TSMdatabase


LAN-FREE DATA TRANSFER ARCHITECTURETCP/IP LANTSMDBStgpoolTSM SrvMeta-data pathMeta-dataUpdates TSMdatabaseTSM ClientStorage agentTSM ClientStorage agentTSM ClientStorage agentData path


SERVER-FREE DATA MOVEMENTTCP/IP LANTSMDBStgpoolTSM SrvMeta-data pathMeta-dataUpdates TSMdatabaseTSM ClientTSM ClientTSM ClientData pathData Mover


PROGRESSIVE BACKUP METHODOLOGYSave time and moneyONLY new or changed files backed upNO redundant backupsRestores dont require the same file to be restored multiple timesNO wasteful weekly full backups and their dependent incremental/differentialData tracked at file level


Deduplication-Enabled Disk Storage PoolFile 1File 2File 3AABBACCCDEFile 1File 2File 31. Data sent from clients to server and stored in primary storage pool2. Identify Duplicates process creates chunks and pointers to hash index in server database to relate files to chunks3. Backup Stgpool operation copies data to non-deduplicated copy storage pool4. Duplicate data chunks removed from primary storage pool during Reclaim operationCopy Storage Pool(non-deduplicated)hashIndexFile 3TSM Server Side Data Deduplication TSM v6.2 Whats New


TSM clients deduplicate file dataBenefits:

Deduplication for file dataReduce network traffic by deduplicating data before transferReduced storage pool space requirementsFaster backupsOptimized to reduce network chattiness when identifying duplicate dataNew Backup-Archive Client statistics report on deduplication and data reduction savingsConserves BandwidthDuplicate files or portions of a file are not moved over the networkConserves bandwidth used during backup operationsSaves Storage Only unique files or portions of a file are stored on diskIndexes are used to act as pointers to the original fileLAN / WANTSM CLIENT DEDUPLICATIONTSM v6.2 Whats New


Copy Storage Pool(non-deduplicated)File 1ABCDEFile 1File 2File 3File 4BEFFFile 41. Client creates chunks2. Client and server identify which chunks need to be sent3. Client sends chunks and hashes to server so that it can represent object in database4. Entire file is reconstructed during Backup Stgpool operation to non-deduplicated stg. poolhashIndexFile 4TSM 6.x clientDeduplication-Enabled Disk Storage PoolTSM ClientTSM ClientTSM Client Side Data DeduplicationTSM v6.2 Whats New


*IBM TIVOLI STORAGE MANAGER INTERFACEWANTSM Server Storage HierarchyWANLANSANTSM ClientOne tool, One interface, Total ControlTSM InterfacesAdministration CenterGUICommand lineAPISQL

BenefitsOne tool., One interfaceTSM reachable from most anywhereNo additional charge


ADMINISTRATIVE USER INTERFACE*FeaturesStorage Manager Central ConsoleSingle task orientated interfaceAdminister multiple servers & clientsAdministrative functionsAll administrative functionsWizards simplify tasksDaily server maintenance script Health monitorStatus of the server selectedStatus of storage devicesSuccessful & unsuccessful schedulesActivity log using searches Calendar base schedules for client & admin tasksBenefitsSimplify and expedite administrators jobNo additional charge


OUT OF THE BOX HISTORICAL REPORTING - SERVER*Server ReportsServer Job statusServer ThroughputServer Resource UsageDatabase DetailsDisk & File UsageTape UsageOther Storage UsageTape Volume Usage AnalysisTape Capacity AnalysisTape Device ErrorsDevice Usage HistoryServer Machine Utilization


OUT OF THE BOX HISTORICAL REPORTING - CLIENT*Client ReportsClient Job statusClient Backup CurrencyStorage Capacity ProjectionBackup DetailsTop 10 BackupsBackup Missed filesBackup HistoryRestore DetailsTop 10 RestoresRestore HistoryArchive detailsTop 10 ArchivesArchive HistoryRetrieve DetailsTop 10 RetrievesRetrieve History


API* Application Program Interface (API)DBTSM Client and APITSM ServerTSM API Allows for third party programs to send their data to the TSM server and storage poolsAPI packaged, developed and supported as part of the backup/archive client API documentationhttp://www.tivoli.com/support/public/Prodman/public_manuals/td/TSMC/GC32-0793-00/en_US/HTML/ansatfrm.htmBenefitsAllows for 3rd party programs to send their data to TSM serverAllows you to further the functionality of TSMNo additional charge


*ENCRYPTIONTSM ClientEncryption of data Last step before client and API data sent to TSM server AES 128-bit & Des 56-bit encryptionSimple key management creates and stores key in TSM dbRegistry key management with backup/archive client encryptionTape drive encryption between TSM server and disk storage poolBenefitsProvides for secure data transferMay be required for Sarbains OxleyNo extra charge


FIREWALL *FirewallBackup, recovery & web client support through firewallsRequires the assignment of only two firewall portsIrrespective of the # of target servers & clients being protectedFirst port allows TSM server & clients TCP/IP communicationSecond port enables scheduling between TSM server & clients Optional third port enable the administrative Web interfaceBenefitsEnables backups &restores to be performed where firewalls are present


DATABASE AND APPLICATION PROTECTIONOn-Line ProtectionTSM for Mail Lotus Domino MS ExchangeTSM for Databases Oracle MS SQLTSM for Enterprise Resource Planning SAP/R3TSM for Microsoft SharePoint Support for Informix and DB2 built inBenefitsOnline (hot) backup24x7 application availability No downtimeIncremental backupMinimize data to store & maintain Faster backupsData integrityUse of certified application APIsAutomated, consistant backup of all needed files Automation/SchedulingNo shutdown requiredAutomated restore of consistently backed up filesNo customized scripts and manual interactionApplication SystemTSM Server BackupRestoreTiered Storage Pools


ONE TOOL TO DO IT ALL*One toolOne interfaceOne product Architected for high ROI


*Thank you


Catalog seperti daftar isi buku. Dengan catalog ini kita dapat mengetahui file yang kita backup dimana lokasinya. Sehingga mempermudah/mempercepat dalam proses restore.

TSM database tracks every file, which client it belongs to, and where it resides in "storage That means TSM knows where every file, version of file and copy of file exists on tape, disk or other storage media. At any time if you destroy a copy of a file in TSM, it will reside somewhere else and can be rebuilt. This also allows you to only the restore that data you need. For example if you have backed up three different versions of the file, the relational DB will allow you to choice the file with the time stamp you need instead of having to restore each version until you find the version of the file you need.

TSM database and recovery log can be mirrored for availability and provide automatic alternate volume switching Mirroring is extremely important. TSM eliminates the single point of failure by creating mirrors of the DB and its recovery log there for allowing you to have that extra piece of mind.

Every transaction involves a "two-phase commit - This means that if the file get interrupted at any time during a transfer the DB will mark it unsuccessful there fore ensuring the validity of your data.

Can dynamically expand or contract The DB will self manage itself so that you do not have to monitor it or change it manually

Recovery log allows for a "point-in-time" recovery of TSM server - Because we are a relational DB we use log files. This allows TSM to recover to a point in time. Some times known as a roll forward recovery.

*FeaturesCentrally defined policies defineWhat data to protectWhere to store the dataHow long to keep itFile level granularityChanges are retroactively applied to already managed data

TSM adjusts to fit your business needs via its flexible policy management. Not only do policies help you customize your backup strategies for specific computers, but they are flexible enough to be applied to individual files if you need that (unique to TSM). Policies help outline what gets backed up to where and how long it is kept. TSMs relational db allows policies to be updated and the changes to be made retroactive no need to re-backup data (unique to TSM).*To be covered on this slideTSM core function is the backup function. TSMs powerful database empowers it to do a progressive backup where just NEW or CHANGED files are backed up. The reason TSM CAN do progressive backup is that TSMs db tracks the individual files.

There is NEVER a dependency on a full backup. ( more in later slide- we well cover this in more detail)

TSM also includes backup functions like mobile backup, volume level backup, backup sets)

*Things to be covered on this slide:

What is archive - long term record retention. It differs from backup in that it keeps files for a specific amount of time (where backup kept a certain number of versions of a file).

Some examples of this would be financial reporting data (weekly, monthly, quarterly, annual data), that needs to be retained for future trending/requirements/audit, but does not need to consume valuable disk space on where live data should reside - so it it archived for quick and easy retrieval by using TSM.

TSMs archive is policy based, if the requirement for how long you need to retain a file for changes, all your admin has to do is update the policy, and then TSM will retroactively update the already archive files! No need to restore and re-archive. (we will talk more on this in a later slide)

*Space Management. eliminate out-of-disk space messageAutomatically migrate files (based upon the policies you set for size of file, length of time the file has not been opened etc) from the TSM client to the TSM server. It leaves behind a little stub file on the actual TSM client, so that if the file is ever accessed, it will automatically recall the file from the TSM server and put it back on the TSM client for reuse - no intervention!! No more out-of-disk space messages will appear. We move the data to the proper media based upon policies you set, free up valuable disk space for active files and provide automated access to these files when needed.Migrating files off of TSM also helps expedite restores, because you dont have to restore migrated files if there is a disaster.

Migrates inactive dataTransparent recallPolicy managedIntegrated with backup

*Disini terlihat ada tape library dan stg pool. Kenapa ada stg pool, jika seandainya kita ingin buat rules/policy dimana file2 besar di store ke tape, sedangkan file ukuran kecil di store ke stg pool.Kemudian jika kita ingin menambah kecepatan backup misalnya, maka kita harus melihat secara keseluruhan dimana letak bottleneck nya.Tidak bisa hanya dari satu sisi saja, misalnya langsung mengganti software backup atau tape (ember) yang lebih besar kapasitasnya, tidak menjamin akan menambah kecepatan backup. Banyak komponent yang harus kita perhatikan, antara lain, harddisk di server client, koneksi dari client ke switch, switch ke storage, harddisk di server tsm(read/write), storage server (disk/tape), tape tipe apa. Baru kita bisa memutuskan di komponen mana yang bisa kita upgrade untuk menambah kecepatan backup.*Sudah jarang digunakan, dan Data Mover IBM sudah tidak ada.*Ini perbedaan TSM dengan product lain yang menggunakan flat file. Incremental hanya membackup file sejak backup terakhir dilakukan. Perbedaannya, karena TSM menggunakan DB, didalam proses restore, DB melakukan query, dimana dimampukan untuk melakukan restore point in time, dapat melakukan restore sesuai dengan kebutuhan, misal kita ingin merestore file dihari tertentu. Jika dengan type backup lain, misal ingin melakukan restore hari senin, maka akan merestore semua file mulai dari hari jumat sampai hari senin.Berbeda dengan TSM, restore dapet langsung restore hanya file yang dihari senin, otomatis menghemat space dan waktu. Jauh lebih cepat dibanding dengan 2 type lain.

This is another large difference between us and every one else.

Three types of backups:Full + incremental Backup - This requires a full backup and then incremental over time. Usually you see a full backup on the weekend once a week then incremental for the following six days. Only data that has changed from the day before is transferred to tape. Then another full must be runRestore The full must be restored then each days incremental data must be applied to it. This means that if you have a full and three incremental of the same file, it will be restored 4 times. It is a waste of time and money

Full + DifferentialBackup - This requires a full backup and then differential over time. Usually you see a full backup on the weekend once a week then differential for the following six days. This means that all data that has changed since the last FULL will be backed up. If you assume 10% growth then on the first day you will backup 100% (full), the second 10%, the third 20%, the fourth 30%, the fifth 40%, the sixth 50% and the seventh 60%. That means that you are backing you half of your environment with out needing too.

Restore - You would restore the Full then the last Differential up to the date you were restoring to. This means that you may be restoring 150% of your environment.

Incremental Forever (progressive incremental) Backup - This requires a full the first time the incremental from then on out. No extra transfers of data which save network bandwidth, transfer time, makes backup and restore faster, and saves thousands of dollars in tape costs. Let us prove itRestore We query the DB then restore the files necessary. Once only. No extra traffic or time. Lots faster then the other two.*Animation***Animation**What Interfaces does TSM have? ISC Enterprise UIWEB based HTML UICommand line

What can be controlledTSM serverThe storage hierarchyAll TSM clients

Why is this important?One tool., One interfaceTSM reachable from most anywhereNo additional charge

*What does it do?Allows for administrator access to the TSM server from any whereWho should it use?Customers wanting easy access to the TSM serverWhat platforms?All TSM servers

Tree and detail framesHTML select boxesIcons and hyperlinksRadio buttonsNo multiple selectionsCommand lineJava appletAll command line functionsLast command recallEvent viewerJava appletDisplays server messages

***API berfungsi untuk menghubungan TSM dengan product lain, seperti Oracle, SQL server dll.Jika kita ingin melakukan backup mysql, kita dapat membuat API untuk mysql agar TSM dapat berkomunikasi dengan mysql(jika memiliki kemampuan).Untuk saat ini sudah ada yang membuat API untuk mysql. Hanya saja tetap tidak di support oleh IBM.

All Tivoli Storage Manager clients except MacintoshFeaturesAllows for third party programs to send their data to the Tivoli Storage Manager serverData managed by Tivoli Storage Manager server and stored in storage poolsAPI packaged as part of the backup/archive clientAPI developed and supported by Tivoli Storage groupAPI documentation:http://www.tivoli.com/support/public/Prodman/public_manuals/td/TSMC/GC32-0793-00/en_US/HTML/ansatfrm.htm

*All Tivoli Storage Manager clients except MacintoshThe data encryption available with Tivoli Storage Manager 5.3 is upgraded from 56-bit DES to 128-bit AES (Advanced Encryption Standard). Encryption is now also available for applications using the Tivoli Storage Manager API, which includes the Tivoli Storage Manager Data Protection Clients for applications and databases. New support for automatic key management enables use of encryption with API applications without any changes to the applications

FeaturesEncryption of file data before they are sent to serverEncryption is last step before data sent to serverAES 128-bit & Des 56-bit encryptionFully transparent to serverWorks on backup and archive and APIHW Tape Drive Encryption ( IBM TS1120)Simple key management with API and HW Registry key management with b/a client

*FeaturesAdvanced backup, recovery & web client support through firewallsAPI-based solution enables TSM server to communicate directly with the target clients that are to be protectedRequires the assignment of only two firewall portsIrrespective of the # of target servers and clients that are to be protectedFirst port allows TSM server & clients TCP/IP communicationSecond port enables scheduling between TSM server & clients Optional third port enable the administrative Web interfaceSupported with all clients and servers

First port allows TSM server & clients TCP/IP communicationThis value is known as the TCPPORT option -defaults to port 1500Second port enables scheduling between TSM server & clients The value is known as TCPCLIENTport and defaults to Port 1501Optional third port enable the administrative Web interface This value is known as the HTTPPORT option and defaults to port 1580Access security and integrity for the web interface is maintained by communication with the Tivoli Storage Manager server

Backup and recovery methods are accepted as proven standard processes within IT operations. However, the introduction of internet environments, with the creation of secure servers in a perimeter network or demilitarised zone (DMZ), creates substantial management challenges to maintaining adequate data protection for these servers, without compromising firewall security. The purpose of the Firewall is to provide security between two independent network environments. Access across a firewall is provided through a port. A port can be securely bound to tight installation security policies. However, competitive backup and recovery products require that the firewall is enabled to allow hundreds of TCP-ports to be used for client communication to enable backup and recovery processing. In this environment it is difficult to build secure infrastructure policies to support this method as port access is random, it cannot be tied down to specific resources and therefore it is not predictable. Consequently, the environment is made vulnerable to security attack and may have major implications for the organisations security and audit policies. Uniquely, Tivoli Storage Manager provides advanced backup and recovery and WEB Client support through firewalls. This is achieved through the implementation of an API-based solution that enables the Tivoli Storage Manager server to communicate directly with the target clients that are to be protected. This mechanism requires the assignment of only two firewall ports, irrespective of the number of target servers and clients that are to be protected in the DMZ. An optional third port may be considered. A port must be opened on the firewall that the Tivoli Storage Manager server and target servers (clients) can communicate over TCP/IP through. This value is known as the TCPPORT option and defaults to port 1500. To enable the Tivoli Storage Manager and clients to communicate they must be defined and validated by the Tivoli Storage Manager infrastructure definitions. The second port is required to enable scheduling communications to be established between the Tivoli Storage Manager server and the backup and recovery clients. The value is known as TCPCLIENTport and defaults to Port 1501. An optional third port could be configured to enable the administrative Web interface to enable backup and recovery administration functions to be conducted. Use of this facility is dependent on what strategy is used to administer local Tivoli Storage Manager client administration within the DMZ. This is achieved by establishing secured HTTP class communication between the Tivoli Storage Manager server and the target clients across a firewall. This value is known as the HTTPPORT option and defaults to port 1580. Access security and integrity for the web interface is maintained by communication with the Tivoli Storage Manager server. Each E-Infrastructure server that requires data protection requires a Tivoli Storage Manager client to be installed on it. This topology allows for data backup and recovery to be effected using two distinct ports with known, fixed, IP addresses. Consequently, installation security can be enhanced for critical backup and recovery operations as the Firewall can be constructed to ensure that only the defined client and server components of the infrastructure communicate and pass data between the defined Firewall ports.In addition to the above Tivoli Storage Manager supports the use of a proxy server configuration to further enhance and secure web administration. By installing Tivoli Storage Managers Secure Web Administrator Proxy for Web administration on a web server that sits on the firewall, the web server can access resources on both sides of the firewall. This provides proxy-based security validation for multiple Tivoli Storage Manager servers that may be used to support the e-Infrastructure. Again, reducing the number of ports that must be maintained on the Firewall. Opportunities to further enhance security exist by using the Tivoli Storage Manager HTTPS service to facilitate secure socket layer (SSL) communication. Together these methods add value to e-infrastructure by creating a more secure environment as opportunities for vulnerable attack points are able to be controlled or have been eliminated. In addition, operational costs are reduced as the complexity of set-up and maintenance of the backup and recovery

*Online (hot) backup for all supported databases/platforms No downtime for revenue generating applications 24x7 application availability can be guaranteedIncremental backup for all supported databases/platformsMinimize data to store and maintain Faster backup time Data integrity Guaranteed by the use of dedicated certified application APIsAll required files automatically backed up consistentlyAutomation and scheduling of application backupsNo shutdown requiredAutomated restore of consistently backed up filesSaves customer from customized scripts and manual interaction

Seamless application integration to provide application specific additional functionstransaction log file managementcluster services and standby server

*Key Messages:

- TSM is a lot more than a backup application. It provides a storage management architecture that can be exploited by many applications that have a need for storage management services:-1) backup and restore2) archive and retrieve3) HSM (Space Management)4) Online backup of databases and applications 5) Bare Machine Recovery 6) Disaster Recovery planning

Why is this important?A singe tool to do many features. Will grow with you as your needs change.

Competitive products like Veritas and Legato require separate products and separate infrastructure to provide all of this

Presentasi TSM New

Documents

Transcript of Presentasi TSM New