Paragon Drive Backup Scheduling

Hello,

I have Drive Backup 8.51 Server Edition on two servers; 1 SBS 2003 Server and one Windows 2003 Standard Server. I can not get paragon to schedule a backup on either server. I can manually backup the servers but the scheduling function does not work.

When attempting to run the backup (on either server) I get the error message 'Bad Object Type'. There seems to be a problem with auto generated script when it calls check errors. I get the same problem whatever I try to backup. I also get the same error backing up to local or remote hard drives.

In my opinion drive backup software without scheduling working is pretty much useless.

Can anyone Please help.
Many Thanks
Paul

 

Hi Paul,

I can't say I've seen that error "Bad Object Type". Can you check the Event log for more details and provide a screenshot please?

To resolve the issue we first need to determine if the Windows Task Scheduler has the problem, or if this is an issue with Drive Backup itself.

Test Windows Task Scheduler:
-Open Control Panel, Scheduled Tasks
-Run Add Scheduled Task, Click Next
-Select Calculator from the list, Click Next
-Choose One Time Only, Click Next
-Set the desired Date & Time, Click Next
-Provide User/Pass to run under, Click Next, Click Finish

Does the task launch as it should? If so, Windows Scheduler is OK. If not, Windows is to blame and the task scheduler needs troubleshooting.

Test Paragon from Command Line:
-Open CMD Prompt
-Navigate to C:\Program Files\Paragon Software\Drive Backup..\Program
-Run Scripts.exe and add an argument that points to your script file
-Scripts for your scheduled tasks are located by default in ..\Drive Backup..\Scripts
-You can right click a Task and view the Properties (inside Drive Backup) to determine the path and filename for the desired script
Example syntax: scripts.exe "c:\program files\paragon software\drive backup\scripts\scr_021208170127682.psl"
It's basically: "(path to scripts.exe)" "(path to script file)"

This will bypass the Windows scheduler and run the task using scripts.exe.

When you Apply a one time task it is run using the main application file, launcher.exe. Scheduled tasks use scripts.exe.

 

Hello Tony,

Thankyou for your reply. I get the same error if if I run the scripts.exe from the command line. "Some error occured: Bad Object Type"
The error seems to originate from the first "call check_error" in the .psl script.

There are no errors in event logs. Very gratefull for any help

Thanks,
Paul

 

Hi Paul,

Can you post a copy of the script file(s) please?

 

Hello Tony,

Thankyou for your reply, please see the script below.

Thanks again for your help,
Paul.

// This file was automatically generated by Paragon script generator
// Time of creation: Fri Aug 21 00:29:19 2009
// Use Paragon Script Interpretator to run this file

// Settings block
settings
surfacetest off
verify off
copyonetoone off
hddrawprocess off
allow64kcluster off
donothidetarget on
copyinsteadofmove off
bigdrives off
compressionlevel 1
sidafterdisk off
sidafterpartition off
defaultsidchanger on
nodellabel off
timeshift 0
oemcodepage 850
timezone 20
langnumber 17
slavecfg off
notforslave off
enablerestart on
enablevirtualdb on
autoconverttofat32 on
sidparams ""
bootcdiso ".\..\ISO\bootcd.iso"
hotbackup lockimpossible
tempdrive C
endsettings

// Turn off confirmation
confirm off

// Backup
img = "H:/arc_200809232900204/arc_200809232900204_$(YEAR)_$(MONTH)$(DAY)_$(HOUR)$(MINUTE).PBF"
select disk 1
select partition primary 1
options
cmp = 1
mfs = 2000 * 1024
notempfiles
label = "No comment"
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

 

Paul,

The script is fine. I recommend that you run CHKDSK /F and then retry. If it fails again try switching from Volume Shadow Copy Service to Paragon Hot Processing.

Switch to Paragon Hot Processing:
-Click the Tools drop-down menu at the top left
-Click Settings
-Open Hot Processing Options
-Switch from Microsoft Volume Shadow Copy to Paragon Hot Processing

Please note that changing this setting will not affect scheduled tasks or scripts that you have already created. To switch this in your current task, find the line "usevss" and delete it; it will automatically switch to Paragon Hot Processing.

If you have problems with that as well, try running CHKDSK /R, and also try backing up other partitions to see if the problem is specific to this one.

 

Hello Tony,

I have tried the following as requested;

1) Ran ChkDsk on both servers no errors. Please note both servers are working fine except for Paragon. I am currently using SBS backup and NTBackup on the servers. Plus praying they don't crash

2) I have changed the hot processing options. Still Same Problem. Please note script does not get to apply changes it fails on the call check_error immediately before.

3) Tried Backing up different partitons. Still same problem.

4) Uninstalled and reinstalled paragon. Still Same Problem.

5) Ahhhhhhhhhhhhhhhhhhhhhhhhhh!

Where is "Bad Object Type coming from", it must be being produced from paragon code somewhere?

If ANYONE can help with error I will be very grateful.

Thankyou Again, Paul

 

Problem still unresolved and becoming more critical.

How good is Paragon Support? I am thinking about paying for a per incident support. What happens if they can't fix the problem do I get my money back?

I also notice that the UK web site states its fees in dollars, does that mean phoning the US for support and how much will that cost?

Thankyou.

 

Hi Tannery,

I'd like to see a copy of your stubact.log file and a screenshot of your disk map if possible. The logs are located by default in 'C:\Program Files\Paragon Software\Drive Backup..\program'.

Also, if you have time please try to backup the system from one of the bootable recovery discs. This will help determine if this is a software issues, or perhaps a hardware problem/incompatibility.

I think our support teams are excellent. If for some reason your problem cannot be resolved we will certainly refund the charges. Our main offices are in Germany, Russia, and the US. If you add the Extended Support plan to our Cart you can switch the currency to Euro and the price will be €149.95 instead of $199.95. I don't believe there would be any cost associated the call on your side. Once you purchase Extended Support you will receive a dedicated 800 # to use.
https://www.cleverbridge.com/80/?scope=cart&id=3KKeBcSABM

I also recommend that you submit a support request through your online Paragon account to bring more visibility to your issue.
https://www.paragon-software.com/my-account/login.htm