Troubleshoot XCP NFS errors
Review the solutions to troubleshoot your issue.
XCP issues and solutions
XCP issue | Solution | ||
---|---|---|---|
|
You are trying to perform operations on an index that was generated using an XCP version older than XCP 1.9. This is not supported. It is recommended to complete any in-progress migrations and then switch to this version of XCP. Alternatively, you can re-run the |
||
|
Execute XCP commands as root user |
||
|
Download the license from the XCP site, copy it to |
||
|
Renew or obtain the new XCP license from the XCP site. |
||
|
License file might be corrupted. Obtain the new XCP license from the XCP site. |
||
|
Run the |
||
This copy is not licensed |
Obtain the appropriate XCP license file. Copy the XCP license to the |
||
|
You are trying to activate the online license and your host system is not connected to the internet. Make sure your system is connected to the internet. |
||
|
Make sure xcp.netapp.com is reachable from your host or request for the offline license |
||
|
Open the editor on the XCP Linux client host and update the configuration file with the proper catalog location. The XCP configuration file is located at |
||
|
Operation did not find the source file(s) on the target NFS export. Run the |
||
|
Previous copy operation was interrupted before the index file was created. Rerun the same command with the new index and when the command is executing, verify that the keyword “indexed” is displayed in the stats. |
||
|
Follow the instructions in the following KB article: Cannot allocate memory when synching NFS data |
||
|
Mount the source and target on the XCP host using NFSv4, for example, |
||
The XCP |
The XCP |
||
The XCP |
The XCP cutover sync operation might not have copied all the data. Rerun the XCP |
||
The XCP |
XCP is not able to read the data, this might be due to an XCP issue. Check the XCP STATUS message after the command operation completes. |
||
The XCP |
There is low available memory on the host or there has been a huge incremental change. Follow the instructions in the following KB article: Cannot allocate memory when synching NFS data |
||
|
As a non-root user, you do not have the correct permissions to access the file system. Check if you can access the file system and perform read write operations. |
||
|
As a non-root user, you do not have the correct permissions to access the file system. Check if you can access the file system and perform read write operations. |
||
|
The path |
||
|
The |
||
The |
You can identify the file and manually copy the file to the destination. |
||
|
Because you cannot resume a single file, it is recommended to run the |
||
|
Because you cannot sync a single file, it is recommended to run the |
||
|
Verify that the node given in the |
||
|
Check if you have permission to write on the destination volume. |
||
|
Increase your system memory and rerun the test. |
||
|
If there is one or more colons in the NFS server share path name, use a double colon (::) instead of a single colon (:) to separate the NFS server IP and NFS server share path. |
||
The SnapLock volume does not retain the WORM files after an |
XCP copies the WORM files to the volume successfully but the files are not retained by the SnapLock volume.
When the above steps are complete, the SnapLock volume starts retaining the copied files.
|
Logdump
If you encounter an issue with an XCP command or job, the logdump
command enables you to dump log files related to the issue into a .zip
file that can be sent to NetApp for debugging. The logdump
command filters logs based on the migration ID or job ID and dumps those logs into a .zip
file in the current directory. The .zip
file has the same name as the migration or job ID that is used with the command.
Example
xcp logdump -j <job id> xcp logdump -m <migration id>
After migration, if you use the XCP_CONFIG_DIR or XCP_LOG_DIR environment variables to override the default config location or log location, the logdump command fails when used with an old migration or job ID. To avoid this, use the same logpath until migration completes.
|