ShadowProtect continuous incrementals and restarting the chain

I did a restore of a continuous incremental and things are OK.

Would you start the continuous incremental with a new full?

I did that - I moved the full and incrementals to another folder.

I thought the existing continuous incremental backup job would see that the full was missing and start over.

That wasnt the case - it gave me an error.

So I connected to the machine and right clicked on the job and chose execute full.

The full started. But before it was complete the next scheduled incremental would start (and stop the full backup, incompleted). The incremental also failed because the full didn't exist.

I went into the schedule for the existing job and removed the incrementals for the next few days and did an execute full. It seemed to not update the change for incrementals and again stopped the full(incomplete) and failed the incremental.

I wound up deleting that job and recreating the job and its doing the backup and Ill see if that solves it.

Is that the answer? you cant restart a Continuous incremental with a new full - you have to recreate the job? if not, how would you do it when the full would not be done before the next incremental is scheduled?

ALSO>>>>>>>>>>>>>>>>>>>>

What does write job file do? (when you right click on a job you get that choice). I looked on the web and didnt find anything."
BeGentleWithMe-INeedHelpAsked:
Who is Participating?
 
noxchoGlobal Support CoordinatorCommented:
You are completely right. But guess that they develop the software and consider that network is fast enough and in standard scenarios the administrator will recreate the complete backup task in case of old backups are moved or deleted.
And yes, many bugs (as we admins consider them) are normally features. I know what I am talking about :) I know how the backup and any other software is developed. I have worked as head of support team for a company which develops backup software (no no, it is not ShadowProtect :) ), and we had always very stresfull discussions with development and product teams managers because of the issues like those described by you.
Some vendors make the software the way that only one instance of its engine could run per time. This way the incremental would not start till the full is finished. Seems like SP decided to let the software run many instances for some reason. Here it put intself into trap.
I agree, some warning or which is much better - automatic detection on engine level that some backup process is already running would be good. So that second process waits till the first one is ready and starts its worm as soon as first one finishes.
You can send these suggestions to SP but do not expect that they implement them. :)
Anyhow, you solution is to divide in time the backup tasks so that no conflict between processes could occur.
0
 
noxchoGlobal Support CoordinatorCommented:
Actually continuous incremental is doing incremental backup to specific full backup. Thus if you move the full it should fail. And if the two instances of backup full plus incremental start at the same time they will fail both. Cant you divide the.pm in time so that you get no collision?
0
 
BeGentleWithMe-INeedHelpAuthor Commented:
move the full it should fail.

yes,  totally get that.

but then it seems if you try to make a new full, the incremental that starts later will cause the full to stop (and fail) and then the incremental fails.  The app isn't smart enough to wait for the earlier job to finish?

Say you have 15 minute incrementals.  And backing up over a slow network connection and it always takes more than 15 minutes to finish an incremental.  It will never work?  at 12:00 the incremental starts.  at 12:15 incremental wants to start and doesn't have enough sense to see the 1200 backup still running and waits or fails, but doesn't end the 1200 also?

maybe gets backups every 1/2 hour, but at least you have something rather than failing every backup.

I guess it's an enterprise app so someone will see all are failing and you have to move backups to every 1/2 hour manually.  it's not a bug, its a feature?  We don't make changes to 1/2 hour on our own.  we'd rather fail to get you to look at it and resolve the problem?

so is it more or less robust : ) ??
0
Network Scalability - Handle Complex Environments

Monitor your entire network from a single platform. Free 30 Day Trial Now!

 
BeGentleWithMe-INeedHelpAuthor Commented:
oh, any thoughts on what 'write job file' does?
0
 
BeGentleWithMe-INeedHelpAuthor Commented:
0
 
noxchoGlobal Support CoordinatorCommented:
Sorry, was doing some sport activities :) yes, that job file is a log file and designed for support team as far as I know.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.