Hi, AFAIK in OrientDB Studio, Enterprise Restore feature, reads some metadata, this could explain why just copying the files won't work.
@Enrico, WDYT? Best Regards, Luca Garulli Founder & CEO OrientDB LTD <http://orientdb.com/> On 30 August 2017 at 17:25, AnSDE007 <[email protected]> wrote: > I am new to OrientDB. > > We are evaluating an open source master patient index application which > uses embedded Enterprise OrientDB 2.2.17. One of the DR (Disaster > Recovery) requirements is to be able to restore the backup on a different > server/instance. Below are the steps that I have taken and so far I have > not been able to get this working. > > 1. On server 1, schedule a non-blocking backup in Full+Incremental mode in > Studio Management > 2. On server 1, wait until *full.ibu and *.ibu are created. In > Production, there will be a script that copy these files to a file system > on a different file server every night. > 3. On server 2, copy those *.ibu and *full.ibu files from step #2 > 4. On server 2, launch Studio Management and attempt to access and restore > the backups > > The issue I am having is that the Studio Management on server 2 does not > appear to recognize the *full.ibu and the *.ibu files. Hence, I am unable > to restore the database on server 2. > > Am I missing any key steps here? Is there a different approach to > accomplish this? > > > > > > > > > -- > > --- > You received this message because you are subscribed to the Google Groups > "OrientDB" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > For more options, visit https://groups.google.com/d/optout. > -- --- You received this message because you are subscribed to the Google Groups "OrientDB" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
