Data archiving

backup

We added a mechanism for making back-up copies in YetiForce. It is used mainly to make copies of data (files and database) on a regular basis. These files are saved in a /backup directory. Administrators often forget that making copies is not the same thing as data archiving (or they do not understand the difference between these two processes) or what is even worse, they modify YetiForce system without making a back-up copy. 

YetiForce Ltd. assumes no responsibility for damages, the person responsible is the administrator of the application or the company that uses YetiForce. It should not be assumed that a back-up copy is complete and correct, it should always be double checked (best is to do it regularly). It is also a good practice to introduce changes directly in testing or laboratory environments.  By saying that we would like you to check an enhancement, migrate or install an update, we mean that you should make a back-up copy of your production environment, then upload this copy to a testing environment and upload an enhancement, migrate or install an update there according to our recommendations.    When we write about data archiving, we mean: 
  1. Making a back-up copy of the application. 
  2. Making a back-up copy of the database. 
  3. Making a back-up copy of the operating system.
  4. Such copies are made regularly and have the following parameters: 
    • time for data to be archived (e.g. data older than a year), 
    • time for storing data (retention) so after the expiry, data will be deleted from the archive,
    • whether archive will be only for read only or for write/read, 
    • defining the maximum time with no access after a failure.
  5. The scheduler:
    • a specified and internally accepted back-up schedule,
    • a regular verification of archive performance,
    • a verification of the maximum time with no access after a failure. 
  6. Defining procedures that support the process of archiving. 
  7. Creating a necessary documentation that describes the process of archiving.
Be aware of the fact that no one will take better care of you data than you will. Relying only on a hosting company or partners is risky, because the future of your company will be in the hands of another company and you will not have a full control over it. When you implement a CRM system, you move to a new management level in your company, because data now stored in the application requires a new approach to insurance it is saved properly. Obviously, resources invested in archiving should not be either too large or too small. It is necessary to define the annual budget that will be adequate to the scale of archive and to the value of data stored in it. 100 euro monthly might be too much for one company, whereas for another 10.000 euro monthly might not be enough. 
  • Thursday, 10 August 2017