Abstract: A system can maintain first data as files and second data as objects. The system can receive a request from a remote computer to convert a file into an object. The system can receive, from a file storage protocol mount point associated with the remote computer, first metadata for the file. The system can receive, from an object storage protocol client associated with the remote computer, second metadata for an object storage bucket of the second data, wherein data of the file is to be stored as the object in the object storage bucket. The system can copy the data of the file into the object in the object storage bucket, based on the first metadata for the file, based on the second metadata for the object storage bucket, and independently of transferring the data of the file to the object storage bucket via the remote computer.

Abstract: Changes made to a database table are accumulated, in durable storage, and snapshots of partitions of the table are obtained. For successive snapshots of a partition, the system accesses a previous snapshot, applies changes from the accumulated changes, and stores the updated snapshot to a durable data store. The accumulated changes and the successive partition snapshots are made available to restore the database to any point in time across a continuum between successive snapshots. Although each partition of the table may have a backup snapshot that was generated at a time different from when other partition snapshots were generated, changes from respective change logs may be selectively log-applied to distinct partitions of a table to generate an on-demand backup of the entire table at common point-in-time across partitions. Point-in-time restores of a table may rely upon a similar process to coalesce partition snapshots that are not aligned in time.

Abstract: Apparatuses, systems, and methods for managing access to metadata stored at a memory. To manage access to metadata, a mode register is configured to receive a metadata enable setting and to provide a metadata enable signal based on the metadata enable setting. A metadata access control circuit configured to receive a column address identifying a particular column to be accessed within a memory array. The metadata access control circuit blocks access to a column corresponding to the column address when the column address matches one of a plurality of particular column addresses designated for storage of metadata and the metadata enable signal has a first value, and permits access to a column corresponding to the column address when the column address is different than every one of the a plurality of particular column addresses designated for storage of metadata or the metadata enable signal has a second value.

Abstract: Systems, methods, and computer-readable media for managing storing of data in a data storage system using a client tag. In some examples, a first portion of a data load as part of a transaction and a client identifier that uniquely identifies a client is received from the client at a data storage system. The transaction can be tagged with a client tag including the client identifier and the first portion of the data load can be stored in storage at the data storage system. A first log entry including the client tag is added to a data storage log in response to storing the first portion of the data load in the storage. The first log entry is then written from the data storage log to a persistent storage log in persistent memory which is used to track progress of storing the data load in the storage.

Abstract: Techniques for improving performance of file system operations are provided. Dirty memory pages may be copied from a file system into a memory associated with a first hardware accelerator. Content of the memory pages may be compressed by one or more cores of the hardware accelerator. The compressed data may be compacted into a payload area of at least one log. Metadata of the at least one log may be prepared by the one or more cores of the hardware accelerator. The at least one log may be flushed into a storage device. A read operation may be performed on the at least one log. On a read path, in response to determining that a size of data from a plurality of logs is greater than a predetermined threshold, a new log may be created by combining the data using compression by a second hardware accelerator.

Abstract: Technique for determining a data recovery duration involve determining a plurality of phases of data recovery. Such techniques further involve determining, based on a metadata metric set of a phase in the plurality of phases, a recovery duration of the phase, the recovery duration of the phase representing a duration required for recovery of the phase. Such techniques further involve determining the data recovery duration based on the recovery duration of the phase. Accordingly, a data recovery duration can be accurately predicted, and a user can know in advance how long data unavailability will last, which helps the user make a decision to schedule the data recovery in an appropriate time period, thereby being more effective and efficient for the user.

Abstract: A method and system for implementing concurrency control in a database system includes receiving a request from a node for handling by a GTM. Registering the request in a slot in a tracking array where each of the slots represents one of the requests for handling by the GTM. A slot is acquired, and a segment of the tracking array is scanned to determine a batch of pending requests. The batch is used to produce an aggregate request and the aggregate request includes an aggregate increment of a total number of commit requests of the batch. The aggregate request is sent to the GTM using one of a plurality of pre-established connections. A response is received from the GTM that includes a current value of an incremented timestamp. The incremented timestamp is distributed to the requests of the batch and the lock is released.

Abstract: A data hierarchy including individual data nodes may be used to represent a wide variety of data collections. Requests to change or add nodes in the data hierarchy may be received from many different sources over time. Instead of considering these change requests individually, an interface allows a plurality of change requests to be consolidated together into a single consolidated request. The consolidated request may be displayed in an interface such that changes from each of the original requests may be displayed together in an interface so that a cumulative effect of each of the change requests may be considered before the data changes are committed to the underlying data structure. The consolidated request may maintain links and update underlying data objects representing each of the original requests to provide a record of actions related to the consolidated request.

Abstract: A database system is operable to, during a first temporal period, facilitate execution of a first query to generate a first query resultant based on access to an initial set of segments. During a second temporal period after the first temporal period, an updated segment is generated based on determining to re-store corresponding column values of an initial segment via applying at least one storage optimization technique. During the second temporal period, execution of a second query is facilitated to generate a second query resultant via access to the initial segment. After the second temporal period, storage of the initial segment is replaced with storage of the updated segment. During a third temporal period after the second temporal period, execution of a third query is facilitated to generate a third corresponding query resultant via access to the updated segment.

Abstract: In some aspects, a computing system may generate a content-defined tree. A content-defined tree may be a tree of cryptographic hashes where each leaf is a hash of a chunk (e.g., data chunk) of a data object, and each parent node (e.g., interior node) is the hash of a concatenation of the hashes of the parent's children nodes. To create parent nodes for the leaf nodes, a computing system may group leaf nodes together based on a rolling hash (e.g., a rolling hash of the hashes of the leaf nodes) satisfying a condition. Each parent node may include a hash that represents the concatenation of the hashes of the leaf nodes that fall under the corresponding parent node.

Abstract: A disclosed framework enables virtually any aggressive Recovery Point Objective (RPO) to be enforced for a production database, without limitation on type of database management system (DBMS) or size of the production database. The framework overcomes technological barriers of the prior art, such as bottlenecks presented by a storage manager computer that traditionally managed database backups. To avoid the bottlenecks, an illustrative data storage management system does not engage the storage manager computer in storage operations that could impact the database RPO. Certain components are added and enhanced to autonomously capture database transaction logs, which are stored securely and persistently away from the DBMS. In a separate and less frequent operation, and with involvement of the storage manager computer, the illustrative system generates secondary copies in their final form. Meanwhile, temporary backup files can be used in restore operations without first being converted into secondary copies.

Abstract: Herein is high availability for online transaction processing with redundancy and redo for a federation of pluggable databases and container databases. In a federation of container database management systems that includes a first container database, first redo data of a first pluggable database in a second container database is obtained based on a database dictionary in the first container database. To the first pluggable database in the first container database, the first redo data of the first pluggable database in the second container database is applied. Based on the database dictionary in the first container database, second redo data of a second pluggable database in a third container database is obtained. To the second pluggable database in the first container database, without modifying content of the first pluggable database in the first container database, the second redo data of the second pluggable database in the third container database is applied.

Abstract: Indexing preferences generally associate each data source with a type of indexing technology and/or with an index/catalog and/or with a computing device that hosts the index/catalog for tracking backup data generated from the source data. Indexing preferences govern which index/catalog receives transaction logs for a given storage operation. Thus, indexing destinations are defined granularly and flexibly in reference to the source data. Load balancing without user intervention assures that the various index/catalogs are fairly distributed in the illustrative backup systems by autonomously initiating migration jobs. Criteria for initiating migration jobs are based on past usage and going-forward trends. An illustrative migration job re-associates data sources with a different destination media agent and/or index/catalog, including transferring some or all relevant transaction logs and/or indexing information from the old host to the new host.

Abstract: System extracts backup metadata, comprising system committed change numbers, system change numbers, types, and database version identifiers, for backup copies. System generates data structure, comprising start system change numbers, based on minimums of system committed change numbers, end system change numbers, based on maximums of system change numbers, database version identifiers, and identifiers for archive log backup copies. System identifies dependent system change numbers, based on start system change number to end system change number for backup copy corresponding to database version identifier. System identifies, in data structure, backed-up system change numbers, based on start system change numbers to end system change numbers for archive log backup copies corresponding to database version identifier, which are included in dependent system change numbers.

Abstract: Methods, systems, and computer-readable storage media for providing a first instance of a database system within the cloud computing environment, determining that scale out of the database system is to be executed, and in response, providing a second instance of the database system within the cloud computing environment, the first instance and the second instance collectively defining a cluster, establish a remote direct memory access (RDMA) connection between the first instance and the second instance, copying data stored within the first instance to a data store of the second instance over the RDMA connection, and configuring the first instance to replicate a first transaction log to the second instance over the RDMA connection, and receiving, by each of the first instance and the second instance, requests from one or more client devices.

Abstract: A method and apparatus are provided for avoiding target database constraint violations in a database replication system. The database replication system includes a source database and a target database, wherein target database transactions automatically abort due to constraint violations. Each database has one or more tables and at least one of the target database tables has one or more constraints. The database replication system replicates source database transactions. For each target database transaction corresponding to a replicated source database transaction, changes made at the source database are replicated to the target database. When it is detected that a replicated change causes a constraint violation as a result of one or more of the target database tables having one or more constraints, the applying of the database change to the target database of the database change is deferred and the database change is posted to an electronic list.

Abstract: Any point in time backups for distributed consistency is disclosed. IOs from a consistency group are received by multiple aggregators and stored in corresponding journals. In response to a bookmark, the multiple journals are synthesized to create a do stream or to add the multiple journals to the do stream. A full synchronization operation can be performed simultaneously with replication operations.

Abstract: Systems and methods are described herein for more efficiently updating a data directory, which maps data objects stored by a data storage service, such as maintained by on premise computing resources of a client of the data storage service. In one example, event data corresponding to operations performed on a plurality of data objects stored in a data storage partition of a data storage service may be obtained. A set of data objects relevant to a directory maintained locally by a client device may be determined. The event data may be filtered, such as by removing entries of the plurality of entries not corresponding to the set of data objects. The filtered event data may then be stored or pushed to a client device, to cause the directory to be updated, without requiring a full examination of the data storage partition.

Abstract: A system may include a memory and a processor in communication with the memory configured to perform operations. The may operations include obtaining transaction logs in blocks from nodes of a data storage system. The operations may include, for each transaction log, splitting the transaction log into log entries, grouping log entries into groups associated with a same data source, and writing the log entries of the groups to empty blocks such that log entries from different groups do not share a same block. The operations may include identifying a same sequence of log entries from the written transaction logs and uploading first blocks of a first transaction log, including the same sequence of log entries, to an object-based storage without uploading second blocks of a second transaction log including the same sequence of log entries to the object-based storage.

Abstract: A system according to certain aspects improves the process of performing snapshot replication operations (e.g., maintaining a mirror copy of primary data at a secondary location by generating snapshots of the primary data). The system can collect and maintain cumulative block-level changes to the primary data after each sub-interval of a plurality of sub-intervals between the snapshots. When a snapshot is generated, any changes to the primary data not reflected in the cumulative block-level changes are identified based on the snapshot and transmitted to the secondary location along with the cumulative block-level changes. By the time the snapshot is generated, some or all of the changes to the primary data associated with the given snapshot have already been included in the cumulative block-level changes, thereby reducing the time and computing resources spent to identify and collect the changes for transmission to the secondary location.

Abstract: One example method includes performing delta operations to protect data. During a delta operation, a primary bitmap and a secondary bitmap are processed using bit logic. The delta generated by the delta operation is transmitted to a receiver. The receiver enqueues the delta into a delta queue configured to allow the replica volume at the target site to be moved to any point in time represented by the deltas in the delta queue.

Abstract: Access to sensitive information in a database can be restricted to improve security and enable efficient auditing. A security engine receives a request from a requesting entity to access data in the database and determines that the requested data includes sensitive information. In response to the requesting entity being authorized to access the data, the security engine retrieves the requested data from the database and modifies the retrieved data by modifying metadata of the retrieved data to include a tag indicating that the retrieved data includes sensitive information. The security engine provides the modified data to the requesting entity and modifies a data access log to identify each attempted access to the modified data. When sensitive data is requested, an interface can include an obscuring element, requiring a user to manually select the element to view the data, enabling the logging of the explicit access request by the user.

Abstract: Systems and methods are described for optimizing logging of decision outcomes in distributed transaction protocols. An example method may comprise: executing, by a processing device, a transaction manager to coordinate a distributed transaction for a plurality of participants; transmitting, by the processing device via the transaction manager, prepare messages to the plurality of participants; serializing a transaction log record of the distributed transaction in parallel with the transmitting of the prepare messages; speculatively writing the serialized transaction log record in persistent memory while the transaction manager performs the serializing of the transaction log record; and updating a speculative indicator associated with the distributed transaction to indicate validity of the transaction log record.

Abstract: A computer-readable recording medium storing an information processing program for causing a computer to execute a process including: specifying an amount of first areas subjected to data update among a plurality of first areas that are contained in a cache storage area and allowed to be synchronized individually from each other with a nonvolatile storage area; and determining whether to individually synchronize the first areas subjected to the data update among the plurality of first areas with the nonvolatile storage area or collectively synchronize a second area that is formed by the plurality of first areas and allowed to be collectively synchronized with the nonvolatile storage area, with the nonvolatile storage area, based on the specified amount, a first processing time taken for synchronization between the first areas and the nonvolatile storage area, and a second processing time taken for synchronization between the second area and the nonvolatile storage area.

Abstract: A computer implemented method comprises receiving at least one log record. A type of operation performed in a source database system may be determined based on the log record. Based on the type of operation, an update strategy may be selected from a set of pre-defined update strategies, wherein the update strategy specifies a sequence of replication operations to be performed in order to apply changes described in the at least one log record to a target database system.

Abstract: This application discloses an audit result data storage method and device, an audit result data query method and device, an audit item storage method and device, an electronic device and a medium. The method includes obtaining a first hash value of audit result data of a first user; signing the first hash value according to a private key of the first user to obtain first signature data; and transmitting the first signature data to an audit result data storage subsystem, the audit result data storage subsystem being configured to store data in the form of a blockchain.

Abstract: Methods, computer program products, and/or systems are provided that perform the following operations: in a data replication environment, analyzing a database workload to generate a knowledge base of information related to compression; dividing a transfer data stream into different segments based, at least in part, on the knowledge base; obtaining candidate compression types for the transfer data stream based, at least in part, on the knowledge base; assigning respective compression types of the candidate compression types to the different segments; generating compressed segments based, at least in part, on the respective compression types assigned to the different segments; and providing the compressed segments to a replication target.

Abstract: One example method includes intercepting an IO that is directed to a volume, writing the IO to a grid-CG that is one of a plurality of grid-CGs that collectively form a distributed CG, adding the IO to a stream journal associated with the grid-CG, receiving a bookmark request, in response to the bookmark request, inserting a bookmark in the stream journal, incrementing a splitter counter and broadcasting a splitter counter value to the grid-CGs in the distributed CG, and inserting the bookmark in respective stream journals of the grid-CGs in the distributed CG.

Abstract: A method and system of processing database transactions in a distributed online transaction processing (OLTP) database is provided. Overhead and network bandwidth associated with a global transaction manager are reduced and scalability improved by determining whether incoming statements are single-shard or multi-shard. For single-shard statements, a local transaction identifier (TXID) stored and associated with a data record reference by the statement is retrieved. The retrieved TXID is compared against a copy of a list of prepared transactions that are pending in a respective data node. If the TXID is in the copy of the prepared list, the statement is caused to await until the previous transaction has been committed or aborted. The visibility of a change committed by the previous is then determined, and the statement is processed.

Abstract: A data collection device can determine that a connection is unavailable between the data collection device and a data processing platform. The data collection device can obtain, after the connection is unavailable, a plurality of readings. The data collection device can determine, based on determining that the connection is unavailable, to discard one or more readings from the plurality of readings to form a set of readings. The data collection device can store, based on determining that the connection is unavailable, the set of readings without storing the one or more readings. The data collection device can determine, after storing the set of readings, that the connection is available. The data collection device can transmit, based on determining that the connection is available, the set of readings to the data processing platform.

Abstract: The subject technology executes a change on an existing micro-partition of a table of a database, the executing of the change comprising generating a new micro-partition that embodies the change. The subject technology receives a request for a delta for the table between a first timestamp and a second timestamp. The subject technology queries at least one change tracking column to determine the delta between the first timestamp and the second timestamp, the delta including information indicating at least one database operation that was performed to at least one row of a set of rows of the table, without including information as to intermediate changes made to at least one row of the set of rows of the table between the first timestamp and the second timestamp, that facilitates a reduction in storage of historical versions of the set of rows of the table.

Abstract: Embodiments include a method for fault tolerance in the delivery of event information within a file system cluster. One or more processors to determine event information associated with file system activity performed by a node of the cluster. The one or more processors add the event information to an event log buffer in memory. The one or more processors receive a first log sequence number (LSN) associated with flushing of recovery information from a recovery log buffer. The one or more processors determine the event information in the event log buffer having a log sequence number less than or equal to the first log sequence number, and determining the event information includes log sequence numbers less than or equal to the first log sequence number, the one or more processors flush the corresponding event information from the event log buffer to disk storage.

Abstract: Information describing changes to a collection of items maintained by a database may be stored in a log file. The information in the log file may be converted into a stream of records describing the changes. The records may be directed to a computing node selected for performing a trigger function in response to the change, based on applying a hash function to a portion of the record, identifying a hash space associated with a value output by the hash function, and mapping from the hash space to the selected computing node.

Abstract: Systems and methods for performing application aware backups and/or generating other application aware secondary copies of virtual machines are described. For example, the systems and methods described herein may access a virtual machine, automatically discover various databases and/or applications (e.g., SQL, Exchange, Sharepoint, Oracle, and so on) running on the virtual machine, and perform data storage operations that generate a backup, or other secondary copy, of the virtual machine, as well as backups, or other secondary copies, of each of the discovered applications.

Abstract: The disclosed embodiments disclose techniques for journaling data received in a cloud-based distributed computing environment (CBDCE). Multiple services simultaneously execute on the CBDCE compute nodes, with each service comprising multiple service instances that simultaneously execute on multiple, distinct compute nodes of the CBDCE. The CBDCE includes a distributed database that enables coordination between the service instances of services that execute in the CBDCE; this distributed database also includes multiple distributed database instances that simultaneously executing on multiple different CBDCE compute nodes. During operation, a service instance executing on one of these compute nodes receives a client request. The service instance submits this client request to a distributed database instance and, in parallel, also submits the client request and its associated user data to a distributed journaling service.

Abstract: Tracking changes to a document by defining a document record having a unique document record and comprising an index and a file name of the document, and defining a backup record for the document in a series of backups, which includes a timestamp for each backup, and a bitmask for the document. The bitmask has a single bit position for each document in the container which is set to a first binary value to indicate that the corresponding document is unchanged and a second binary value to indicate whether the document is changed or deleted. A primary query is received and resolved for the document by analyzing the document record to find the file name. A secondary query using the document record ID is resolved to find all tracked versions of the document, and the results are returned to the user in the form of a version history list.

Abstract: Methods, computer program products, computer systems, and the like are disclosed that provide for scalable deduplication in an efficient and effective manner. For example, such methods, computer program products, and computer systems can include determining whether a source data store and a replicated data store are unsynchronized and, in response to a determination that the source data store and the replicated data store are unsynchronized, performing a resynchronization operation. The source data stored in the source data store is replicated to replicated data in the replicated data store. The resynchronization operation resynchronizes the source data and the replicated data.

Abstract: A storage device is disclosed. A first storage media may store data. The first storage media may be of a first storage type, and may be organized into at least two blocks. A second storage media may also store data. The second storage media may be of a second storage type different from the first type, and may also be organized into at least two blocks. A controller may manage reading data from and writing data to the first storage media and the second storage media. Metadata storage may store device-based log data for errors in the storage device. The drive-based log data for errors may include a unified log data for the first storage media and the second storage media. An identification circuit may identify a suspect block in the at least two blocks in the first storage media and the second storage media, responsive to the unified log data.

Abstract: Providing continuous data protection includes maintaining a database having substantially all data modifications made to a primary volume over a recovery interval. The database is maintained in conjunction with a copying operation where the data of the primary volume are mirrored to a remote volume to permit recovery of mirrored data in the event of loss of primary volume data. The contents of the remote volume generally lag behind the contents of the primary volume by substantially the recovery interval. Providing continuous data protection also includes providing data roll-back to a precise point in time within the recovery interval by applying, to the contents of the remote volume, all data modifications in the database that occurred between the latest data modification to the remote volume and the precise point in time within the recovery interval. A time stamp mechanism of sufficient precision and granularity may be used.

Abstract: Methods and systems for searching directory access groups are disclosed. A set of groups associated with a logon user is determined. The set of groups is partitioned into one or more disjoint subsets, wherein each of the disjoint subsets is represented by a data representation including a root node and one or more intermediate nodes. For each of the disjoint subsets, the disjoint subset is path compressed to flatten a structure of the data representation representing the disjoint subset. The data representation is cached to a database cache.

Abstract: Systems and methods are provided for intent tracking asynchronous operations. An example method can include receiving, at a content management system (CMS), a first request to perform an operation on a content item stored at the CMS; adding the request to perform the operation to a queue of operations to be processed by the CMS; and prior to completing the operation: receiving, from a client device associated with a user account registered at the CMS, a second request to access the content item; in response to the second request, determining a predicted state of the content item, the predicted state of the content item reflecting a result of performing the operation on the content item; and providing, to the client device, a response including the predicted state of the content item.

Abstract: Systems and methods for performing data protection operations including replication operations. A replication operation may automatically learn and predict when a replication system will need to switch modes, such as to a protective mode or to a fast-forward mode. The replication operation ensures that the data is replicated in a manner that optimizes the ability to retain data needed to perform point in time recovery operations while prioritizing the replication operation of new data.

Abstract: Described herein are embodiments of a database system for performing multi-document transactions. The database system comprises a database comprising a plurality of data storage nodes. The database system receives transactions that access at least two documents stored in the database. The database system generates a transaction identifier associated with the transaction and associates operations in the transaction with the transaction identifier. The database system performs at least part of the transaction on the database and determines whether an error occurred in performing in performing the transaction. When the database system determines that an error occurred in performing the transaction, the database system reverses any performed operations of the transaction. When no error occurs in performing the transaction, the database system outputs a confirmation.

Abstract: Recovery of a database system by taking the database system offline is initiated. Thereafter, recovery operations specified by a redo log of the database system are replayed. A cleanup log is generated that identifies cleanup operations occurring during the replay of the recovery operations for garbage collection. Concurrent with the startup of the database, garbage collection of the cleanup operations as specified in the database savepoint is initiated. In addition, concurrent with the replay of the recovery operations, garbage collection of the cleanup operations specified by the cleanup log is initiated. The database system is later brought online after all of the recovery operations are replayed.

Abstract: Facilitating checkpoint locks for distributed systems is provided herein. A system can comprise a processor and a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations. The operations can comprise generating an ordered data structure that comprises respective identifications of a group of nodes granted a shared lock for a data file. The group of nodes can comprise a node having a respective identification of the respective identifications. The operations also can comprise, based on a determination that a checkpoint function associated with the shared lock has completed at a node of the group of nodes, removing the respective identification of the node from the ordered data structure. In an example, the shared lock can be a checkpoint application program interface. In another example, the group of nodes can be nodes arranged in a distributed computing hierarchy.

Abstract: A method, system and computer-readable storage medium for performing a cognitive information processing operation.

Abstract: Techniques for dynamically detecting objects that are out of sync in an active mirrored environment are provided. A request is received at a local node of an active mirroring environment from a system function to perform a change operation on an object. Upon determining that the object is OOS, it is determined whether the local node or a remote node of the active mirroring environment has the most recent changes for the object. In one embodiment, the determination includes analyzing corresponding time stamps of changes listed in a repository of changes for objects in the mirrored environment. Upon determining that a remote node has the most recent changes for the object, a blocking attribute is set and the requested operation on the object blocked. However, upon determining that the local node has the most recent changes for the object, a tracking attribute is set and the requested operation allowed.

Abstract: Example embodiments may flatten structured data (e.g., extensible markup language (XML)) to two tables, a lineage table and an attribute table. The lineage table describes hierarchical relationships in the structured data and values of respective elements. The attribute table contains a normalized list of attributes in the structured data. Together the lineage and attribute tables comprise data that could enable recreation of the structured data without any loss of data. In some examples, the tables may be compressed. The flattening of the structured data into two tables, and optional compression of the tables, provides for efficient access and querying of the data. Example embodiments may provide automated and/or processing of additional structured data, ongoing over time, even if the expected hierarchy of the data changes over time.

Abstract: A cloud storage server accesses a plurality of server-stored files of a cloud storage account of a client device. The cloud storage server determines that one or more server-stored files from the plurality of server-stored files are affected by a malware activity. The cloud storage server generates a graphical user interface that includes a detection notification and a confirmation request, the detection notification indicating a detected presence of malware in the one or more server-stored files and metadata corresponding to the one or more server-stored files, the confirmation request indicating a request for the client device to confirm the detected presence of malware in the one or more server-stored files. A confirmation response is received from the client device. The confirmation response identifies at least one of the one or more server-stored files and confirming the presence of malware activity in the identified server-stored files.

Abstract: A storage system comprises a disk array enclosure comprising an enclosure controller, a cache comprising a metadata journal, a plurality of data storage devices and a plurality of metadata storage devices. The enclosure controller is configured to write a stripe metadata page to the metadata storage devices that corresponds to a stripe of data stored on the data storage devices and to determine that the write of the stripe metadata page failed for a first metadata storage device. The enclosure controller is configured to add an entry to the metadata journal based on the determination that the write failed. The entry comprises an indication of the first metadata storage device and the stripe of data. The enclosure controller is configured to set an indication in a data structure associated with the disk array enclosure that the stripe metadata page has not been written to the first metadata storage device.