Услуга · System administration

Restoring 1C to working order

Our area is the technical health of the accounting system: that the database opens, documents post, and the next update does not leave the company without records on the eve of a filing deadline. Methodology and customisation are handled by your own specialists.

The same day
for emergencies
Archive
taken first of all
Trial run
updates on a copy
Cause
traced through the logs

What the work includes

There is one rule and no exceptions: the database archive first, any action second. Even when the situation looks trivial.

Discuss the scope

Will not start

The database will not open, licences drop out, the server is invisible, platform versions have diverged.

Corruption

An integrity check and repair, and where repair is impossible, a restore from the archive.

Updates

Platform and configuration are updated after a trial run on a copy and with a rollback route ready.

Slow performance

We work out what is going on: mutual locks, disks, lack of memory, jobs running at the wrong time.

Licences

Software and hardware keys, the licensing server, surprises after components are changed.

Moving to a server

When the file-based option can no longer cope with the number of people working at once.

How it goes

Emergencies we take on the day you call. Planned work we move to the evening or the weekend.

01

Archive

We take a full copy of the database. That is always the first action, whatever the situation.

02

Cause

We identify it from logs and symptoms rather than by trying options at random.

03

Repair

We repair it, if necessary on a copy first, then carry the fix to the live database.

04

Prevention

We set up backups and housekeeping jobs so that it does not happen again.

A database that has never been rolled up grows to the point where it cannot be worked with. Ten years of history drags behind every report and every document posting. Rolling up old periods and moving the archive into a separate database speeds work up more than any server replacement.

Questions and answers

By pinning down what exactly is slow: one particular operation, all documents alike, or only at certain hours. The usual culprits are mutual locks during shared work, mechanical disks and housekeeping jobs launched in the middle of the day. The analysis takes a few hours.

The file-based option is bearable for five to ten people and a modest volume. Beyond that the risk of corruption and the response time both grow. For twenty users the server option is essential, not least for the safety of the data.

No, that is work for accounting specialists, and we work alongside them. Ours is the platform, the server, the database, updates and speed - that is, everything that can stop the system opening.

We will repair the accounting database

Describe what is happening and since when. In an emergency we join the same day and start with an archive.