Support

I created a new profile that is intended to back up just one directory that exists outside of the site's root directory.  The pattern is as follows:

   root directory:  /abc/xyz/public_html/

   target directory:  /abc/my_docs

 

I was able to use Akeeba to find and select this 'off-site' directory, but when I restore on my local machine... well, I assume the content was not included because my WAMP does not have the same directory structure underneath the site.

What I'm after is a way to archive that directory, store it on S3 along with the full backup, and be able to restore the directory so I have a copy of the directly/files on my local machine.

Is the only way to do this is to replicate the underlying directory structure?  (in my example:  /abc/xyz/public_html)  I do prefer an alternate way, but at the least I'd like be able to restore on a local machine so that I can confirm the backup file is backing up the directory as I expect.

 

 

 

Thank you.  I now see how it works, and I see what I did wrong. 

I had not declared a virtual subdirectory (because I did not know what that meant nor that it was required).  I just now discovered that by not declaring a virtual subdirectory that the entire record is not saved.  So, when I made the backup, the off-site directory was not included within the backup file, and I never encountered the screen you just referenced.

I fixed the problem on my end, tried to restore again, and now I see the screen you mentioned.

However, I have encountered a problem after this point --  it seems that the amount of large documents in this folder exceeds what the restoration can copy within 120 seconds.  ("Maximum execution time of 120 seconds exceeded in ...")  I have rerun this multiple times, and it seems only a few files are added to those already copied over (the folder and its subfolders exceed a gig in size).  Is there some setting that instructs this portion of restoration to be performed in chunks so as never to exceed the time limit?  Or some other way?  

I suspect the issue is file size and not the number of files.  Of what is restored by the time it times out, the directory has only 73 files but the restored files are 840 meg with a .tmp folder that contains 1.88 gig.  This is a large directory of the hundreds of documents stored through eDocman.  

OK.  I appreciate the candid answer.  I'll look into FTP as a solution.  ...Or perhaps try to restore the files on a fast webserver (so that the archive process still used Akeeba profiles uploading to S3).

This ticket has been automatically closed. All tickets which have been inactive for a long time are automatically closed. If you believe that this ticket was closed in error, please contact us.