11-21-2017 03:27 AM
Is there any way to reduce the length of the filename of a scheduled database backup?
We are using Office 365 and the automatically produced file names are too long and so are not being stored on the cloud.
Apart from manually changing filenames, any suggestions?
11-21-2017 05:27 AM
11-21-2017 07:26 AM
I saw that however it saves with a lot of other characters & time e.g.
Act! DATABASE_NAME da7e2fced85a422eb31fda7a92f7b740 2017-11-21 15-18-01
hence it's too long.
11-21-2017 07:41 AM
11-22-2017 03:31 AM
No, not using Carbonite or any other backup services apart from Office 365 Onedrive. But it;s ACT that creates the file.
I deleted the old ACT scheduled backup, deleted the old backup files and also moved the save location. But it still generates the random extra characters & adds a time.
As such, backup files aren't getting saved to the Onedrive cloud - which defeats the objective.
11-22-2017 03:56 AM
11-22-2017 08:05 AM
As per last post, I did try completely recreating the backup task, I removed the existing one and recreate it - using a different backup location too. This gave the same error.
The same issue happens with a demo database.
This is a very recent re-install and a new (re-created fresh database) following issues regards: https://community.act.com/t5/Act/Error-The-INSERT-statement-conflicted-with-the-FOREIGN-KEY/td-p/340...
However, I have 2 other recurring issues with ACT!:
Do all these issues point to a fix?
11-23-2017 02:15 AM