The following is a list of recent changes and improvements made to i-2-S3. Most changes are made as the direct result of a customer request. If you have changes you would like to see made to i-2-S3, send E-mail to us by clicking here Support@Kisco.com and we'll add your change to our list of possible implementations.
Effective date: February 21, 2018
i-2-S3 now allows for a save set name to be duplicated. Prior to this change, i2S3 specifically prevented a save to a specific bucket to use the same save set name as one that already existed there. With this change, it is the customer's responsibility to check when a duplicate is being used and to be aware that the prior saved set at Amazon S3 will be replaced with the new set being sent. If you want your save sets at S3 to be versioned, then you must control the naming yourself before the save is stored at S3.
Effective date: February 5, 2018
With this release, level 1.10, i-2-S3 now supports a new command called S3RTV (Retrieve IFS File from S3). While other commands in i-2-S3 are designed for save/restore processing, this new command will let customers transfer any file from S3 to the IFS without extracting it from save/restore format. This allows customers to transfer content from S3 as is to the IFS.
Effective date: January 26, 2018
With this release, level 1.10, i-2-S3 now supports a new command called S3SND (Send IFS File to S3). While other commands in i-2-S3 are designed for save/restore processing, this new command will let customers transfer any file from the IFS to Amazon S3 without putting it into save/restore format first. This allows customers to transfer content to S3 as is from the IFS.
Effective date: July 22, 2010
With this release, level 1.06, i-2-S3 now supports using data compression prior to sending a backup set to Amazon S3 for storage. This option is available on the S3SAVOBJ, S3SAVCHGOB, S3SAV and S3SAVLIB commands. i-2-S3 offers the settings of *NO (no compression, the default setting), *YES (a medium compression) and *HIGH (the best compression option). Using compression can cause more processing on your server prior to tranmission to Amazon, but the resulting transmission time can be reduced along with the charges from Amazon for total storage used.
Effective date: June 16, 2010
With this release, level 1.05, i-2-S3 now has a printed report showing the object details for every object in a backup set stored at Amazon S3. This report can be produced for any backup set stored.
Effective date: March 25, 2010
With this release, level 1.04, i-2-S3 now includes automatic retry processing when a transmission error causes a save (send) operation to fail. A retry limit has been implemented and i-2-S3 will automatically retry your save process until it is either successful or the retry limit is reached.
Effective date: March 25, 2010
With this release, level 1.04, i-2-S3 now captures and shows the elapsed time for all save (send) operations. This information is rounded to the nearest minute and provides you with the ability to measure the time for backup operations with Amazon S3.
Effective date: February 8, 2010
With this release, level 1.03, i-2-S3 now includes the ability to generate a printed report showing all of the current backup sets stored at Amazon S3. If a backup set is encrypted, the key needed to decrypt the file is included.
Effective date: December 3, 2009
As of i-2-S3 Release 1.02, all save operations have an option to encrypt the save set prior to sending it to be stored at Amazon S3. All restore operations have also been changed to allow for the use of a decryption key to decrypt a save set during restore processing.
Effective date: October 5, 2009
All of the save operations implemented in i-2-S3 now support an optional parameter for the target OS level. The save file created can be restored to the OS level specified.