TECH Oh BackupExec, 12 versions later and you still have the same fucking bug

[5Gen_Prelude]

Every DST change means the next backup won't work.

 

[retorq]

I'm so glad I live in Arizona and don't have to deal with that shit.

 

[deusexaethera]

Some reason why you can't disable DST on the backup server?

 

[5Gen_Prelude]

Some reason why you can't disable DST on the backup server?

a) It's also the main file server
b) 12 fucking versions.

 

[deusexaethera]

a) It's also the main file server
b) 12 fucking versions.

a) Ah. Can you move backup functions to another server, perhaps a VM if you can't afford more hardware?

b) Yes, but ultimately you have to make it work.

 

[TomDlgns]

more info on this.

DST time changes fuck up our backups if we want to restore?

haha, that is funny.

 

[7960]

Syncback free version


/thread

 

[retorq]

Move operations to AZ.

/thread

 

[5Gen_Prelude]

a) Ah. Can you move backup functions to another server, perhaps a VM if you can't afford more hardware?

Doesn't make any sense to do that for once a year (maybe twice, can't remember if it does it in the fall too). The backup is on that server so that it can dump from one SCSI bus to another for the majority of the files. The tape drive is actually faster than the local drives they're backing up (well, based on the fact it reads back the data faster).

b) Yes, but ultimately you have to make it work.

Yeah, I can make it work correctly by restarting the services after DST. It's just the scheduler that is coded wrong.

 

[5Gen_Prelude]

Syncback free version


/thread

I'm not trusting that to backup SQL and Exchange data...

 

[5Gen_Prelude]

more info on this.

DST time changes fuck up our backups if we want to restore?

haha, that is funny.

I'm not sure if that was a question or not - it just doesn't start the backup job.