Abstract: Disclosed herein is a system for treating a magnesium or a magnesium alloy substrate comprising: a first pretreatment composition comprising a fluorometallic acid and free fluoride in an amount of 10 ppm to 500 ppm based on total weight of the first pretreatment composition and having a pH of 1.0 to 4.0; and a second pretreatment composition comprising a lanthanide series metal, the second pretreatment composition being substantially free of peroxide. Also disclosed are methods of treating a magnesium or magnesium alloy substrate. Treated magnesium and magnesium alloy substrates also are disclosed.

Abstract: The disclosure herein describes providing access to documents in a document storage platform using a document access facilitator. A base address and a security key associated with the document storage platform is obtained. A document summary presentation message is received from a presenter including a document identifier of a document and a recipient identifier of a recipient. A document summary presentation notification is sent to the recipient using the recipient identifier, the notification including the document identifier, and a document presentation request is received from the recipient. A secure access link to the document is generated using the base address, the document identifier, and the security key associated with the document storage platform. The secure access link is then sent to the recipient in response to the received document presentation request, whereby the recipient is enabled use the secure access link to access the document in the document storage platform.

Abstract: A network-agnostic processor (NAP) is configured to receive, from a first account-holding institution (AHI), an alias request to initiate a transfer. The NAP queries directory servers to retrieve one or more account numbers associated with the alias, transmits a response to the first AHI including the one or more account numbers, receives a P2P transfer request specifying one of the account numbers, and transmits an approval to an originating institution. The approval specifies one or more payment networks capable of clearing and settling funds between an initiating account and the specified account number. The originating institution is one of the first AHI or a second AHI associated with the specified account number. The NAP causes initiation of clearing and settlement of a funds transfer between the initiating account and the specified account number via a designated settlement system network (DSSN) that is one of the specified payment networks.

Abstract: Disclosed herein are systems and methods for treating a metal substrate. The system includes a first pretreatment composition comprising a fluorometallic acid and free fluoride and having a pH of 1.0 to 4.0 and a second pretreatment composition comprising a Group IVB metal or a third pretreatment comprising a lanthanide series metal and an oxidizing agent. The method includes contacting at least a portion of a surface of the substrate with the first pretreatment composition and optionally contacting at least a portion of the substrate surface with the second pretreatment composition or the third pretreatment composition. Also disclosed are substrates treated with one of the systems or methods. Also disclosed are magnesium or magnesium alloy substrates comprising a bilayer comprising a first layer comprising silicone and a second layer comprising fluoride.

Abstract: Storage of data that no longer has a useful life is established by the data objects’ user(s) and overcomes predetermined rules required by information management policies. An illustrative data agent may receive instructions from an illustrative storage manager to perform secondary copy operations for certain data objects. The instructions may instruct that expiry-marked data objects are to be treated based on parsing each data object’s user-supplied expiry timeframe. The illustrative system (i) will delete expired data objects including expired secondary copies; (ii) will refrain from making secondary copies of expired data objects; and (iii) if an expiry-marked data object is not expired, the illustrative system will make secondary copies according to the instructions, but will track those expiry-marked secondary copies for future deletion after they expire, (iv) and will delete expired secondary copies even if the original expiry-marked data object has been deleted from the system prior to its expiration.

Abstract: Storage of data that no longer has a useful life is established by the data objects' user(s) and overcomes predetermined rules required by information management policies. An illustrative data agent may receive instructions from an illustrative storage manager to perform secondary copy operations for certain data objects. The instructions may instruct that expiry-marked data objects are to be treated based on parsing each data object's user-supplied expiry timeframe. The illustrative system (i) will delete expired data objects including expired secondary copies; (ii) will refrain from making secondary copies of expired data objects; and (iii) if an expiry-marked data object is not expired, the illustrative system will make secondary copies according to the instructions, but will track those expiry-marked secondary copies for future deletion after they expire, (iv) and will delete expired secondary copies even if the original expiry-marked data object has been deleted from the system prior to its expiration.

Abstract: Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

Abstract: Snapshot-based disaster recovery (DR) orchestration systems and methods for virtual machine (VM) failover and failback do not require that VMs or their corresponding datastores be actively operating at the DR site before a DR orchestration job is initiated, i.e., before failover. An illustrative data storage management system deploys proprietary components at source data center(s) and at DR site(s). The proprietary components (e.g., storage manager, data agents, media agents, backup nodes, etc.) interoperate with each other and with the source and DR components to ensure that VMs will successfully failover and/or failback. DR orchestration jobs are suitable for testing VM failover scenarios (“clone testing”), for conducting planned VM failovers, and for unplanned VM failovers. DR orchestration jobs also handle failback and integration of DR-generated data into the failback site, including restoring VMs that never failed over to fully re-populate the source/failback site.

Abstract: A first electronic device for communication with a second electronic device on a single wire interface, includes: a memory; and a processor executing an application stored in the memory. The processor is configured to: receive, from the second electronic device, interrupt signals related with a frequency and a time space, over the single wire interface; decode an input data associated with the interrupt signals based on an interrupt protocol table; and provide the decoded input data to the application on the first electronic device.

Abstract: A computer-implemented method to transfer an electronic value amount to a recipient comprising: receiving an electronic message indicating the electronic value amount and the recipient; determining a category associated with the recipient of the electronic value amount; selecting, based on the determined category, the one of the plurality of parties storing electronic value from which to transfer the electronic value amount, the selected one of the plurality of parties storing electronic value being associated with the determined category; and outputting an electronic message to a computing device associated with the selected one of the plurality of parties storing electronic value instructing the computing device to transmit a request message to a user device operable by an owner of the electronic value.

Abstract: Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

Abstract: Snapshot-based disaster recovery (DR) orchestration systems and methods for virtual machine (VM) failover and failback do not require that VMs or their corresponding datastores be actively operating at the DR site before a DR orchestration job is initiated, i.e., before failover. An illustrative data storage management system deploys proprietary components at source data center(s) and at DR site(s). The proprietary components (e.g., storage manager, data agents, media agents, backup nodes, etc.) interoperate with each other and with the source and DR components to ensure that VMs will successfully failover and/or failback. DR orchestration jobs are suitable for testing VM failover scenarios (“clone testing”), for conducting planned VM failovers, and for unplanned VM failovers. DR orchestration jobs also handle failback and integration of DR-generated data into the failback site, including restoring VMs that never failed over to fully re-populate the source/failback site.

Abstract: An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.

Abstract: An illustrative storage management appliance is interposed between client computing devices and one or more cloud storage resources. The appliance uses cloud storage resources in conjunction with a network attached storage device configured within the appliance to provide to the client computing devices seemingly unlimited network attached storage on respective network shares. The storage management appliance monitors data objects on the network shares and when a data object meets one or more criteria for archiving, the storage management appliance archives the data object to a cloud storage resource and replaces it with a stub and preview image on the network share. When access to the stub and/or preview image is detected, the storage management appliance restores the data object from the cloud storage resource. The criteria for archiving flexibly allow individual data objects to be archived to cloud storage without archiving frequently-accessed “neighboring” data objects on the same network share.

Abstract: The present invention relates to polymers, compositions thereof, and methods of producing polymers in general. Furthermore, the present invention relates to pharmaceutical compositions and uses of said polymers, compositions and pharmaceutical compositions. More particular, the present invention relates to polymers of jasmine lactone, where pendant groups of said polymers can readily be used for attaching functional moieties comprising active agents. Furthermore, the present invention relates to modified jasmine lactones that can readily be used in methods of producing polymers of the present invention. More particular, the invention relates to polymers from renewable monomers, which can be used in applications such as drug delivery and diagnosis, polymer-drug conjugates, medical devices, cosmetic products, polymers with marker unit, polymers usable as flame retardants, tissue engineering, coatings, paints, lubricants and biodegradable plastics.

Abstract: Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

Abstract: Snapshot-based disaster recovery (DR) orchestration systems and methods for virtual machine (VM) failover and failback do not require that VMs or their corresponding datastores be actively operating at the DR site before a DR orchestration job is initiated, i.e., before failover. An illustrative data storage management system deploys proprietary components at source data center(s) and at DR site(s). The proprietary components (e.g., storage manager, data agents, media agents, backup nodes, etc.) interoperate with each other and with the source and DR components to ensure that VMs will successfully failover and/or failback. DR orchestration jobs are suitable for testing VM failover scenarios (“clone testing”), for conducting planned VM failovers, and for unplanned VM failovers. DR orchestration jobs also handle failback and integration of DR-generated data into the failback site, including restoring VMs that never failed over to fully re-populate the source/failback site.

Abstract: Certain embodiments described herein relate to an improved selective data backup system. In some embodiments, one or more components in an information management system can determine that a portion of the primary data scheduled for backup was previously backed up or is scheduled to be backed up as part of another backup operation. For example, a data agent performing a cluster-level backup operation for an entire cluster of storage servers may check whether any part of the primary data was previously backed up by a prior server-level backup operation for one of the storage servers in the cluster. If so, the data agent may skip, in the cluster-level backup operation, any portion of the primary data stored in the storage server previously backed up as part of the prior server-level backup operation.

Abstract: Storage of data that no longer has a useful life is established by the data objects' user(s) and overcomes predetermined rules required by information management policies. An illustrative data agent may receive instructions from an illustrative storage manager to perform secondary copy operations for certain data objects. The instructions may instruct that expiry-marked data objects are to be treated based on parsing each data object's user-supplied expiry timeframe. The illustrative system (i) will delete expired data objects including expired secondary copies; (ii) will refrain from making secondary copies of expired data objects; and (iii) if an expiry-marked data object is not expired, the illustrative system will make secondary copies according to the instructions, but will track those expiry-marked secondary copies for future deletion after they expire, (iv) and will delete expired secondary copies even if the original expiry-marked data object has been deleted from the system prior to its expiration.

Abstract: Snapshot-based disaster recovery (DR) orchestration systems and methods for virtual machine (VM) failover and failback do not require that VMs or their corresponding datastores be actively operating at the DR site before a DR orchestration job is initiated, i.e., before failover. An illustrative data storage management system deploys proprietary components at source data center(s) and at DR site(s). The proprietary components (e.g., storage manager, data agents, media agents, backup nodes, etc.) interoperate with each other and with the source and DR components to ensure that VMs will successfully failover and/or failback. DR orchestration jobs are suitable for testing VM failover scenarios (“clone testing”), for conducting planned VM failovers, and for unplanned VM failovers. DR orchestration jobs also handle failback and integration of DR-generated data into the failback site, including restoring VMs that never failed over to fully re-populate the source/failback site.