A method, system and computer program product for backup assignment of a mobile electronics device is disclosed. In response to one or more device assignment requests received by a controller apparatus when a server is operating in an off-line mode, one or more device assignment records are created within the controller apparatus, and which indicate assignment of the at least one mobile electronics device to a respective one or more users. When the server is operating in an off-line mode such that communication between the controller apparatus and the server is off-line, the one or more device assignment records, in relation to the at least one mobile electronics device, are stored in the controller apparatus. In response to the server re-entering the on-line mode, the server is updated with the one or more device assignment records.

Data recovery systems and methods utilize object-based storage for providing a data protection and recovery methodology with low recovery point objectives, and for enabling both full recovery and point-in-time based recovery. Data generated at a protected site (e.g., via one or more virtual machines) is intercepted during write procedures to primary storage. The intercepted data is replicated via a replication log, provided as data objects, and transmitted to an object based storage system. During recovery, data objects may be retrieved through point-in-time based recovery directly by the systems of the protected site, and/or data objects may be provided via full recovery, for example, within a runtime environment of a recovery site, with minimal data loss and operation interruption by rehydrating data objects within the runtime environment via low-latency data transfer and rehydration systems.

Devices and techniques for a storage backed memory package save trigger are disclosed herein. Data can be received via a first interface. The data is stored in a volatile portion of the memory package. Here, the memory package includes a second interface arranged to connect a host to a controller in the memory package. A reset signal can be received at the memory package via the first interface. The data stored in the volatile portion of the memory package can be saved to a non-volatile portion of the memory package in response to the reset signal.

Embodiments for a storage classifier that provides recommendations to a backup server for storage targets among a plurality of disparate target storage types. The storage classifier receives metadata (name, type, size), and the Service Level Agreement with information such as: retention time, Recovery Point Objective, and Recovery Time Objective) from the backup software. The backup software itself receives policy recommendations from a data label rules engine based on certain file attributes. The storage classifier receives an initial recommendation for the storage type and location (e.g., on-premises deduplication storage or public-cloud object storage, etc.) from a data classifier. Based on these inputs, the storage classifier provides recommended specific storage targets to the backup software on a file-by-file basis for data stored in a backup operation.

Provided is a backup system including a storage system and a backup server, in which the backup server includes a ledger for managing a copy number and a backup acquisition date and time for each backup image, a data volume that stores data accessed by a business server, a backup image volume that stores a plurality of backup images at different time points of the data volume, an access volume having a volume ID for accessing the backup image from the backup server, and a data protection area including at least one volume having an internal volume ID instead of the volume ID for accessing from the backup server are configured in the storage system, and the backup image stored in the data protection area and the access volume are associated, and the backup image in the data protection area is provided to the backup server.

A method and system for auto live-mounting database golden copies. Specifically, the disclosed method and system entail reactively auto live-mounting golden copy databases on hosts or proxy hosts based on the operational state of one or more database hosts and/or one or more assets (or databases) residing on the database host(s). Should a database host prove to be unresponsive, through periodic monitoring, databases residing on the database host may be brought back online on a proxy database host using stored golden copies respective of the aforementioned databases. Alternatively, should a given database on any database host exhibit an operational abnormality (e.g., an error, failure, etc.), the given database may be brought back online on the database host or a proxy database host using a stored golden copy respective of the given database. Accordingly, through the disclosed method and system, database outages may be minimized.

Described in detail herein is a method of copying data of one or more virtual machines being hosted by one or more non-virtual machines. The method includes receiving an indication that specifies how to perform a copy of data of one or more virtual machines hosted by one or more virtual machine hosts. The method may include determining whether the one or more virtual machines are managed by a virtual machine manager that manages or facilitates management of the virtual machines. If so, the virtual machine manager is dynamically queried to automatically determine the virtual machines that it manages or that it facilitates management of. If not, a virtual machine host is dynamically queried to automatically determine the virtual machines that it hosts. The data of each virtual machine is then copied according to the specifications of the received indication.

In one example, initiating data replication process to copy source data set as target data sets to a plurality of target devices during a predefined time period, determining progress information regarding completion of the replication process based on historical and current performance information of the plurality of target devices, and if the progress information indicates that the replication process is not to be completed within a predefined time period, then selecting a target device from the plurality of target devices to complete the complete the replication process based on historical and current performance information of the plurality of target devices, and causing the selected target device to continue with the completion of the replication process, causing the non-selected target devices to discontinue with the replication process, and causing the replicated target data set to be copied to another target device of the plurality of target devices.

In one embodiment, automated storage target selection includes automatically selecting a storage node of a plurality of candidate storage nodes as a function of a plurality of selection criteria. Further, a backup data object is transmitted to the selected storage node. In one embodiment, selecting a storage node includes retrieving stored user-defined parameters for selection criteria for selecting a storage node, retrieving storage node-defined parameters for selection criteria, comparing user-defined parameters and storage node-defined parameters, and selecting a storage node as a function of the comparing. In another aspect of the present description, comparing user-defined parameters and storage node-defined parameters includes broadening a first user-defined parameter to a second user-defined parameter broader than the first user-defined parameter if no candidate storage nodes have a storage node-defined parameter within the first user-defined parameter. Other features and aspects may be realized, depending upon the particular application.

An upgradable electronic device is disclosed. The electronic device includes: a main controller including a single-chip microcomputer including an internal memory and a processing unit; and a communication unit receiving upgrade data from outside the electronic device, wherein, when existing program data stored in a first area of the internal memory has a size less than or equal to a reference size, the processing unit updates the existing program data stored in the first area based on the upgrade data after backing the existing program data up to a second area of the internal memory, the second area being different from the first area.