A method for authorizing I/O (input/output) commands in a storage cluster is provided. The method includes generating a token responsive to an authority initiating an I/O command, wherein the token is specific to assignment of the authority and a storage node of the storage cluster. The method includes verifying the I/O command using the token, wherein the token includes a signature confirming validity of the token and wherein the token is revocable.

A method for exchange of equipment performance data includes the steps of: obtaining performance data of a communicatively-insulated device; converting the performance data into a scannable code; capturing an image of the scannable code; decoding the scannable code using a communicatively-enabled device to extract an address string encoded in the scannable code, the address string comprising an address of a remote server and the performance data; initiating, by the communicatively-enabled device, a communications link with the remote server using the address string thereby to provide the performance data to the remote server; performing, by the remote server, analytics on the performance data; and sending historic device performance data and/or analytical results to a remote computing device and/or sending a link to the historic device performance data and/or analytical results to the remote computing device; wherein the communicatively-insulated device is packaging equipment and wherein obtaining the performance data comprises: running a calibration phantom through the packaging equipment; scanning the calibration phantom with a calibration unit; and using the calibration unit to generate a system status report identifying one or more operational parameters of the packaging equipment.

A technique for tracking web browsing activity of a client device that includes storing, in a memory, a client profile having a client identifier associated therewith, providing a client device with a cache file having the client identifier embedded therein, receiving from the client device an identification of a client action and the client identifier, and updating the client profile to include the identification of the client action.

Intelligent collection and analysis of in-app failure data is disclosed herein. Upon an application failure in a client device, the client device may collect failure information uniquely identifying a specific failure and provide the failure information to an analysis system. The analysis system may identify a specific failure that identifies the application and a specific portion of the code in the application, based on the failure information and match an action correlated to the specific failure where the action is uniquely designed to resolve the specific failure in the application. The action may include instructions for the client device used to intelligently lead to a resolution of the specific failure. The analysis system may transmit the action to the client device to perform the action and provide any follow up information to the analysis server. The analysis server may use the information to further analyze the specific failure.

Technologies are provided for assigning developers to source code issues using machine learning. A machine learning model can be generated based on multiple versions of source code objects (such as source code files, classes, modules, packages, etc.), such as those that are managed by a version control system. The versions of the source code objects can reflect changes that are made to the source code objects over time. Associations between developers and source code object versions can be analyzed and used to train the machine learning model. Patterns of similar changes to various source code objects can be detected and can also be used to train the machine learning model. When an issue is detected in a version of a source code object, the model can be used to identify a developer to assign to the issue. Feedback data regarding the developer assignment can be used to re-train the model.

A server computer may receive diagnostic logs from a plurality of electronic devices, each having a particular application installed. The diagnostic logs include information about call stacks within the particular application on the plurality of electronic devices for writing data to a storage device that is on each of the plurality of electronic devices. The server computer may filter out a set of call-paths from the call stacks to obtain a set of functions that can be used identify a set of call-path signatures. The server computer may for each function, determine a cumulative measure of write operations to the storage device performed by the function across the electronic devices and identify at least one function from the set of call-path signatures matching one or more predetermined criteria associated with the cumulative measures. The server computer may provide a notification and a corrective action to a developer.

A method and system for live-mounting database backups. Specifically, disclosed method and system entail recovering database data—in entirety or at any granular level—without needing to provision storage resources for point-in-time database copies (i.e., backup database data), or without needing to wait for large amounts of data, representative of the point-in-time database copies, to traverse a network from backup storage to a target device. Substantively, through live-mounting, the physical point-in-time database data, as well as the associated structural metadata, may be retained on backup storage while a pointer-based snapshot, mapping to the physical point-in-time database data and structural metadata, may be generated thereon. Thereafter, a file system—mapping to the pointer-based snapshot on the backup storage—may be mounted on the target device, which exposes an interface through which the backup database data may be accessed and/or manipulated using a distributed file system protocol.

An apparatus is provided, connectable to a memory and one or more peripherals. The apparatus includes translation request circuitry to receive a translation request from one of the peripherals to translate an input address within an input domain to an output address within an output domain. Signing circuitry generates a signature of at least part of the output address using a private key. Translation response circuitry responds to the translation request by transmitting to the one of the peripherals a translation response, including the output address and the signature. Gateway circuitry receives access requests to the memory. Each of the access requests comprises a desired memory address in the output domain and a signature of the desired memory address. The gateway performs validation of the signature of the desired memory address using the private key and in response to the validation of a given access request failing, performs an error action.

Systems, apparatus and methods for generation of XOR signature metadata and XOR signature management are presented. In one or more embodiments, a storage device controller includes a host interface, configured to receive one or more string lines (SLs) of data from a host, the one or more SLs to be programmed into a non-volatile memory (NVM), and processing circuitry. The processing circuitry is configured to, for each of the one or more SLs, generate signature metadata and provide the signature metadata in a header of the SL. The processing circuitry is still further configured to XOR two or more of the SLs with their respective signature metadata to generate a snapshot, and write the snapshot to the NVM.

Techniques are provided for detection of anomalous backup files using known anomalous file fingerprints (or other file-dependent values such as hash values, signatures and/or digest values). One method comprises obtaining first file-dependent values corresponding to respective known anomalous files; obtaining a second file-dependent value for a stored backup file; comparing the second file-dependent value to the first file-dependent values; and performing an automated remedial action in response to a result of the comparing. The second file-dependent value for the stored backup file may be determined by a backup server in response to a source file corresponding to the stored backup file being backed up by the backup server, and may be stored as part of metadata associated with the stored backup file.