Dump and Load with Multiple Stripes

When multiple stripes are used with dump database or dump transaction, each stripe creates a separate backup object at the TSM.

You can use the same or different backup object names for multiple stripes when TSM handles the backup media. In this example, each stripe has the same name. TSM uses a low-level identifier to distinguish between each backup object, for example, obj.2. See the error log later in this section.

Using the same object name for each stripe

For example, to dump “testdb” using multiple stripes with the same stripe object name “obj”, enter:
dump database testdb to "syb_tsm::obj" 
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"

In this example, Backup Server provides uniqueness for TSM backup objects by appending the stripe identifier to the supplied backup object name “obj”. Check the Backup Server error log to verify that the TSM low-level backup object name is unique for each stripe.

Backup Server prints:
Backup Server session id is: 5. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj::00'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj::01'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj::02'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj::03'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj::04'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740CDAD ' section number 1 mounted on byte stream 'syb_tsm::obj::03'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740CDAD ' section number 1 mounted on byte stream 'syb_tsm::obj::00'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740CDAD ' section number 1 mounted on byte stream 'syb_tsm::obj::01'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740CDAD ' section number 1 mounted on byte stream 'syb_tsm::obj::02'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740CDAD ' section number 1 mounted on byte stream 'syb_tsm::obj::04'
Backup Server: 4.188.1.1: Database testdb: 24 kilobytes (87%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 106 kilobytes (88%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 646 kilobytes (97%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 760 kilobytes (99%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 874 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database testdb: 898 kilobytes (100%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database testdb).

Check the Backup Server error log to see the TSM backup object names and IDs. Check the complete Backup Server error log attached as well. The Backup Server displays this information:

Oct  1 14:37:43 2009: A00: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj.0,  Copyids: (0, 80898).
Oct  1 14:37:43 2009: A03: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj.3,  Copyids: (0, 80897).
Oct  1 14:37:43 2009: A02: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj.2,  Copyids: (0, 80899).
Oct  1 14:37:43 2009: A01: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj.1,  Copyids: (0, 80900).
To load “obj” to the same database, enter:
load database testdb from "syb_tsm::obj" 
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"
stripe on "syb_tsm::obj"

Using different object names for each stripe

To dump “testdb” using multiple stripes with different strip object names, enter:

dump database testdb to "syb_tsm::obj0"
stripe on "syb_tsm_obj1"
stripe on "syb_tsm_obj2"
stripe on "syb_tsm_obj3"
stripe on "syb_tsm_obj4"

In this example, each stripe has a unique backup object name; Backup Server appends a stripe identifier to each one.

Backup Server prints:
Backup Server session id is: 13. Use this value when executing the 'sp_volchanged' system stored procedure after fulfilling any volume change request from the Backup Server.
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj0::00'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj1::01'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj2::02'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj3::03'
Backup Server: 4.132.1.1: Attempting to open byte stream device: 'syb_tsm::obj4::04'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740D1A6 ' section number 1 mounted on byte stream 'syb_tsm::obj1::01'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740D1A6 ' section number 1 mounted on byte stream 'syb_tsm::obj0::00'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740D1A6 ' section number 1 mounted on byte stream 'syb_tsm::obj3::03'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740D1A6 ' section number 1 mounted on byte stream 'syb_tsm::obj4::04'
Backup Server: 6.28.1.1: Dumpfile name 'testdb092740D1A6 ' section number 1 mounted on byte stream 'syb_tsm::obj2::02'
Backup Server: 4.188.1.1: Database testdb: 24 kilobytes (87%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 106 kilobytes (88%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 220 kilobytes (90%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 334 kilobytes (92%) DUMPED.
Backup Server: 4.188.1.1: Database testdb: 874 kilobytes (100%) DUMPED.
Backup Server: 3.43.1.1: Dump phase number 1 completed.
Backup Server: 3.43.1.1: Dump phase number 2 completed.
Backup Server: 3.43.1.1: Dump phase number 3 completed.
Backup Server: 4.188.1.1: Database testdb: 898 kilobytes (100%) DUMPED.
Backup Server: 3.42.1.1: DUMP is complete (database testdb).
The Backup Server error log displays the TSM backup object name and its IDs.
Oct  1 14:54:33 2009: A00: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj0.0,  Copyids: (0, 80904).
Oct  1 14:54:33 2009: A03: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj3.3,  Copyids: (0, 80903).
Oct  1 14:54:33 2009: A02: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj2.2,  Copyids: (0, 80905).
Oct  1 14:54:33 2009: A01: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj1.1,  Copyids: (0, 80902).
Oct  1 14:54:33 2009: A04: Database 'testdb' dumped. Tivoli Storage Manager backup object name: fs = /demo_srv1, high = /testdb.DB, low = /obj4.4,  Copyids: (0, 80906).
Oct  1 14:54:34 2009: Backup Server: 3.42.1.1: DUMP is complete (database testdb).
To load this dump to the same database, enter:
load database testdb from  "syb_tsm::obj0"
stripe on "syb_tsm::obj1"
stripe on "syb_tsm::obj2"
stripe on "syb_tsm::obj3"
stripe on "syb_tsm::obj4"