TM1 Forum

I would like to modify some rule, process for a cube, how to backup data in a cube and metadata for the cube?

If you have access to the Server you can copy the .cub, .dim, .pro, and .rux files to a backup folder - ensure you run a SaveData before you do so that all data in memory is written to disk.

Alternatively you can export the whole cube, right-click on the cube and use Export as ASCII/Text File. This will export the data in the cube to a .cma (text) file. Note that this won't backup your dimensions or processes so if you are planning on modifying those, then you should still copy the files, or create duplicates of the originals.

The big question is, though, why aren't you doing these changes in a development environment first?

Christopher Kernahan wrote:The big question is, though, why aren't you doing these changes in a development environment first?

Maybe because not all customers have a dev environment... As a consultant, I often see this.

Wim Gielis wrote:Maybe because not all customers have a dev environment... As a consultant, I often see this.

Very true. But on the other hand, it's not difficult to create your own version of a dev environment using the Local Server functionality for which you don't even need an additional licence. There might be an issue of available resource if the TM1 application is big, but in this case you should be able to just make a copy of the bit you will be working on.
It's always better than developing directly in production!

You're right qml.

What I do experience, however, is:
- I even do not have always access to the server (IT policy), so copying the data dir is far from feasible most of the time
- applying changes to an existing TM1 model take about 1-2 days of worth of consultancy. Hence if we need to copy a model, wait for it to be up and running, make and test the changes, copy the changes to the real TM1 environment... we "lose" time as well. It is a lot safer but not always possible.

Of coruse having DEV and PROD is better

Maybe because not all customers have a dev environment... As a consultant, I often see this.

Wim, I would hope your first recommendation is that they create one.

Christopher Kernahan wrote:

Maybe because not all customers have a dev environment... As a consultant, I often see this.

Wim, I would hope your first recommendation is that they create one.

Sure, but that's more a sales discussion in which I'm npot very much involved.
I can only stress the benefits of having it set up, and risks of not having it set up.