Update 3 - IBM Storage Integration

[ferrus]

I've just started looking into the IBM storage intregration in 9.5 u3, and have a question about access permissions.
Do you know which User Group is required for the level of access required by Veeam? Admin, Restricted Admin, Copy Operator etc ...

[nielsengelen]

The right role can be found in the User Guide. For IBM we need an account with admin privileges.

[ferrus]

Thanks - I was looking in the user guide, but I missed that page.

There's still three levels of admin users on our IBM SAN - SecurityAdmin, Admin, RestrictedAdmin.
I'll try RestrictedAdmin and make my way up.

[ferrus]

SecurityAdmin - too much, RestrictedAdmin - too little (can create the snapshot, but not delete), standard Administrator is the one to choose.

Only problem now, is that there's a snapshot left on the v7000. It isn't being picked up in the Storage Infrastructure tab, or removed on subsequent backups.
Is that normal? I could delete it from the v7000 gui, but not a SAN admin so I'd rather Veeam could do it.

[foggy]

Just a guess, could it be a leftover from the time when you used RestrictedAdmin (which doesn't have rights to remove snapshots)? If there are no new leftovers with the current permissions level, this might be the case. You can remove it manually, Veeam B&R doesn't delete old stuff to prevent deletion of something useful.

[cgrvy]

Hi - just trying to figure out what level of access the user needs when using IBM or Lenovo Storwize SAN integration. Its not specified in the documentation as far as I can see.

I'm setting up a Veeam user on my units and can specify if they are:
SecurityAdmin
Admninistrator
CopyOPerator
Service
Monitor
RestrictedAdmin

I'm thinking CopyOperator as from the IBM documentation it states:

Copy Operator
Users can start and stop all existing FlashCopy®, Metro Mirror, and Global Mirror relationships. Copy-operator-role users can run the system commands that administrator-role users can run that deal with FlashCopy, Metro Mirror, and Global Mirror relationships

Thanks!

[ferrus]

See my thread here - vmware-vsphere-f24/update-3-ibm-storage ... 47757.html

I didn't try with CopyOperator, but got an error with RestrictedAdmin.
Backups currently working with Administrator.

[cgrvy]

Thanks - I'll go with Administrator.

[neilmurphy65]

Hi.

Is there a best practice guide or whitepaper for integrating VBR with IBM Storwize? I've already looked at the official documentation for v9.5 but it doesn't have much that is specific to Storwize.

Thanks,
Neil.

[DGrinev]

Hi Neil,

Can you clarify what information related to IBM StorWize integration you want to get?
Please review this thread as it might contain useful information. Thanks!

[neilmurphy65]

Hi Dmitry. Sorry I missed your reply. I work for a Veeam disti and a partner called my looking for anything I might have on best practices when integrating VBR and Storewize. I couldn't find anything online so I turned to the forums.

[DGrinev]

Hi Neil,

You can review Backup from Storage Snapshots section in the best practices portal it might be useful.
The rest information related to storage integrations is in the User Guide. Thanks!

[crackocain]

Hello

When i use Primary Snapshot Integration Veeam creates a snapshot in the IBM Spectrum Virtualize.

But this name is too long. Veeam add "VeeamProductionSnapshot" in the beginning. So snapshot name is

VeeamProductionSnapshot_JobName.year-month-day-hourminutes

This is too long for IBM Spectrum Virtualize so job name is shrinking automatically. Not understandable which job related to which snapshot. Could you please change "VeeamProductionSnapshot" to "VPS" or something? I searched registry but i can not see any DWORD key for that.

[Andreas Neufert]

Thanks for the feedback. Can you please send us an example how the snapshot names are look like at the moment?


FYI @foggy

[crackocain]

I remove the first section for security but job name is XXXXXXXXXX-pri_sas_vol1

We see only "XXXXXXXXXX-pri_sas_v"

Which job is vol1, vol2, vol3?

This limitation is IBM related but Veeam spend character a lot

[Andreas Neufert]

Thanks this helps to understand the situation better.

[foggy]

Thanks, Mehmet, will discuss this with R&D, I think we can cut the prefix a bit.

[crackocain]

Thanks Alex

[crackocain]

Hello Alex, Andreas

In V11 this issue is resolved. (spend a lot of characters) Thank you very much!

[foggy]

Thanks for confirming it has resolved for you, Mehmet!