Trying to create a very simple backup that will repeat automatically Monday
thru Thursday using the same group of media. The same will go for Friday's
backup.
The problem seems to be the naming of the tape.
I tried creating a ntbackup with the tape name of 'daily'. That doesn't
work. It seems like the ntbackup program uses more then the name 'daily' to
designate a tape.
I found this switch /um which is said to reformat the tape in combination
with /p for specifing the tape device ie. 4mm DSS. Doesn't work.
When I run the scheduled service it keeps reporting 'mounting tape' for ever.
In simple terms what I'd like to do is have my 3 daily tapes and 2 weekend
tapes backup my 2003 server. On Monday of week one I'd like to backup all the
files that have changed since the last full backup, which was completed last
Friday night. Then Tuesday, append to the same tape the same differential
files. Same with Wed & Thur. Friday night I insert the weekend tape 1 or 2
and backup the whole server. I know I'll need at least 3 different scripts.
I've searched high and low, but have yet to find the answer. Any suggestions
of where to look or what to look for?
Thanks
Jim

"Jim" <Jim@discussions.microsoft.com> wrote in message
news:FAECAFE4-42CE-4D7D-9F4E-5EB18C02B64B@microsoft.com...
Are you running the backup in direct mode or as a scheduled
job? If it is a scheduled job, let's have a look at your command line!

"Pegasus (MVP)" wrote:

Here's the current version which is not working.
Jim

C:\WINDOWS\system32\ntbackup.exe backup "@C:\Documents and
Settings\Administrator.DC1\Local Settings\Application Data\Microsoft\Windows
NT\NTBackup\data\Daily Data Drive Only.bks" /v:yes /r:no /rs:no /hcn /m
differential /j "Daily Data Drive Only" /l:f /p "4mm DSS" /um

"Jim" <Jim@discussions.microsoft.com> wrote in message
news:F82FFDA8-38DE-4475-9C07-CE8F732D7769@microsoft.com...
So what happens when you run this command from the Command Prompt?

Am 14.04.2006, 02:13 Uhr, schrieb Jim <Jim@discussions.microsoft.com>:


Use only a 8.3 named bks file EG daily.bks, because it seems that ntbackup
can't handle spaces in the selection file name.

This was my first error creating a backub shedule
--
Mit freundlichen Grüssen / Best regards

David Meixner

"David Meixner" <webmaster@chatfreak.at> wrote in message
newsp.s7zoiln0d2ls4w@david-meixners-computer.local...
This is incorrect - ntbackup.exe has no problem handling long file
names. If you use the wizard to create a job then it will by default
create the .bks file in your profile folder, whose name has several
spaces. It looks like this:

ntbackup.exe backup "@C:\Documents and Settings\Pegasus\Local
Settings\Application Data\Microsoft\Windows NT\NTBackup\data\test.bks" etc.

I recommend you try it for yourself.

In article <Ow6i095XGHA.3448@TK2MSFTNGP04.phx.gbl>,
"Pegasus \(MVP\)" <I.can@fly.com> wrote:

Hmmm O.K. it seems to be worked with spaces, but i can remember, i had
the same line with "C:\WINDOWS\system32\ntbackup.exe backup
"@C:\Dokumente und Einstallungen\*\Lokale
Einstellungen\Anwendungsdaten\Microsoft\Windows
NT\NTBackup\data\Tägliche Sicherung.bks" /v:yes /r:no /rs:no /hcn /m
normal /j "Tägliche Sicherung" /l:f /p "4mm DSS" /um

and recivied a message, that "C:\Dokumente und Einstallungen\*\Lokale
Einstellungen\Anwendungsdaten\Microsoft\Windows
NT\NTBackup\data\Tägliche" not found.

But Now it works. Sorry for my incorrect Informatin

--
Mit freundlichen Grüssen / Best regards

David Meixner

When I try to run it from a command prompt, the ntbackup program starts for a
second, then goes away. I then get a meesage in the backup.log file that
reads:

The operation was not performed because an invalid Removable Storage backup
destination was specified.

It's the same storage name '4mm DSS' that is in the box created when I run
the wizard. I can run a backup manually, but need to specify that I want to
overwrite in the last message box. If I choose to run the backup later, it
will fail.

Any other ideas?

Thanks gang!

Jim




"Pegasus (MVP)" wrote:

The message you report gets generated when the RSM is
unable to locate the backup medium it expects. The problem
can be overcome by using the /um switch. Since you say that
you use this switch, I can think of two options only:

a) You have discovered a previously unknown issue within RSM, or

b) Although you think that you're using the /um switch, you're
running a command or a batch file that does not use this switch.

If you are absolutely convinced that you're doing the right thing
and that the job fails intermittently then I suggest you ring the
Microsoft helpdesk in your area. You will be charged a standard
fee for the call. If this is a Windows problem then your fee will
be fully refunded. If it is due to an oversight on your part then
you should consider it as a tuition fee.


"Jim" <Jim@discussions.microsoft.com> wrote in message
news:2C7D5DBD-901B-4CBC-ABE8-3AF3BC98F3F8@microsoft.com...

I'm running server 2003. When I run ntbackup.exe /? I do not see the /um
switch so it might not be valid.
Then what? Surely there is some combination of switches, naming media that
will work.
Perhaps the only work around is to create a single script for each and every
one of the individual tapes??? It's like there is some unique identifier that
is being added to each tape which is not visible or usable.
To test this I manually created 3 different tapes, all using the same
'daily' tape name. They show up as 3 different tapes in the media list and
each of the 3 scripts, which look exactly the same, will only run with the
one script that created it.
Jim

"Pegasus (MVP)" wrote:

The /um switch is undocumented in Win2003 Server but still
valid. Here is a backup line I have been using without a problem
for several years on one of these machines, with lots of
different tapes:

ntbackup backup @c:\Logs\Full.bks /j "%date%" /n "Tape1" /d "%date%" /v:y
/r:no /rs:no /m Normal /p "Travan" /L:S /um


"Jim" <Jim@discussions.microsoft.com> wrote in message
news:EDCB8107-36AE-47C1-9B0F-880A98DFF1A8@microsoft.com...