1. IBM Spectrum Protect 7.1.4.x & 7.1.5
1st Quarter 2016 Technical Updates
Spectrum Protect Server, OC, Snapshot
Tricia Jiang
Sean Sperry / Cyrus Niltchian

2. 7. 1. 5 & 7. 1. 4. x Spectrum Protect Overview 7. 1
& x Spectrum Protect Overview available 3/11/ x available in near future
SERVER 7.1.5
Creating and Managing IBM Cleversafe backed storage pools
Enable, Disable and Visualize Server-side Compression for Container pools
Cross platform server migration specifically for AIX to xLinux migration
PROTECT STGPOOL enhanced in to replace damaged extents on target servers
OC 7.1.5
CLIENT x
pLinux LE Ubuntu support
Red Hat Enterprise Linux 7.2 support
SUSE Linux Enterprise Server 12.1 support
SPACE MANAGEMENT x
IBM Spectrum Scale™ 4.2 support
VE x
vmdatastorethreshold option
Snapshot 4.1.4
Providing hardware-based snapshot protection for Oracle 12c single-tenant databases
GPFS file system snapshots with offload
Dynamic target adaptor
Support for Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12
Snapshot x
Support for Microsoft Exchange Server 2016
New functions for IBM Spectrum Protect Extend IBM Spectrum Protect’s native object storage support to IBM Cleversafe’s reliable and scalable storage platform Administrators can provision Cleversafe object storage for use as a target for IBM Spectrum Protect container storage pools. Cleversafe’s object storage delivers the scalability, security, availability and cost efficiency required by your enterprise data protection solution. Combine IBM Spectrum Protect’s powerful software-defined inline data deduplication with the scalability and efficiencies of Cleversafe to create an unmatched data protection solution. IBM Spectrum Protect server-side compression for container pools Add more capacity to IBM Spectrum Protect container pools without adding more storage. This is achieved with by a new feature to turn on inline compression for container pools using the latest highly efficient compression algorithms. Utilizing data compression in addition to data deduplication allows for further data reduction to minimize storage space requirements and associated storage costs. Support for Microsoft Exchange Server 2016 IBM Spectrum Protect for Mailboxes now supports Microsoft Exchange Server The new platform support enables customers to increase system availability for Microsoft Exchange Servers. Note: Mailbox restore browser is not supported when running in an Exchange Server 2016 environment and restores from Data Protection for VMware backups of Exchange Server 2016 Virtual Machine are not supported. IBM Spectrum Protect Snapshot 4.1.4: Providing hardware-based snapshot protection for Oracle 12c single-tenant databases Administrators can set up hardware-based snapshots for Oracle’s 12c single-tenant databases with optional, subsequent data offload into an IBM Spectrum Protect Server Snapshot-based data protection for IBM Spectrum Scale environments Frequent, non-disruptive data protection leveraging IBM Spectrum Scale snapshots with offload into Spectrum Protect Server. Administrators can set up IBM Spectrum Scale snapshots on file set level with optional, subsequent data offload into an IBM Spectrum Protect Server. Dynamic allocation for IBM Spectrum Virtualize FlashCopy target volumes Introduces dynamic allocation for IBM Spectrum Virtualize FlashCopy target volumes in UNIX and Linux environments. When configuring Spectrum Virtualize, administrators can define storage pools containing target volumes where the snapshots should reside. At run time, when a FlashCopy operation takes place, the required target volumes are dynamically allocated by IBM Spectrum Protect Snapshot. This function increases administrator’s productivity through ease of use. Expand IBM Spectrum Protect Snapshot for Windows to support Instant Restore for 3rd-party storage arrays in clustered configurations This new capability extends Instant Restore support to 3rd-party storage arrays when running IBM Spectrum Protect Snapshot in Windows clustered environments. It improves application availability through faster recoveries. Integrated Capacity Reporting of snapshots for licensing purposes The new licensing reporting capability allows to query the size of snapshots managed by IBM Spectrum Protect for Snapshots, which are kept within the local storage array. It can be used for planning purposes and Front-End licensing compliance to minimize administration costs. New platforms IBM Spectrum Protect Snapshot for Linux: - Support for Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12
Footnote goes here

3. Disclaimer
This presentation describes potential future enhancements to IBM Spectrum Protect.
IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion. Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision. The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.
New functions for IBM Spectrum Protect Extend IBM Spectrum Protect’s native object storage support to IBM Cleversafe’s reliable and scalable storage platform Administrators can provision Cleversafe object storage for use as a target for IBM Spectrum Protect container storage pools. Cleversafe’s object storage delivers the scalability, security, availability and cost efficiency required by your enterprise data protection solution. Combine IBM Spectrum Protect’s powerful software-defined inline data deduplication with the scalability and efficiencies of Cleversafe to create an unmatched data protection solution. IBM Spectrum Protect server-side compression for container pools Add more capacity to IBM Spectrum Protect container pools without adding more storage. This is achieved with by a new feature to turn on inline compression for container pools using the latest highly efficient compression algorithms. Utilizing data compression in addition to data deduplication allows for further data reduction to minimize storage space requirements and associated storage costs. Support for Microsoft Exchange Server 2016 IBM Spectrum Protect for Mailboxes now supports Microsoft Exchange Server The new platform support enables customers to increase system availability for Microsoft Exchange Servers. Note: Mailbox restore browser is not supported when running in an Exchange Server 2016 environment and restores from Data Protection for VMware backups of Exchange Server 2016 Virtual Machine are not supported. IBM Spectrum Protect Snapshot 4.1.4: Providing hardware-based snapshot protection for Oracle 12c single-tenant databases Administrators can set up hardware-based snapshots for Oracle’s 12c single-tenant databases with optional, subsequent data offload into an IBM Spectrum Protect Server Snapshot-based data protection for IBM Spectrum Scale environments Frequent, non-disruptive data protection leveraging IBM Spectrum Scale snapshots with offload into Spectrum Protect Server. Administrators can set up IBM Spectrum Scale snapshots on file set level with optional, subsequent data offload into an IBM Spectrum Protect Server. Dynamic allocation for IBM Spectrum Virtualize FlashCopy target volumes Introduces dynamic allocation for IBM Spectrum Virtualize FlashCopy target volumes in UNIX and Linux environments. When configuring Spectrum Virtualize, administrators can define storage pools containing target volumes where the snapshots should reside. At run time, when a FlashCopy operation takes place, the required target volumes are dynamically allocated by IBM Spectrum Protect Snapshot. This function increases administrator’s productivity through ease of use. Expand IBM Spectrum Protect Snapshot for Windows to support Instant Restore for 3rd-party storage arrays in clustered configurations This new capability extends Instant Restore support to 3rd-party storage arrays when running IBM Spectrum Protect Snapshot in Windows clustered environments. It improves application availability through faster recoveries. Integrated Capacity Reporting of snapshots for licensing purposes The new licensing reporting capability allows to query the size of snapshots managed by IBM Spectrum Protect for Snapshots, which are kept within the local storage array. It can be used for planning purposes and Front-End licensing compliance to minimize administration costs. New platforms IBM Spectrum Protect Snapshot for Linux: - Support for Red Hat Enterprise Linux 7 and SUSE Linux Enterprise Server 12
Footnote goes here

4. Server - Cleversafe backed storage pools
What is Cleversafe
Content repository solutions that deliver data availability at petabyte and beyond scalability
Scalable object storage platform delivers carrier-grade security
A single copy of original content is dispersed geographically, ensuring data integrity
Slicing of data requires 50% less storage capacity than traditional storage approaches
On premise, hybrid and off-premise solutions
Data
Accesser Software
Site 1
Site 2
Site 3
Slicestor Software
S3 Compatible API
Openstack Swift
Compatible API
Simple Object API
ARCHIVE
OTHERS
NAS
Accessers are deployed to access the underlying storage
Spectrum Protect introduced container stgpools
Directory Container
File based local storage using file system directories
Cloud Container (On-Premises or Off-Premises)
Object based IBM® SoftLayer, V1Swift or OpenStack Swift cloud computing system
Only difference in on-premises or off-premises, is who is managing the cloud and what type of cloud
Slicestors are deployed to store data
Footnote goes here

5. Server - Cleversafe backed storage pools
Cleversafe can be a cloud container for Spectrum Protect
define stg cloudpool stgtype=cloud cloudtype=s3 cloudurl= id=cleverapiID pa=secretapikey
Uses Amazon S3 protocol to access Cleversafe
On-premises S3 support currently only for Cleversafe
Instead of lots of smaller containers like in Swift, it will use fewer big buckets (all under the cover)
cloudurl is the Cleversafe accessor
ID & PA are the API key & API passwords
Setup a vault template in the Cleversafe UI
SecureSlice disabled
Name Index disabled
Recovery Index enabled
NOT the admin ID & PW
Must have Vault Provisioner Role
Developed on on-premises appliance
Can be used on hybrid and off-premises
Performance will depend on location
Footnote goes here

6. OC - Creating & Managing Cleversafe storage pools
Create and manage IBM Cleversafe backed storage pools in the OC
*NOTE: If Cleversafe is actually off-premises, by default OC on-premises cloud sets encryption off

7. Server - Cleversafe backed storage pools
Performance
Consider required restore rates, before choosing which data to place in Cleversafe pools
Test and ramp up this solution slowly, do not immediately replace all disk with Cleversafe
Optimize performance by utilizing multiple accessers
CLOUDURL parameter is normally set to the address of the accesser
To use more than one accesser, list accesser addresses separated by a vertical bar (|), with no spaces
For example: CLOUDURL=<accesserURL1>|<accesserURL2>|<accesserURL3>
255 characters limit for CLOUDURL parameter, will limit how many accessers for a single storage pool
Highly dependent on network bandwidth and latency
More Spectrum Protect client sessions → better throughput
Under ideal conditions:
Up to 3.6 TB/hour ingest*
Up to 30 TB/day ingest* (based on an 8 hour backup window)
Restores are slower – a consideration if there is limited recovery time
*On-prem Cleversafe, 3 accessor nodes, 10GB network, Blueprint large file workload, lots of sessions, default vault template changed: SecureSlice & Name Index disabled and Recovery Listing enabled
Recovery time objective
Footnote goes here

8. Server - Server-side Compression for Container Pools
In-line, server-side LZ4 compression for Container Pools (directory & cloud)
Increases the amount of available space in a container storage pool
Does not require additional DB space
New storage pool level option DEFINE/UPDATE STGPOOL … COMPression=Yes|No
Defaults to YES when defining new container pool
Server containers support LZ4 compression
LZ4 is a lossless data compression algorithm that is focused on compression and decompression speed
LZ4 is preferred over the LZW compression currently used by the client
Choose to use server compression over client compression
HW real time compression should not be used
When compression turned on, will only compress new data being stored in the container
Data extents examined as they are ingested, IF not suitable for compression will not be compressed
ie metadata extents, data previously encrypted or compressed, or if compression leads to a growing chunk length
Dedupe, then compression, then encryption

9. Server - Server-side Compression for Container Pools
Container pool compression is applied after deduplication
CPU impact of compression
CPU impact varies depending on how well data responds to deduplication
Only data which is not eliminated by deduplication needs to be compressed
Largest CPU impact will occur for data which does not deduplicate well
In the lab, typically seeing an additional 30% CPU cost for using compression
Once storage pool I/O becomes a bottleneck, the data savings from compression increase the aggregate backup throughput
Blueprint systems, have sufficient CPU to perform compression and still reach the published aggregate backup throughput
Except Power blueprint where the medium CPU allocation is increasing from 8 to 10 cores
Blueprint sizing spreadsheet including CPU calculations & the cost of performing compression, will be available shortly
Overall Space Savings of deduplication + compression
Combined savings can result in a significant jump in overall storage savings
Data with a 2 to 1 dedupe rate and 50% compression results in a 4 to 1 space savings rate

10. Server - Server-side Compression for Container Pools
Replicate Node & Protect STGPOOL
Source Server
Target Replication Server
Action
Container stgpool compression=yes
Container Stgpool compression=yes
Data extents sent as they are
Container Stgpool compression=no
Data extents sent as they are, because container can handle compressed or non-compressed data
Any Stgpool <7.1.5 / non-container >=7.1.5
Inline compressed data extents will be decompressed on source; non-compressed extents sent as they are
Container stgpool compression=no
Data extents are compressed inline on Target
Container stgpool <7.1.5
Any stgpool <7.1.5
Destination storage pool on TARGET server determines what action to take
. Every data extent has its flag to indicate whether it's compressed or not.     target pool keep the extents as they are, when the data extents are required to restore, it will decompress correspondingly
Footnote goes here

11. Server - Server-side Compression for Container pools
Q stgpool
Enhanced to show a compression ratio
Q DEDUPSTATS
Shows compression ratio statistics
Compressed data extent count
Uncompressed data extent count
Compression saving bytes
Compression percentage
SELECT * FROM table STGPOOLS
Table field COMP_SPACE_SAVED shows space savings in bytes
AUDIT CONTAINER
No parameter changes, data extents will be de-compressed when they are required for audit

12. OC - Server-side Compression for Container pools
Enable, Disable and Visualize Server-side Compression for Container pools

13. Server - Server-side Compression for Container Pools
Comprestimator is available for all server platforms
Predicts compression results by reading at the volume level from a client system and sampling ranges from within the volume
Lab results shows Spectrum Protect actual results coming in almost 15% higher than the comprestimator estimate

14. Server - Cross Platform Server Migration AIX to xLinux
Previously no migration for AIX to xLinux Spectrum Protect Server
Database backup & restore failed due to endianness: pSeries is big-endian, Intel x86_64 is little-endian
Export/import or node replication is not practical because of the large volumes of data involved
SSAM servers using Centera have data locked in & *cannot* be moved using export/import or node replication
Now can migrate IBM Spectrum Protect server db from AIX to xLinux
Command line utilities must be used (extractdb/insertdb)
V5 Upgrade Wizard cannot be used to perform this migration
Migration does not move any server managed storage
Supported versions
Target server must be v7.1.5 or higher
Source must be at the same level as the target
Methods
Network: db contents extracted from source and transmitted over network to target db
Media: db contents extracted from source db and stored on tape or file media
Initially supported paths will be AIX (Big-endian Unix) to Linux for x86_64 via EXTRACTDB/INSERTDB
Windows to Linux for x86_64 or Linux x86_64 to Windows is currently not supported
Additional platforms might be added if there is sufficient demand
See white paper “Migrating TSM Servers from one Operating System to another” on the TSM wiki 20Manager%20Servers%20from%20one%20Operating%20System%20to%20another
Three Different Scenarios for DB Migration to Different Platforms
Upgrade from V5 DB from one platform to another as part of a V5 to V6 database upgrade, using the EXTRACTDB/INSERTDB migration utility.
This scenario was implemented in TSM 6.3.4
Moving from a TSM/IBM Spectrum Protect V6/V7 DB from one platform to another when the platforms have the same endianness.
When the two platforms are UNIX variations, and they have the same endianness, database backup and restore can be used to move the database. In this context, Unix means AIX, Solaris, HP-UX, or Linux
Moving an IBM Spectrum Protect DB2 database from one platform to another when the platforms have different endianess.
When scenario 3 is being done, DB backup and restore cannot be used. This is the enhancement being added with this update.
For customers moving from V5 to V6.3.4 or higher, work was started on the migration utilities to make automatically make any adjustments necessary to account for the change in endianness.
This enhancement is a port of the V5 upgrade utilities to work with a DB2 source database. 
With the upgrade utilities in V5 to V6, EXTRACTDB was used from the V5 database and then the INSERTDB utility was used to place the data into a DB2 database. The utilities have been enhanced to allow EXTRACTDB from a DB2 DB (at V7.1.5 or later) and then use INSERTDB (with adjustments for changes in endianness) to allow migration from AIX to xLinux.
Note: the command line utilities must be used. The Upgrade Wizard that was available in V5 cannot be used to perform this cross platform migration from AIX to xLinux.
Supported versions
On the target server, (the one doing the INSERTDB process), changes in endianness are only being made in the IBM Spectrum Protect v7.1.5 and higher server. This means that your target server, if doing a platform migration, must be at a V7.1.5 or higher level. Also, the source and target need to be at the same level for the cross platform migration.
Initially supported paths will be AIX (Big-endian Unix) to Linux for x86_64 via EXTRACTDB/INSERTDB. Note that Windows to Linux for x86_64 or Linux x86_64 to Windows is not supported with this enhancement
Additional platforms can be added if there is sufficient demand.
Migration process
The migration process is very similar to the techniques used in the V5 to V6 extractdb/insertdb utilities.
However, there is one key difference: cross platform migration has to deal with differences between the two platforms.
Disk based storage being managed by the source server (either random access disk or sequential file) might not be accessible on the target system.
As a result, much of the pre- and post-migration process will deal with moving data between disk & tape in order to ensure that client data stored on disk will be available once the migration has finished.
Other issues exist as well, covered on next slide
Many issues to consider; most are documented already as part of existing V5 to V6 migration utilities. Partial list includes:
Review of target DB. The target DB will need at least as much space as the source server DB.
Review of target system server option files. Some options on source system may not be applicable to target options.
Raw Logical Disk Volumes (RLV); TSM/IBM Spectrum Protect does not support RLVs on xLinux. As a result, data stored on RLVs will need to be treated just like DISK or FILE volumes stored on an incompatible file system, and will be moved to tape prior to the migration.
Device support needs to be considered carefully before committing to a cross-platform migration. The TSM/IBM Spectrum Protect server does not support all devices equally across all platforms
Can the existing hardware be attached to the existing computer, or will new hardware be required? In either case, determine how to access the hardware from the target computer (I.e, what is the path to each device from the target computer?).
Determine whether the server uses DISK or FILE storage. If FILE storage is on an NFS server or on a GPFS file system, then make sure that the target computer can access the storage. Also, Identify the directories in which volumes are stored on the source server. Ensure that the directories will be accessible via the same path on the target server.
Ensure clients have network connectivity to the target computer.
On source server, upgrade to V7.1.5 or higher.
On target, install same level of IBM Spectrum Protect as source.
Client Option files: If the IP address of the target computer will be different from the IP address of the source server, or if the target server will use a different TCP/IP port, then plan on updating every client and server with the new address/port.
If the server is a library client, then identify the corresponding library servers. Path information for the shared libraries and drives will need to be updated on the library server after the migration is over.
Other issues will be identified and documented in publications.
Footnote goes here

15. Server - Cross platform server migration AIX to xLinux
Issues to consider are documented as part of existing V5 to V6 migration utilities
Target DB space: needs at least as much space as the source server DB
Target system server option files: some source options may not be applicable to target options
Raw Logical Disk Volumes (RLV): Spectrum Protect does not support RLVs on xLinux
Data stored on RLVs treated just like DISK or FILE volumes stored on an incompatible fs
Will be moved to tape prior to the migration
Device support needs to be considered : not all devices supported equally across all platforms
Can the existing hw be attached to the existing computer, or will new hw be required?
Determine whether the server uses DISK or FILE storage
If FILE storage is on an NFS or GPFS, make sure that the target computer can access the storage
Ensure that the directories on the source server will be accessible via the same path on the target server
Ensure clients have network connectivity to the target computer
Client Option files: If IP address or port is different, update every client & server option file
If the server is a library client:
Identify the library servers
Path information for the shared libraries & drives needs to be updated on the library server after the migration is over
Three Different Scenarios for DB Migration to Different Platforms
Upgrade from V5 DB from one platform to another as part of a V5 to V6 database upgrade, using the EXTRACTDB/INSERTDB migration utility.
This scenario was implemented in TSM 6.3.4
Moving from a TSM/IBM Spectrum Protect V6/V7 DB from one platform to another when the platforms have the same endianness.
When the two platforms are UNIX variations, and they have the same endianness, database backup and restore can be used to move the database. In this context, Unix means AIX, Solaris, HP-UX, or Linux
Moving an IBM Spectrum Protect DB2 database from one platform to another when the platforms have different endianess.
When scenario 3 is being done, DB backup and restore cannot be used. This is the enhancement being added with this update.
For customers moving from V5 to V6.3.4 or higher, work was started on the migration utilities to make automatically make any adjustments necessary to account for the change in endianness.
This enhancement is a port of the V5 upgrade utilities to work with a DB2 source database. 
With the upgrade utilities in V5 to V6, EXTRACTDB was used from the V5 database and then the INSERTDB utility was used to place the data into a DB2 database. The utilities have been enhanced to allow EXTRACTDB from a DB2 DB (at V7.1.5 or later) and then use INSERTDB (with adjustments for changes in endianness) to allow migration from AIX to xLinux.
Note: the command line utilities must be used. The Upgrade Wizard that was available in V5 cannot be used to perform this cross platform migration from AIX to xLinux.
Supported versions
On the target server, (the one doing the INSERTDB process), changes in endianness are only being made in the IBM Spectrum Protect v7.1.5 and higher server. This means that your target server, if doing a platform migration, must be at a V7.1.5 or higher level. Also, the source and target need to be at the same level for the cross platform migration.
Initially supported paths will be AIX (Big-endian Unix) to Linux for x86_64 via EXTRACTDB/INSERTDB. Note that Windows to Linux for x86_64 or Linux x86_64 to Windows is not supported with this enhancement
Additional platforms can be added if there is sufficient demand.
Migration process
The migration process is very similar to the techniques used in the V5 to V6 extractdb/insertdb utilities.
However, there is one key difference: cross platform migration has to deal with differences between the two platforms.
Disk based storage being managed by the source server (either random access disk or sequential file) might not be accessible on the target system.
As a result, much of the pre- and post-migration process will deal with moving data between disk & tape in order to ensure that client data stored on disk will be available once the migration has finished.
Other issues exist as well, covered on next slide
Many issues to consider; most are documented already as part of existing V5 to V6 migration utilities. Partial list includes:
Review of target DB. The target DB will need at least as much space as the source server DB.
Review of target system server option files. Some options on source system may not be applicable to target options.
Raw Logical Disk Volumes (RLV); TSM/IBM Spectrum Protect does not support RLVs on xLinux. As a result, data stored on RLVs will need to be treated just like DISK or FILE volumes stored on an incompatible file system, and will be moved to tape prior to the migration.
Device support needs to be considered carefully before committing to a cross-platform migration. The TSM/IBM Spectrum Protect server does not support all devices equally across all platforms
Can the existing hardware be attached to the existing computer, or will new hardware be required? In either case, determine how to access the hardware from the target computer (I.e, what is the path to each device from the target computer?).
Determine whether the server uses DISK or FILE storage. If FILE storage is on an NFS server or on a GPFS file system, then make sure that the target computer can access the storage. Also, Identify the directories in which volumes are stored on the source server. Ensure that the directories will be accessible via the same path on the target server.
Ensure clients have network connectivity to the target computer.
On source server, upgrade to V7.1.5 or higher.
On target, install same level of IBM Spectrum Protect as source.
Client Option files: If the IP address of the target computer will be different from the IP address of the source server, or if the target server will use a different TCP/IP port, then plan on updating every client and server with the new address/port.
If the server is a library client, then identify the corresponding library servers. Path information for the shared libraries and drives will need to be updated on the library server after the migration is over.
Other issues will be identified and documented in publications.
Footnote goes here

16. Server - PROTECT STGPOOL Enhancement
PROTECT STGPOOL enhanced to replace damaged extents on target servers
Previously
PROTECT STGPOOL protects all extents in a directory container pool (introduced in 7.1.3)
REPLICATE NODE still needed to replicate object metadata
Extents can become damaged in a number of ways
Disaster to the storage pool, such as loss of drives
Corruption on write to pool, such as loss of power
REPAIR STGPOOL only repaired extents on source (prior to v7.1.5)
Did not repair (replace) or even detect damaged extents on the target server In
AUDIT CONTAINER or client retrieval detect damaged extents and flag them as damaged
PROTECT STGPOOL operation in v synchronously replaces damaged extents on target servers
No new commands or parameters
Queries the target directory container pools to determine which extents are damaged
Target responds to source with identity of damaged extents
Only those extents that have a matching extent on the source
Source finds extents matching those identified as damaged
Replacement extents sent to target
DB inventory mapping cleanup occurs asynchronously after PROTECT STGPOOL completes
New messages: ANR1758I
ANR1758I Repaired <extents> damaged extents in directory container pools.
Explanation: The server repaired the specified number of extents.
System Action: Server operation continues.
User Response: None.
Footnote goes here

17. Server - PROTECT STGPOOL EnhancementIn
Limitations
Source and target replication servers must be level v7.1.5 or above
Repair operation only works with Directory Container pools, not with Cloud Container pools
Repair operation does not detect damaged extents
Extents belonging to encrypted files do not get repaired
No hash value stored for these extents
When using REPLICATE NODE in addition to PROTECT STGPOOL:
REPLICATE NODE can generate unique extents on the target that do not exist on the source
Target extents that are unmatched on the source can not be repaired
New messages: ANR1758I
ANR1758I Repaired <extents> damaged extents in directory container pools.
Explanation: The server repaired the specified number of extents.
System Action: Server operation continues.
User Response: None.
Footnote goes here

18. CLIENT – 7.1.4.x pLinux LE Ubuntu support added
pLinux LE for SLES 12 and RHEL 7 added in 7.1.4
Red Hat Enterprise Linux 7.2 support added
SUSE Linux Enterprise Server support added
vmdatastorethreshold option, introduced on data mover
It is not possible to predict how much space a snapshot will need
Bad things happen when datastores fill-up!
Ensure customers that backup snapshots won’t fill-up datastores to the point that they run out of space
At least have a space threshold that has to be met before a snapshot is initiated for the backup process
Establish policy that says: "in order for DP for VMware to take a backup, ensure my datastores are not above 90% full"
vmdatastorethreshold percent
Each data mover’s option file: vmdatastorethreshold 90
Command line: dsmc backup vm vm1 -vmdatastorethreshold=90
Prevents out-of-space errors during VMware virtual machine backups
Sets the threshold percentage of space usage for each VMware datastore of a virtual machine
If the threshold is exceeded, the virtual machine is not backed up
To prevent out-of-space errors during virtual machine backups, you can set a data
usage threshold for VMware datastores by using the vmdatastorethreshold option.
You use the vmdatastorethreshold option to the set the threshold percentage of
space usage for each VMware datastore of a virtual machine. When you initiate a
virtual machine backup, the client checks the data usage of the VMware datastores
before the virtual machine snapshot is created. If the threshold is exceeded in any
of the VMware datastores, the virtual machine is not backed up.
For example, virtual machine vm1 spans datastore1 and datastore2. You can issue
the following command to ensure that the VMware datastores of a virtual machine
are at most 90% full before the virtual machine is backed up:
dsmc backup vm vm1 -vmdatastorethreshold=90
As a result, the client checks the space usage of both datastore1 and datastore2
before the snapshot operation begins. If the space usage of either VMware
datastore exceeds the 90% threshold, the backup request for vm1 is not started.
Requirements:
v Ensure that the threshold is low enough so that the snapshot does not use up all
the available space in the VMware datastores. Otherwise, you will run out of
space on the VMware datastores and the snapshot will not be created.
v If you use multiple clients that act as data mover nodes, you must add the
vmdatastorethreshold option to the options file for each data mover.
v The client checks the data usage of the VMware datastore that contains the
virtual machine disk snapshots. By default, the snapshots are created in the
same directory as that of the parent virtual disk (.vmdk) file.
If you change the snapshot location to a new directory on the same datastore or
on another datastore with the workingDir option in the VM configuration file,
ensure that the path of the working directory is correct. If the path is incorrect,
the client might validate the data usage of the wrong datastore.
If you use the EXCLUDE.VMDISK option to exclude one or more disks from a backup,
the threshold check is still run on these disks. Even though these disks are not
backed up, VMware still takes a snapshot of these disks.
Independent disks are not checked during space verification processing because a
snapshot of these disks does not use any VMware datastore space.
Footnote goes here

19. HSM – 7.1.4.x Spectrum Protect for Space Management
IBM Spectrum Scale™ 4.2 support added Red Hat Enterprise Linux 7.2 support added SUSE Linux Enterprise Server 12.1 support added
To prevent out-of-space errors during virtual machine backups, you can set a data
usage threshold for VMware datastores by using the vmdatastorethreshold option.
You use the vmdatastorethreshold option to the set the threshold percentage of
space usage for each VMware datastore of a virtual machine. When you initiate a
virtual machine backup, the client checks the data usage of the VMware datastores
before the virtual machine snapshot is created. If the threshold is exceeded in any
of the VMware datastores, the virtual machine is not backed up.
For example, virtual machine vm1 spans datastore1 and datastore2. You can issue
the following command to ensure that the VMware datastores of a virtual machine
are at most 90% full before the virtual machine is backed up:
dsmc backup vm vm1 -vmdatastorethreshold=90
As a result, the client checks the space usage of both datastore1 and datastore2
before the snapshot operation begins. If the space usage of either VMware
datastore exceeds the 90% threshold, the backup request for vm1 is not started.
Requirements:
v Ensure that the threshold is low enough so that the snapshot does not use up all
the available space in the VMware datastores. Otherwise, you will run out of
space on the VMware datastores and the snapshot will not be created.
v If you use multiple clients that act as data mover nodes, you must add the
vmdatastorethreshold option to the options file for each data mover.
v The client checks the data usage of the VMware datastore that contains the
virtual machine disk snapshots. By default, the snapshots are created in the
same directory as that of the parent virtual disk (.vmdk) file.
If you change the snapshot location to a new directory on the same datastore or
on another datastore with the workingDir option in the VM configuration file,
ensure that the path of the working directory is correct. If the path is incorrect,
the client might validate the data usage of the wrong datastore.
If you use the EXCLUDE.VMDISK option to exclude one or more disks from a backup,
the threshold check is still run on these disks. Even though these disks are not
backed up, VMware still takes a snapshot of these disks.
Independent disks are not checked during space verification processing because a
snapshot of these disks does not use any VMware datastore space.
Footnote goes here

20. © Copyright IBM Corporation 2013
Course title
Spectrum Protect Snapshot for Unix Spectrum Scale snapshot and offload
IBM Spectrum Protect Snapshot has supported the creation and management of IBM Spectrum Scale snapshots as local backups since
IBM Spectrum Protect Snapshot allows a media change for backup data through offloading snapshots to an IBM Spectrum Protect server
Calls mmbackup command for offloading
Offload node can be located on any management node of the Spectrum Scale cluster with IBM Spectrum Protect client setup for mmbackup
multiple nodes in the GPFS cluster can be used to perform the offload backup to Spectrum Protect (controlled by mmbackup parameter -N)
© Copyright IBM Corporation 2013

21. Private, Public or Hybrid Cloud
2121
Spectrum Protect Snapshot for Unix Spectrum Scale snapshot and offload
IBM Spectrum Protect Snapshot offload node
acsgen -D -M
IBM Spectrum Scale Cluster
IBM Spectrum Protect server
Private, Public or Hybrid Cloud
Optional
Spectrum Protect backup
integration
IBM Spectrum Protect Snapshot node acsd acsgen -D
fcmcli -D
GPFS filesystem

22. © Copyright IBM Corporation 2013
Course title
Spectrum Protect Snapshot for Unix – SVC Dynamic Target Allocation adapter
Spectrum Protect Snapshot for Unix and earlier requires snapshot target volumes be predefined on SVC based storage systems
Presented to Spectrum Snapshot using .fct file or target volume naming
Spectrum Protect Snapshot for Unix provides the option to dynamically allocate the SVC snapshot target volumes of the FlashCopy
Greatly improves ease of use
Already supported in SPS for VMware
Already supported in SPS for Windows via the VSS Provider
Note: The new adapter – for now – does not replace the old SVC adapter completely because it lacks some of its features:
Remote mirroring support
INCR copy mode (new adapter uses Space Efficient volumes in principle)
SVC based Storage Systems
The IBM System Storage SAN Volume Controller
The IBM Storwize V7000, V5000 and V3700
The IBM Flex System V7000 Storage Node
The IBM Storwize V7000 Unified
The IBM FlashSystems V840 and V9000
© Copyright IBM Corporation 2013

23. Spectrum Snapshot Device Adapter Architecture
The following picture illustrates the architectural overview with the extension for the new SVC adapter using the Spectrum Protect Snapshot Storage device API. The green ellipse shows the new component SVC-DTA – Dynamic Target Allocation adapter.
fcmcima
(DS8k / SVC)
XIV
Adapter
NetApp
SVC-DTA
Java
API
acsd
acsgen
Device
Vendor
/ 3rd Party
BP RocketSoftware
SVC DTA - Dynamic Target Allocation
Hides complexity of FlashCopy target volumes
Eliminates additional .fct file for target volumes
read/write mount of read-only snapshot backups
Non-destructively restores
Static target allocation:
Target Volume File parameter in the profile
...
>>> DEVICE_CLASS STANDARD
TARGET_SETS VOLUMES_FILE
VOLUMES_FILE <ACS_DIR>/volumes_file.fct
<<<
Unified Interface

24. SVC Dynamic Target Allocation Adapter – Unix vs VMware
Added:
Full copy mode (reintroduced FLASHCOPY_TYPE parameter)
Default is NOCOPY for backup DEVICE_CLASSes and COPY for cloning DEVICE_CLASSes
NOCOPY for cloning only allowed in combination with ALLOW_NOCOPY_FLASHCOPY = YES, further restrictions apply
Note: Even though there is also a release for VMware, COPY mode is exclusively available in Spectrum Protect Snapshot Unix
Changed:
Migration scenario is different than Vmware (you can restore older backups via Flashback but it destroys any newer backups)
SVC_CLEAN_RATE is not an official parameter – it is now fixed to 0 for creating backups and fixed to 100 for restore operations
Specifics:
No duplicates created for cloning, the original target volumes are mounted directly

25. Spectrum Protect Snapshot for Unix 4. 1
Spectrum Protect Snapshot for Unix and Spectrum Protect for Enterprise Resource Planning – Oracle 12c Support
Spectrum Protect for Databases supports Oracle 12c
RMAN Media Manager
Spectrum Protect Snapshot Oracle 12c toleration
64-bit Oracle 12c, and later mod levels and fix packs
IBM Spectrum Protect Snapshot does not back up multitenant container databases (CDB) or pluggable databases (PDBs).
Spectrum Protect for Enterprise Resource Planning 7.1.3
Must use 64-bit Oracle 12c and later mod levels and fix packs at a level required by the respective SAP release
Pluggable databases are not supported
See Product All Requirements documents for specific information
Google “<Product Name> All Requirements Document”

26. IBM Spectrum Protect Snapshot 4.1.4 Capacity Data Collection
ftp://public.dhe.ibm.com/storage/tivoli-storage-management/front_end_capacity_measurement_tools
Client Type
Manual Data Collection via Script
Automated Data Collection
Spectrum Protect for VE (VMware)
Spectrum Protect for VE (HyperV)
Spectrum Protect for Mail (Exchange)
Spectrum Protect for Mail (Domino)
Spectrum Protect for DB (SQL)
Spectrum Protect for DB (Oracle)
Spectrum Protect for ERP (SAP HANA)
Spectrum Protect for ERP (DB2)
Spectrum Protect for ERP (Oracle)
Spectrum Protect for Space Management
Spectrum Protect BA Client
YES (Avaliable with Spectrum Protect 7.1.1)
YES to Operations Center (Available with Spectrum Protect 7.1.3)
Spectrum Protect Snapshot for DB2
Spectrum Protect Snapshot for Oracle
Spectrum Protect Snapshot for Oracle (SAP)
Spectrum Protect Snapshot for Custom Applications
Spectrum Protect Snapshot for Microsoft Exchange
Spectrum Protect Snapshot for Microsoft SQL
Spectrum Protect Snapshot for VMware
YES (Available with Spectrum Snapshot Protect 7.1.3)
YES to standalone GUI if applicable (Available in Spectrum Protect Snapshot 4.1.4)

27. IBM Spectrum Protect Snapshot 4.1.4 Capacity Data Collection
Specteum Protect Snapshot for Windows
Use Capacity Licensing property page
XML Report generated after backup
Spectrum Protect Snapshot for Unix
Generated using the fcmcli –f managed_capacity command
XML reports are generated and saved in the <ACS_DIR>/capacity_reports directory
Spectrum Protect Snapshot for Vmware
Use the Reports → Managed Capacity panel to generate capacity metrics reports or with fcmcli –f managed_capacity

28. Spectrum Protect Snapshot for Windows 4. 1. 4
Spectrum Protect Snapshot for Windows x and Spectrum Protect for Mail x Support for Microsoft Exchange Server 2016
Microsoft Exchange Server 2016 supported by Spectrum Protect components
Backup to a Spectrum Protect Server using Spectrum Protect for Mail
Snapshot using Spectrum Protect Snapshot
Cooperative application support for Exchange Server 2016 using Spectrum Protect for Virtual Environments – Data Protection for VMware expected later this year
See Product All Requirements documents for specific information
Google “<Product Name> All Requirements Document”
Mailbox browser is not supported

29. Useful Links
Cyrus’ Spectrum Protect Blog:
Sean’s Spectrum Protect Blog:
Spectrum Protect Technical Enablement Youtube Channels:
EVDP Hands on labs access: contact
© Copyright IBM Corporation 2015

30. © Copyright IBM Corporation 2016