The task "Create backup of VPS 'hostname' from HN 'hw_name'" or "Backup VPS 'hostname'" fails with the following error messages:
417 : Environment 'UUID' doesn't exist
414 : Access is denied
VPS does not exist on the hardware node. It may happen if the VPS was migrated to another server manually, not via the POA Control Panel.
Find the hardware node where the problem VPS is actually located and migrate it back to the server where it is located according to the POA database. After that process the failed task and migrate the VPS back if necessary.
Alternatively, you may contact the Parallels Support Team to change information about the VPS location in the POA database. In this case the existing task to backup the VPS has to be cancelled, failed backup has to be removed from POA and the new task to backup the VPS may be scheduled after the POA database was adjusted.
In case you do not know where the VPS is currently located find some advices how to find missing VPS below.
Login to the hardware node where the VPS in question is located according to the POA database. The required hardware node may be found in the failed task name or in the list of VPSs in the POA Provider Control Panel at Service Director > Virtuozzo Manager > VPSs.
Make sure that the VPS is absent on the server - use the 'vzlist -a' command to see the list of all VPSs on the server and check if the VPS with required hostname and ID is present in the list. The ID and hostname of the problem VPS may be found in the POA Provider Control Panel in the list of all VPSs.
Try to find the server where the VPS is located actually:
Check all POA-managed VPS hardware nodes of the same platform (Windows/Linux) in the POA Provider Control Panel:
- Go to Service Director > Virtuozzo Manager > VPS Hardware Nodes
- Click on a hardware node
- Switch to the VPS > Not registered VPSes tab
- Check if the VPS in question is present on the server
Log into every single VPS hardware node and check if the missing VPS is there.
If the VPS was migrated manually then information about the target node may be found in the log file on the server where VPS is located according to the POA database:
- Log into the server
Linux hardware node:
Try to find the entries like below in the /var/log/messages file:
Oct 28 12:43:46 vzlin01 vzmsrc: Connection to destination node (192.168.55.83) is successfully established Oct 28 12:43:46 vzlin01 vzmsrc: Moving/copying CT#1226 -> CT#1226, ,  ...
The log entries above mean that the VPS #1226 was migrated to the server with the IP address 192.168.55.83
Windows hardware node:
Try to find the entries like below in the log files in the c:/vzlog/pva/agent/ folder, e.g. 2013.10.28-vzagent.log:
T=12:48:38:781; L=(inf); PID=2464; TID=1550; P=VZLMigratorLocal [VZL::VZLMigratorLocal::migrateVirtualToVirtual] [VZL::VZLMigratorLocal::migrateVirtualToVirtual] migrate EID=52c7f406-e1b4-4b86-8a24-b6ca67ff4fa7, timeout=36000 ...... T=12:48:39:468; L=(inf); PID=2464; TID=1650; P=VZLOperatorCommon [VZL::VZLHaulControlOperatorPrototype::ChannelHandlerPrototype::doConnect] [VZL::VZLHaulControlOperatorPrototype::ChannelHandlerPrototype::doConnect] Connecting to 10.39.18.66:4435
The log entries above mean that the VPS with EID (UUID) 52c7f406-e1b4-4b86-8a24-b6ca67ff4fa7 was migrated to the server with the IP address 10.39.18.66