Page 1 of 1
This destination path is already owned by other destination in different server
Posted: June 16th, 2021, 6:13 pm
by Nirjonadda
Hello,
We have problem Create New Destination for SSH after upgraded v5. Create New Destination will be happened error but we have used this info for v4 without any issue. Please can you let me know that how can fixing this issue?
Code: Select all
Error: This destination path is already owned by other destination in different server. (Server Id: ff93d08b873fdaab91b3467db75d4069)
Thanks
Re: This destination path is already owned by other destination in different server
Posted: June 17th, 2021, 12:39 am
by JetAppsRichard
On JetBackup 5, In order to increase the security of your backups, JetBackup has decided to allow only one Destination per Backup Directory. If the destination with the exact same Backup Directory path was used on a previous installation of JetBackup 5 it will result in the following error:
Code: Select all
Error: This destination path is already owned by other destination in this server. (Destination: "NAME" ###################)
If you want to work around this error you can create the destination as a Read-Only Destination which will allow you to access the backups from that Backup Directory but will not be able to write new backups to that directory. More information on Read-Only Destinations can be found here:
SSH - Read Only Destination.
Otherwise, you will need to remove the `.jetbackup` file that is located within the Backup Directory. Once this lock file has been removed, you will be able to create the destination with the original Backup Directory. However please note that since this is a "New Destination" JetBackup 5 will not be able to continue incremental backups on the existing backups. It will start from new backups. This has been gone through in detail in the forum:
Change cpanel server with same backup job
Please let us know if you have any more questions.
Re: This destination path is already owned by other destination in different server
Posted: July 8th, 2021, 5:38 pm
by Nirjonadda
Yes, This issue fixed with remove the `.jetbackup` file. Thanks