HULFT Short Stories

Vol.3 History Management

Hello.
My name is Okazaki and I am in charge of HULFT seminar.

Hello, this is Okazaki, in charge of HULFT seminar.
It's almost September, but the hot days are still continuing.
The Summer Olympics were held in August, and fierce competition was waged in Rio de Janeiro.
Japanese athletes won a record-breaking 41 medals, creating a buzz in Japan, on the other side of the world!
The Paralympics will begin on September 7th, and we hope to continue to have high hopes for Japanese athletes.

This is the third installment of our HULFT short stories, which will explain how to use HULFT and how it can be used.
We will be delivering it to you this month too!!

The third installment is about "history management"
Let me introduce you to...

When file transfer, it is essential to record the history so that you can check the results.
Nowadays, there are cases where it is necessary to record and store transfer history as a measure for IT control. It is one of the essential elements of corporate governance. In addition, in the event of unauthorized access or operation, you may want to refer to the history to track whether it was intentional or simply an operational error.

However, the history output function is sometimes missing or insufficient.
For example, if the history is not displayed in real time but is output with a time lag, have you ever been in trouble because you were unable to respond in a timely manner when something happened?

In addition, there may be no mechanism to automatically delete the output history or overwrite it when it reaches a certain size.
Before you know it, it may have grown to a considerable size and start to interfere with your work.

It is possible to manage this type of history output by creating it yourself or using some kind of tool, but it takes time and effort and can be inconvenient.

HULFT 's history management records information about each file transfer as transfer history.
Furthermore, an operation log records when, who, and what operation was performed, making it possible to track unauthorized access and operational errors.

The forwarding history will leave a trail of information such as what time the message was sent, whether it was received, and the result.

If an error occurs during transfer, an error code corresponding to the error that occurred will be displayed, and you will also be able to check the details of the error and how to resolve it from the screen.
This allows you to quickly see what errors have occurred and deal with them.

Operation logs are managed in two types: "File access logs" and "Command operation logs."

The "File Access Log" records which files were created, updated, or deleted and when, and the "Command Operation Log" allows you to see who performed what operation.

Furthermore, with HULFT, you can set a threshold for switching history files, which allows you to automate log rotation and improve operational efficiency!

Now, let's talk about "History Management"
I gave an introduction.

HULFT file transfer not only allows you to check the history in a timely manner, but also allows you to set the history output settings, such as the log switching value, so you can flexibly manage logs to suit your environment, such as by taking automatic backups or operating without putting a load on the system.

From next time onwards, we will continue to bring you some tips on how to use HULFT!
Stay tuned!

Inquiry

We look forward to receiving your opinions, comments, and letters regarding this column.
Contact:hulseminar@hulft.com

Experience HULFT Products.

Related Content