Highlighted

More improvements to AMS in 3.2 ?

Have any improvements been made to the AMS software in v3.2 ? Like maybe allowing you to run it on an existing Master/Media Appliance instead of having to dedicate an entire box to the function ? Or if you're going to leave it on a dedicated box, then make available a downloadable VM image of an AMS that you can deploy without needing a full costly license ? Maybe allowing the AMS to auto-submit hardware failure tickets to Support on behalf of Appliances that don't have direct Internet access ? Or even something simple like allowing the same user account to have both AMS & NetBackup roles ?

It feels like the AMS has a lot of promise but I'm still waiting to see what happens with it.

1 Solution

Accepted Solutions
Accepted Solution!

Re: More improvements to AMS in 3.2 ?

Thank you for your question.

There are number of improvements that we have put into AMS for NBA 3.2. This will be called as AMS 1.3:

  1. EEB install end to end automation with minimal (unavoidable) or no manual intervention required
    1. Restart services during EEB install
    2. Override conflicting EEBs
    3. Uninstall EEB remotely
  2. Upgrade support for NBA 3.2
  3. Appliance overview enhancements (Enter & save your metadata related to appliance or rack information)

Our next version is AMS 2.0 which will be in virtual form factor.  AMS 2.0 can be deployed as a virtual appliance in your infrastructure (planned).

The features like RBAC, hardware monitoring, support case automation are all part of the roadmap.

Also, want to clarify that, even today you can use your NBA hardware appliance as AMS. AMS coexists on NBA with your master or media server, it doesn’t need dedicated resources as of AMS 1.2. You can use NBA for your data protection needs & use it as AMS at the same time.

1 Reply
Accepted Solution!

Re: More improvements to AMS in 3.2 ?

Thank you for your question.

There are number of improvements that we have put into AMS for NBA 3.2. This will be called as AMS 1.3:

  1. EEB install end to end automation with minimal (unavoidable) or no manual intervention required
    1. Restart services during EEB install
    2. Override conflicting EEBs
    3. Uninstall EEB remotely
  2. Upgrade support for NBA 3.2
  3. Appliance overview enhancements (Enter & save your metadata related to appliance or rack information)

Our next version is AMS 2.0 which will be in virtual form factor.  AMS 2.0 can be deployed as a virtual appliance in your infrastructure (planned).

The features like RBAC, hardware monitoring, support case automation are all part of the roadmap.

Also, want to clarify that, even today you can use your NBA hardware appliance as AMS. AMS coexists on NBA with your master or media server, it doesn’t need dedicated resources as of AMS 1.2. You can use NBA for your data protection needs & use it as AMS at the same time.