Copying Databases

[Kevin Mayfield]

I'm after copying one of our databases to a new server. The database is on 2013.1 and the destination is on 2015.1.

I assume this is possible - Backup using management portal and then restore using ^DBREST. It isn't at the moment - which I may need to log with wrc.

Can I do this another way? As the database is part of a mirror, so I could stop the mirror and do a copy of the database folder and move that to the new location.

Would I be able to unmark this database as a mirrored read only db and bring it online?

(I used to do the this side of things with MSM but Cache admin is new(ish) to me!)

Many thanks

[Kevin Mayfield]

Amendment... the backup and restore does seem to work, I'm just a little impatient :)

[Dubois]

Maybe you can try GBLOCKCOPY routine 

--
--
Caché, Ensemble, DeepSee

---
You received this message because you are subscribed to the Google Groups "Caché, Ensemble, DeepSee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to intersystems-publi...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Tom Fitzgibbon]

Kevin -

There are some unanswered configuration questions (same platform?, etc) in your post but most of the time:

1) You can take down Cache on your source box

2) Copy Cache.dat file to your destination box

3) Add Database/Namespace on your destination and setup whatever resource security you want.

4) Immediately access your globals and routines

5) You may have to recompile routines by Do ^%RCOMPIL

6) You probably have to recompile objects, classes, etc. by Do $SYSTEM.OBJ.CompileAll("")

7) Look for any odd methods, classes that are no longer in Cache 2015 from Cache 2013 and replace.

8) Do ^INTEGRIT and check app for problems.

Hope this helps.

Tom Fitzgibbon | Multidata | 212-967-6700 x537

On Thu, Apr 30, 2015 at 10:38 AM, Kevin Mayfield <mayfiel...@gmail.com> wrote:

Amendment... the backup and restore does seem to work, I'm just a little impatient :)

[Kevin Mayfield]

In the end I copied the classes over and started a new production.

I couldn't get around the restored database thinking it was still in a mirrored environment (mirror was 2013 and non mirrored 2015.1). As it thought it was still part of the mirror, the database refused to come online in read/write mode and remained read only.

GBLOCKCOPY may have worked though.

Thanks for the help

[Adam Lees]

Did you try the ^MIRROR routine to edit the mirrored/non-mirrored flag?  

Thinking about it, it might actually be one of the flags in ^DATABASE.

I had to do similar at one point before I left your place.  ;)

[Kevin Mayfield]

Your correct, our normal DBA said the same. :)