An automatic or manual cloud backup process should be implemented for the node system with Android version first. The algorithm should be as follows:
a- A cloud system connection information box should be created with a password.
b- Then, the necessary API access is provided to the supported cloud backup system (such as Dropbox or Google Drive) by using the information in the cloud system connection information box to access the infrastructure.
c- This API access should be checked before the backup process to see if it is valid. If it is not valid, a notification should be sent to the Android device indicating that the backup cannot be performed and that the connection information needs to be checked. When the notification is clicked, the backup procedure should be restarted.
d- If the API connection is valid, the backup file on the cloud system will be checked after 00:00 every night. If the date in the backup file name is 2 weeks or older, the backup file taken 4 weeks ago will be marked for deletion and a new backup file will be taken, named (mini_bkup_HHMMSSddmmyyyy.zip), and sent to the cloud server via the API.
e- The file marked for deletion after a successful backup will be deleted from the server.
f- The backup process can be designed as a separate application under Android to be lighter.
f1- The Android mini backup app consists of the following steps. It checks if the minimum node is not running (for power saving or if it has been put into sleep mode by Android for a long time).
f2- If it is running, synchronization is not performed, and the backup process is directly synchronized.
f3- If it is not running, the minimum node is started for synchronization (Only the part that is necessary to synchronize the blocks will be executed.).
f4- When the synchronization process is completed, the node is closed, and the necessary backup file is created and the cloud upload process is initiated."
An automatic or manual cloud backup process should be implemented for the node system with Android version first. The algorithm should be as follows:
a- A cloud system connection information box should be created with a password.
b- Then, the necessary API access is provided to the supported cloud backup system (such as Dropbox or Google Drive) by using the information in the cloud system connection information box to access the infrastructure.
c- This API access should be checked before the backup process to see if it is valid. If it is not valid, a notification should be sent to the Android device indicating that the backup cannot be performed and that the connection information needs to be checked. When the notification is clicked, the backup procedure should be restarted.
d- If the API connection is valid, the backup file on the cloud system will be checked after 00:00 every night. If the date in the backup file name is 2 weeks or older, the backup file taken 4 weeks ago will be marked for deletion and a new backup file will be taken, named (mini_bkup_HHMMSSddmmyyyy.zip), and sent to the cloud server via the API.
e- The file marked for deletion after a successful backup will be deleted from the server.
f- The backup process can be designed as a separate application under Android to be lighter.
f1- The Android mini backup app consists of the following steps. It checks if the minimum node is not running (for power saving or if it has been put into sleep mode by Android for a long time).
f2- If it is running, synchronization is not performed, and the backup process is directly synchronized.
f3- If it is not running, the minimum node is started for synchronization (Only the part that is necessary to synchronize the blocks will be executed.).
f4- When the synchronization process is completed, the node is closed, and the necessary backup file is created and the cloud upload process is initiated."