User's Manual

NOTE: The fluid_cache service cannot be running when you run the fldc_restore command.

NOTE: The fldc_restore command accepts up to three UIDs on the command line. The more UIDs you include

on the command line, the more likely the utility can locate and use the correct journal for the restore process.

NOTE: For a system with only one PCIe SSD, run the command: ./fldc_restore -f <uid>. For

example: ./fldc_restore WWN 500A07510202EE60 -f . Use the force option (-f) only if you are

sure that the WWN (UID) you are entering is the most recent, pre-disaster running configuration.

The command returns the following output:

[root@devvm14 ~]# /opt/dell/fluidcache/bin/fldc_restore

6E6E6E6E6E6E6E6E6E6E6E6E6E736464 Journal Cluster ID [58f002fb-80f7-4640-

ac8a-fadfc6deb75b]

Journal mirror locations

location type [Cache Device] - location [6E6E6E6E6E6E6E6E6E6E6E6E6E736464]

location type [Cache Device] - location [6E6E6E6E6E6E6E6E6E6E6E6E6E736465]

location type [Cache Device] - location [6E6E6E6E6E6E6E6E6E6E6E6E6E736467]

Found configuration record at block 5

uncompressing xml to /tmp/<any_name>config.xml

Configuration restored to [/opt/dell/fluidcache/conf/fldc.conf]

You have now restored the Fluid Cache for DAS configuration you had before the disaster.

4. Restart the fluid_cache service.

5. Ensure that the product has started successfully by running the command: fldc --status

This command returns a set of information similar to the following:

Fluid Cache Service

Cache size: 0 GiB

Status: ok

SSDs in Cache: 0

Disk being cached: 0

Write Back: unavailable

Cache ID: <any node>.example.com

License: node – limited to 4 nodes

License Status: valid

SSDs in cache No SSDs are configured in the cache

pool

Disks being cached No Disks are being cached

Caching now continues as before the disaster occurred.