Restore failing

Submitted by Brook on Thu, 07/23/2015 - 07:30

Trying to restore I get this error:

Restoring backup for virtual server directory.mydomain.com ..
Restoring virtual server password, quota and other details ..
.. done
Updating administration password and quotas ..
.. done

Restoring Cron jobs ..
.. done

Extracting TAR file of home directory ..
.. TAR failed!

/bin/tar: ./apps/mydirectory/current: Cannot open: File exists
/bin/tar: Exiting with failure status due to previous errors
.. failed! See the progress output above for the reason why.

I am not sure now, but I think I might have done a restore previously (as a test) but deleted it - could that be an issue?

Or, that this is a subdomain and the root domain does not exist yet (hasn't been restored yet).

All other restores have worked fine, but this is the first sub-domain restore so wondering if it is some sort of bug (or a bug that only appears in the above circumstances).

Status: 
Active

Comments

Submitted by andreychek on Thu, 07/23/2015 - 09:01

Howdy -- it looks like in "./apps/mydirectory/", there is an existing file or directory named "current".

What are the permissions on that file or directory?

You can determine that with this command:

ls -la ./apps/mydirectory/

Submitted by Brook on Thu, 07/23/2015 - 09:10

Here ya go Eric:

# ls -la ./apps/mydirectory/
total 20
drwxrwxr-x   5 mydirectory mydirectory 4096 Jan  6  2014 .
drwxrwxr-x   3 mydirectory mydirectory 4096 Dec 21  2012 ..
drwxr-xr-x   3 mydirectory mydirectory 4096 Jul 23 14:14 current
drwxrwxr-x 105 mydirectory mydirectory 4096 Jun 28  2013 releases
drwxrwxr-x   8 mydirectory mydirectory 4096 Dec 21  2012 shared

Submitted by andreychek on Thu, 07/23/2015 - 09:21

If the "current" directory is contained within the backup, you may want to try deleting the contents of that directory there and see if that allows it to work.

Submitted by Brook on Thu, 07/23/2015 - 11:53

Hi Eric,

On the original server I have:

# ll
total 12K
lrwxrwxrwx   1 root            root              66 Jan  6  2014 current -> /home/mydirectory/apps/mydirectory/releases/20130628205833
drwxrwxr-x 105 mydirectory mydirectory 4.0K Jun 28  2013 releases
drwxrwxr-x   8 mydirectory mydirectory 4.0K Dec 21  2012 shared

Do you think that is causing the issue? (That's a symlink right?)

When you say delete the contents of that directory, do you mean on the old server (before taking a new back up) or on the newly restored server and then try the restore again?

Submitted by JamieCameron on Thu, 07/23/2015 - 13:08

You should try removing that symlink on the destination system, and then do the restore again.

Submitted by Brook on Thu, 07/23/2015 - 16:32

Hi Jamie, there isn't a symlink on the destination system - but I deleted the directory and it's worked! (And contains a symlink as per the original).

What happened there then? Was it because I had carried out a restore previously? (Though I am not 100% sure I did on this install).

Submitted by JamieCameron on Thu, 07/23/2015 - 19:08

Do you perhaps have some script hat runs after a domain is created which adds that symlink?

Submitted by Brook on Fri, 07/24/2015 - 06:49

No, it's just a normal backup and restore.

I will be doing the same again soon as I am moving all sites back to the old server once its reformatted with centos7... will be interesting to see if it happens again.

Actually I have another site with a similar set-up that needs to be transferred over yet too..