Trouble Adding Data Domain Repository

[Jsiver]

So incase I've missed something simple here and someone can point it out to me. We are in the process of migrating off of VMware/ESXi to Nutanix/AHV. We have a Data Domain 6900 as our primary repository for all of our VMware backups, its currently being used with DDboost and has no issues.

Now mabye this is where the problem lies, but, we've spun up a new VBR instance that is not connected to the old VMware VBR server in anyway and want to connect this to the same DD6900. I added a new DDboost storage unit with a new account associated to it on the DD6900. I've run through all the installs for VBR with the AHV plugin on the new Server 2022 on the AHV cluster. When I try to Add the DD6900 backup repository it tells me that the destination is unreachable, I've tried connecting to the new one and current storage unit the old VBR server is using. From the new server I have tested and added every port listed and all showed connectivity correctly. There is no Antivirus/EDR enabled yet. I've tried disabling windows firewall entirely to rule that out. I've opened a ticket with support but while I'm waiting is there something stupid I've missed?

Thanks!

[foggy]

Can you please share the support case ID number? Thanks!

[Jsiver]

Sure, Case #07561678

[Jsiver]

Apparently there is a character limit for stored credentials in 12.3?

We've used a 100 character generated password for our existing VBR server and DDboost account but when using a similarly length password on the new VBR server it was failing. Lowing the password to 50 characters allowed it to work. The old VBR server is version 11 still so mabye this is a new limitation?

Anyway, that was the issue and I was able to add the repository after changing the DDboost password to a shorter one.

[foggy]

100-character password - wow.

It comes down to a max password length limitation in DDBoost SDK. On the Data Domain itself, you can create a DDBoost user with a password length of 100 characters, while DDBoost SDK supports a maximum of 64 characters.

Code: Select all

[10.01.2025 10:47:45.427] < 12224> ddboost  |   [DDP][ERROR] [ 2536] [12224] ddp_connect_with_user_pwd() failed, Hostname: 172.25.25.143, Err: 5008-Password length > 64

Chances are, a previous DDBoost SDK version used in v11 didn't have this limitation or had it set to a higher value, which is why it worked fine. I also believe you can set the DDP_MAX_PASSWORD_LEN value to a higher limit if you still want to use your lengthy password with 12.3.