Verification of the Automatic Backup Process on Client Storage Devices
Table of Contents
Introduction
In many collections, sales, customer service, and other operations, it is necessary to automatically replicate call and chat recordings to the client's storage systems, whether local or in the cloud. That is why wolkvox offers the service of automatic copying of audio files and chat conversations specifically to wolkvox Storage, RSYNC (NAS or SAN), Azure Blob Storage, and AWS S3.
This automatic backup system runs every night to ensure data integrity. It is important to note that the transfer speed depends directly on the connectivity and available processing power in each cycle. This process is incremental and resilient: if, for any reason, not all files can be transferred in a single cycle, the system will mark them as pending and resume the upload the next day from the last successfully transferred file, thus ensuring the final delivery of all audio files. However, it is important for the client to implement a verification and auditing process to guarantee the storage of all data.
When does this verification apply?
It applies when the client activates the automatic copying services for chats or audio files in GSM or MP3 format.
Who is responsible for verifying the automatic copy?
When the client activates these services, they are responsible for creating a process to verify the automatic copy.
On which devices or services can this backup be performed?
On the client's storage devices or services, such as wolkvox Storage, RSYNC (NAS or SAN), Azure Blob Storage, and AWS S3 (Amazon Web Services).
Why should the automatic copy process be verified?
Because situations may arise that affect the copying process, and therefore, it is necessary for the client to perform a responsible verification.
What are some common problems that can affect the automatic copy?
Common problems include: filling up local hard drives on the client's NAS or SAN, issues related to credit cards linked to Azure Blob Storage/AWS, network or internet failures at the client's location during the copying process, synchronization losses between storage devices due to network maintenance, among other reasons.
What guidelines should the client keep in mind?
If the client activates the automatic copying services for chats or audio files in GSM or MP3 format, they must have a process to verify the automatic copy to validate that the backup is being performed correctly on their storage devices or services.
How long does the automatic copy system attempt to synchronize pending information?
When there is information that could not be transferred to external storage, the automatic copy system continues attempting to synchronize the pending files for a maximum period, depending on the type of storage configured:
Storage Service |
Maximum Retroactive Synchronization Time |
| wolkvox Storage | 30 days |
| RSYNC (NAS or SAN) | 15 days |
| Azure Blob Storage | 10 days |
| AWS S3 | 10 days |
Once the maximum period defined for each service has elapsed, the system will stop attempting to automatically transfer the pending information. In these cases, the client must manually transfer the files.
Example: If the configured destination is AWS S3 and, for some reason, the information generated today cannot be copied, the system will continue attempting to transfer those files for the next 10 days. If the transfer is still not completed after this period, the system will stop making new attempts for that information, and the client will need to transfer it manually.