Page 1 of 1

Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 8:11 am
by ravi
Hi

Would like to know -the best practice tm1 data directory -while refreshing data directory from test to prod and dev.

while refreshing dev environment from prod Is there any code in dev that needs to be saved so that we don’t lose it with the refresh?

Regards,
Ravi

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 8:37 am
by Christopher Kernahan
How are you "refreshing"? Are you copying the Prod data directory over the Dev data directory? In this case you'll overwrite anything in Dev.

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 8:41 am
by ravi
Steps:

1) take back of dev data folder
2) delete the data directory objects from folder
3) copy data objects from prod and paste it in dev

ravi

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 1:36 pm
by tomok
ravi wrote:Is there any code in dev that needs to be saved so that we don’t lose it with the refresh?
How would anybody but yourself know this????? No one on this forum could possibly know what you have done in DEV versus PROD. The bottom line is that if you refresh DEV by copying in the contents of the data folder from PROD then you will be replacing everything that USED TO BE in DEV. To the extent that you have done development in DEV that had not already been promoted to PROD then it will be gone. Best practive is always to make a backup copy of the data folder in DEV before doing the refresh. Actually, you should do this for ALL environments any time you do a promotion so that youi can have a direct and easy recovery path in case you want to back it out.

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 4:03 pm
by ravi
Hi

I noticed that Views that are built in prod are lost when i refreshed the data from Prod to dev-

could you please comment.

Raavi

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 6:33 pm
by David Usherwood
Errr....
How did you refresh the data?
If you copied the cubes, wouldn't it be sensible to copy the views as well?
But really, you need to have a better understanding of this admittedly quite tricky task. Iboglix provide no tools at all to help so you have to do it yourself.

Re: Tm1 data Backup - best practice

Posted: Thu Sep 29, 2011 10:32 pm
by afshin
"Steps:

1) take back of dev data folder
2) delete the data directory objects from folder
3) copy data objects from prod and paste it in dev"

"I noticed that Views that are built in prod are lost when i refreshed the data from Prod to dev-
could you please comment."

At no point you restore the views back on the dev server !!

Re: Tm1 data Backup - best practice

Posted: Fri Sep 30, 2011 1:08 am
by winsonlee
Which version of TM1 are you using ?

CX9.5 comes with a very handy tool for you to backup your data. On Cognos Express Manager under administration, you can use Backup and Restore. Create a backup for your dev server before restoring the data from the production.

If you are not, you can create a batch script to zip the data folder in your dev folder before replacing it with your production data. The two files that needs to be excluded from the copying process are tm1s.cfg and tm1rawstore.*.

Re: Tm1 data Backup - best practice

Posted: Sun Oct 02, 2011 1:42 am
by afshin
You will also find "IBM Cognos TM1 Backup and Recovery Guide" from the IBM Developer Works helpful !!

Re: Tm1 data Backup - best practice

Posted: Tue Oct 04, 2011 1:23 am
by Kyro
For those not running Cognos Express w/ Manager - I've just posted this solution for backing up a TM1 Server. Its implemented as a TI process with a commercially free command line executable (7-Zip).
Heres the link: http://blog.tm1tutorials.com/2011/10/04 ... 1-backups/
Let me know if this helps, or if theres a better way - theres always a better way when it comes to TM1.

Re: Tm1 data Backup - best practice

Posted: Wed Mar 20, 2013 10:19 pm
by jameswebber