Download Presentations http://ouo.io/XKLUj Student Guide & Best http://ouo.io/8u1RP

1. GPFS 4.1 System Administration
Spectrum Scale (GPFS) 4.1
Functions
(mmbackup, Snapshots, SOBAR),, Quota, Clones and Extended Attributes)
© Copyright IBM Corporation 2014

2. © Copyright IBM Corporation 2015
Course objectives
After completing this course, you should be able to:
• Understand the value and use of mmbackup for Data backups
• Understand the integration of SOBAR with GPFS
• Understand the Snapshots, limitations and best practice
• Understand the use of Quotas
• Understand the use, value and limitation of File Clones
• As well as Extended Attributes.

3. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Backing up data

4. Backing up GPFS with TSM
• Two types of data to back up
– GPFS configuration
– File data
• Configuration
– Cluster configuration
– File System configuration
• File data
– Backup just like any other file system
© Copyright IBM Corporation 2013

5. User exits and what they do
• User exit:
– A user exit is an event triggered script. The script name determines
which event will trigger it’s execution.
• Some user exits:
– mmsdrbackup – backup configuration data on change
– syncfsconfig – runs each time a file system configuration is
changed
– nsddevices – executed on GPFS start during device discovery
© Copyright IBM Corporation 2013

6. Backing up and restoring GPFS File System configuration
• File system information
– These commands allow you to backup and restore file system
configuration.
– Backup up the file system definition
> Usage: mmbackupconfig Device -o OutputFile
– Restore the file system information
– Usage: mmrestoreconfig Device -i InputFile
– [-I {test | yes | continue }] [-Q {yes | no}]
– [-W NewDeviceName] [-z {yes | no}]
© Copyright IBM Corporation 2013

7. Backing up and restoring GPFS cluster
configuration
• Cluster configuration
– The cluster configuration data is stored in the file
/var/mmfs/gen/mmsdrfs
– Backed up using user exit /var/mmfs/etc/mmsdrbackup
– Restore cluster configuration data
• Usage:
• mmsdrrestore [-p NodeName] [-F mmsdrfsFile] [-R
RemoteFileCopyCommand] [-a | -N {Node[,Node...] | NodeFile |
NodeClass}]
© Copyright IBM Corporation 2013

8. Backing up data with Tivoli Storage Manager
• Backup up data using mmbackup
– Uses Policy engine for inode scan
– Takes snapshot
Usage:
mmbackup {Device|Directory} [-t {full|incremental}]
[-N {Node[,Node...] | NodeFile | NodeClass}]
[-g GlobalWorkDirectory ] [-s LocalWorkDirectory]
[-S SnapshotName] [-f]
• This Only works with IBM Tivoli Storage Manager (TSM).
© Copyright IBM Corporation 2013

9. Building backup work lists for 3rd
party backups
• As mentioned, you can use the mmbackup command to back
up the files of a GPFS file system to a Tivoli® Storage Manager
(TSM) server.
• Alternatively, you can utilize the GPFS policy engine
(mmapplypolicy command) to generate lists of files to be
backed up and provide them as input to some other external
storage manager.
• So you can generate lists with GPFS policy engine that provide
the work list for an external backup system (non TSM), that has
mount privileges to the file system to know what needs to be
backed up.
© Copyright IBM Corporation 2014

10. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Scale out Backup and Recovery (SOBAR)
SOBAR

11. 11
GPFS Scale Out Backup and Recovery
• SOBAR Relies on two well integrated components
– TSM HSM capability to premigrate files
– GPFS capability to dump file system image
• TSM HSM integrates with GPFS policy engine
– Allows to premigrate files (backup) which have
changed in between „backup“ cycles
– Versioning is not possible
• GPFS file system image includes all file system
metadata (inodes, etc)
– File system image is backed up to TSM
• For recovery the file system image is re-applied to
a new GPFS file system
– All data appears migrated and can be recalled
• SOBAR provides disaster protection
– Backup data resides in TSM server
GPFS Cluster
TSM Servers
Tape
LAN
TSM HSM
SOBAR

12. 12
• Recovery of the GPFS file system includes all directories and files in stub
format
– Most recent files can be selectively recalled
• High backup scalability:
– Leverages GPFS policy engine for fast file identifcation
– Files are “backed“ up incrementally forever
• High restore performance
– Only file metadata is applied without transferring file data
– File data resides on the TSM Server and recall happens on demand
• Lifts the ACL/Extended Attribute limitation of the TSM Server.
– Because Complete inode information is part of the image file.
• Requires TSM HSM and Backup client to be licensed and installed
• No versioning possible
GPFS SOBAR Characteristics

13. 13
stub
Object ID
(DMAPI handle)
TSM Server
file
migrated
Object ID
(DMAPI handle)
filepremigrated
stub
Object ID (new
DMAPI handle)
after
Image restore
migstate=yes
file
file
premigrate
migrate
recall
HSM Client on GPFS cluster
TSM HSM file states
File HSM state
recall
resident file

14. 14
Scale Out Backup And Restore – Backup process
File Data
Directory Data &
Directory Tree Relation
Metadata
(Inode & ACL)
File System and Cluster
Configuration Data
Continously:
Premigrate all file data
to TSM Server using
TSM for Space Management
and GPFS policy engine
Backup Step 1:
Collect and backup
file system configuration
to TSM Server using
TSM Client
Backup Step 2:
Create file system
image files and
Backup to TSM
Server using TSM
Client
TSM Server

15. 15
Scale Out Backup And Restore – Recovery process
File Data
Directory Data &
Directory Tree Relation
Metadata
(Inode & ACL)
File System and Cluster
Configuration Data
Recovery Step 1:
Restore file system
configuration
And recreate files
system manually
TSM Server
Recovery Step 2:
Mount file system and
restore file system
image files from TSM
Server
Automatically recreate
file system metadata
and directory tree
Recovery Step 3:
Enable space management and start
production.
Recall file data (on demand & background
using GPFS policy engine)

16. © Copyright IBM Corporation 2014
This slide provides a detailed example of the backup procedure used with SOBAR.
Throughout these sample procedures, the sample file system used is called smallfs.
1.Backup the cluster configuration information.
2.Preserve disk configuration information.
3.Backup the GPFS™ file system configuration information.
mmbackupconfig smallfs -o /tmp/smallfs.bkpcfg.out925
4.Pre-migrate all newer file data into secondary storage.
dsmmigrate -Premigrate -Recursive /smallfs
To optionally check the status of the files that were pre-migrated with the previous command,
use the following command:
dsmls /smallfs/*
1.Create a global snapshot of the live file system, to provide a quiescent image for image
backup, using a command similar to the following:
mmcrsnapshot smallfs smallfssnap
•Choose a staging area in which to save the GPFS metadata image files.
•Backup the file system image.
mmimgbackup smallfs -S smallfssnap -g /u/user/backup -N aixnodes
•After the image backup is complete, delete the snapshot used for backup with the
following command:
mmdelsnapshot smallfs smallfssnap

17. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Snapshots

18. Snapshots: Overview
• Context
– File system
– Fileset (independent file sets)
• A logical, read-only copy of the file system or fileset at a point in
time.
• Typical uses
– To run a file system backup on a consistent state of the file system
– On-line access to previous file system state
• Protect data from user errors.
• Space efficient
– Redirect-on-write: A file in a snapshot does not occupy disk space until the file
is modified or deleted, and at that time it only consumes the changed blocks.
– Fast snapshot create.
• Maximum of 256 outstanding snapshots for a file system or file set
© Copyright IBM Corporation 2013

19. Snapshot administration
• Create a snapshot
Usage: mmcrsnapshot Device Directory [-j Fileset]
• Viewing snapshot information
mmlssnapshot Device [-d [--block-size {BlockSize | auto}]] [-s {all
| global | Snapshot[,Snapshot...]} | -j Fileset[,Fileset...]]
• Delete a snapshot
– -N parameter allows for faster delete of snapshot
Usage: mmdelsnapshot Device Directory [-N {Node[,Node...]
| NodeFile | NodeClass}]
• Restore a file system from a snapshot
– Most of the time restore from snapshot is partial using file system
commands to copy from snapshot directory to active area
– To restore the entire file system from a snapshot
Usage: mmrestorefs Device Directory [-c]
© Copyright IBM Corporation 2013

20. Accessing snapshot data
• Accessing snapshot data
– Snapshots are accessible through .snapshots sub-directory in file
system root directory, for example:
/gpfs/.snapshots/snap1 – last week’s snapshot
/gpfs/.snapshots/snap2 – yesterday’s snapshot
• Changing access path
– Change the name of the .snapshots directory
– Create a link to access snapshot in each subdirectory
mmsnapdir Device {[-r | -a] [-s SnapDirName]}
or
mmsnapdir Device [-q]
© Copyright IBM Corporation 2013

21. 21
Comparison of GPFS backup methods
Characteristic Snapshot mmbackup SOBAR
RTO Recovery Time Objective Low High (reading tape) Medium (partial tape read –
on demand)
RPO Recovery Point Objective Low Medium - High Medium
Backup window Low High Medium
Versioning Yes (multiple Snapshots) Yes No (stubbed)
Disaster protected No Yes Yes
Complete restore Yes Maybe Yes
Backup to tape No Yes Yes
Integration with ILM No Yes Yes

22. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Clones

23. Clones
• A Clone is a “writeable” snapshot of a file or files
– Similar to creating a copy of a file or files
– Cloning is much faster than copying a file
• Because no additional disk space is consumed until the clone or the original
file is modified (it does not rewrite the blocks of the file), but rather captures
and copies the point in time reference of the metadata.
• Only when blocks are changed in the source or the clone is data
actually written.
– In this way, Snapshots and Clones are “Space Efficient”.
© Copyright IBM Corporation 2013

24. Why would I need Clones?
• If you have limited disk space available
– Perhaps because you don’t have much disk space
– Possibly because you are under tight quotas
• Example
– Cloning can be used for large QA/Test or Development groups
• A Master build tree can be created
• Hundreds of Developers can then all clone the Master build tree without
using any additional space until files change.
It is possible to use the mmclone command to split a file clone from a
clone parent (creating two full copies).
© Copyright IBM Corporation 2013
•Using the mmclone redirect command to split the file clone from the immediate clone parent only. The
clone child remains a file clone, but the clone parent can be deleted.
•Using the mmclone split command to split the file clone from all clone parents. This converts the former
clone child to a regular file. The clone parent does not change.

25. Creating Clones
• File clones can be created from a regular file or a file in a
snapshot using the mmclone command.
• To create a read-only snapshot of a file to be cloned issue:
– mmclone snap file1 snap1
• This creates a clone parent called snap1 of the original file file1
• To create a writeable clone copy clone parent issue:
– mmclone copy snap1 file2
• This creates a writeable file clone called file2 from the clone parent snap1
© Copyright IBM Corporation 2013

26. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
File System Quotas

27. File System quotas
• The GPFS quota system controls
– Number of files (inodes)
– Number data blocks (# of bytes)
• GPFS quotas can be defined on
– Individual users
– Groups of users
– Individual filesets
• Two approaches to quotas
– Enforced (traditional)
– Usage reports
• GPFS policy engine
• Write your own /usr/lpp/mmfs/samples/util/tsgetusage
© Copyright IBM Corporation 2013

28. Setting up quotas
© Copyright IBM Corporation 2013

29. Enabling quotas on a file system
• File System parameter –Q
– mmcrfs or mmchfs
• Enabling quota on a new file system
– Set file system –Q parameter on creation
– Mount the file system
• Enabling quota on an existing file system
– Set file system parameter (-Q)
– Collect inode and disk block statistics for the file system
(mmcheckquota)
– Note that on a large file system mmcheckquota can be a GPFS Scan
engine intensive operation, and it may be best to choose and off peak
time to run the command.
© Copyright IBM Corporation 2013

30. Establishing default quota
• Setting default quotas
– Enabled via mmdefquotaon
mmdefquotaon [-u] [-g] [-j] [-v] [-d] {Device[ Device...] | -a}
– Values set via mmdefedquota
mmdefedquota {-u | -g | -j} Device
• Using the gpfs_quotactl( ) subroutine.
– Manipulates disks quotas on file systems
© Copyright IBM Corporation 2013

31. Setting Individual quotas
• Quotas are set using the mmedquota command
• Use mmedquota to set quotas for user, groups or filesets
mmedquota {-u [-p [ProtoFileset:]ProtoUser] [Device:Fileset:]User ... |
-g [-p [ProtoFileset:]ProtoGroup]
[Device:Fileset:]Group ... |
-j [-p ProtoFileset] Device:Fileset ... |
-d {-u User ... | -g Group ... | -j Device:Fileset ...} |
-t {-u | -g | -j}}
Confirm using mmrepquota command
• Example – Edit quota for user user1
# mmedquota –u user1
*** Edit quota limits for USR tests
NOTE: block limits will be rounded up to the next multiple of the block size.
block units may be: K, M, or G.
fs1: blocks in use: 0K, limits (soft = 0K, hard = 0K)
inodes in use: 0, limits (soft = 0, hard = 0)
mmedquota launches
your default editor.
© Copyright IBM Corporation 2015

32. Report Quota Usage
•mmrepquota command
• Usage:
mmrepquota [-u] [-g] [-j] [-e] [-q] [-n] [-v]
[--block-size {BlockSize | auto}]
{-a | Device[:Fileset] ...}
• Example
# mmrepquota fs1
Block Limits | File Limits
Name type KB quota limit in_doubt grace | files quota limit in_doubt grace
root USR 8 0 0 0 none | 1 0 0 0 none
user10 USR 0 307200 1048576 0 none | 0 0 0 0 none
root GRP 8 0 0 0 none | 1 0 0 0 none
root FILESET 8 0 0 0 none | 1 0 0 0 none
© Copyright IBM Corporation 2013

33. Report Quota Usage
© Copyright IBM Corporation 2013
The mmlsquota command displays the file system quota
limits, default quota limits, and current usage information.
If the scope of quota limit enforcement is the entire file
system, mmlsquota -u or mmlsquota -g will list all
instances of the same user or group on different GPFS™
file systems.
If the quota enforcement is on a per-fileset basis,
mmlsquota -u or mmlsquota -g will list all instances of the
same user or group on different filesets on different GPFS
file systems.

34. Course materials may not be reproduced in whole or in part without the prior written permission of IBM. 8.0
Notes on TSM & HSM & Extended Attributes

35. Notes on TSM & HSM
© Copyright IBM Corporation 2014

36. Extended Attributes
© Copyright IBM Corporation 2014
To show extended attribute names and values for the file /ba1/newfile,
Issue this command:
mmlsattr -d -L /ba1/newfile
The system displays information similar to:
file name: /ba1/newfile
metadata replication: 1 max 2
data replication: 1 max 2
immutable: no
appendOnly: no
flags: directio
storage pool name: system
fileset name: root
snapshot name:
creation time: Wed Feb 22 15:16:29 2012
Windows attributes: ARCHIVE
user.attr1: "value1"
user.attr: "val1"
gpfs.DIRECTIO: "1"
user.ea1: "value1"

37. Extended Attributes
© Copyright IBM Corporation 2014
To show extended attribute names and values for the file,
For HSM / EA point of view, a Resident file looks like this:
(Note: these next samples from 3 different files!)
[root@melbssonas.mgmt001st001 demo1]# mmlsattr -d -L cacheTestfile2.txt
file name: cacheTestfile2.txt
metadata replication: 1 max 2
data replication: 1 max 2
immutable: no
appendOnly: no
flags:
storage pool name: system
fileset name: demo1
snapshot name:
creation time: Fri Feb 20 09:28:25 2015
Windows attributes: ARCHIVE

38. Extended Attributes
© Copyright IBM Corporation 2014
An HSM Migrated File looks like this:
[root@melbssonas.mgmt001st001 demo1]# mmlsattr -d -L homeTestfile2.txt
file name: homeTestfile2.txt
metadata replication: 1 max 2
data replication: 1 max 2
immutable: no
appendOnly: no
flags:
storage pool name: system
fileset name: demo1
snapshot name:
creation time: Fri Feb 20 09:27:13 2015
Windows attributes: ARCHIVE OFFLINE
dmapi.IBMObj: "???????????????s??P?K?????
#????????????????????????????????????????????????????????????? ????
0?????????C????????????????????"
dmapi.IBMexID:
"0101020C000000001FAC0288D1F7107301DF50A24B9DA6841781239F?"
gpfs.dmapi.region: 0x000000000000000000000000000000000700000000000000
[root@melbssonas.mgmt001st001 demo1]

39. Extended Attributes
© Copyright IBM Corporation 2014
An HSM PreMigrated file looks like this:
[root@melbssonas.mgmt001st001 demo1]# mmlsattr -d -L homeTestfile1.txt
file name: homeTestfile1.txt
metadata replication: 1 max 2
data replication: 1 max 2
immutable: no
appendOnly: no
flags:
storage pool name: system
fileset name: demo1
snapshot name:
creation time: Fri Feb 20 09:27:08 2015
Windows attributes: ARCHIVE
gpfs.dmapi.region: 0x0000000000000000000000000000000006000000FF7F0000
dmapi.IBMPMig: "????????????~??s??????`F%???"
dmapi.IBMexID:
"0101020C000000001FAC02847ED310730001E8C5B6CC604625E0978B?"

40. Questions on
Backups,SOBAR Snapshots, Clones,
Questions
© Copyright IBM Corporation 2013