How to add additional storage (different file location) as part of same repository (documentum 6.7 s

We are running documentum content server 6.7 SP2. We have a single repository for all the data and the applications are setup to only query that single repository. For technical reasons, the repository is now full so I need to do something about that without affecting the current applications. I want to create a new storage area in NAS and somehow add it as part of the same repository and move a lot of the older documents over to it because it's slower storage. So in effect, I want to split a single repository into 2 storage locations.

Is there anyone that can help me figure out how to do this or if it is possible?

Thank you for your time.

Find more posts tagged with

Note:

If there are Accepted Answers, those will be shown by default. You can switch to 'All Replies' by selecting the tab below.

Accepted answers

Andrea Paci

Reading your comments I believe that you have a standard OOTB configuration. You could therefore check your current configuration for Location (storage_01 object of dm_location type) and File Store (filestore_01 object of dm_filestore type) to create new ones and later on migrate content from the original file store to the new one (in your NAS).

You can use DA for this purpose:

go to "Administration / Storage"
click on "File / New / Location" to create a new Location object (look at how storage_01 is set to create this one)
click on "File / New / File Store" to create a new File Store object (look at how filestore_01 is set to create this one)

Moving older content to the newly created File Store may look simple in the first place but you might hit a number of small problems along the line (not that you cannot overcome them by yourself!).

To migrate content from one store to another

go to "Job Management / Administrative Methods / MIGRATE_CONTENT"
in the condition, set "All content satisfying a query"
configure the rest of the options (this is the challenging part )

I suggest that you play around with DQL to get the query right (matching the content you want to move) before you commit.

Good luck!

All comments

Andrea Paci

You can use DA for this purpose:

go to "Administration / Storage"
click on "File / New / Location" to create a new Location object (look at how storage_01 is set to create this one)
click on "File / New / File Store" to create a new File Store object (look at how filestore_01 is set to create this one)

Moving older content to the newly created File Store may look simple in the first place but you might hit a number of small problems along the line (not that you cannot overcome them by yourself!).

To migrate content from one store to another

go to "Job Management / Administrative Methods / MIGRATE_CONTENT"
in the condition, set "All content satisfying a query"
configure the rest of the options (this is the challenging part )

I suggest that you play around with DQL to get the query right (matching the content you want to move) before you commit.

Good luck!

dustinb

I don't think this is what I am asking but I could be wrong. I know how to move ALL the data from one location to another but what I'm trying to do is split it between two.

I want to setup a kind of "tiered' storage where the repository is physically in two different locations or drives but they share the same repository name and so can be accessed as if it were a single repository.

Is there any way to do this? If not then I guess my only option would be to copy all the data to another location off the virtual server and update the location objects.

Andrea Paci

That is exactly what I proposed. Create a second file store in the same repository and migrate to this new file store whatever you do not want to sit on the old one.

A single repository can have many file stores; content will be accessed seamlessly.

Read my comment again, you will see that

DCTM_Guru

I believe the MIGRATE_CONTENT admin method allows you to provide a DQL predicate. This means you can specify criteria against which documents you want to migrate to the other filestore.

dustinb

Ok, I wasn't sure if that would require a different repository name. I have been trying to add a file storage location but what I want to add is not attached to the system. It is on external network share which I created a local drive mapping to Z: drive but this drive does not show up under the selections when selecting location. Is it possible to do it this way or does the location have to be physically attached?

EDIT: I was able to get it to show up by mapping the drive under the computer system account which needed me to download some external tool. Now I think I added the filestore and I have to figure out how to use the dm_migration.

Thank you.

Andrea Paci

Good to hear about your positive progress.

Keep it up!