Archiving: WRITE task only runs in a single job while DELETE runs on 4 jobs

[Former Member]

Hi,

I am archiving Change documents (archiving object CHANGEDOCU).

I have assigned in customizing (transaction SAR_OBJ_IND_CUS) the server group for background processing BATCH.

This server group has in SM61 assigned 4 servers.

The customzing F1 says:

Server Group Name for Data Archiving Jobs

The background processing system distributes all data archiving jobs (write jobs, delete jobs, read jobs, and so on) to application servers in the specified server group.

When I run the WRITE task it only creates 1 job

If I run the DELETE task it runs in 4 jobs

The WRITE job takes too much time and I am wondering why it does not use the server group.

Anyone can help?

Thanks in advance!

Thomas

[JPReyes · Accepted solution]

You can run as many write jobs as you wish as long as you use different variants to catch different data. As far as I know theres no way to run a particular write job using parallel processes. Server Group name is simply used to set a specific group of instances to handle the archiving load.

Regards

Juan