Skip to main content

We've Moved!

Product Documentation has moved to docs.hitachivantara.com
Hitachi Vantara Knowledge

Troubleshooting HCP

This section provides guidelines for how to troubleshoot issues that might occur when using Hitachi Content Platform.

Changing the namespace size on HCP node has no effect

Problem:

Changing the namespace size once an HCP node has been created has no effect.

Solution:

To change the namespace size please use the HCP user interface.

Cannot connect to HCP or HTTP 503 Service Unavailable

Problem:

The messages:

Couldn't connect to server

or

HTTP status 503 Service Unavailable

might appear when attempting to authorizing an HCP node.

Solution:

Check that the Management API is enabled in the Tenant Console on HCP for that tenant.

Couldn’t resolve HCP host name

Problem:

The message:

Couldn't resolve host name

might appear when attempting to authorize an HCP node, or might be logged when tiering.

Solution:

Check that the HCP tenant can be contacted; for example, by pinging the tenant using the host name to ensure DNS is working correctly.

If system level credentials were provided then ensure that the Allow HCP system-level users to manage me and search across my space check box is checked on the HCP’s Tenant’s Overview window.

HCP connection returns HTTP status 403 Forbidden

Problem:

The message:

HTTP status 403 Forbidden

might appear when authorizing an HCP node or might be logged when tiering.

Solution:

Check all the HCP node details are correct including Username, Password and Tenant.

HCP returns Request Entity Too Large error

Problem:

The message:

Request Entity Too Large

might be logged when tiering to HCP.

Solution:

Check on HCP that the namespace has not exceeded its quota and that the tenant has not exceeded its quota.

HCP restore finished with minor issues

Problem:

The message:

The restore finished with minor issues.

might be logged when restoring from HCP.

Solution:

This may occur if files have been deleted from HCP by an application other than Protector. The log attachment lists the paths that the missing files were originally backed up from by Protector.

HCP Node stays offline after node creation

Problem:

After creating a HCP node, it remains offline:

Solution:

Ensure that the Proxy Node defined within the wizard and the Hitachi Content Platform node are time synced. If the time is different by over 5 minutes, then the node creation and future backup may fail. It is recommend that the system time on all nodes should have the correct date/time associated with their particular region and time zone.

 

  • Was this article helpful?