An Error Message Is Displayed Indicating that the Path of a Storage Unit Is Invalid

Symptom

When you create a storage unit on eBackup, the system prompts a message indicating that the path of the storage unit is invalid. See Figure 1.

Figure 1 Error message

Troubleshooting

Possible causes are listed here in order of their probability.

If the fault persists after you have ruled out one cause, move on to the next one.

Figure 2 Troubleshooting

The System Time of eBackup Is Greatly Different from the Actual Time

On the navigation bar of eBackup, choose > System Time & Zone to check whether the difference between the system time and the actual time is greater than 1 minute.

If yes, change the system time to the actual time. For details, see Configuring System Time & Zone.

The Network Between eBackup and CBR Is Inaccessible

Run the curl -kv https://Domain name:443 command to ping the endpoint of the region where your CBR service resides. For details about the regions and endpoints, see "Regions and Endpoints".

• If the endpoint can be pinged but the problem persists, submit a service ticket.
• If the endpoint cannot be pinged, check whether the public network has been configured.
  • If the public network has been configured, check whether the domain name resolution is complete by following the instructions in How Do I Test Whether Record Sets Have Taken Effect?
    • If the resolution is complete but the problem persists, submit a service ticket.
    • If the domain name has not been resolved, configure the correct user DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 114.114.114.114.
      Figure 3 Modifying the DNS
      
  • If the public network has not been configured, configure it by following instructions in Planning the Network.

The Network Between eBackup and OBS Is Inaccessible

VMware backups are automatically uploaded to an OBS bucket. If the communication between eBackup and OBS is abnormal, an error will be reported.

Run the curl -kv https://Domain name:443 command to ping the endpoint of the region where your OBS service resides. For details about the regions and endpoints, see "Regions and Endpoints".

• If the endpoint can be pinged but the problem persists, submit a service ticket.
• If the endpoint cannot be pinged, check whether the public network has been configured on premises.
  • If the public network has been configured, check whether the domain name resolution is complete by following the instructions in How Do I Test Whether Record Sets Have Taken Effect?
    • If the resolution is complete but the problem persists, submit a service ticket.
    • If the domain name has not been resolved, configure the correct user DNS, and run vi /etc/resolv.conf to edit the /etc/resolv.conf file. Add the DNS server IP address above the existing nameserver information. The DNS server IP address is 114.114.114.114.
      Figure 4 Modifying the DNS
      
  • If the public network has not been configured, configure it by following instructions in Planning the Network.

Submitting a Service Ticket

If the problem persists, submit a service ticket.