Troubleshooting remote replication – HP StoreAll Storage User Manual

Page 270

–

is for a device

–

is for a special file (for example, named sockets and First Ins, First Outs (FIFOs)).

◦

The other letters in the %i string are the actual letters that are outputted if the associated
attribute for the file is being updated or a dot (.) for no change. Three exceptions to this
are the following:

–

A newly created item replaces each letter with a plus sign (+)

–

An identical item replaces the dots with spaces.

–

An unknown attribute replaces each letter with a question mark (?). This situation
can happen when talking to an older version of ibrcfrworker.

The attribute that is associated with each letter is as follows:

–

means the checksum of the file is different and will be updated by the file transfer

(requires -checksum and is not used in StoreAll version 6.0 or later).

–

means the size of the file is different and will be updated by the file transfer.

–

means the modification time is different and is being updated to the sender’s value

(requires --times). An alternate value of T means that the time will be set to the transfer
time (without --times).

–

means the permissions are different and are being updated to the sender’s value

(requires --permissions).

–

means the owner is different and is being updated to the sender’s value (requires

--owner and super-user privileges).

–

means the group is different and is being updated to the sender’s value (requires

--group and the authority to set the group).

–

means the atime is different and is being updated to the sender’s value.

–

means the CIFS ACL is different and is being updated to the sender’s value.

–

means the POSIX extended attributes are different and are being updated to the

sender’s values.

◦

Another possible output for %i is - when deleting the files, the "%i" represents the string
"*deleting" for each item that is being removed.

Sample Output of the ibrcfrworker log

(2012/11/19 15:50:40),,<4449>,.d..t......,./

(2012/11/19 15:50:40),,<4449>,cd+++++++++,new_dir/

(2012/11/19 15:50:40),,<4449>,

Troubleshooting remote replication

Continuous remote replication job stops when target cluster is down or
rebooted

If a continuous remote replication job is running when the target cluster is rebooted or goes down,
the job will stop. However, on the source cluster, the Active state field still displays "yes". To resolve
this issue, use either the Management Console or CLI to stop the job. Then, start a new job on the
file system.

270 Using continuous remote replication