"RSM View /CG{Guid} /TPhysical_Media" no longer works on W2003

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

From: Jordan (nojunk_allowed_at_nospam.com)
Date: 01/03/05 

Date: Mon, 3 Jan 2005 09:50:37 -0500

I have been using a script to backup on my W2003 server running Exchange
2003 for months and it just stopped working in the past couple of weeks.
The command that is the problem is:

"RSM View /CG{Guid} /TPhysical_Media"

Where {Guid} is the ID of my Sony AIT 3 tape drive. The GIUD is correct
because I have checked it multiple times and copied and pasted it in. The
error I get when the RSM command runs is:

"Enumerate Object api failed."

Normally I would get the label of tape. If I backed up and called the tape
"Backup 12-31-04 11:00PM" I would get back "Backup 12-31-04 11:00PM" as a
response. I have even swapped out the tape drive a couple of times to see
if it was a problem with the drive even though there is not problem with
backing up or other routines through the Removable Storage GUI interface.
(Yes, I was sure to get the correct GUIID for each drive on each swap).

I need to find out the name of the tape in the drive because I do appends to
the previous nights backup throughout the day and I need the tape name for
my ntbackup command where I am using the /t {TapeName} option.

I have even tried to get around this by changing my full backup script to
write a file (loadedtape.txt) that has the name I gave the tape for the
backup and then pass this to my append script however NTbackup is now
behaving a little screwy because it use to be that if I used the /t {tape
name} option to append, whatever the {tape name} was ntbackup would use
that, but now I get prompted for "{tape name} - 1" which is the Media Name,
not the Side Name of the tape.

For example, I have been using:

Set tapename="Backup 12-31-04 11:00PM"
"ntbackup backup "@C:\Windows\Daily Exchange.bks" /t %tapename% /j
"MyAppend" /a /v:yes /r:yes /rs:no /hc:on /m differential /l:s

This would work fine. Now NTbackup prompts me to insert "Backup 12-31-04
11:00PM - 1" into the drive.

Have there been any Windows Update changes that affect RSM or NTBackup
behavior?

Relevant Pages

  • Re: Ntbackup seems not to start properly 30 to 50% of the time.
    ... Ntbackup seems not to start properly 30 to 50% of the time. ... I have a simple script running from scheduler. ... I built a small test server and using AT instead of Windows Scheduler, ... It would appear that a re-boot allows the backup to complete once. ...
    (microsoft.public.windows.server.general)
  • Re: NTBackup for Exchange 2003
    ... >I am trying to save a client some money by using NTBackup rather than ... Backup the file server to tape. ...
    (microsoft.public.exchange.admin)
  • Re: Ntbackup seems not to start properly 30 to 50% of the time.
    ... Ntbackup seems not to start properly 30 to 50% of the time. ... I have a simple script running from scheduler. ... It would appear that a re-boot allows the backup to complete once. ...
    (microsoft.public.windows.server.general)
  • Re: NTBackup hangs after restoring files...
    ... NTBackup hangs after it has completed restoring the files to the hard ... tape I can see all the files that are mean't to be on there. ... Operation: Verify After Backup ...
    (microsoft.public.windows.server.sbs)
  • Re: NTBackup on Windows Server 2003
    ... I can't believe it is this complicated just to append a backup to the ... with the "- 1" is the side name, not the tape name. ... you may get the incorrect GUID. ... Take the reformatted logical_media GUID and plug it into the ntbackup ...
    (microsoft.public.windows.server.sbs)