Backup to Amazon S3 and schedule multiple backups with v5.8.2

You will find that Amazon S3 has been added as a new option for your backup files. From the Appliance Manager, you can now schedule backups to be sent automatically to S3 on a regular schedule.

The SFTP server settings now take port name and key as options.

You can now add multiple backup schedules and send your backups to different destinations. Last status for each job has been added as well.

• /api/1.0/multinodes/ to add devices which might have duplicate serial #s and UUID.
• /api/1.0/pdus/ PUT call to edit existing PDUs.
• /api/1.0/patch_panel_module_model/ POST call to add Patch Panel Module Models.

A number of API calls were modified to accept object names in addition to IDs. We will soon be updating the API docs to reflect these changes

• patch_panel_ports API call now accepts patch panel name, module slot, front port name and port number combination and back port name and number combination.
• imgfile(name of the image file) can now be used in addition to imgfile_id when adding/updating hardware models, PDU models, and assets by adding the imgfile parameter to the API calls.
• The switchport post call now supports direct device connection.

Two system-generated event types have been added to the event pulldown in the Asset Lifecycle sections of the Device and Asset edit screens. You can now check out and check in devices and assets. A device can only be checked in if it’s already checked out and can only be checked out if it’s not already checked out.

You will also find a “Checked Out To” column in the Device and Asset reports that will display the end user who the device/asset is checked out to.

The Device and Asset reports now have two new filters: Has Been … and Has Not Been…

For example, if you want to see only devices that have been inventoried, select Inventoried from the Has Been… filter. If you want to see only devices that have been destroyed, select Destroyed from the Has Not Been… filter.

As same device is discovered from multiple discovery methods (e.g. Cisco UCS Discovery, vCenter Host discovery and IPMI discovery), the first discovered name is used for that device. OS level discovery will most probably have the correct name, and hence we have added an option for hostname precedence for vServer discovery.

• Permission issue for showing parts per device with read-only access has been fixed.
• Mail server settings in the main app and appliance manager restricted the password length to 32 characters. Now fixed.
• Modular patch panel ports were not showing the full path – now fixed.

Current users can grab the update file from: /update/