ntbackup - incomplete command line?

S

Stephen Ford

The ntbackup command line is listed as "ntbackup backup ... "@bks file name"
...."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford
 
P

Pegasus \(MVP\)

Stephen Ford said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford

So what exactly is your question?
 
R

Rock

Stephen said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford

Listed where and examples from where? What's the question?
 
S

Stephen Ford

Pegasus (MVP) said:
Stephen Ford said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford

So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.
 
P

Pegasus \(MVP\)

Stephen Ford said:
Pegasus (MVP) said:
Stephen Ford said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford

So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.

Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.
 
S

Stephen Ford

Pegasus (MVP) said:
Stephen Ford said:
Pegasus (MVP) said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file
name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.

Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.

Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup Utility
help or the Help & Support Centre. From the latter, search for ntbackup. The
ntbackup topic should be found, which describes its command-line syntax. The
syntax states that the "@bks file name" option must be included, and then
continues to quote examples using a folder name but omitting the "@bks file
name" option. "@bks file name" appears to be optional and mutually exclusive
in conjunction with a folder name.

Regards
Stephen Ford
 
B

Bob I

Try this

at the command prompt enter

ntbackup /?

ntbackup wizard will open and then proceed to open help and then it will
open the command line reference. Read the contents AND examples for
clarification on the use of parameters.

Stephen said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file

name"

..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.

Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.


Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup Utility
help or the Help & Support Centre. From the latter, search for ntbackup. The
ntbackup topic should be found, which describes its command-line syntax. The
syntax states that the "@bks file name" option must be included, and then
continues to quote examples using a folder name but omitting the "@bks file
name" option. "@bks file name" appears to be optional and mutually exclusive
in conjunction with a folder name.

Regards
Stephen Ford
 
S

Stephen Ford

Yes, that's the same help that I'm referring to. The help says one thing for
"@bks file name" and then shows examples which contradicts itself.

Stephen

Bob I said:
Try this

at the command prompt enter

ntbackup /?

ntbackup wizard will open and then proceed to open help and then it will
open the command line reference. Read the contents AND examples for
clarification on the use of parameters.

Stephen said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file

name"

..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.



Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.


Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup Utility
help or the Help & Support Centre. From the latter, search for ntbackup.
The ntbackup topic should be found, which describes its command-line
syntax. The syntax states that the "@bks file name" option must be
included, and then continues to quote examples using a folder name but
omitting the "@bks file name" option. "@bks file name" appears to be
optional and mutually exclusive in conjunction with a folder name.

Regards
Stephen Ford
 
B

Bob I

And just what part of this example is the contradiction? I think you are
misreading something.

Example 3
The following example performs a backup using the backup type that is
specified in the Backup program. It uses the backup selection file named
Commandline.bks, located in the C:\Program Files\Windows
NT\ntbackup\data\ directory to choose which files to backup. The backup
job is named "My Job 3" and it overwrites the tape named "Command Line
Backup 1" with the new name "Command Line Backup 2."

ntbackup backup "@C:\Program Files\Windows
NT\ntbackup\data\commandline.bks" /j "My Job 3" /t "Command Line Backup
1" /n "Command Line Backup 2"



Stephen said:
Yes, that's the same help that I'm referring to. The help says one thing for
"@bks file name" and then shows examples which contradicts itself.

Stephen

Try this

at the command prompt enter

ntbackup /?

ntbackup wizard will open and then proceed to open help and then it will
open the command line reference. Read the contents AND examples for
clarification on the use of parameters.

Stephen Ford wrote:

The ntbackup command line is listed as "ntbackup backup ... "@bks file

name"


..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.



Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.


Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup Utility
help or the Help & Support Centre. From the latter, search for ntbackup.
The ntbackup topic should be found, which describes its command-line
syntax. The syntax states that the "@bks file name" option must be
included, and then continues to quote examples using a folder name but
omitting the "@bks file name" option. "@bks file name" appears to be
optional and mutually exclusive in conjunction with a folder name.

Regards
Stephen Ford
 
P

Pegasus \(MVP\)

Stephen Ford said:
Pegasus (MVP) said:
Stephen Ford said:
The ntbackup command line is listed as "ntbackup backup ... "@bks file
name"
..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me that
"@bks file name" must appear, but then goes on to offer an example where
"@bks file name" is not present but a pathname is present. I wondered if
anyone else agreed or maybe had further information of any other
peculiarities of ntbackup and its documentation.

Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you
believe is incomplete. This makes it a little hard to offer any
explanation.

Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup Utility
help or the Help & Support Centre. From the latter, search for ntbackup. The
ntbackup topic should be found, which describes its command-line syntax. The
syntax states that the "@bks file name" option must be included, and then
continues to quote examples using a folder name but omitting the "@bks file
name" option. "@bks file name" appears to be optional and mutually exclusive
in conjunction with a folder name.

Regards
Stephen Ford

The documentation for ntbackup.exe is rather sloppy. I checked
it in four places:
- ntbackup /? (Win2000)
- Windows Help (Win2000)
- ntbackup /? (WinXP)
- Windows Help (WinXP)

Out of the four places, only one document mentioned the "@" symbol
which is compulsory in front of the selection file name. The others
made no reference to it at all.

Secondly, none of the documents mentions that you can specify a
folder name instead of the @ selection file name. It is an
undocumented feature which becomes apparent in the example.

In other words, the documentation for ntbackup is not impressive.
 
S

Stephen Ford

(Have sent this again. Does not seem to have arrived on this thread)

Yes, that's the same help that I've been referring to. The help says one
thing for "@bks file name" and then shows examples which contradicts itself.

Stephen

Try this

at the command prompt enter

ntbackup /?

ntbackup wizard will open and then proceed to open help and then it
will open the command line reference. Read the contents AND examples
for clarification on the use of parameters.
Stephen Ford wrote:
The ntbackup command line is listed as "ntbackup backup ... "@bks
file

name"

..."

but if you look at the examples it appears to be -

"ntbackup backup ... ["@bks file name" | pathname] ..."

The listed example is "ntbackup backup d:\ /j ..."

Stephen Ford



So what exactly is your question?

I'm wondering if the documentation is incomplete, or whether I've
interpreted it incorrectly. The command line definition says to me
that "@bks file name" must appear, but then goes on to offer an
example where "@bks file name" is not present but a pathname is
present. I wondered if anyone else agreed or maybe had further
information of any other peculiarities of ntbackup and its
documentation.



Unfortunately you chose not to reveal what "documentation" you're
referring to, nor did you quote verbatim the example that you believe
is incomplete. This makes it a little hard to offer any explanation.


Ah, sorry - see what you mean...

The specific documentation is for ntbackup as found in the Backup
Utility help or the Help & Support Centre. From the latter, search for
ntbackup.
The ntbackup topic should be found, which describes its command-line
syntax. The syntax states that the "@bks file name" option must be
included, and then continues to quote examples using a folder name
but omitting the "@bks file name" option. "@bks file name" appears to
be optional and mutually exclusive in conjunction with a folder name.

Regards
Stephen Ford
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Similar Threads


Top