Sched. Task Fails on Drive Backup Server?

Discussion in 'Paragon Drive Backup Product Line' started by Byrdman2000, Jan 25, 2010.

Thread Status:
Not open for further replies.
  1. Byrdman2000

    Byrdman2000 Registered Member

    Joined:
    Jan 25, 2010
    Posts:
    1
    We are intermittantly have issues where our Scheduled tasks will fail? Some times it will have an exit code of 0x80 and other times it is 0xC0000005?

    We have 3 drives in the system and we backup each individually as some were being skipped when we had them all together?

    We do a Full Backup of each Drive on Sunday, here is the script:

    Code:
    // This file was automatically generated by {VENDOR_NAME} script generator
    // Use {VENDOR_NAME} Script Interpretator to run this file
    // Time of creation: Tue Dec 15 10:09:02 2009
    
    
    // Settings block
    settings
    	surfacetest off
    	verify off
    	copyonetoone off
    	hddrawprocess off
    	allow64kcluster off
    	donothidetarget on
    	copyinsteadofmove off
    	bigdrives off
    	compressionlevel 10
    	sidafterdisk off
    	sidafterpartition off
    	defaultsidchanger on
    	nodellabel off
    	timeshift -300
    	oemcodepage 437
    	timezone 10
    	langnumber 3
    	slavecfg off
    	notforslave off
    	enablerestart on
    	enablevirtualdb on
    	autoconverttofat32 on
    	sidparams ""
    	bootcdiso ".\..\ISO\bootcd.iso"
    	hotbackup lockimpossible
    	tempdrive C
    	vss2hbswitch on
    	vssattempts 3
    	vsstimeout 120
    endsettings
    
    // Turn off confirmation
    confirm off
    
    // Backup
    img = "\\BCAppliance\IntergyBackup\IntergyServerFull-1\img_0_IntergyServerFull-C-1.PBF"
    select disk 0
    select partitions all
    options
    	cmp = 10
    	notempfiles
    	label = "IntergyServer Full Backup #1"
    	autonames
    	hotbackup lockimpossible
    	tempdrive C
    	usevss
    store
    
    // Check for errors
    call check_error
    
    // Apply all scheduled operations
    apply all
    
    // Check for errors
    call check_error
    
    // Exiting
    // exit(0)
    
    // Function for checking error
    check_error:
    	if (errorcode(1) != 0)
    	then
    		print "Some error occured: "
    		strerror(errorcode(1))
    		print ""
    		print "Exiting"
    		print ""
    		exit(errorcode(1))
    	endif
    endcall
    Each Drive full backup is the same except the paths and drive selected.

    Here is the Differential Backup script:

    Code:
    // This file was automatically generated by {VENDOR_NAME} script generator
    // Use {VENDOR_NAME} Script Interpretator to run this file
    // Time of creation: Tue Dec 15 13:03:13 2009
    
    
    // Settings block
    settings
    	surfacetest off
    	verify off
    	copyonetoone off
    	hddrawprocess off
    	allow64kcluster off
    	donothidetarget on
    	copyinsteadofmove off
    	bigdrives off
    	compressionlevel 10
    	sidafterdisk off
    	sidafterpartition off
    	defaultsidchanger on
    	nodellabel off
    	timeshift -300
    	oemcodepage 437
    	timezone 10
    	langnumber 3
    	slavecfg off
    	notforslave off
    	enablerestart on
    	enablevirtualdb on
    	autoconverttofat32 on
    	sidparams ""
    	bootcdiso ".\..\ISO\bootcd.iso"
    	hotbackup lockimpossible
    	tempdrive C
    	vss2hbswitch on
    	vssattempts 3
    	vsstimeout 120
    endsettings
    
    // Turn off confirmation
    confirm off
    
    // Set Start Time-Date of Script
    SET VALUE g_StartTime = NOWTIME
    
    SET STRING NameOfDay = STRINGDAYOFWEEK(value(g_StartTime))
    
    // Backup
    img = "\\BCAppliance\IntergyBackup\IntergyServerDiff-C-1"+string(NameOfDay)+"\img_0_IntergyServerDiff-C-1"+string(NameOfDay)+".PBF"
    base = "\\BCAppliance/IntergyBackup/IntergyServerFull-C-1/img_0_IntergyServerFull-C-1_0000p.000"
    select disk 0
    select partition primary 0
    options
    	cmp = 10
    	notempfiles
    	label = "Intergy Server "+string(NameOfDay)+" C-Differential Backup"
    	autonames
    	base_pwd = ""
    	hotbackup lockimpossible
    	tempdrive C
    	usevss
    store
    
    // Apply all scheduled operations
    apply all
    
    // Check for errors
    call check_error
    
    // Exiting
    // exit(0)
    
    // Function for checking error
    check_error:
    	if (errorcode(1) != 0)
    	then
    		print "Some error occured: "
    		strerror(errorcode(1))
    		print ""
    		print "Exiting"
    		print ""
    		exit(errorcode(1))
    	endif
    endcall
    Again only the drive letters and disk number changes in each script.

    The scripts do work most of the time but intermittantly they will error out?

    Does anyone have any insight in to what I should try? Support keeps asking me to make a new script with the wizard and if it works then they are happy? I need a reliable backup rotation that works.

    Also I forgot to mention we have 2 complete sets of these scripts set to run every 2 weeks so that we have a full week backups and differentials at a minimum at all times.

    Thanks for any assistance.

    Scott Byrd
     
  2. Paragon_MattK

    Paragon_MattK Paragon Moderator

    Joined:
    Jan 14, 2010
    Posts:
    176
    Location:
    Irvine, CA
    Hello,

    I recommend checking the scheduled task to make sure it is set to run even when no user is logged in, as well as making sure to set the credentials for the script to run as. Also, how close to each other are the scripts scheduled to run? It is possible that one of them has not finished when another is attempting to run, there doesn't appear to be a problem with your scripts, it is most likely that something is either interrupting the VSS service or otherwise preventing it from starting when the backup is scheduled to run, be sure to check the event log as well.

    Is there anything else you can tell me about when these errors occur?
     
Loading...
Thread Status:
Not open for further replies.