Search results for query: *

SSO for NDMP, rather

NDMP for SSO is supported in NBU 6. For me, having multiple NDMP hosts, I have a specific set of devices that they share only. I do not have them sharing the devices utilized by my traditional media servers, which consist of two STU groups, 3 STUs each. (My Master is the traffic cop, it...

Control-M for Distributed Systems.

wrong thread

Control-M for Distributed Systems.

VERSIONINFO is only valid on NBU 5.0 and up

for i in `bpplclients -allunique -noheader | awk '{print $3}'` do echo $i, `bpgetconfig -s $i -l | awk -F";" '{print $8,","$5}'` >>verlist.txt done # Output of bpgetconfig -s # 1 = Client/Master # 2 = NetBackup Client Platform # 3 = NetBackup Client Protocol Level # 4 = Product # 5 = Version...

zone 1 datamover to one drive, the other datamover to the other drive. Config NBU accordingly.

It is the Veritas supported way, yes. I have dragged catalog files over the wire in the past with success.

Sounds like a spurious lock file somewhere. Since it's only one drive why not delete it from the config, recycle services, add drive back....just a thought

You cannot bprecover your 5.1 catalogs to a fresh install on NBU6.0. Build out your new 5.1 - bprecover it - upgrade in place to NBU 6.0

By taking the tapes out manually you have managed to defeat the integrity of the media in the library (robotic inventory) and defeat the Netbackup auditing of the tapes. Do you reinventory the robot after manually removing the cartridges? If you do, then netbackup will at least know they no...

I think comtech is on the right track, except it is at the individual schedule level. Here's what we use to keep things sorted, in just about every possible schedule you can think of runs in this enviro. Daily = 18hr freq weekly = 5 day frq Monthly = 26 day freq ...you can see where this is...

If using ITC, the above multiplied by 3

From 3.x to 4.x, and from 4.x to 5.x. We did just do a fresh install of NBU on new hardware and then bprecover the previous catalog without any problem, it is not supported by Veritas to do it this way. Our reasoning for upgrading in that manner was to keep the backout quick and clean, just...

Yes, there are numerous reports you can select to have printed from the vault process, and not just under NBU 6.0, earlier versions of vault had the capability as well. Reports for Media Going Off-Site ? Reports for Media Coming On-Site ? Inventory Reports ? Container Inventory Report ...

xxx01, Yes. On our test boxes, I did a fresh install of 6.0, SFW_HA 4.2 and successfully recovered our 5.0 MP4 catalog data. For those using VCS, the NBU 6.0 agent for VCS actually works.

You call BLAT from backup_exit_notify.cmd Here's a little snippet that creates a log of failures only, and then emails the info in the subject line of blat. @echo %DATE% ----------------------------- >> %OUTF% @echo %DATE% CLIENT: %1 >> %OUTF% @echo %DATE% POLICY: %2 >> %OUTF%...

If you use the backup_exit_notify.cmd, the following are already passed and they can be blat'd too: CLIENT: POLICY: SCHEDULE: SCHEDULE TYPE: STATUS: STREAM: Not real sure what you mean by "content of the backups

Job56 is a catalog backup. Catalog backups and regular media backups cannot reside on the same tape. You may wish to revisit how you use your volume pools. Catalog backup tapes must reside in the "NetBackup" pool. If the tape was a dbbackup tape, you would get a like error from the regular...