12.07.2015 Views

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

IBM Tivoli Storage Manager for UNIX and Linux Backup-Archive ...

SHOW MORE
SHOW LESS
  • No tags were found...

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

file system is available to other system applications. This is the default <strong>for</strong> filesystems residing on logical volumes created by the <strong>Linux</strong> Logical Volume<strong>Manager</strong>. Valid <strong>for</strong> <strong>Linux</strong> clients only.NONESpecifies that you do not want to per<strong>for</strong>m a snapshot-based image backupoperation. This will per<strong>for</strong>m a static image backup operation using thespecified file system. This is the default <strong>for</strong> file systems other than AIX JFS2<strong>and</strong> <strong>Linux</strong> LVM.ExamplesOptions file:snapshotprovideri JFS2include.image /kalafs1 snapshotprovideri=JFS2Comm<strong>and</strong> line:-snapshotprovideri=NONESnapshotrootUse the snapshotroot option with the incremental, selective, orarchive comm<strong>and</strong>sin conjunction with a third-party application that provides a snapshot of a logicalvolume, to associate the data on the local snapshot with the real file space datathat is stored on the <strong>Tivoli</strong> <strong>Storage</strong> <strong>Manager</strong> server.The snapshotroot option can be used to back up NFS mounted file systems. Boththe back up specification (source) <strong>and</strong> the snapshotroot value can be a NFSmounted file specification. For example, the snapshotroot option can be used toback up a NFS file system hosted on a network-attached storage (NAS) thatsupports snapshot.This option should be used with an incremental backup of a NAS filer volumeinstead of a simple incremental or incremental with snapshotroot option wheneverthe NAS filer is running ONTAP V7.3 <strong>for</strong> per<strong>for</strong>mance reasons. The snapdiff <strong>and</strong>snapshotroot options should not be used together.In the following example, filesystem test495 is NFS-mounted from a NAS filerphilo <strong>and</strong> /philo/test945/.snapshot/backupsnap represents the snapshot createdat the NAS filer.dsmc i /philo/test945 -snapshotroot=/philo/test945/.snapshot/backupsnapYou can also specify a directory with the snapshotroot option when backing upeach fileset as a separate file space.The snapshotroot option does not provide any facilities to take a volume snapshot,only to manage data created by a volume snapshot.For example, consider an application that takes a snapshot of the /usr file system<strong>and</strong> mounts it as /snapshot/day1. If you back up this data using the followingcomm<strong>and</strong>, a unique file space called /snapshot/day1 is created on the server.dsmc incremental /snapshot/day1Chapter 10. Using processing options 405

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!