SPFLDHSTech Posted December 16, 2013 Posted December 16, 2013 (edited) I've six batch files that run backup operations for our server, five scheduled overnight Mon-Fri and an Emergency script which is run manually if backup fails, all to a files on a local NAS. All scripts are identical. We have a two week archive of data with manual snapshots each month. The scripts delete the two week old archive, rename week one to week two, and create a new week one set. The local NAS files are then copied to an off-site NAS. The backups have been consistently failing after less than 30 seconds of execution, not even attempting to back up any files. I'd be ever so grateful if someone experienced in ntbackup command line switches and script construction could have a quick look... I can't see anything amiss. Log files are useless, just saying that 0 files were backed up. Files attached. EDIT: There are three separate operations as backups are over 100GB total in size. If there's an error backing up the whole set, better to have 2/3 ok than nothing at all.CandSysState.bks.txtDNoUsers.bks.txtEmergency.cmd.txtUsers.bks.txt Edited December 16, 2013 by SPFLDHSTech Additional info
SPFLDHSTech Posted December 18, 2013 Author Posted December 18, 2013 Well, it turns out that the file lists need to be in unicode, not ANSI. Let's see what difference that makes.
SPFLDHSTech Posted December 19, 2013 Author Posted December 19, 2013 Didn't help at all. It doesn't look like any job except "EmergencyD" is running. Anyone figure out why?
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now