Predicting replication health with background replication

1. A system, comprising:

a processor; and

a memory that stores executable instructions that, when executed by the processor, facilitate performance of operations, comprising:

creating a group of at least one file on a source computer, wherein the group of at least one file is configured to test data backup operations, and wherein the group of at least one file is separate from data that is to be backed up;

performing iterations of backing up the group of at least one file to a destination computer;

storing respective job status indications of respective iterations of the iterations of backing up the group of at least one file; and

in response to determining to back up the data, and

in response to determining that the job status indications indicate that at least one iteration of the iterations of backing up the group of at least one file was successful, backing up the data to the destination computer, or

in response to determining that the job status indications indicate that the iteration of the iterations of backing up the group of at least one file was unsuccessful, refraining from backing up the data to the destination computer.

2. The system of claim 1 , wherein the operations further comprise:

determining a recommended time at which to initiate backing up the data based on the job status indications; and

sending an indication of the recommended time.

3. The system of claim 1 , wherein the respective job status indications indicate whether the respective iterations of backing up the group of at least one file succeeded.

4. The system of claim 1 , wherein the respective job status indications indicate whether was a failover success or a failback success associated with the respective iterations of backing up the group of at least one file succeeded.

5. The system of claim 1 , wherein the operations further comprise:

before performing iterations of backing up the group of at least one file to the destination computer, setting up backups from the source computer to the destination computer.

6. The system of claim 1 , wherein the operations further comprise:

in response to the determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful, creating an event or an alert that indicates a reason why the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful.

7. The system of claim 1 , wherein respective iterations of the iterations of backing up the group of at least one file are performed at a time interval, and wherein a value of the time interval is determined in response to receiving time interval data associated with a user account.

8. The system of claim 1 , wherein respective iterations of the iterations of backing up the group of at least one file are performed at a time interval, and wherein a value of the time interval is determined independently of receiving time interval data associated with a user account.

9. A method, comprising:

performing, by a system comprising a processor, iterations of backing up a group of at least one file from a source computer to a destination computer, wherein the group of at least one file is configured for testing data backup operations, and wherein the group of at least one file is separate from data that is to be backed up;

storing, by the system, respective job status indications of respective iterations of the iterations of backing up the group of at least one file; and

in response to determining back up the data, and

in response to determining that the job status indications indicate that at least one iteration of the iterations of backing up the group of at least one file was successful, backing up, by the system, the data to the destination computer, or

in response to determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful, refraining from backing up, by the system, the data to the destination computer.

10. The method of claim 9 , further comprising:

receiving, by the system, replication mode data associated with a user account, wherein the replication mode data indicates to perform the iterations of backing up the group of at least one file, before performing the iterations of backing up the group of at least one file.

11. The method of claim 9 , further comprising:

creating, by the system, the group of at least one file based on determining to perform the iterations of backing up the group of at least one file.

12. The method of claim 11 , wherein respective files of the group of at least one file have respective sizes, and wherein creating the respective files comprises:

creating the respective files with the respective sizes based on file size data received from a user account.

13. The method of claim 11 , wherein respective files of the group of at least one file have respective sizes, and wherein creating the respective files comprises:

determining the respective sizes independently of receiving file size data from a user account.

14. The method of claim 9 , further comprising:

raising, by the system, an alert in response to determining that a first iteration of the iterations has failed.

15. The method of claim 9 , further comprising:

determining, by the system, a recommended time at which to initiate backing up the data based on the job status indications; and

sending, by the system, an indication of the recommended time.

16. A non-transitory computer-readable medium comprising instructions that, in response to execution, cause a system comprising a processor to perform operations, comprising:

performing iterations of backing up a group of at least one file from a source computer to a destination computer;

storing respective job status indications of respective iterations of the iterations of backing up the group of at least one file;

in response to determining to back up data, determining whether the job status indications indicate that at least one iteration of the iterations of backing up the group of at least one file was successful;

in response to determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was successful, backing up the data to the destination computer; and

in response to determining that the job status indications indicate that the at least one iteration of the iterations of backing up the group of at least one file was unsuccessful, refraining from backing up the data to the destination computer.

17. The non-transitory computer-readable medium of claim 16 , wherein respective iterations of the iterations are initiated after respective time intervals of a time interval have passed.

18. The non-transitory computer-readable medium of claim 16 , wherein the group of at least one file is configured for testing data backup operations, and wherein the data differs from the group of at least one file.

19. The non-transitory computer-readable medium of claim 16 , wherein the operations further comprise:

determining a recommended time at which to initiate backing up the data based on the job status indications; and

sending an indication of the recommended time.

20. The non-transitory computer-readable medium of claim 16 , wherein the respective job status indications indicate whether the respective iterations of backing up the group of at least one file succeeded.