You can determine if objects are permanently unavailable by making a request using the TSM administrative console.
The active audit log file is named audit.log. Once a day, the active audit.log file is saved, and a new audit.log file is started. The name of the saved file indicates when it was saved, in the format yyyy-mm-dd.txt. After a day, the saved file is compressed and renamed, in the format yyyy-mm-dd.txt.gz, which preserves the original date.
[AUDT:[CBID(UI64):0x498D8A1F681F05B3][VLID(UI64):20091127][RSLT(FC32):ARUN][AVER(UI32):7][ATIM(UI64):1350613602969243][ATYP(FC32):ARCE][ANID(UI32):13959984][AMID(FC32):ARCI][ATID(UI64):4560349751312520631][ASQN(UI64):62][ASES(UI64):1350580983645305]]
See the instructions for understanding audit messages.
Select Support > Grid Topology. Then, select Archive Node > ARC > Target > Overview.
The file space name is the Archive Node's node ID.
Equivalent to the volume ID assigned to the object by the Archive Node. The volume ID takes the form of a date (20091127), and is recorded as the VLID of the object in archive audit messages.
Low Level Name
Equivalent to the CBID assigned to an object by the StorageGRID Webscale system.
Use the administrative user name and password that are configured for the ARC service. Enter the user name and password in the Grid Manager. (Select Support > Grid Topology. Then, select Archive Node > ARC > Target > Configuration.)
> query actlog begindate=-1 search=276C14E94082CC69 12/21/2008 05:39:15 ANR0548W Retrieve or restore failed for session 9139359 for node DEV-ARC-20 (Bycast ARC) processing file space /19130020 4 for file /20081002/ 498D8A1F681F05B3 stored as Archive - data integrity error detected. (SESSION: 9139359) >
Note that depending on the nature of the error, the CBID might not be recorded in the TSM activity log. It might be necessary to search the log for other TSM errors around the time of the request failure.
> query content TSM-Volume-Name Node Name Type Filespace FSID Client's Name for File Name --------------- ---- ---------- ---- -------------------------------- DEV-ARC-20 Arch /19130020 216 /20081201/ C1D172940E6C7E12 DEV-ARC-20 Arch /19130020 216 /20081201/ F1D7FBC2B4B0779E
The “Client’s Name for File” is the Archive Node volume ID (TSM “high level name”) followed by the object’s CBID (TSM “low level name). That is: /Archive Node volume ID /CBID or, in the first line of this example: /20081201/ C1D172940E6C7E12
Recall also that the “Filespace Name” is the node ID of the Archive Node.
You will need the CBID of each object stored on the volume and the node ID of the Archive Node to cancel the retrieval request in step 3.
where CBID is the identifier of the object that cannot be retrieved from the TSM.
If the only copies of the object are on tape, the “bulk retrieval” request is canceled with a message “1 requests canceled”. If copies of the object exist elsewhere in the system, the object retrieval is processed by a different module so the response to the message is “0 requests canceled”.
where CBID is the identifier of the object that cannot be retrieved from the TSM server.
For Archive Nodes, you cannot use a range of CBIDs.
node_ID is the node ID of the Archive Node where the retrieval failed.
In most cases, the StorageGRID Webscale system immediately begins to make additional copies of object data to ensure that the system's ILM policy is followed. In a StorageGRID Webscale system configured to use an ILM rule with only one active content placement instruction, copies of an object are not made. If an object is lost, it cannot be recovered. In this case, running the Object_Lost command purges the lost object’s metadata from the StorageGRID Webscale system.
When the Object_Lost command completes successfully, it returns the message CLOC_LOST_ANS returned result ‘SUCS’.