Abstract: A mechanism for disaster recovery configurations and management in virtual tape applications. Specifically, the introduction of an additional computer process executing at an active datacenter site and at another active (or alternatively, a standby) datacenter site permit: (i) the generation and management of global configurations implemented on the active datacenter site prior to the occurrence of a failover event; and (ii) the implementation of global configurations on the another active (or standby) datacenter site after the occurrence of the failover event.

Abstract: Writing new data to a tape volume of a tape emulation unit includes determining if the new data is an update to data that was previously written, writing the new data to a new section of the tape emulation unit in response to the new data not updating data that was previously written, deleting the data that was previously written and writing the new data to a new section in response to the new data updating data that was previously written, the new data being larger than the data that was previously written, and the underlying file system not supporting variable size records/blocks, and overwriting the data that was previously written in response to the new data updating data that was previously written and either the new data not being larger than the data that was previously written or the underlying file system supporting variable size records/blocks.

Abstract: Writing new data to a tape volume of a tape emulation unit includes determining if the new data is an update to data that was previously written, writing the new data to a new section of the tape emulation unit in response to the new data not updating data that was previously written, deleting the data that was previously written and writing the new data to a new section in response to the new data updating data that was previously written, the new data being larger than the data that was previously written, and the underlying file system not supporting variable size records/blocks, and overwriting the data that was previously written in response to the new data updating data that was previously written and either the new data not being larger than the data that was previously written or the underlying file system supporting variable size records/blocks.

Abstract: A mechanism for disaster recovery configurations and management in virtual tape applications. Specifically, the introduction of an additional computer process executing at an active datacenter site and at another active (or alternatively, a standby) datacenter site permit: (i) the generation and management of global configurations implemented on the active datacenter site prior to the occurrence of a failover event; and (ii) the implementation of global configurations on the another active (or standby) datacenter site after the occurrence of the failover event.

Abstract: A mechanism for disaster recovery configurations and management in virtual tape applications. Specifically, the introduction of an additional computer process executing at an active datacenter site and at another active (or alternatively, a standby) datacenter site permit: (i) the generation and management of global configurations implemented on the active datacenter site prior to the occurrence of a failover event; and (ii) the implementation of global configurations on the another active (or standby) datacenter site after the occurrence of the failover event.

Abstract: A mechanism for multiple coexisting configurations support in virtual tape applications. Specifically, the introduction of various additional computer processes facilitate the introduction or modification of user specific configurations on a virtual tape solution: (i) without requiring the shutdown and re-initialization of the virtual tape solution; and (ii) without compromising the performance of computing resources allocated towards the implementation of other user specific configurations already existing on the virtual tape solution.

Abstract: A mechanism for non-disruptive virtual tape libraries configuration. Specifically, the introduction of various additional computer processes permit the configuration of a virtual tape library without requiring the shutdown and re-initialization of the host application on which the virtual tape library resides.

Abstract: A mechanism for non-disruptive virtual tape drives removal and reconfiguration. Specifically, the introduction of various additional computer processes permit the removal and reconfiguration of a virtual tape drive without requiring the shutdown and re-initialization of the host application on which the virtual tape drive is being emulated.

Abstract: A mechanism for multiple coexisting configurations support in virtual tape applications. Specifically, the introduction of various additional computer processes facilitate the introduction or modification of user specific configurations on a virtual tape solution: (i) without requiring the shutdown and re-initialization of the virtual tape solution; and (ii) without compromising the performance of computing resources allocated towards the implementation of other user specific configurations already existing on the virtual tape solution.

Abstract: A mechanism for multiple coexisting configurations support in virtual tape applications. Specifically, the introduction of various additional computer processes facilitate the introduction or modification of user specific configurations on a virtual tape solution: (i) without requiring the shutdown and re-initialization of the virtual tape solution; and (ii) without compromising the performance of computing resources allocated towards the implementation of other user specific configurations already existing on the virtual tape solution.

Abstract: A mechanism for non-disruptive virtual tape libraries removal and reconfiguration. Specifically, the introduction of various additional computer processes permit the removal and reconfiguration of a virtual tape library without requiring the shutdown and re-initialization of the host application on which the virtual tape library resides.

Abstract: Data de-duplication (“de-dupe”) allows IT organizations to replace aging tape systems with disk-based backup solutions and minimize the storage allocated to backup and data protection. The effectiveness of de-dupe technology is dependent on the data being protected. Data streams with little data repetitiveness provide disappointing results when processed through a block-level de-dupe engine. To avoid this problem, Assisted Mainframe De-Dupe (AMDD) technology can insure that filesystem block-level de-dupe products efficiently de-dupe tape backup streams received from IBM™ and/or compatible mainframes. By pre-processing backup tape volumes before sending the data to storage, AMDD insures that large amounts of unchanged data lines up on de-dupe block boundaries each time the data is sent to the de-dupe process engine.

Abstract: Data de-duplication (“de-dupe”) allows IT organizations to replace aging tape systems with disk-based backup solutions and minimize the storage allocated to backup and data protection. The effectiveness of de-dupe technology is dependent on the data being protected. Data streams with little data repetitiveness provide disappointing results when processed through a block-level de-dupe engine. To avoid this problem, Assisted Mainframe De-Dupe (AMDD) technology can insure that filesystem block-level de-dupe products efficiently de-dupe tape backup streams received from IBM™and/or compatible mainframes. By pre-processing backup tape volumes before sending the data to storage, AMDD insures that large amounts of unchanged data lines up on de-dupe block boundaries each time the data is sent to the de-dupe process engine.

Abstract: Data de-duplication (“de-dupe”) offers IT organizations the opportunity to replace aging tape systems with disk-based backup solutions and minimize the storage allocated to backup and data protection. The effectiveness of de-dupe technology is extremely dependent on the data being protected. Data streams with little data repetitiveness will provide disappointing results when processed through a block-level de-dupe engine. To avoid this problem, Assisted Mainframe De-Dupe (AMDD) technology can be used to insure that filesystem block-level de-dupe products efficiently and effectively de-dupe tape backup streams received from IBM and or compatible mainframes. By pre-processing backup tape volumes before sending the data to storage, AMDD will insure that large amounts of unchanged data will line up on de-dupe block boundaries each time the data is sent to the de-dupe process engine.