Quantcast

backup.sh restore problems

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

backup.sh restore problems

mountainbiker
ITEM 1
When trying to do a partial database restore via the command line with backup.sh -- as described in the documentation on http://exist-db.org/exist/apps/doc/backup.xml like

bin/backup.sh -u admin -p admin-pass -P backup-pass
                        -r /var/backup/hd060501/db/__contents__.xml

The script is giving an error that -b is null.  Providing -b /tmp allows the restore to occur, but contents are also written to /tmp.

Am I doing something incorrectly?

ITEM 2
I have 2 instances of eXist of the same VM.  One is at port localhost:8080 and the other is at localhost:8081.  When attempting to restore to localhost:8081, it is restoring to localhost:8080.  I have modified the EXIST-HOME/backup.properties.

What might be causing this?
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: backup.sh restore problems

mountainbiker
ITEM 2 -- disregard; non-issue.
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: backup.sh restore problems

Adam Retter
In reply to this post by mountainbiker
Yes there was a bug, this was fixes 27 days ago here -
https://github.com/eXist-db/exist/commit/c3c035ab5264d93997f09c1d28b4d060757fcbfe

I believe that it is fixed in the eXist-3.1.1 release

On 14 April 2017 at 04:02, mountainbiker <[hidden email]> wrote:

> *ITEM 1*
> When trying to do a partial database restore via the command line with
> backup.sh -- as described in the documentation on
> http://exist-db.org/exist/apps/doc/backup.xml like
>
> bin/backup.sh -u admin -p admin-pass -P backup-pass
>                         -r /var/backup/hd060501/db/__contents__.xml
>
> The script is giving an error that -b is null.  Providing -b /tmp allows the
> restore to occur, but contents are also written to /tmp.
>
> /*Am I doing something incorrectly?*/
>
> *ITEM 2*
> I have 2 instances of eXist of the same VM.  One is at port localhost:8080
> and the other is at localhost:8081.  When attempting to restore to
> localhost:8081, it is restoring to localhost:8080.  I have modified the
> EXIST-HOME/backup.properties.
>
> /*What might be causing this?*/
>
>
>
> --
> View this message in context: http://exist.2174344.n4.nabble.com/backup-sh-restore-problems-tp4672075.html
> Sent from the exist-open mailing list archive at Nabble.com.
>
> ------------------------------------------------------------------------------
> Check out the vibrant tech community on one of the world's most
> engaging tech sites, Slashdot.org! http://sdm.link/slashdot
> _______________________________________________
> Exist-open mailing list
> [hidden email]
> https://lists.sourceforge.net/lists/listinfo/exist-open



--
Adam Retter

eXist Developer
{ United Kingdom }
[hidden email]
irc://irc.freenode.net/existdb

------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Exist-open mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/exist-open
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: backup.sh restore problems

mountainbiker
Thanks Adam.  Yeah, I can confirm we have 3.1.0.
Loading...