issues with scheduled back up

[Ty1989]

I'm having issues with the scheduled backup 3cx does not seem to impress me as there is no support to reach anybody from the company or to even be able to successfully post on here without playing around with the system improve the support system because I'm sure as not spending $75 just for a simple solution to the problem I need to understand why this back up is not happening. I even gave my server a higher memory and I keep getting this message.

Your 3CX backup failed due to the following reason(s): System.IO.IOException: Entries cannot be created while previously created entries are still open. at System.IO.Compression.ZipArchive.AcquireArchiveStream(ZipArchiveEntry entry) at System.IO.Compression.ZipArchiveEntry..ctor(ZipArchive archive, String entryName) at System.IO.Compression.ZipArchiveEntry..ctor(ZipArchive archive, String entryName, CompressionLevel compressionLevel) at System.IO.Compression.ZipArchive.DoCreateEntry(String entryName, Nullable`1 compressionLevel) at _3cxNetBackupAndRestore._3cxBackup.CreateEntry(String name) at _3cxNetBackupAndRestore._3cxBackup.ZipFile(String dst, IFile src) at _3cxNetBackupAndRestore.BackupTasks.BaseFilesTask.BackupFiles() System.IO.IOException: Entries cannot be created while previously created entries are still open. at System.IO.Compression.ZipArchive.AcquireArchiveStream(ZipArchiveEntry entry) at System.IO.Compression.ZipArchiveEntry..ctor(ZipArchive archive, String entryName) at System.IO.Compression.ZipArchiveEntry..ctor(ZipArchive archive, String entryName, CompressionLevel compressionLevel) at System.IO.Compression.ZipArchive.DoCreateEntry(String entryName, Nullable`1 compressionLevel) at _3cxNetBackupAndRestore._3cxBackup.CreateEntry(String name) at _3cxNetBackupAndRestore._3cxBackup.ZipFile(String dst, IFile src) at _3cxNetBackupAndRestore.BackupTasks.BaseFilesTask.BackupFiles() System.IO.IOException: No space left on device : '/var/lib/3cxpbx/Instance1/Data/Backups/3CXScheduledBackup.zip.tmp' at System.IO.RandomAccess.WriteAtOffset(SafeFileHandle handle, ReadOnlySpan`1 buffer, Int64 fileOffset) at System.IO.Strategies.OSFileStreamStrategy.Write(ReadOnlySpan`1 buffer) at System.IO.Strategies.BufferedFileStreamStrategy.WriteSpan(ReadOnlySpan`1 source, ArraySegment`1 arraySegment) at System.IO.Compression.DeflateStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at System.IO.Compression.CheckSumAndSizeWriteStream.Dispose(Boolean disposing) at System.IO.Compression.ZipArchiveEntry.DirectToArchiveWriterStream.Dispose(Boolean disposing) at System.IO.Stream.Close() at System.IO.Compression.ZipArchive.WriteFile() at System.IO.Compression.ZipArchive.Dispose(Boolean disposing) at System.IO.Compression.ZipArchive.Dispose() at _3cxNetBackupAndRestore._3cxBackup.FinishingTask()

 

[Charles_3CX]

Entries cannot be created while previously created entries are still open.

The giveaway is this part above. Usually caused by another incomplete backup tmp file still in your remote backup location.

Delete any 3cxScheduledBackup.tmp files and the check permissies on the remote backup location to ensure that you have what is required before retrying.

 

[Ty1989]

The giveaway is this part above. Usually caused by another incomplete backup tmp file still in your remote backup location.

Delete any 3cxScheduledBackup.tmp files and the check permissies on the remote backup location to ensure that you have what is required before retrying.

I'll try to double check and see if there's anything in a remote location on any of my resources but it's weird because once I expanded the memory of the EBS because for some reason I can't post in self host I was only able to post it here with my system information which I thought was odd but long story short it's in AWS so I basically was able to expand the EBS volume restart so the partition actually updated. I didn't have to do the extend partition. that's only if I keep the system running I didn't keep it running when doing the upgrade of the memory.

 

[Ty1989]

The giveaway is this part above. Usually caused by another incomplete backup tmp file still in your remote backup location.

Delete any 3cxScheduledBackup.tmp files and the check permissies on the remote backup location to ensure that you have what is required before retrying.

So basically, I'm not getting a message anymore, but it just kind of makes me wonder the same thing that you mentioned why it's stating that as if it's in a remote location and I don't see no resources with that bucket I looked upon all my resources and there's no file name in that

 

[Charles_3CX]

Are you having using AWS S3 buckets as the backup location?