How to Remove Document Management Hurdles with X-Docs?
Disaster Recovery using Spectrum Scale Active File Management
1. IBM Systems
Technical Symposium
A Disaster Recovery
Solution using
Spectrum Scale with
Active File
Management
Trishali Nayar
(Spectrum Scale
Development)
2. Please note
• 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.
• Performance is based on measurements and projections using standard IBM benchmarks in
a controlled environment. The actual throughput or performance that any user will
experience will vary depending upon many factors, including considerations such as
the amount of multiprogramming in the user’s job stream,
the I/O configuration, the storage configuration, and the workload processed. Therefore, no
assurance can be given that an individual user will achieve results similar to those
stated here.
3. Introduction
• Spectrum Scale is a fast, scalable and complete storage
solution for today’s data-intensive enterprise.
• Integrated tools designed to help organizations manage
petabytes of data and millions of files.
• Active File Management is a clustered file system cache,
using the underlying file system.
• Moves data on demand, periodically and continuously
which makes it extremely flexible.
• Helps increase global collaboration and immensely
increases data availability.
5. Disaster Recovery
Primary and Secondary
• AFM can be used for disaster recovery (DR) solutions and there are
2 sites/clusters in this case.
• These two sites can be considered as the Production and DR sites.
• Both these sites have the entire data on them.
• The AFM modes useful for DR are called primary and secondary
filesets.
Note: AFM DR feature is disabled by default and customers need
to review the deployment with the Spectrum Scale development
for approval.
6. Disaster Recovery
Primary and Secondary Modes
• The primary site/fileset (RW, Active) can exclusively create or
writes data.
• The secondary site/fileset (RO, Passive) cannot modify the data.
• AFM DR has a mandatory 1:1 mapping between primary and
secondary filesets. This ensures that only a particular primary
can talk to a secondary.
8. Disaster Recovery
Failover
An operational mode in which the functions of a system component (such as a
server/network) are assumed by secondary system components when the
primary component becomes unavailable through either failure or scheduled
down time.
Failback
The process of restoring operations and applications to the primary facility after
they had been moved to a secondary machine or facility during failover.
Recovery Point Objective (RPO)
The interval indicating the amount of data loss which can be tolerated in the
event of failures or disasters.
Recovery time objective (RTO)
The amount of time it takes for an application to fail over when a disaster
occurs.
9. Primary site goes down
Client
AFM
(configured as primary)
AFM
(configured as
secondary)
Push all updates
asynchronously
Client switches to
secondary on failure
10. Failover to acting primary
NAS client
AFM
(was configured as
primary)
AFM
(configured as
secondary is now acting
primary)
Client switches to
secondary on failure
11. Failback when old primary comes back
NAS client
AFM
(configured as primary)
AFM
(configured as
secondary)
Push all updates
asynchronously
12. mmpsnap
• Apart from automatic RPO snapshots, admins can create user
snapshots using mmpsnap create command with -rpo option.
• When a failure occurs on the primary the customer may need to
roll back to the last consistent snapshot present on the
secondary, while converting it into acting primary.
• When applications are moved to the acting primary, RPO
snapshots are not taken. So RPO will not be applicable on
acting primary.
13. Planned Maintenance
Primary site needs to go down for planned maintenance.
1. Create a RPO snapshot to sync both the sites.
2. Initiate a failover and move over the applications.
3. Start a failback
• Start
• Applyupdates
• Stop
14. Role Reversal – possible with some steps
NAS client
AFM
(old primary becomes
the new secondary)
AFM
(configured as acting
primary becomes the
new primary)
Push all updates
asynchronously
17. Notice and disclaimers continued
Information concerning non-IBM products was obtained from the
suppliers of those products, their published announcements or
other publicly available sources. IBM has not tested those
products in connection with this publication and cannot confirm
the accuracy of performance, compatibility or any other claims
related to non-IBM products. Questions on the capabilities of
non-IBM products should be addressed to the suppliers of those
products. IBM does not warrant the quality of any third-party
products, or the ability of any such third-party products to
interoperate with IBM’s products. IBM expressly disclaims all
warranties, expressed or implied, including but not limited
to, the implied warranties of merchantability and fitness for
a particular, purpose.
The provision of the information contained herein is not intended
to, and does not, grant any right or license under any IBM
patents, copyrights, trademarks or other intellectual
property right.
IBM, the IBM logo, ibm.com, AIX, BigInsights, Bluemix, CICS,
Easy Tier, FlashCopy, FlashSystem, GDPS, GPFS,
Guardium, HyperSwap, IBM Cloud Managed Services, IBM
Elastic Storage, IBM FlashCore, IBM FlashSystem, IBM
MobileFirst, IBM Power Systems, IBM PureSystems, IBM
Spectrum, IBM Spectrum Accelerate, IBM Spectrum Archive,
IBM Spectrum Control, IBM Spectrum Protect, IBM Spectrum
Scale, IBM Spectrum Storage, IBM Spectrum Virtualize, IBM
Watson, IBM z Systems, IBM z13, IMS, InfoSphere, Linear
Tape File System, OMEGAMON, OpenPower, Parallel
Sysplex, Power, POWER, POWER4, POWER7, POWER8,
Power Series, Power Systems, Power Systems Software,
PowerHA, PowerLinux, PowerVM, PureApplica- tion, RACF,
Real-time Compression, Redbooks, RMF, SPSS, Storwize,
Symphony, SystemMirror, System Storage, Tivoli,
WebSphere, XIV, z Systems, z/OS, z/VM, z/VSE, zEnterprise
and zSecure are trademarks of International Business
Machines Corporation, registered in many jurisdictions
worldwide. Other product and service names might
be trademarks of IBM or other companies. A current list of
IBM trademarks is available on the Web at "Copyright and
trademark information" at:
www.ibm.com/legal/copytrade.shtml.
Linux is a registered trademark of Linus Torvalds in the United
States, other countries, or both. Java and all Java-based
trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.