Possible Backup Issues on SMA 13.1 (4372732)

1. Backups do not complete due to insufficient space.
2. Backups do not complete due to error "An unexpected issue happened during the file backup."

1. K1-34401: Disk space requirement calculations for backups are inaccurate in certain scenarios
2. K1-34402:Some unsupported unicode characters cause tar failure during backup

When checking the Backup Logs by going to Settings > Logs > Backup Log, searching near the end of the log, look for the following lines depending on the scenario

Scenario 1

[2023-07-17 01:14:08 -0400] BACKUP [debug] Backup target uncompressed size calculation: 48817053884416 bytes (44.4 TB) 
[2023-07-17 01:14:08 -0400] BACKUP [debug] Min disk threshold: 10% free space, Backup size req: 146451161653248 (133.2 TB) 
[2023-07-17 01:14:08 -0400] BACKUP [debug] Free space required: 146451161653248 bytes (133.2 TB), Free space available: 1788412694528 bytes (1.63 TB) 
[2023-07-17 01:14:08 -0400] BACKUP [critical] We have less than required free space available. Aborting backup. 
[2023-07-17 01:14:08 -0400] BACKUP [critical] Failed to Backup Incremental Files 
[2023-07-17 01:14:08 -0400] [BACKUP] ERROR: Scheduled Backup Failed...exiting

• Reasons and ways to free up space on the SMA
• Service Desk Tickets with Large attachments

Scenario 2

[2023-07-25 16:40:24 -0500] BACKUP [critical] An unexpected issue happened during the file backup. 
[2023-07-25 16:40:24 -0500] BACKUP [critical] Array 
( 
    [0] => tar: /kbox/kboxwww/packages/hd_attachments/test: Cannot stat: No such file or directory 
    [1] => tar: .png: Cannot stat: No such file or directory 
    [2] => tar: Error exit delayed from previous errors. 
)

If any of the Scenarios are happening on the SMA, please contact support here. If possible, enable Tether, instructions here.