Backup error: unable to set timestamp

[LawnBoy]

GW 6.5.1 on NW 6.5.4 running BE 9.1.1156 using the Open File Option (gwtsa and tsafs /enableGW both skip files that I know I need and I'm tired of screwing with them).

When I backup the /ofuser dir I get sms errors on every file that hasn't been timestamped. I have used the gwtmstmp utility but sms still errors, I'm guessing because the timestamps are a minute old by the time the files are processed.

The thing is, I don't care at all about the timestamps. We don't purge records, we archive everything to keep compliance with the Open Records Act. I could live with the errors except that BE doesn't verify the job because of the errors. I need the verify.

Is there any way to cause sms to stop reporting these timestamp errors?

Weird thing is, these errors just started happening. This job's been running for a month and all of a sudden they occur, and nothing has changed on the server.

 

[terry712]

you mean when the summertime finish at end of october?

 

[marvhuffaker]

Can't remember the specifics.. But I have seen that in the past and it was a known problem that required either GW6.5 SP3 or SP4 to get past this.

If I recall, it was a specific problem with the integrated GW function of TSAFS. Not sure what errors you would see when just using the open file option.

Marvin Huffaker, MCNE

http://www.redjuju.com

 

[LawnBoy]

Planning on going to GW6.5 sp5 this weekend. Will update here when I have run more tests.

Terry, it's not a DST issue if that's what you mean. The timestamp error just started showing up on Monday night's backup.