What is syntax for Automated Incremental Backups?

[monkeyteeth]

I read the white paper on automated backups with BING and IFD. I'm excited but it didn't explain how to do it for incrementals. With full backup, the partition name never changes. When doing differentials, the original backup file name doesn't change either. But with incrementals it changes each successful incremental backup. Manual style, I choose the last one. (I haven't actually done an incremental yet, so just assuming here it appends a plus number after the name for you). Is there a way to use syntax and have it understand to choose the last in the set for automated incremental style backup. Thank you.

[TeraByte Support]

see the /savename option and the "File Path Variables" section of the
manual.

There are also some existing scripts you may be interested in.
http://www.terabyteunlimited.com/downloads-image-for-windows.htm (and in the
scripting forum).

"monkeyteeth" wrote in message news:[email protected]...

I read the white paper on automated backups with BING and IFD. I'm excited
but it didn't explain how to do it for incrementals. With full backup, the
partition name never changes. When doing differentials, the original backup
file name doesn't change either. But with incrementals it changes each
successful incremental backup. Manual style, I choose the last one. (I
haven't actually done an incremental yet, so just assuming here it appends a
plus number after the name for you). Is there a way to use syntax and have
it understand to choose the last in the set for automated incremental style
backup. Thank you.

[monkeyteeth]

I understand the file path variables, and how they can assign a date to a file name you are to save in the future. But, I don't understand how this helps a script choose a previously created file...say the last one in a set of incremental backups.

I searched for /savename /save, etc.. I can't find this in the manual. Is it possible it's only for IFL?

[TeraByte Support]

the /savename is on page 115 of the IFW manual. That should help explain it
....

"monkeyteeth" wrote in message news:[email protected]...

I understand the file path variables, and how they can assign a date to a
file name you are to save in the future. But, I don't understand how this
helps a script choose a previously created file...say the last one in a set
of incremental backups.

I searched for /savename /save, etc.. I can't find this in the manual. Is it
possible it's only for IFL?

[monkeyteeth]

1. Ok, I get the gist. Thank you for the reference to the Windows manual.

But, does it work on IFD done in a script tied to a boot item under BootIT Bare Metal?

The manual says the /savename puts the end result file name in the registry. Is there some "registry" in IFD within BootIT Bare Metal install? I assume its stored in the EMBR 8mb section somewhere? I'm thinking the .ini file?

2. Beside the question above, Can you critique this workflow please. My plan was to start (but cancel out in end) a manual incremental backup pointing to the previous full backup. Then click on "show me the command line" and save and manipulate that.

Somewhere in that command line it'll have to have something like this: (I'm just making up the /f here for example purposes):

".....'/f:WinServer2003-2013-05-25'....."

So, next, the parts between the single quotes I'm expecting to change to something.

Example, using the /savename from the manual

1. First do a manual full backup...
.../f:WinServer2003 /savename:snoopy... <--- this puts "WinServer2003" in registry variable named snoopy

2. Next, do an incremental backup from script...
.../f:$~snoopy$ /incrementaloption /savename:snoopy

So this calls up the old saved file name in the registry via snoopy variable, and re-writes the snoopy registry at the end of a successful backup. The real filename probably has some incremental number appended to it automatically so not overwrite existing file, but that trick here is the append itself is not referenced in the script, and the variable is RE-WRITTEN everytime.

Is that right?

3. I've been thinking to switch to IFL as it appears to have more friends here are the forum. But can IFL run from EMBR partition? I have to compliment the combination of BootIT and IFD is a potent duo in one install, and update package.

Thank you.

[TeraByte Support]

No, that's windows only, you'd want to use TBScript to have full control
over everything - you can setup your own file names or just search for the
oldest *.tbi file and use it. Wouldn't have to be too fancy, just find the
oldest/newest file and set the name to a variable that you use on the
command line for /base



"monkeyteeth" wrote in message news:[email protected]...

1. Ok, I get the gist. Thank you for the reference to the Windows manual.

But, does it work on IFD done in a script tied to a boot item under BootIT
Bare Metal?

The manual says the /savename puts the end result file name in the registry.
Is there some "registry" in IFD within BootIT Bare Metal install? I assume
its stored in the EMBR 8mb section somewhere? I'm thinking the .ini file?

2. Beside the question above, Can you critique this workflow please. My plan
was to start (but cancel out in end) a manual incremental backup pointing to
the previous full backup. Then click on "show me the command line" and save
and manipulate that.

Somewhere in that command line it'll have to have something like this: (I'm
just making up the /f here for example purposes):

".....'/f:WinServer2003-2013-05-25'....."

So, next, the parts between the single quotes I'm expecting to change to
something.

Example, using the /savename from the manual

1. First do a manual full backup...
..../f:WinServer2003 /savename:snoopy... <--- this puts "WinServer2003"
in registry variable named snoopy

2. Next, do an incremental backup from script...
..../f:$~snoopy$ /incrementaloption /savename:snoopy

So this calls up the old saved file name in the registry via snoopy
variable, and re-writes the snoopy registry at the end of a successful
backup. The real filename probably has some incremental number appended to
it automatically so not overwrite existing file, but that trick here is the
append itself is not referenced in the script, and the variable is
RE-WRITTEN everytime.

Is that right?

3. I've been thinking to switch to IFL as it appears to have more friends
here are the forum. But can IFL run from EMBR partition? I have to
compliment the combination of BootIT and IFD is a potent duo in one install,
and update package.

Thank you.

[monkeyteeth]

Sir, I am very confused. So the method you directed me to is windows only when my original question was for IFD. Let's start with a simpler question.

Are automated incremental backups possible with a single download and installation of BootIT Bare Metal with IFD and Scritping support both checked yes?

[TeraByte Support]

Yes, using TBScript you can do all sorts of things, but for this it can be
fairly simple, just get the oldest file and use that with the /base: .....
Can you be specific with what you want and then someone may be able to
provide a sample script.

"monkeyteeth" wrote in message news:[email protected]...

Sir, I am very confused. So the method you directed me to is windows only
when my original question was for IFD. Let's start with a simpler question.

Are automated incremental backups possible with a single download and
installation of BootIT Bare Metal with IFD and Scritping support both
checked yes?

[monkeyteeth]

> Can you be specific with what you want

As I mentioned earlier, automate incrementals. Reboot computer, pick specially created bootitem that launches a script that simple takes another incremental snapshot of a partition based on which bootitem I selected. To complicate the issue, this partition may already have 5 incrementals, so this would be creating the 6th incremental.

I've looked at /base from page 141 of IFD manual. It talks about combining incrementals into single file. I don't see how it applies here. I don't see another switch that gets get past the circular reference problem of calling a file (say the 5th incremental...i.e. the last incremental), when the file doesn't exist yet at the time the script is created. /savename would seem to work, but it needs registry per manual. Can't a .ini file be saved in the root of EMBR that IFD would save the results of /savename to?

[Brian K]

monkeyteeth,

What have you got against differential images? They are easier to work with than incrementals.