cancel
Showing results for 
Search instead for 
Did you mean: 

compatibility of SMI-S with backup exec 12.5

daedro
Level 2

compatibility of SMI-S with backup exec 12.5

Hi my name is Daniel,

I have to configure a Virtual library system of hp with this feature:

Smart Copy
Smart copy allows the backup application to trigger copies from virtual cartridges to destination cartridges, and the VLS then performs that copy inside the device. The backup application can only use this feature if it supports the HP smart copy mechanism (via SMI-S v1.3 or later copy services).

 

And the question is: is compatible back up exec 12.5 with smi-s v1.3 copy services.

 

Thank you

1 ACCEPTED SOLUTION

Accepted Solutions

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi daedro,

 

Looks like that is a specific feature of the HP VTL...much like the snapshot technology built into an EVA controller.

In this regard, as long as your HP VTL is on the HCL for BE 12.5 (and there a couple mentioned in the BE 12.5 HCL; you don't mention yours!), it will be able to work with the backup software. If not, check the HCL for BE 2010 R2 which might be a worthwhile upgrade if you're able to.

That said, you won't be able to use that Smart Copy software. However, you can duplicate backup sets within BE itself, so you can do what you need to this way. It is built into the software, and doesn't need any additional licensing. You'd simply create a duplicate job to run after your initial job which will duplicate that backup set to another VTL drive. Using this, you would not need to use Smart Copy.


Thanks!

View solution in original post

5 REPLIES 5

RahulG
Level 6
Employee

Here the compatibility list http://www.symantec.com/business/support/index?page=content&id=TECH62114

and its not supported

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi daedro,

 

Looks like that is a specific feature of the HP VTL...much like the snapshot technology built into an EVA controller.

In this regard, as long as your HP VTL is on the HCL for BE 12.5 (and there a couple mentioned in the BE 12.5 HCL; you don't mention yours!), it will be able to work with the backup software. If not, check the HCL for BE 2010 R2 which might be a worthwhile upgrade if you're able to.

That said, you won't be able to use that Smart Copy software. However, you can duplicate backup sets within BE itself, so you can do what you need to this way. It is built into the software, and doesn't need any additional licensing. You'd simply create a duplicate job to run after your initial job which will duplicate that backup set to another VTL drive. Using this, you would not need to use Smart Copy.


Thanks!

daedro
Level 2

sorry, the virtual library system is vls9000 series of hp and physical library will be msl2024 fc 1840.

on the HCL appears the vls9000 but the doubt is with this:

The backup application can only use this feature if it supports the HP smart copy mechanism (via SMI-S v1.3 or later copy services).

You know if backup exec 12.5 have SMI-S protocol

 

thank you

CraigV
Moderator
Moderator
Partner    VIP    Accredited

Hi,

 

Not sure why you want to use this feature...SMI-S is a SAN communication tool, and as such has nothing to do with the BE software at all.

You'd basically use SMI-S to talk to WBEM on HP Systems Insight Manager for instance, or to get a server to manage that VLS on the SAN...nothing more.

BE will duplicate the data in the same way that Smart Copy does. You can do disk-to-disk-to-tape, disk-to-tape-to-tape etc.

SMI-S in this context is unnecessary.

 

Thanks!

teiva-boy
Level 6

As others pointed out, what you want, would be to assume you have an ALL HP system including SAN's, VTL, Tape, and HP's dataprotector as well.

If BE can use HP's VTL, you can already duplicate the VTL images to physical tape TODAY.  The only thing that would need to happen is that your tape library is physically connected to your BackupExec server via either FC/SCSI/SAS.  If it were direct connected to your VTL, it would not be possible.

 

Smart Copy is nothing more than a fancy gimmick by HP to sell more HP products with proprietary features that are unique to that manufacturer.  BTW, SMI-S is a lost cause and not embraced as much as it should be. I refer to it as SNMP for SAN's, on steroids..