Giveback operation mode

Giveback process

The giveback process is described in the following table.

Stage	Description
1	The giveback process is initiated in one of two ways: An operator issues a `cf giveback` command. If the option `cf.giveback.check.partner` is enabled on the takeover filer, the takeover filer checks whether its partner is in "waiting for giveback" mode before actually executing the `cf giveback` command. If the `cf giveback -f` command is issued, then the giveback operation will start whether the partner is in "waiting for giveback" mode or not. If the option `cf.giveback.auto.enable` is enabled on the takeover filer, the takeover filer automatically executes giveback when the state of its partner goes to "waiting for giveback." No manual `cf giveback` command is necessary.
2	The takeover filer updates the failed filer disks.
3	The takeover filer destroys the emulated filer so that no more writes can occur to the failed filer disks.
4	The takeover filer releases the disk reservations that it held on behalf of the failed filer. This action returns control to the failed filer of the disks it owns.
5	The failed filer resumes normal operations, serving its own data. The users of that filer experience the effects of a reboot.

Caution
Avoid initiating the giveback process on the takeover filer before its partner, the failed filer, is ready to resume operations. If the options cf.giveback.check.partner command is not enabled or not supported on the takeover server, the giveback process might proceed on the takeover filer, whether or not its partner is in a "waiting for giveback" mode.

Messages indicating a successful giveback

During a typical giveback, the cluster monitor issues messages on the console of the takeover filer:

filer1(takeover)> Tue Jul 21 22:37:34 GMT [filer1 (takeover): 
cf.misc.operatorGiveback:info]: Cluster monitor: giveback initiated 
by operator

Tue Jul 21 22:37:34 GMT [filer1: cf.fm.givebackStarted:warning]: 
Cluster monitor: giveback started

Tue Jul 21 22:37:35 GMT [filer1: cf.fm.givebackComplete:warning]: 
Cluster monitor: giveback completed

The preceding message indicates that the giveback process was successful. When the failed filer reboots, the following messages appear:

Tue Jul 21 22:37:35 GMT [filer1: cf.fsm.stateTransit:warning]: 
Cluster monitor: TAKEOVER --> UP

Tue Jul 21 22:38:35 GMT [filer1: cf.fsm.firmwareStatus:info]: 
Cluster monitor: partner booting

Tue Jul 21 22:38:45 GMT [filer1: cf.fsm.firmwareStatus:info]: 
Cluster monitor: partner kernel loaded

Tue Jul 21 22:39:35 GMT [filer1: cf.fsm.partnerOk:notice]: Cluster 
monitor: partner ok

Tue Jul 21 22:39:35 GMT [filer1: cf.fsm.takeoverDisabled:notice]: 
Cluster monitor: takeover of partner disabled (unsynchronized log)

Tue Jul 21 22:39:41 GMT [filer1: cf.fsm.takeoverEnabled:notice]: 
Cluster monitor: takeover of partner enabled

Tue Jul 21 22:39:55 GMT [filer1: monitor.globalStatus.ok:info]: The 
system's global status is normal

The last message indicates that the filers are operating normally and, therefore, either filer can take over for its partner if necessary.