Curtis-
Dennis' postscript is correct.
i.e., it is *not* possible to run bpbackup -i from a remote host
unless the master server thinks that host is a media server.
Otherwise, bprd logs an error saying,
hostname is not a valid server for manual backup request
You're right that a normal
ugh, if you want to point to recent 6.0 press, might I suggest the
storage article instead?
http://storagemagazine.techtarget.com/magLogin/
1,291245,sid35_gci1214739,00.html
That Sharon Fisher article feels to me like she took several individual
data points and worked hard to extrapolate
I'm sorry Greg, but I'm still not 100% clear which vault product you
are talking about in your complaints that duplication from VTL -- real
tape isn't possible.
Can you confirm that you're talking about Enterprise Vault, the
relatively new-to-NetBackup Exchange-specific product, only runs on
Paul-
Bottom Line: What you are seeing is nothing to worry about.
This is a cosmetic bug in the bpdbm -consistency 2 command.
What's happening is, bpdbm is encountering the pseudo-images that are
part of the DSSU relocation operation. (you can tell from the
__DSSU_POLICY_ prefix...)
These
Asiye-
See also technote 279718, which also discusses the status code 134
error as it relates to duplication.
STATUS CODE: 191 - Duplications from tape, disk or from a Disk Staging
Storage Unit (DSSU) will fail with a status 191 if a status 134 occurs
during the relocation of images to
That Worman guy has got no clue!;-)
My correction below was no correction. The MAX_STAGING_JOBS and
STAGING_JOB_LIMIT files are read by the bpbrmds process, and that
process runs on the MEDIA SERVER that's associated with the DSSU. This
may be the master server, but it certainly doesn't
