|
|
Rank: Member  Groups: Registered
Joined: 5/9/2012 Posts: 20
|
Why if the job fails for whatever reason after successfully compressing the .bak file the compressed files are deleted?
Have encountered situations on where the backup files location becomes unreachable and the compressed files are deleted on the temp folder leaving me without a backup. Is there a way to avoid that?
|
|
|
|
Rank: Administration
Groups: Administrators, Registered
Joined: 12/1/2011
Posts: 433
|
Do you want to keep .bak files in temporary folder if job execution has failed for whatever reason?
|
|
|
Rank: Member Groups: Registered
Joined: 5/9/2012 Posts: 20
|
AlexP wrote:Do you want to keep .bak files in temporary folder if job execution has failed for whatever reason? If the job failed because the destination was unreachable I would like to have the .zip in the temp folder and deal with it manually, is better than having nothing. If the job fails for any other reason it may be incomplete, corrupt or unusable so it will have no use. Is what I'm asking for possible?
|
|
|
|
Rank: Administration
Groups: Administrators, Registered
Joined: 12/1/2011
Posts: 433
|
Hi,
We aren't planning to implement this behavior. I believe in this case we'd get feedback with an issue of cleaning up temporary folder and saving disk space. Many users are using large databases.
Please use email notifications for failed jobs to make decisions immediately or backup to folders in addition to FTP.
|
|
|
Rank: Member Groups: Registered
Joined: 5/9/2012 Posts: 20
|
Understand the possible issue of filling up the disks and can relate because my db's are over 140Gb but if the FTP or network access fails the backup files will be deleted, I would prefer to manually compress and erase temp files than loosing my backup.
|
|
|
|
|
