5 Types of disaster recovery strategies offered by IBM Spectrum Protect (TSM)

IBM Spectrum Protect offers different disaster recovery strategies to help planning for any disaster situation. When you implement Spectrum Protect (TSM) server to backup your organization data, it is also highly recommended to plan and implement the secondary TSM server at DR site to make sure that you are ready to face any unexpected data loss or disaster situations. The below video from IBM employee will explain you the different types of disaster recovery strategies which you can choose to implement in your organisation based upon your requirements and resources.

You can protect the IBM Spectrum Protect server and all the backed-up data by using one or more of the following strategies. Remember that proper planning, implementation and regular DR drills will help you to learn from the mistakes and also it will put you in a good position to recover the data loss ASAP. You can implement any of the following disaster recovery strategies by using TSM server.
  • You can take TSM Data base backup and copy storage pools daily in and send them via a carrier to an offsite location. 
  • You can Utilise the existing SAN technical features (like storage replication) for the storage pool copies 
  • You can Implement HADR with off site copies
  • You can also do hardware replication of the TSM DB and storage pools 
  • You can configure Spectrum Protect Node Replication techniques which comes with TSM server.
Disaster recovery strategies by using TSM

The video also explains the common and frequently seen disaster situations, causes of disaster, what needs to be protected in terms of spectrum protect server, and the seven tiers of disaster recovery scenarios by using spectrum protect. The video also covers the Recovery Point Objectives (RPO), Recovery Time Objectives (RTO) and costs for each solution as shown in the above figure.

Also Read: Installation & Configuration of IBM Spectrum Protect (TSM) Server

IBM Spectrum Protect V8.1 high level introduction video guide

IBM Spectrum Protect was formerly known as Tivoli Storage Manager, TSM, ADSM. The below  latest video from IBM covers basic functions, components and related products of TSM. This high level overview is an introduction to IBM Spectrum Protect as of version 8.1. IBM has introduced many new features in Spectrum Protect version v8.1 where you can take backup to 4 of the widely used cloud storage services and you can fastly transfer data to DR servers by integrating Aspera FASP technologies.

The below video covers why any organization needs a data protection solution to protect its IT infrastructure, applications and its business critical data and why IBM Spectrum Protect is one of the best choice to implement. The video covers
  • Basic concepts of TSM Backup and Archive and benefits of using it.
  • Different types of Backup methods supported by TSM
  • How to protect various applications, databases and virtual environment using TSM (hot and cold backups).
  • Various data reduction techniques which helps in saving storage space.
  • Different kinds of Disaster Recovery Strategies that can be implemented by using TSM.
  • Different types of snapshots and Bare metal recovery techniques supported by TSM.
  • Finally, how to use TSM operations center to configure backup schedule and administer the daily house keeping activities with ease.
Also Read: IBM Spectrum Protect (TSM) Basic Free Tutorials

How to repair damaged data on the directory-container storage pool on a target server

IBM has introduced new set of commands to easily repair the damaged data on the directory-container storage pool on both source and target TSM servers when you enable replication techniques. By using these commands you can save lots of time and money which we spend on recovering the damaged storage pools earlier. You can use PROTECT STGPOOL, AUDIT CONTAINER and REPAIR STGPOOL commands to repair the damaged data on the directory-container storage pool on the target TSM servers. 

The repairing process of the directory-container storage pool  on the target server is done automatically by using the above commands. If the damaged data extent was backed up on a directory-container storage pool on the target server, you can repair the data extent manually by using the REPAIR STGPOOL command. Information about what is repaired is recorded in the activity log for the target server. However, the automatic repair process has the following limitations:
  • Both the source server and the target server must be at V7.1.5 or later.
  • To be repaired, extents must already be marked as damaged on the target server. The repair process does not run an audit process to identify damage.
  • Only target extents that match source extents are repaired. Target extents that are damaged but have no match on the source server are not repaired.
  • Extents that belong to objects that were encrypted are not repaired.
  • The timing of the occurrence of damage on the target storage pool and the sequence of REPLICATE NODE and PROTECT STGPOOL commands can affect whether the repair process is successful. Some extents that were stored in the target storage pool by a REPLICATE NODE command might not be repaired.

So to repair the damaged data, you need to first find out what is the damaged data in the target storage pool. To identify the damaged data, we use AUDIT CONTAINER command and QUERY DAMAGED commands. The AUDIT CONTAINER command is used to scan for inconsistencies between database information and a container in a directory-container storage pool. Whereas QUERY DAMAGED command is used to display information about damaged data extents in a directory-container or cloud-container storage pool. Use this command together with the AUDIT CONTAINER command to determine a recovery method for the damaged data.

Steps to follow to repair damaged data on the directory-container storage pool on the Target server

Step 1: Verify the consistency of database information for a directory-container on the target TSM server

Use AUDIT CONTAINER  command to scan for inconsistencies between database information and a container in a directory-container storage pool. You can use this command to complete the following actions for a container in a directory-container storage pool
  • Scan the contents of a container to validate the integrity of the data extents
  • Remove damaged data from a container
  • Mark an entire container as damaged


You can Specify the name of the container or the the name of the directory-container storage pool or the  name of the container storage pool directory that you want to audit.  For example, to mark as damaged all of the data in a directory-container storage pool
audit container stgpool=prdpool maxprocess=5 action=markdamaged

Also you can specify the type of action to be performed when using this command by using Action parameter. It specifies what action the server takes when a container in a directory-container storage pool is audited. It has the following options
SCANAll - Specifies that the server identifies database records that refer to data extents with inconsistencies. This value is the default. The server marks the data extent as damaged in the database.
REMOVEDamaged - Specifies that the server removes any files from the database that reference the damaged data extent.
MARKDamaged - Specifies that the server explicitly marks all data extents in the container as damaged.
SCANDamaged - Specifies that the server checks only the existing damaged extents in the container.


If the audit does not detect an error with a data extent that is marked as damaged, the state of the data extent is reset. The data extent can then be used. This condition provides a means for resetting the state of damaged data extents if errors are caused by a correctable problem. The SCANALL and SCANDAMAGED options are the only options that reset a damaged extent if it is found not to be damaged.

Step 2: Query damaged data in a directory-container or cloud-container storage pool - optional

Use QUERY DAMAGED command to display information about damaged data extents in a directory-container or cloud-container storage pool. Using this command together with the AUDIT CONTAINER command will help you to determine a recovery method for the damaged data.
For example, to display status information about damaged or orphaned data extents
query damaged prdpool type=status

Storage Pool     Non-Deduplicated          Deduplicated   Cloud Orphaned   Name             Extent Count                     Extent Count      Extent Count  ---------------         -------------                           ----------             -------------POOL1                  65                                       238                     18

Use the Type parameter to specify the type of information to display. You can use the following options
Status - Specifies that information is displayed about damaged data extents. For cloud storage pools, orphaned extents are also displayed. This is the default.
Node Specifies that information about the number of damaged files per node is displayed.
INVentory - Specifies that inventory information for each damaged file is displayed.
CONTAiner - Specifies that the containers that contain damaged data extents or cloud orphaned extents are displayed. For directory-container storage pools, storage pool directories are also displayed.
Nodename - Specifies that damaged file information for a single node is displayed.

Step 3: Automatic Repair of damaged extents 

Starting from Tivoli Storage Manager Version 7.1.5, when a storage pool protection process runs for a directory-container storage pool on a source server, damaged extents in the target server's storage pool are repaired automatically. 

You can check the information about what is repaired is recorded in the activity log for the target server once the storage pool protection process gets completed. Ideally it is recommended to schedule the step 2 and step 3 in regular intervals so that the damaged data extents are automatically repaired during daily storagepool protection process.

SAN basic interview questions

This is the next part of the 50 questions shared earlier. Below are some of the frequently asked Storage (SAN) basic interview question and answers. Check the Storage Area Networks (SAN) basic & advanced concepts page in this site to learn more SAN basics. 

Storage Area Networks (SAN) Basic concepts Interview Questions and Answers


51. what are FC protocols?
Ans :- i)FCP
ii)FCIP
iii)IFCP
iv)FCOE

52. FC tolpologies?
i)Point –Point
ii)FC-AL
iii)Switched Fabric

53. Types of Logis?
Ans :- i)FLOgi
ii)PLOGI
iii)PRLOGI

54. What is ISL?
Ans:- Inter switch Link physical connection between two switches.
With E-Port .It Aggregates the bandwidth

55. How to turn on trunk port?
Ans :- >portcfgtrunk portID 1

56. How to check zone status?
Ans :- >zoneshow zonename

57. What is domain id / port ID?
Domain ID name/ID of the switch and port id means port number.

58. What is dark fiber?
Ans :- lease line cable which is established but not in use called Dark Fiber.

59. SAN topologies?
Ans :- i)Point –Point
ii)FC_AL
iii)Switched Fabric

60. Diff b/w brocade 3850 & latest Model ?
Ans : Brocade 3850 supports 16, 32 ports & 5100 supports 8 gbps -40 ports

61. How to add license in switch?
Ans :- >licenceshow
>licenceadd “key”

62. Diff b/w DAS & NAS?
DAS -> Direct Attached Storage
NAS -> Network Attached storage

63. RAID LEVELS?
RAID 0:-Concatination /Stripping min 2 disks max 8 disks
RAID 1:- Mirroring min 2 disks max 8 disks
RAID2:-Bit level striping min 2 disks max 8 disks
RAID 3 :-Byte level striping with fixed parity to perform this we need to have m in 3 disks max 15 disks
RAID 4:-Block level striping with fixed parity to perform this we need to have m in 3 disks max 15 disks
RAID 5 :- striping with Distributed parity to perform this we need to have min 3 disks max 15 disks
RAID 6:- Block level striping with Distributed parity to perform this we need to have min 4 disks max 16 disks
RAID 10: Stripped mirror to perform this we need to have min 4 disks max 16 disks
RAID 01 :-mirror stripped to perform this we need to have min 4 disks max 16 disks

64. How to take switch backup?
Ans: -by doing of >configupload
After that Through FTP we need to give server name
IPaddress
UserID:
Password:
Of target server here we can save the configuration of the switch.

65. What is port address?
FCID , it is 24 bit address contains Domain Id, Port Number & Loop Number

66. HBA ?
A: Host Bus Adaptor , it resides in the Host. It is Network interface card.

67. Port swapping ?
A: it is a process of when one port is failure , the other port is changed as a communication port

68. What is meant by up streaming and down streaming?
(upstream) The ISL is an upstream path toward the principal switch of the fabric.
(downstream) The ISL is a downstream path away from the principal switch of the fabric.
(Trunk Primary) The port is the master port in a group of trunking ports.
Up If the ISL is connected and the link is up
Down No ISL is connected

69. How to start Automated config upload?
A: automate configuration

How to repair damaged data on the directory-container storage pool on a source server

IBM has introduced new set of commands to easily repair the damaged data on the directory-container storage pool on both source and target TSM servers when you enable replication techniques. By using these commands you can save lots of time and money which we spend on recovering the damaged storage pools earlier. You can use PROTECT STGPOOL, AUDIT CONTAINER and REPAIR STGPOOL commands to repair the damaged data on the directory-container storage pool on both source and target TSM servers. 

Infact, the repairing process of the directory-container storage pool  on the target server is done automatically by using the above commands. In this post we will see the steps to repair damaged data on the directory-container storage pool on a source server.

Steps to follow to repair damaged data on the directory-container storage pool on a source server

Step1: Enable protection manually or automatically

You can protect the storagepools by configuring automatic protection or manual protection. 
To enable storagepool protection automatically, specify the PROTECTSTGPOOL parameter on the DEFINE STGPOOL or UPDATE STGPOOL command to back up the data. For example
update stgpool prodpool protectstgpool=proddrpool

To enable storagepool protection manually, use PROTECT STGPOOL command to protect data in directory-container storage pools by storing the data in another directory-container storage pool on the target server. When you issue this command, data that is stored in the directory-container storage pool on the source server is backed up to a directory-container storage pool on the target server. You should issue this command on the server that is the source server for data.
How to repair damaged data on the directory-container storage pool on a source server

For example to protect a storage pool to a target replication server
protect stgpool devpool maxsessions=5

Use the FORCEREConcile parameter to specify whether to reconcile the differences between data extents in the directory-container storage pool on the source server and target server. If you specify NO to this option, the data backup does not compare all data extents in the directory-container storage pool on the source server with data extents on the target server. Instead, data backup tracks changes to the data extents on the source server since the last backup and synchronizes these changes on the target server. If you specify YES, the data backup compares all data extents on the source server with data extents on the target server and synchronizes the data extents on the target server with the source server.

Step 2: Repair the storagepool by using REPAIR STGPOOL command

If you notice any damage of data on the source storagepool, you can repair the storagepool by using REPAIR STGPOOL command


By protecting the directory-container storage pool, you can repair damaged storage pools by using the REPAIR STGPOOL command. It is used to repair deduplicated extents in a directory-container storage pool. Damaged deduplicated extents are repaired with extents that are backed up to the target server. 
repair stgpool command

For example, to repair a storage pool 
repair stgpool devpool maxsessions=5

You must issue the PROTECT STGPOOL command to back up data extents to the directory-container storage pool on the target server before you issue the REPAIR STGPOOL command. The REPAIR STGPOOL command fails when any of the following conditions occur:
  • The target server is unavailable.
  • The target storage pool is damaged.
  • A network outage occurs.

Limitations of enabling compression on TSM DB backups

Deduplication and replication techniques are server intensive processes and if you enable these techniques, you might additionally notice that your TSM DB size has been increased rapidly. If you are taking DB backups on a FILE or SERVER device class, it is obvious that you might require additional space to store the multiple versions of DB backups. This situation costs lots of disk space for the organizations and it might necessary to store the DB backups on disks if you have stringent recovery times. 

So in this kind of situations, you can enable compression when taking TSM DB backups.  By compressing volumes that are created during database backups, you reduce the amount of space that is required for your database backups.

How to enable compression for TSM DB backups

You can enable compression while running BACKUP DB command manually or you can enable the compression setting for all the DB backups by using SET DBRECOVERY command. For example, to enable compression for a full DB backup taking on to FILE device class
backup db devc=FILE type=full compress=yes


And the syntax for enabling compression for all backups automatically is


By default, the compress value is NO as shown above. You need to specify YES, to enable compression automatically for all DB backups. If you specify the COMPRESS parameter on the BACKUP DB command, it overrides any value that is set in the SET DBRECOVERY command. Otherwise, the value that is set in the SET DBRECOVERY command is the default.

Also Read: Taking TSM server DB backup when the server is down

Limitations of enabling compression during DB backup

  • This feature is valid only if you are planning to take DB backup on to a disk storage, generally FILE device classes. 
  • Using compression during database backups can reduce the size of the backup files. However, compression can increase the time that is required to complete database backup processing.
  • Also, it might take extra time to decompress the DB backup files during TSM DB restore. This will put additional pressure if it is a disaster recovery situation. The whole purpose of this setting is to save storage space only, not to increase DB backup performance.
  • Do not back up compressed data to tape. If your system environment stores database backups on tape, set the COMPRESS parameter to No in the SET DBRECOVERY and BACKUP DB commands.

Protecting directory-container storage pool by using new type of copy storagepool

IBM has frequently adding new features to Tivoli Storage Manager after they changed its name to IBM Spectrum Protect.  The 2 new storage pool types which are Directory Container Storagepool and Cloud Container storage pool types helps us to deduplicate data faster and also backup to cloud. 

Starting from Tivoli Storage Manager Version 7.1.7, another new storage pool type is added by which you can protect directory-container storage pools by copying the data to container-copy storage pools, where the data can be stored on tape volumes. Previously, you can only protect the data in directory-container storage pools by enabling replication. With this new type of storage pool, you can now copy data from directory-container storage pools to tape to send it to offsite location if required. 

Container-copy storage pool Overview

A container-copy storage pool is a new type of storage pool that provides an alternative to using a replication server to protect data in a directory-container storage pool. Container-copy storage pools can be used to repair minor to moderate directory-container storage pool damage, which includes damaged containers or directories. However, replication is the only way to provide complete disaster recovery protection for directory-container storage pools. With replication, you can directly restore client data from the target server if the source server is unavailable. You cannot create container-copy storage pools if you are using replication.

Also Read: What is Directory Container Storagepool ?

As per IBM, It is not recommended to use container-copy storage pools for disaster recovery protection, even in a small configuration. Repairing an entire directory-container storage pool, even for a small backup configuration, can take several days. Adding more drives or using the latest generation of tape technologies does not decrease the time that is required for the repair activity.

Also Read: What is Cloud Container Storagepool ?

Now lets see how to configure container-copy storage pool in both command line and Operations Center by using wizards.

Configuring container-copy storage pool by using commandline

1) To configure container-copy storage pool, you should first define at least one tape library to the server by using the DEFINE LIBRARY command. Provision enough tape drives and scratch volumes to meet your storage requirements. Also remember that Virtual tape libraries are not supported, regardless of which library type is defined. Only physical tape is supported.

2) Next you need to define container-copy storage pool by using DEFine STGpool command. Use the below syntax and optional parameters to define this

For example, 
define stgpool container_copy LTO6 pooltype=copycontainer maxscratch=100 reusedelay=30

PROTECTPRocess specifies the maximum number of parallel processes that are used when you issue the PROTECT STGPOOL command to copy data to this pool from a directory-container storage pool.

Also Read: TSM Storage Pool Concepts (V7 Revised)

3) Then you need to define or update the directory container storage pool with the container-copy storage pool to be used for protection. You need to update PROTECTLOCalstgpools parameter with the copy container storage pool name which you defined earlier. This will help you to automatically schedule the protection. 
update storagepool directory_stgpool  PROTECTstgpool =container_copy

PROTECTLOCalstgpools parameter specifies the name of the container-copy storage pool on a local TSM server where the data is backed up. You should update this parameter with copy container storage pool while defining the directory container storage pool. This container-copy storage pool will be a local target storage pool when you use the PROTECT STGPOOL command.

4) Next you can define a schedule, or use PROTECT STGPOOL command to manually protect the data in a directory-container storage pool by storing a copy of the data in the container copy storagepool.


For example
protect stgpool directory_stgpool  type=local

Configuring container-copy storage pool by using Operations Center

To configure storage pool protection to tape for an existing directory-container storage pool by using Operations Center, complete the following steps:
  • On the Operations Center menu bar, click Storage > Storage Pools.
  • On the Storage Pools page, select the directory-container storage pool that you want to protect to tape.
  • Click More > Add Container-Copy Pool.
  • Follow the instructions in the Add Container-Copy Pool window to schedule protection to tape.
Note that to copy the data in directory-container storage pools to tape, the Operations Center creates a schedule to run the PROTECT STGPOOL command. When the protection schedule runs, one tape copy is created. At least one volume must be available when the protection schedule runs. Otherwise, the operation fails.

Also Read: How to restore damaged files in a primary storagepools from replication server automatically

If you created a container-copy storage pool as part of the Add Storage Pool wizard, you do not have to use this procedure. When you completed the wizard, the Operations Center configured the container-copy storage pool and a protection schedule.

Check the below video to understand how to configure Container-Copy Pool and define a schedule to start protecting data in directory container storagepool by using OC wizards.