Abstract: A quick buffer validity check can optionally be performed when a potential invalidity of the content of a buffer is identified. The identifying of the potential invalidity condition can include determining that a most recent lifecycle management event timestamp is more recent than a most recent buffer validity check timestamp for the buffer. To determine whether the buffer contents need to be refreshed, a list of the last changed timestamps for the constituent elements of the buffer can be compared to a new list. If the new list and the old list are not identical, the buffer can be rebuilt.

Abstract: A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative.

Abstract: A cluster of computer system nodes connected by a storage area network include two classes of nodes. The first class of nodes can act as clients or servers, while the other nodes can only be clients. The client-only nodes require much less functionality and can be more easily supported by different operating systems. To minimize the amount of data transmitted during normal operation, the server responsible for maintaining a cluster configuration database repeatedly multicasts the IP address, its incarnation number and the most recent database generation number. Each node stores this information and when a change is detected, each node can request an update of the data needed by that node. A client-only node uses the IP address of the server to connect to the server, to download the information from the cluster database required by the client-only node and to upload local disk connectivity information.

Abstract: A mechanism is provided for message reconciliation during disaster recovery in an asynchronous replication system. A message is intercepted at a gateway remote from a primary data centre to which the message is being sent. A copy of the message request is stored in a request message history remotely from the primary data centre. The message is forwarded to the primary data centre. A transaction history of the message request is stored at the primary data centre which is mirrored to a disaster recovery site with other data from the primary data centre. In response to determining that the primary data centre has failed, messages in the request message history are compared with messages in the transaction history as retrieved from the disaster recovery site.

Abstract: A software module capable of simultaneously supporting multiple services provides log message throttling for each service with a separate “per service” log message buffer. When the software module is a device driver, for example, each device controlled by the device driver is allocated a message buffer to store descriptive log messages. Upon generation of a warning log message, descriptive log messages in the message buffer are flushed to a log file for review by an administrator. Furthermore, log message throttling may be implemented by only flushing the message buffer upon certain occurrences of warning log messages, such as in accordance with an exponential back-off algorithm.

Abstract: A method for recovering hard disk data, a server and a distributed storage system relate to a computer technology. In the method, a data recovery request is received. The request includes at least one ID of sectors whose data is to be recovered. Based on the at least one ID of the sectors whose data is to be recovered, at least one sector whose data is to be recovered is located. Obtain at least one standby sector ID and a file backup corresponding to the at least one ID of the sectors whose data is to be recovered, and locate at least one standby sector based on the at least one standby sector ID. Write, into the at least one standby sector, data that is in the file backup and the same as the data stored in the at least one sector whose data is to be recovered.

Abstract: Systems and methods for providing automated computer support are described herein. One described method comprises receiving a plurality of snapshots from a plurality of computers, storing the plurality of snapshots in a data store, and creating an adaptive reference model based at least in part on the plurality of snapshots. The described method further comprises comparing at least one of the plurality of snapshots to the adaptive reference model, and identifying at least one anomaly based on the comparison.

Abstract: Methods by a processing system are disclosed that control recovery of operational state values of a complex event processing (CEP) engine that processes values of events. A window size is determined based on a property of an event query. Events' values are retrieved from a distributed log which are restricted to occurring within a timeframe defined based on the window size. The distributed log stores events' values that have been processed by the CEP engine. The retrieved events' values are replayed to the CEP engine for processing to recover the operational state values of the CEP engine. Related processing systems are disclosed that control recovery of operational state values of a CEP engine that processes values of events.

Abstract: Some embodiments of the invention provide techniques whereby a user may perform a system reset (e.g., to address system performance and/or reliability degradation, such as which may be caused by unused applications that unnecessarily consume system resources, an attempted un-install of an application that left remnants of the application behind, and/or other causes). In some embodiments, performing a system reset replaces a first instance of an operating system on the system with a new instance of the operating system, and removes any applications installed on the system, without disturbing the user's data.

Abstract: An approach is provided for integrating data. Data is collected from one or more source systems and workflow data is extracted from the collected data. One or more predetermined tasks associated with execution of a workflow based on the workflow data are identified. Status information relating to progress of the workflow towards completion is estimated by correlating the workflow data with the one or more predetermined tasks.

Abstract: Backup applications that use externally connected hard disk drives for storing full image backups of a windows system disk or compressed image or file by file backups of a windows system disk. A system incrementally updates the images, including the system registry, and puts information on the external drive that makes it bootable.

Abstract: An approach is provided for migrating data. Data is received from a plurality of source systems. The received data is processed for conversion to a target system. A failure condition associated with the processing is detected. An action is selectively initiated from a point of failure corresponding to the detected failure condition. The action includes either retrying the processing, aborting the processing, initiating simulation of the process, forcing completion of the processing, or a combination thereof.

Abstract: A technique manages a virtual hard disk tree in a computing system executing a hypervisor to provide a client virtualization environment. The technique involves linking, by a client executing within a control virtual machine of the client virtualization environment, a first delta image of a virtual hard disk generated later in time to a base image of the virtual hard disk. The technique further involves modifying contents of the first delta image, the base image, and a second delta image which is linked to the base image; and deleting the second delta image after modifying the contents of the first delta image, the base image, and the second delta image. The base image and the first delta image, together with additional delta images of the virtual hard disk comprise a tree of images of the virtual hard disk.

Abstract: Data replication in a distributed node system including one or more nodes. A consensus protocol for failure recovery is implemented. Data items and information relating to consensus protocol roles of participant nodes are stored in at least some of the plurality of nodes. Logical logs stored in at least some of the plurality of nodes are created. The logical logs contain additional consensus protocol information including container metadata and replicated data.

Abstract: A disaster recovery system, including a target datastore for replicating data written to source datastores, and a checkpoint engine (i) for transmitting, at multiple times, quiesce commands to a plurality of host computers, each quiesce command including a timeout period that is adjusted at each of the multiple times, (ii) for determining, at each of the multiple times, whether acknowledgements indicating that a host has successfully stopped writing enterprise data to the source datastores, have been received from each of the host computers within the timeout period, (iii) for marking, at each of the multiple times, a cross-host checkpoint in the target datastore and reducing the timeout period for the quiesce commands at the next time, if the determining is affirmative, and (iv) for increasing, at each of the multiple times, the timeout period for the quiesce commands transmitted at the next time, if the determining is not affirmative.

Abstract: Technologies are described herein for incorporating streaming and/or sampling in real-time log analysis. Representative samples of log data are extracted from the log files on a number of monitored hosts and streamed in real-time to log processors for processing. The log processors accumulate and process the representative samples of log data, and track a data completeness value representing an indication of a proportion of total log data represented by the representative samples received. The representative samples of log data are merged and collated. Estimated metrics are calculated from the merged and collated representative samples and the data completeness, and the estimated metrics are published to consumers in near real-time.

Abstract: A method and system for managing operational states of database tables within a multiple-database system. If a particular user session issues a query against a target table that causes a data inconsistency, the target table transitions into an errant state and the session will become interrupted. This errant state is then propagated onto any other table associated with the user session. A session-level recovery process can thereafter be executed to repair and restore database tables associated with the interrupted user sessions without the need to take an entire database system offline.

Abstract: A computer system configured to provide fault tolerance includes a first host system and a second host system. The first host system is programmed to monitor a number of portions of memory of the first host system that have been modified by a guest running on the first host system and, upon determining that the number of portions exceeds a threshold level, determine that a checkpoint needs to be created. Upon determining that the checkpoint needs to be created, operation of the guest is paused and checkpoint data is generated. After generating the checkpoint data, operation of the guest is resumed while the checkpoint data is transmitted to the second host system.

Abstract: In a mechanism for supporting detection of a failure event, history information of a system including log information of the system including plural components and/or failure information output from each component upon occurrence of a failure in the system is collected. A detection rule for detecting an event included in a component related to the failure that has occurred is generated, and a symptom with additional information added to the generated detection rule is applied to detect the event that has caused the failure. System configuration information as configuration information of the system is acquired, and from the acquired system configuration information, partial configuration information as system configuration information related to the component that sent out the event the selection of which has been accepted is extracted. The extracted partial configuration information is added to the symptom to update the symptom.

Abstract: Technologies are described herein for providing snapshot-assisted synchronous replication between a first storage server and a second storage server. For example, a notification is received at the second storage server that the first storage server has resumed operations following a failure. At this time, the first storage server is in a first current state and the second storage server is in a second current state. Upon receiving the notification, a common snapshot is identified between the first storage server and the second storage server. Upon identifying the common snapshot, the first storage server is rolled back from the first current state to a previous state according to the common snapshot, and upon rolling back the first storage server from the first current state to the previous state, the first storage server and the second storage server are resynchronized using the common snapshot.

Abstract: On demand tracing of application code execution includes: during the execution of the application code, writing trace statements to a circular trace buffer (at a selected and potentially variable detail level); determining whether a pre-defined trigger event has occurred; in response to determining that the trigger event has occurred, outputting one or more trace statements in the circular trace buffer according to pre-defined trace parameters; determining whether a trigger end event has occurred; and in response to determining that the trigger end event has occurred, terminating the outputting of the trace statements. The trigger event and the trigger end event may be defined by names of application code variables, values for the variables, and operators to be used. The trigger end event may further be defined by a time duration for which trace statements are to be outputted, or a number of trace statements to be outputted.

Abstract: Embodiments perform automatic selection of hosts and/or datastores for deployment of a plurality of virtual machines (VMs) while monitoring and recovering from errors during deployment. Resource constraints associated with the VMs are compared against resources or characteristics of available hosts and datastores. A VM placement engine selects an optimal set of hosts/datastores and initiates VM creation automatically or in response to administrator authorization. During deployment, available resources are monitored enabling dynamic improvement of the set of recommended hosts/datastores and automatic recovery from errors occurring during deployment.

Abstract: Data communications systems and methods comprise a conductive media infrastructure in communication with a baseband data universe propagating at least one first signal and a broadband data universe propagating at least one second signal. At least one segmentation device is in communication with the conductive media infrastructure and partitions the broadband data universe from the baseband data universe. A coupling device is in communication with the at least one segmentation device and modulates transmission parameters of the second signal such that information travels within the broadband data universe via the conductive media infrastructure and avoids the baseband data universe.

Abstract: In general, embodiments of the present invention provide a DR solution for a networked computing environment such as a cloud computing environment. Specifically, a customer or the like can select a disaster recovery provider from a pool (at least one) of disaster recovery providers using a customer interface to a DR portal. Similarly, using the interface and DR portal, the customer can then submit a request for DR to be performed for a set (at least one) of applications. The customer will then also submit (via the interface and DR portal) DR information. This information can include, among other things, a set of application images, a set of application files, a set of recovery requirements, a designation of one or more specific (e.g., application) components for which DR is desired, dump file(s), database file(s), etc. Using the DR information, the DR provider will then generate and conduct a set of DR tests and provide the results to the customer via the DR portal and interface.

Abstract: Exemplary embodiments disclose a method and system for detecting a failure and resuming processing in a computing system encompassing at least two sites, a primary site and a secondary site. In a module, an exemplary embodiment generates a record of a logically consistent state and data of system components of the primary site periodically and transfers the record of a logically consistent state and data of system components of the primary site to the secondary site. In another module, an exemplary embodiment detects a failure in the primary site, halts the generation of the record of a logically consistent state and data of system components of the primary site periodically with a data freeze function, and resumes a processing of the primary site on the secondary site with secondary site components updated with a most recent logically consistent state and data of system components of the primary site.

Abstract: Provided are systems and methods for managing asynchronous replication in a distributed database environment, wherein a cluster of nodes are assigned roles for processing database requests. In one embodiment, the system provides a node with a primary role to process write operations against its database, generate an operation log reflecting the processed operations, and permit asynchronous replication of the operations to at least one secondary node. In another embodiment, the primary node is the only node configured to accept write operations. Both primary and secondary nodes can process read operations. Although in some to settings read requests can be restricted to secondary nodes or the primary node. In one embodiment, the systems and methods provide for automatic failover of the primary node role, can include a consensus election protocol for identifying the next primary node. Further, the systems and methods can be configured to automatically reintegrate a failed primary node.

Abstract: In an embodiment, a computer system accesses various different data entries in dense data array, where at least one of those data entries in the dense data array is invalid. The computer system creates an associated sparse data array that includes multiple data entries with zero values as well as data entries with non-zero values. The non-zero data entries are configured to store location information and data values for each of the invalid data entries in the dense array. The zero-value data entries are inferred from the location information of the non-zero data entries. The computer system stores the location information and data values of the non-zero data entries in the sparse data array. Those data values stored in the sparse array are proportional to the number of invalid values in the dense array.

Abstract: A method for storing objects in an object storage system includes the steps of establishing a network connection with a client over an inter-network, receiving an upload request indicating an object to be uploaded by the client, selecting at least two storage nodes on which the object will be stored, receiving the object from the client via the network connection, and streaming the object to each of the selected storage nodes such that the object is stored on each of the selected storage nodes. The method can also include writing an object record associating the object and the selected storage nodes to a shard of an object database and generating a Universally Unique Identifier (UUID). The UUID indicates the shard and the object ID of the object record, such that the object record can be quickly retrieved. Object storage infrastructures are also disclosed.

Abstract: A data grid node that is hosted by a computing system receives a request to prepare transaction operations for a multi-operational transaction for a commit. The transaction operations are associated with other data grid nodes in the data grid. The data grid node stores transaction state data for the multi-operational transaction in local memory associated with the data grid node and identifies other data grid nodes in the data grid that manage the data pertaining to the transaction operations for the multi-operational transaction. The data grid node sends the transaction state data to the other data grid nodes and the other data grid nodes store the transaction state data in local memory associated with the corresponding data grid node.

Abstract: A data processing apparatus has a plurality of storage elements residing at different physical locations within the apparatus, and fault history circuitry for detecting local transient faults occurring in each storage element, and for maintaining global transient fault history data based on the detected local transient faults. Analysis circuitry monitors the global transient fault history data to determine, based on predetermined criteria, whether the global transient fault history data is indicative of random transient faults occurring within the data processing apparatus, or is indicative of a coordinated transient fault attack. The analysis circuitry is then configured to initiate a countermeasure action on determination of a coordinated transient fault attack.

Abstract: A messaging system comprises a message source, a message receiver and a message service. The message service is intermediate of the message source and message receiver, and a compensation component is established at the message source. A one way message is transmitted from the message source, where the one-way message is part of a plurality of one way messages of an overall business transaction. The message is received at the message service and is transmitted to the message receiver, which processes the received message. The message receiver transmits a communication indicating success or failure of the processing of the message. The system causes compensation logic defined by a compensation component to execute responsive to receiving an indication of a failure of part of the overall business transaction despite the communication from the message receiver indicated that processing of the particular one way message succeeded.

Abstract: A checkpoint marker can be received at a first operator. The first operator can process the checkpoint marker by sending the checkpoint marker to a second operator and sending state checkpoint information representing a state of the first operator to a checkpoint writer. The checkpoint information can be used to rehydrate the state of one or more operators. For example, after a system failure, system shutdown, etc., checkpoint information can be received from a reader unit at a checkpoint information input queue of the first operator. A state of the first operator can be rehydrated using the checkpoint information. Processing of information in a data input queue of the first operator can be suspended while the checkpoint information is used to rehydrate the state of the first operator. Other operators in a system with the first operator (e.g., the second operator) may be checkpointed and rehydrated in the same manner as the first operator.

Abstract: The present invention is directed to a method and apparatus for storing and reconstructing data. In one embodiment of the present invention, both real-time (i.e., dynamic) information and static information are stored in a Digital Video Disk (DVD) to replicate or restore an information system. The dynamic and static information are considered trust-support data. The trust-support data provides a complete view of the information system. For example, the state of current transactions operating in the information system is part of the trust-support data. The trust-support data may include GUI information, timestamp information, network information, authentication information, generalized receipts, and specialized receipts.

Abstract: A method for reading a kernel log upon a kernel panic in an operation system is applicable to a computing device including a processing unit and a storage unit, coupled to the processing unit, for storing the kernel and including a log backup partition and a user data partition. The method includes the computing device performing the operating system by the kernel; the computing device generating a kernel log upon performing the operating system, and writing the kernel log into the log backup partition; and upon a kernel panic occurring and then the processing unit being reset, the computing device performing a kernel initialization procedure including reading and then writing the kernel log in the log backup partition into the user data partition, wherein the kernel log in the log backup partition includes information of a process of operating the kernel before the processing unit is reset.

Abstract: In a particular embodiment, a method of monitoring interrupts during a power down event at a processor includes activating an interrupt monitor to detect interrupts. The method also includes isolating an interrupt controller of the processor from the interrupt monitor, where the interrupt controller shares a power domain with the processor. The method also includes detecting interrupts at the interrupt monitor during a power down time period associated with the power down event.

Abstract: A bus monitoring and debugging system operating independently without impacting the normal operation of the CPU and without adding any overhead to the application being monitored. Users are alerted to timing problems as they occur, and bus statistics that are relevant to providing insight to system operation are automatically captured. Logging of relevant events may be enabled or disabled when a sliding time window expires, or alternatively by external trigger events.

Abstract: A computer-implemented method may include monitoring a computing system for evidence of potential data failures within the computing system. The computer-implemented method may also include detecting evidence that indicates a potential data failure while monitoring the computing system and identifying data implicated in the potential data failure based on the detected evidence. The computer-implemented method may further include initiating an action configured to proactively facilitate restoration of at least a portion of the data implicated in the potential data failure prior to determining whether the data implicated in the potential data failure needs to be restored. Various other methods, systems, and computer-readable media are also disclosed.

Abstract: Technology is disclosed herein for resolving synchronization conflicts when synchronizing application state data between computing devices. According to at least one embodiment, a server detects a first set of application state data at a first computing device conflicting with a second set of application state data at a second computing device. The first and second sets of application state data represent application states of the same computer application running at the first and second computing devices, respectively. Accordingly, the first computing device presents a user interface prompting a user to choose a preferred set of application state data between the first and second sets of application state data. If the user chooses the second set of application state data as the preferred set, the first computing device uses the second set of application state data to overwrite the first set of application state data at the device.

Abstract: Certain example embodiments provide a single pass, reverse chronological approach to write-ahead log recovery, enabling space- and time-efficient the recovery of stored data from large write-ahead logs to a transient storage medium. The techniques described herein can in certain instances enable fast and efficient recovery, even in scenarios where at the time of a failure requiring such a recovery the live log is potentially multiple terabytes or larger in size. Certain example embodiments make use of a filtering mechanism (e.g., involving potentially stateful delete, skip, and/or transaction filters), a key/value property (allowing a live set of data, once identified, to be applied in any arbitrary order), etc. A simplified environment with a small closed set of mutative operations allows for the performing of recovery backwards by scanning the log from the most recent written record backwards in time (and, in other words, finishing with the oldest record).

Abstract: In a method for determining information about a computing system, a designated process in the computing system is monitored. A determination whether a selected event has occurred in the designated process is made. State information and configuration information regarding the computing device is collected in response to a determination that the selected event has occurred. Meta information associated with the designated process is determined in response to a determination that the selected event has occurred. The state information, the configuration information and the meta information is recorded in an accessible file.

Abstract: Technologies are described herein for providing information lifecycle management (ILM)-assisted synchronous replication between a first storage server having a first current state and a second storage server having a second current state. For example, a notification is received at the first storage server that indicates the second storage server has resumed operations following a failure that occurred at a failure time. At this time, the first storage server is in the first current state and the second storage server is in the second current state that is different than the first current state. Then, ILM data for the first storage server is retrieved, and at least one block of data on the first storage server that was accessed after the failure time is identified. After identifying the at least one block of data, the identified block of data is re-synchronized between the first storage server and the second storage server.

Abstract: An image forming apparatus includes: an image forming unit configured to form images based on image data transmitted from information processing apparatus of users including registered users and unregistered users; a setting unit configured to set permission information for each user based on a log of the image forming and limit information; a first judging unit configured to determine whether user identification information is attached to image data; a second judging unit configured to determine, based on the permission information that is set for an unregistered user, whether to permit execution of image forming of the image data, when the first judging unit determines that the user identification information is not attached to the image data.

Abstract: A data management system (“DMS”) provides an automated, continuous, real-time, substantially no downtime data protection service to one or more data sources. A host driver embedded in an application server captures real-time data transactions, preferably in the form of an event journal. The driver functions to translate traditional file/database/block I/O and the like into a continuous, application-aware, output data stream. The host driver includes an event processor that can perform a recovery operation to an entire data source or a subset of the data source using former point-in-time data in the DMS. The recovery operation may have two phases. First, the structure of the host data in primary storage is recovered to the intended recovering point-in-time. Thereafter, the actual data itself is recovered. The event processor enables such data recovery in an on-demand manner, by allowing recovery to happen simultaneously while an application accesses and updates the recovering data.

Abstract: A method and apparatus for creating and using a snapshot in data backup and/or other data services. The method creates snapshot(s) of volume(s) using a select set of Snapshot Providers, transports the snapshots to a server for processing and processes the snapshots. Processing may include creating a backup, data mining the snapshot, and the like.

Abstract: Systems and methods are disclosed to check properties of bounded concurrent programs by encoding concurrent control flow graph (CFG) and property for programming threads as a first-order formula F1; initializing an interference abstraction (IA); encoding the IA as a first-order formula F2; checking a conjunction of F1 and F2 (F1^F2); if the conjunction is satisfiable, checking if an interference relation (IR) is spurious, and iteratively refining the IA; and if the conjunction is unsatisfiable, checking if an interference relation (IR) is spurious, and iteratively refining the IA.

Abstract: A messaging entity configured in a memory of first node of a plurality communicatively coupled nodes is disclosed. The nodes are included in a distributed computing system. The messaging entity is configured to operate as a secondary messaging entity in a messaging server for the plurality communicatively coupled nodes. The messaging entity is communicatively couple to a primary messaging entity configured in a memory of a second node of the plurality of nodes. The primary messaging entity is configured to store a message; store a copy of the message. Also, the messaging entity is configured to be promoted to a new primary messaging entity in the event of failure of the primary messaging entity.

Abstract: A method for updating firmware of a plurality of nodes constituting a wireless sensor network is disclosed. The wireless sensor network includes a server, a gateway and the plurality of nodes. The firmware to be updated is transmitted from the server through the gateway to an uppermost node. The firmware is sequentially transmitted to the plurality of nodes from the uppermost node to a lowermost node using wireless communication, and the respective nodes, which have received the firmware, record the firmware in their own memory. When the recording of the firmware is completed in all the nodes, boot programs of the respective nodes are run and the firmware, stored in the memory, is recorded in program memory, the firmware recorded in the nodes are executed, and the nodes constitute a new network while communicating with the peripheral nodes thereof.

Abstract: Among other aspects disclosed are a method and system for processing a batch of input data in a fault tolerant manner. The method includes reading a batch of input data including a plurality of records from one or more data sources and passing the batch through a dataflow graph. The dataflow graph includes two or more nodes representing components connected by links representing flows of data between the components. At least one but fewer than all of the components includes a checkpoint process for an action performed for each of multiple units of work associated with one or more of the records. The checkpoint process includes opening a checkpoint buffer stored in non-volatile memory at the start of processing for the batch.

Abstract: A technique for operating a group of virtual machines (VMs) includes utilizing a checkpoint procedure to maintain secondary VMs to assume tasks of primary VMs within a cluster in the event of failover. On failover of a first one of the primary VMs, a first one of the secondary VMs assumes the tasks from the checkpoint immediately preceding a failover event. Each of the primary VMs is connected to receive data from remaining ones of the primary VMs via an internal bus and process the data on receipt. Checkpoints for the primary VMs are synchronized. For each of the primary VMs, release to the external bus of data generated on the basis of received internal bus data is prevented until a subsequent checkpoint has occurred. On failover of one of the primary VMs, all of the primary VMs are directed to initiate failover to an associated one of the secondary VMs.

Abstract: The present invention is aimed to provide means and methods for recovery of an IP Multimedia Subsystem ‘IMS’ where a Home Subscriber Server ‘HSS’ holding subscriber data for subscribers of the IMS has suffered a restart. A first method of recovery is applied after detecting a HSS restart, and as receiving a registration from a given subscriber or an invitation to communicate with a given subscriber from another subscriber. A second method of recovery is applied after detecting a HSS restart, and as receiving a request from a given subscriber at a S-CSCF previously assigned for serving the given subscriber in the IMS.