Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

IBM Tivoli Storage Manager V7.1 > TSM V7.1 Node Replication > Flashcards

TSM V7.1 Node Replication Flashcards

1
Q

At what version level of TSM was Node Replication introduced?

A

V6.3

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Which function was added to Node Replication in TSM V7.1?

A

automatic failover

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

if the automatic failover feature is configured what functionality ia available to the TSM client when the first server goes down and the client is automatically redirected to the target (2nd) server?

A

restore and retrieve only (in the backup/archive GUI the backup/archive options are greyed out)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What level of TSM is necessary on all participants (servers and clients) for automatic failure to be possible?

A

clients and servers at level V7.1 .

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

what additional parameter needs to be set for automatic failover functionality to be added to the already configured (and working properly!) node replication environment?

A

tsmserver1>set failoverhladdress server2

the client option file then also gets automatically updated

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Can 1 server be both a target and a source replication server?

A

Yes, A server can function as the source of replicated data for some client nodes and as the target of replicated data for other client nodes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

what types of data can be replicated? (3)

A
  • backup (inactive and active)
  • archive
  • Space managed (HSM data that hasmigrated to the source server)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What levels of TSM are required for node replication?

A

server: TSM V6.3+
client: TSM V6.3 or earlier

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Can the Operating System of source and target be different?

A

Yes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Does the storage pool layout of source and target have to be the same?

A

No, e.g: the data of 2 source storage pools may be stored in 1 stgpool on the target…

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

How about deduplication and node replication?

A

Node replication is deduplication-aware

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Is SSL supported for node replication communication?

A

Yes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Can data be replicated more than once?

A

No, the data is replicated to the target and cannot be replicated to another server after that. Also it is not possible to replicate the same object to multiple servers

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Command set to create the server definitions (with crossdefine)
Source : server-a
Target: server-b

A 
1)on target server (server_b):
set servername server_b
set serverpassword mylife
set serverhladdress 9.115.20.80
set serverlladdress 1860
set crossdefine on
2)on source server (server_a):
set servername server_a
set serverpassword yourlife
set serverhladdress 9.115.20.97
set serverlladdress 1500

3)on server_a (source):
define server server_b hladdress=9.115.20.80 lladdress=1860 serverpassword=mylife crossdefine=yes

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

Node replication configuration: the server definitions have been created, what is the next step? (+ command)

A

set the default replication server on the source server:

tsm>set replserver server_b

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What command is used to show the default replication server and replication settings?

A

tsm>query status
…
Server host name or IP address: 9.115.44.121
Server TCP/IP port number: 5511
Server URL:
Crossdefine: Off
…
OutBound Replication: Enabled
Server Password Set: Yes
Target Replication Server: DRSERVER
Default Replication Rule for Backup: ALL_DATA
Default Replication Rule for Archive: ALL_DATA
Default Replication Rule for Space Managed: ALL_DATA
Replication Record Retention Period: 14 Day(s)
…

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

What is the default number of days that replication records are kept in the TSM database of the source server? How can I change that value?

A

30 days

tsm>set replretention 10

18
Q

10 steps (in words) to configure node replication

A
  1. Create the server definitions on the source and target servers
  2. Set the default target replication server
  3. Setup policy and storage hierarchy on the target server
  4. Determine nodes and filespace data to replicate
  5. Configure nodes for replication
  6. Modify filespace, node or server replication rules if needed
  7. Validate replication rules (VALIDATE REPLICATION command)
  8. Perform replication (REPLICATE NODE command)
  9. Verify results (QUERY REPLICATION command)
  10. Monitor replication (QUERY REPLNODE command)
19
Q

How about setting policies on source and target server

A

keep them the same (recommended)

20
Q

How does the target server know which policy to use for the data that is being sent by the source?

A

The REPLICATE NODE command includes the management class specification. If the management class is also found on the target (same name) it is used, otherwise the default mgmtclass is used.

21
Q

How about version control and retention?

A

It is managed by the source server.

22
Q

Replication rules can be set at 3 different levels, which ones?

A

-filespace level (update filespace … replrule=)
when default then:
-node level (update node… bkreplruledefault=…, arreplruledefault=…,spreplruledefault=…

when both node and filespace are default then:

-server level (set bkreplruledefault all_data, set arreplruledefault all_data, set spreplruledefault all_data )

23
Q

6 possible settings for replication rules, which ones?

A 
all_data
all_data_high_priority
active_data (backup rule only)
active_data_high_priority (backup rule only)
default
none
24
Q

How can you delete the data in a filespace from a target server?

A

on the source server:
tsm>update filespace node1 /b replstate=purgedata
note: after data in filespace is deleted, automaticcaly the replstate for this filespace is set to disabled to prevent further replication.

25
Q

How do you enable a node for replication?

A

update node … replstate=enable

parameter is optional, if not specified it means not ready for replication

26
Q

if the target node does not exist on the target server, when/how is it created?

A

autmatically when the first replication occurs (with “replicate node” )

27
Q

the replmode parameter (for update node) is often managed by TSM itself, in what scenarion do you have to define a value for it manually?

A

when data has been partially exported/imported to the target server (in order to populate the target server fast).
Then you want to sync the data of the source (syncsend) and target (syncreceive) server.

28
Q

What happens automatically after you issue the >set replserver command?

A

The default replication rules (BK/AR/SPREPLRULEDEFAULTare set to ALL_DATA at the server level .

29
Q

How can you determine whether a client node is enabled for node replication?

A

tsm>query node

30
Q

How can you test your replication rule settings (+ replication connection) for your nodes?

A

tsm>validate replication node1,node2,node3 verifyconnection=yes

31
Q

example of replicate node command:

A

> replicate node node1 datatype=backupactive,archive priority=high

32
Q

replicate node cmd: datatype parameter: which values? (5)

A

all, backup, backupactive, archive, spacemanaged

33
Q

replicate node cmd: priority parameter, which values?

A

all,high, normal

34
Q

replicate node cmd: what happens if you specify”preview=yes” and the data was never before replicated?

A

The node and filespace definitions are created on the target server

35
Q

tsm>cancel replication :function?

A

cancel all replication processes

36
Q

tsm>remove replnode node1 :what happens?

A
  • the replstate for the node is set to none.
  • can be issued on both target and source
  • data is not deleted
  • after this, the target may receive backup/archive/sp data from the node
37
Q

Command to show the number of client files stored on replication servers.
What if the output shows an empty “target server” field?

A

tsm>query replnode node1

target server field is empty if a replication was never completed.

38
Q

Cmd to show the details about all/running /ended/failed/

replication processes for a node?

A

tsm>query replication node1 f=d

39
Q

How do you check whether replication is enabled for the source server?

A

> q status [check : oubound replication setting]

40
Q

If the server is not enabled for replication, how do you set it?

A

tsm>enable replication

41
Q

How do I disable any further replication for the 9source) server?

A

tsm>disable replication [note: running replication processes will keep running till they are completed]

IBM Tivoli Storage Manager V7.1 (9 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2024 Bold Learning Solutions. Terms and Conditions