Archive SAP HTTP Content Server

[Former Member]

Hi

we are facing some problems with our SAP Content Server

we have a content server repository of our SAP system CRM ABAP 7.0

next are the settings:

Storage type: SAP HTTP Content Server,  File system

version no: 0046,  content server version 4.6

Server version:  6400

Server patch: 9

Server build:  201

our content server right now has more than 3 Tera Bytes just in one drive (unit P) we don't have much more space to provide to this drive so my boss is asking me if we can make archiving, something like move some historical files to a different server with a diferent speed of IO but more cheaper than actual storage and the same time with the posibility of be queried on line.

I have been looking for information about archiving of content server without succes,

please could you help me with some ideas or documentation to solve this problematic please,,

bets regards

[benedikt_wagner_mdt · Accepted solution]

Hi Alfredo,

I don't think that there is a possibility to "archive" a Content Server.

But you could create another content repository on the existing or a new Content Server and move files from the old repository to the new one.

You could use Report RSIRPIRL for this.

For the new repository (Transaction OAC0) a new category has to be defined (Transaction OACT).

I've done this a long time ago for a small number of documents. Please test this before moving a large number of files and create a backup of the old system before moving. The files will be deleted in the original system.

Regards,

Benedikt

[Former Member · Accepted solution]

Thanks for the answer Benedit,

but I have one doubt,  if I'd create another content repository on the existing, could users continuing seeing the old files online?

Thanks for the answer Benedit,

but I have one doubt,  if I'd create another content repository on the existing, could the users continuing seeing the old files online?

I mean the problem here is that at last I'm going to need the old information online so I wonder if this approach help us

thanks ind advance

[benedikt_wagner_mdt · Accepted solution]

Hi Alfredo,

there will be no problem accessing the files (as long as you use SAP standard KPro). They are moved from the old repository to the new repository. In the SAP tables the old category is replaced by the new category, so SAP knows where the files are located.

Regards,

Benedikt

[Former Member · Accepted solution]

Hi Benedikt

So If I want to create another repository  on the existing content server we have to migrate the old files?

I think this won't be helpful because the reason to create other repository is to divide in two drives the information because the actual drive is too huge, more than 3 TB.

what we want is to have two repositories  online at the same time,the first with the historical files and the second with the new files.

on the other hand you mentioned that

"In the SAP tables the old category is replaced by the new category, so SAP knows where the files are located."

my content server is a file server without DB, so I'm not sure if the same solution apply

thanks in advance

[benedikt_wagner_mdt · Accepted solution]

Hi Alfredo,

I think, there are two issues:

1. storage issue: fact is, you will need a new repository (let's name it ZNEW) because the old repository is full. Repository is created in transaction OAC0. There are two options which will have the same effect.

a) add a second disc/drive to the existing server and create new repository on this new disc (I'm no hardware expert).

b) install a second content server on another computer and create new repository on this computer

Your CRM system does not know about the type of the content server. File based or DB based does not matter. If you store a file on content server only repository name and physical ID (PHIO) are necessary and used.

After that you have to create a new category referencing the new repository in transaction OACT (copy old category). Let's name it ZNEWCAT.

2. second issue is about managing old and new files. There are also two options with the same effect:

a) first solution is to migrate the files from the old to the new repository using report RSIRPIRL. This would be used if the new repository is on a slower hardware than the old repository and you want to have faster access to new files.

b) better solution if both repositories have same performance: go to transaction SKPR08 and maintain the new storage category to be used instead of the old one.

Example from GTS system (I have no access to a CRM system):

After that new documents are stored in the new repository; the old documents are still accessable in the old repository. No migration is needed.

To find the class you can use table SDOKIOCL. Select this table in SE16 with DOCUSPACE = <Document area from transaction OACT, old category>.

Regards,

Benedikt

[Former Member · Accepted solution]

excellent aportation Benedikt, I could  perform a test with next suggestions:

I created a new repository Z_CONT_CSP_DEV in OAC0 tcode

I created a new drive in other hardware cheaper than actual

the new repository was mapped with network path (\\servername\contentserver)

I created a new category referencing the new repository (ZNEW)

In tcode SKPR08 we mantained the new category in the appropiate class

and it was a succes, new documents are being saved in new drive and the old files are still accesible from old drive,

Just i have one doubt because we are not sure if the class we selected is the correct class because when we run se16 table SDOKIOCL  DOCUSPACE = (documentarea of old category) we couldn't get results as above image.

Thanks in advance

[benedikt_wagner_mdt · Accepted solution]

Hi Alfredo,

apparently you use the correct class. Otherwise the replacement would not work.

But I'm wondering why there is a Z-docuspace (ZCRM as far as I can see in the screenshot). Does the class you've used in SKPRO08 exist in SDOKIOCL? What docuspace is assigned to the class?

Regards,

Benedikt

[Former Member · Accepted solution]

Hi  benedikt

the class is CRM_P_ORD and it exists  in the table with docuspace  CRM next is the evidence:

on the other hand we realized that our content server stores other kind of documents like cases(sacse) or guides (commpr01)  and this documents have other kind of classes (CRM_P_CASE,BDS_POC22 )

but in SKPR08 we can't see that classes to map the new category,

best regards

[benedikt_wagner_mdt · Accepted solution]

Hi Alfredo,

you can set flag CAT_MAINT in table SDOKPHCL for the classes you want to map.

This table is part of the view maintained in SKPR08 and classes with set flag will be visible.

But it could be that SAP will overwrite this flag in future support packages.

It would be interesting if Christoph Hopf has an opinion on changing table SDOKPHCL.

Regards,

Benedikt