09-06-2012 06:36 AM
Hi,
We are having some problems with setting up BackupExec 2012 when we try to edit or create a backup for a Windows server.
When we attempt to edit an existing job or creating a new one, and save the changes, we receive the following error:
HostId: The length of the value must fall within the range "0" (Inclusive) - "32" (Inclusive).
The HostId that's been assigned to the server (to be backed up) is it's IPv6 address, which is obvously longer than 32 characters in length. The server is running SP1a with all available updates according to LiveUpdate.
How would we go about fixing this error?
We are having a few other problems (it's our first time setting up BackupExec) but I will post them separately.
Thanks,
Stephen N
09-06-2012 07:01 AM
Try to add the server with any of the following by clicking on Add Servers:
1) IPv4 address. 2) Netbios Name 3) FQDN name.
Hope this helps.
Thanks,
Riyaj
09-06-2012 05:01 PM
Trying any of these options still results in Backup Exec selecting IPv6 address of the server to use for the host ID.
Is there a way of manually setting the host ID to something else?
Are others using IPv6 in a Backup Exec environment and what have been the results?
What should the host ID usually end up being set to (when it's working properly)?
09-06-2012 05:15 PM
09-06-2012 05:55 PM
You could try to force BE to use only IPv4. Click on the BE button ---> Configuration and Settings ---> Backup Exec Settings
09-06-2012 09:06 PM
I've tried that to no avail. We do have a support ticket open, but here are the details of the problem I've been able to work out so far:
09-07-2012 08:23 AM
Please open a support case for this issue. This issue is under investigation.
Thanks,
Riyaj
09-08-2012 12:20 AM
Hi Riyaj,
Yes we do have a support case open at the moment.
For others who may be experiencing the same issue you can, as a temporary solution, reduce the lengths of the IPv6 address of the server (by using ::). If the length of the address is 32 characters or less the host ID will be accepted and the backup will proceed.
You will need to restart all BE services (including Deduplication ones) to generate the new host ID.
Cheers,
Stephen
09-17-2012 10:13 AM
Where you able to get a reolution? Having the same issue here.
09-17-2012 04:34 PM
Hi,
No we haven't as yet. Symantec are still investigating the issue. My guess is that we'll need a hotfix to correct the problem.
As a workaround, if you can get the IPv6 address of client down to less than 32 characters (using ::) you can continue to perform the backup - though I realise this might not be possible in some environments.
Note that if you change the IPv6 address of the client you will need to restart the Backup Exec services in order for it to update the Host ID.
Cheers,
Stephen
09-18-2012 06:06 AM
Yeah I dont want to mess with IP setting in our live enviroment, but I was able to do another work around of deleting the trust and publishing on the agent and restarting BUE, then adding the info back in. That seems to work for now.
09-19-2012 11:29 AM
Same issue here : Case 418-536-806