Community
Showing results for 
Search instead for 
Do you mean 
Reply

Automated Backup Filename

New Member
Posts: 3
Country: United States

Automated Backup Filename

I'm running ACT 2009 using ACT Scheduler to perform daily backups.  The documentation says ACT adds the date and time to the .zip filename, which is great, but the actual filenames I'm getting look like this:

 

"Clients c091d476207b4ae48d1ca15a02705829 2009-02-12 10-55-01.zip"

 

Not this:

 

"Clients 2009-02-12 10-55-01.zip "

 

Is this "working as intended" because I see no need for the additional garbage in the middle of the filename.  The date/time stamp provides all that's necessary for a unique filename.

Moderator
Posts: 4,395
Country: USA

Re: Automated Backup Filename

The cause of "c091d476207b4ae48d1ca15a02705829" is because of duplicate file names.  Is there another backup already named "Clients 2009-02-12 10-55-01.zip "?
New Member
Posts: 3
Country: United States

Re: Automated Backup Filename

No, the very first backup file created, and every subsequent one, has had the extraneous characters in the file name.  Oddly, the extra characters remain the same, while the date/time stamp changes:

 

 Clients c091d476207b4ae48d1ca15a02705829 2009-02-12 10-55-01.zip

 Clients c091d476207b4ae48d1ca15a02705829 2009-02-13 10-55-08.zip

 Clients c091d476207b4ae48d1ca15a02705829 2009-02-16 10-55-02.zip

 

 

Moderator
Posts: 4,395
Country: USA

Re: Automated Backup Filename

After further research, the file names are expected.  The GUID is added to avoid issues with simultaneous scheduled events in the scheduler.
New Member
Posts: 3
Country: United States

Re: Automated Backup Filename

Correct me if I'm wrong, but the Scheduler can only perform one of each type of activity.  The only available activities to schedule that I can see as a database Admin are Backup and Database Maintenance, which simply runs an Integrity Check and/or a Re-index.  How does this require such a horrendously long filename?  Unless Database Maintenance includes a backup, it shouldn't even be creating any files in the folder, much less with the same name and date/time as the Backup file.  Not to mention that the date/time stamp includes hours, minutes, and seconds, so I can't even conceive of a situation where the Scheduler would be writing two identically named files simultaneously, even if two different computers are running Scheduler and both attempt to write Backup files at exactly the same instant...it's just not going to happen.  So wherein lies the need for an additional 32 characters in the filename?