Drive backup triggers a reboot loop

Discussion in 'Paragon Drive Backup Product Line' started by davitof, Feb 8, 2013.

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

    davitof Registered Member

    Joined:
    Feb 8, 2013
    Posts:
    1
    Hello,

    I have been experiencing a problem with Paragon Drive Backup 9 Personal. I have version 9.0 build 7267, and I am running Windows XP SP3 multimedia version 6.00.2900.5931

    I am using PDB9 to create a copy of my system partition on a separate drive. My aim is to be able to reboot from the second drive if there is a problem on the first.

    My first disc is split in two partitions: the system partition (number 0, seen as drive C: in Windows) and a data partition (number 1, seen as D). My second disc has a partition 0 which is empty and has the same size and formatting parameters as C:. This last partition is seen as G: in Windows.

    The script I use works in 2 steps: first it backups C: on D:, then it "restores" the backup on G:. This script worked flawlessly for 2 years, until approximately October 2012. Until that time, the script did not trigger a system reboot. Since then, without my changing anything in the script, the script triggers a system reboot, which itself runs the script, then reboots again, then runs the script again, and so on. The only way to get out of the loop is to forcefully stop the machine. I must then mount the main drive as an auxiliary drive on another system and from there patch the registry.

    You'll find below the script I am using.

    Currently Paragon Drive Backup has become almost useless to me. What can I do to make this work again as I expect?


    Script save_restore.psl

    Code:
    // This file was automatically generated by Paragon script generator - manually modified
    // Time of creation: 28/06/09
    // Use Paragon Script Interpretator to run this file
    
    // backup and restore
    
    // Settings block
    settings
    	surfacetest off
    	verify off
    	copyonetoone on
    	hddrawprocess off
    	allow64kcluster off
    	donothidetarget on
    	copyinsteadofmove off
    	bigdrives off
    	compressionlevel 10
    	sidafterdisk off
    	sidafterpartition off
    	defaultsidchanger on
    	nodellabel off
    	timeshift 0
    	oemcodepage 850
    	timezone 20
    	langnumber 12
    	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 = "D:/paragon_backup_dell3/paragon_backup_c.PBF"
    select disk 0
    select partition primary 0
    options
    	cmp = 10
    	cas
    	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)
    
    // Settings block
    settings
    	surfacetest off
    	verify off
    	copyonetoone on
    	hddrawprocess off
    	allow64kcluster off
    	donothidetarget on
    	copyinsteadofmove off
    	bigdrives off
    	compressionlevel 10
    	sidafterdisk off
    	sidafterpartition off
    	defaultsidchanger on
    	nodellabel off
    	timeshift 0
    	oemcodepage 850
    	timezone 20
    	langnumber 12
    	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
    
    // Restore
    img = "D:/paragon_backup_dell3/paragon_backup_c.PBF"
    select disk 1
    select partition primary 0
    select image all
    resize image max
    options
    	start = 63
    restore
    
    // Check for errors
    call check_error
    
    // Apply all scheduled operations
    apply all
    
    // Check for errors
    call check_error
    
    // Mount/dismount partition
    print "Mount/dismount partition"
    print ""
    select disk 1
    select partition primary 0
    mount "G"
    
    // 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
     
  2. seekforever

    seekforever Registered Member

    Joined:
    Oct 31, 2005
    Posts:
    4,751
    If it used to work well then something has changed. Could be software like a Windows Update or even hardware. I assume that you haven't done anything to the disk setup so the partitions and drives are located exactly as you think.

    What happens if you do the steps manually without the script?

    Do a Verify on the resulting image on the D:drive!!

    What is the registry fix you are doing?

    Can you put "stops" into the script and see exactly where the failure is happening? My very, very brief experience with scripting indicated I couldn't get a print out of any messages but that may have been me.

    Are you able to roll back to a pre-October 2012 backup and see if it still works on it? If you can't rollback then it shows the basic flaw in your methodolgy - you only have one backup.

    Run chkdsk /r on all your partitions in case a bad sector is fouling things up. For completenese, you could also run a RAM test like Memtest86+, free from www.memtest.org - let it run for at least a few passes.
     
  3. JosephB

    JosephB Registered Member

    Joined:
    Jan 3, 2008
    Posts:
    310
    davitof,

    Your using a very old version of paragon backup. There could be the possibility that a ms windows update change to windows has caused an incompatabilty with the old version of paragon. Did the problem start right after a ms windows security update in the month of october ?
    ... Anyway, I would *not* expect paragon to fix/support such an old version of paragon backup (there already up to version 12 and the product is now called Backup and Recovery, even if you paid for a support incident. I would guess they would say upgrade to the latest version and see if it fixes it.

    ... Also, I hope your additionally making backups to another partition on that 2nd internal disc or an external drive. You should always have more than 1 backup. Personally, I would say a minimum of 3 backups (the "son", "father", "grandfather" approach).
     
    Last edited: Feb 9, 2013
Loading...
Thread Status:
Not open for further replies.