Troubleshooting Tip: Empty backup folder uploaded with an scheduled backup for reports of Call Center Data Service using SFTP protocol

The folder of a report backup of the Call Center Data Service uploaded with the SFTP protocol is empty.

This issue began after the upgrade to FortiVoice with firmware v7.0.5 GA.

1. Go to the admin GUI, at Call Center -> Configuration -> Data Service -> Remote,
   or at System -> Maintenance -> Scheduled backup -> Remote Backup, choose SFTP as transfer protocol
   Note: Configure SFTP-Server parameters.
2. Configure a scheduled backup.
3. Check the folder/files at the SFTP server after the scheduled backup time.
4. A folder was created, but no file was in the folder.

SFTP-Server:

qa@test-ubuntu-desktop:~/test1$
qa@test-ubuntu-desktop:~/test1$ ls
FO3HET3616000031
qa@test-ubuntu-desktop:~/test1$ cd FO3HET3616000031/
qa@test-ubuntu-desktop:~/test1/FO3HET3616000031$ ls -al
total 8
drwxrwxr-x 2 qa qa 4096 Dec 9 16:35 .
drwxrwxr-x 3 qa qa 4096 Dec 9 16:35 ..
qa@test-ubuntu-desktop:~/test1/FO3HET3616000031$

If the report backup is uploaded with FTP protocol, the backup folder with all files in it is stored successfully.

FTP-Server:

qa@test-ubuntu-desktop:~/FO3HET3616000031$ ls -al
total 78432
drwxrwxr-x 42 qa qa 4096 Dec 9 15:34 .
drwxr-xr-x 6 qa qa 4096 Dec 9 16:43 ..
-rw------- 1 qa qa 80141646 Dec 5 10:35 config_FO3HET3616000031_v70b0232_2024-12-05-1000_primary_FO3HET3616000031.tgz
drwxrwxr-x 2 qa qa 4096 Dec 4 18:34 daily_2024-12-04_18
drwxrwxr-x 2 qa qa 4096 Dec 4 21:34 daily_2024-12-04_21
drwxrwxr-x 2 qa qa 4096 Dec 5 00:34 daily_2024-12-05_00
drwxrwxr-x 2 qa qa 4096 Dec 5 03:34 daily_2024-12-05_03
drwxrwxr-x 2 qa qa 4096 Dec 5 06:34 daily_2024-12-05_06
drwxrwxr-x 2 qa qa 4096 Dec 5 09:34 daily_2024-12-05_09
drwx------ 2 qa qa 4096 Dec 5 12:34 daily_2024-12-05_12
drwx------ 2 qa qa 4096 Dec 5 15:34 daily_2024-12-05_15
drwx------ 2 qa qa 4096 Dec 5 18:34 daily_2024-12-05_18
drwx------ 2 qa qa 4096 Dec 5 21:34 daily_2024-12-05_21
drwx------ 2 qa qa 4096 Dec 6 00:34 daily_2024-12-06_0

This is a known-issue 1105967 already fixed in the following releases:

• v7.0.6.
• v7.2.1.