[Veritas-bu] Help 6.5 media server

Have you restarted services on the new media server now that it is recognized by the master? If it was not allowed access to the master when it was installed, you may need to restart. +-- |This was sent by jhilt...@excite.com v

[Veritas-bu] Using bpsetconfig to set exclusions

Did you drop the -e from the command this time? I was told that was not implemented on windows clients. +-- |This was sent by jhilt...@excite.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +---

[Veritas-bu] Using bpsetconfig to set exclusions

Give it a try this way. I have done it this way for windows clients from a windows master, but not from a unix master. bpsetconfig -h hostname filename Entries in your file need to be like this. exclude = C:\Program Files\Veritas\NetBackup\bin\*.lock exclude = C:\Program Files\Veritas\NetBacku

[Veritas-bu] Netbackup MSEO issue adding tags to netbackup policy

I am not sure about the special barccode rules, but I believe you can use a windows administration console to add the MSEO tags. +-- |This was sent by jhilt...@excite.com via Backup Central. |Forward SPAM to ab...@backupcentral

[Veritas-bu] NetBakcup Service Set to Automatic 6.5.3 SAN CLIENT

Just a question about this for my own clarity. You say the service fails on reboot. On my machines it comes up and then shuts itself down again, it that what you mean when you say it fails? +-- |This was sent by jhilt...@excite

[Veritas-bu] Synthetic Backups

There is a case open with Symantec about this issue, and I am told an EEB will be made available soon. You are not supposed to have to keep a full around, but once the full expires a new full is taken automagically. Quote +--

[Veritas-bu] Only 128 drives allowed on Linux?!?

Post subject: Only 128 drives allowed on Linux?!? ltid[4709]: The currently licensed version allows up to 128 drives per server. You have configured 200 drives. What exactly does it mean? What license? Is there a license for this at all or is it just Symantec’s way of telling me that I should

[Veritas-bu] bpduplicate socket read failed

How many duplication jobs are you kicking off at once? Or, are the fragments very large? You should check to see if you have any insufficient system resources messages in the application log on the media server. Microsoft has a support article here. http://support.microsoft.com/kb/304101/en-u

[Veritas-bu] Catalog Backup Question

This is done from one hot catalog policy? What is the window for these backups, and the retention on the full? The only time I have seen a diff run as a full is if NBU does not think there is a valid full for that policy. +--

[Veritas-bu] VCB-backup failes with Error 36

I don't think VCB is supported on a GPT disk. Check here. http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003793 +-- |This was sent by jhilt...@excite.com via Backup Central. |Forwar

[Veritas-bu] Media server is showind Active for Disk

I guess he did say it is showing up on the GUI didn't he. I usually use the wizard to add devices/storageunits now. I used to have issues with the wizard and added them manually, but not anymore. +-- |This was sent by jhilt...@

[Veritas-bu] Media server is showind Active for Disk

It sounds like the master does not know about the media server. On the master go to admincmd directory and run nbemmcmd -listhosts. If your media server is not listed, run nbemmcmd -addhost to add it. These entries are required when you run add a host (-machinename, -machinetype, -masterserver,

[Veritas-bu] LTO4 recognized as DLT

I believe he was saying the tapes themselves are being recognized as dlt media. That sounds like you have the wrong bar codes on the tapes to me. First, check what the library itself is reporting, and change the barcodes if neccessary. If the library does not think the tapes are LTO4, NBU won'

[Veritas-bu] Why can't my backups fill up a tape?

As Judy asked, do you allow backups to span tape volumes? I could see this causing you not to get any full tapes. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--

[Veritas-bu] which 64bit client to use

The amd 64 is the right install for x64 machines. IA64 is for Itanium processor machines. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--

[Veritas-bu] Restore problems

I see that you have looked at the GUI, but I do not understand what you meant by connected. If you go to the Host Properties/Clients on the GUI and then bring up your client usmidea-esrv01, Are the names of the master and media server being used for this backup and restore shown in the server

[Veritas-bu] User Archive Skipping Files?

In my setup with windows clients and specifying a directory for the file list, the directory and newly added files do not get removed by the archive job. Only the files that existed at the time the archive started get removed. +---

[Veritas-bu] Sharepoint (MOSS) 2007 Document Level Backups

Hi Simon I have a couple of questions for you. What are you choosing for your backup selection when trying to do the Document level restore backup? I believe it only works when you choose the web app site, or the content database(s). Secondly, is your SQL backend running on a cluster? I know

[Veritas-bu] Client Properties

Check to see if the client name is in the server list on that client. I think I remember there being an issue with 6.5 where the client name is added to the additional server list during an install. +-- |This was sent by [EMAI

[Veritas-bu] NetBackup Disk Staging Area Problem

The machine with access to the disks can't be used as your media server? Or can you give your server SAN access to them? When you set it up with \\servername\share\ , the client will use the network to backup to your media server which will then in turn send it over the network again to the ma

[Veritas-bu] NetBackup Disk Staging Area Problem

mbrogan wrote: > > > 8/22/2008 1:23:52 PM - Critical bpdm(pid=3888) sts_create_lsu on LSU > \\servername\Disk_Staging_Area_2 failed: 17 > 8/22/2008 1:23:52 PM - Critical bpdm(pid=3888) Invalid STS storage device: > \\servername\Disk_Staging_Area_2 > > Did you create your ds

[Veritas-bu] NDMP Error 154

Is the tape drive on the master configured for remote ndmp? Also the manual for 5.1 says the tape drive must be used for NDMP backups only. 6.0 and above does not require a dedicated ndmp tape drive. +-- |This was sent by [EMAI

[Veritas-bu] NDMP Error 154

Is the policy type set to NDMP? Make sure it is not a windows or standard policy type. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-

[Veritas-bu] Need a command line command to change the Backup Selection f

admincmd>bpplinclude -help USAGE: bpplinclude policy_name [-v] [-M master_server,...] -L|-l bpplinclude policy_name [-v] [-M master_server,...] -add path_name ... bpplinclude policy_name [-v] [-M master_server,...] -add -f filename bpplinclude policy_name [-v] [-M master_serve

[Veritas-bu] Reg: Unable to enable Encrption

You need to install the base level(or 60mp4) encryption from the uoptions cd (on the master only). Then apply the encryption patch (on the master). Then push the encryption to the client using "bpinst -ENCRYPTION -force_install clientname". Then you need to add a key to the client using "bpkey

[Veritas-bu] Upgradering to NBU 6.5.2 soon because of Windows 2008

> These aren't necessarily all issues. There are a handful of issues for > which there are fixes available *today*. > "Issues" that I would expect for a major or minor release (not a MP). I would like to put my two cents worth in on this particular point. 6.5.2 may be a double dot release,

[Veritas-bu] Netbackup 6.5 Updating the tapes

Yup, that was basically my point. If the robot does not see the barcodes, they won't show up for NBU. But I guess I never asked if the robot actually had a barcode reader. +-- |This was sent by [EMAIL PROTECTED] via Backup Cent

[Veritas-bu] verify catalog backup

netbackup\bin\bpdown -f -v netbackup\bin\bpps (to make sure everything is actually down) netbackup\bin\bpup -f -v +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +---

[Veritas-bu] Media server move, now getting 219 errors

If the new storageunit does not have the same name as the old, you may need to change the storageunit in the policy. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +---

[Veritas-bu] Netbackup 6.5 Updating the tapes

Does the robot itself show the barcodes on the media? You can use volmgr\bin\robtest to check, s s to show slots. If the barcodes are not showing up netbackup will not know this is different media from what you removed. Did you use netbackup to eject the media from the robot? +--

[Veritas-bu] Change barcode for a volume do not work !

Are you getting any error messages when you run the command? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--

[Veritas-bu] Jobs 196ing at midnight (6.5.2)

The jobs failling with 196 at midnight is a bug, and I was told that the fix for this is going to be in 6.5.3. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-

[Veritas-bu] Status code 28 (failed trying to fork a process) NBU 6.5.1 o

Thanks for letting me know it helped. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- __

[Veritas-bu] Removing 6.5.2 and going back to 6.5.1

When I inquired about the same issue, I was told that: 1> It was not just a database rev change, it was a change to the images themselves to accomodate new features in 6.5.2. 2> This is not the same as the old "patches", the release updates for 6.5X and above can have significant feature conte

[Veritas-bu] Do we use NetBackup because its a good product or because it

Jamie I am wondering why you used bprecover to recover a catalog after you did the upgrade? At what level of NBU did you make that catalog backup? A database level missmatch could explain nbemm not coming up. +-- |This was se

[Veritas-bu] Netbackup verify at write time

If you use bpverify, it reads the media and compares the contents of the media to the catalog. It is faster than a restore but Ed is right, it will not tell you if you are backing up the right things. It should not be affected by changing files on the client though. +-

[Veritas-bu] How to send email notifications on a windows master

Once you have blat installed, you will need to edit nbmail.cmd to allow the emails to be sent. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-

[Veritas-bu] Addition of New Drives in Existing Setup

Make sure you don't leave media assigned to the old server. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--

[Veritas-bu] How to send email notifications on a windows master

Does your master have something like blat installed to allow it to send email? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +--

[Veritas-bu] How to add clients to the master

To add that client you need to remove your MP4 client patch. Then re-run the 51GA client install and choose to install your specific clients, or all clients. Then reapply the mp4 client patch. You should be able to push then. +

[Veritas-bu] NetBackup 6.5.1 Catalog move

I would not try copying it. I would name the new server same as the old, and recover from a catalog backup. Treat it as a disaster recovery. There are articles on that on NBU support site. +-- |This was sent by [EMAIL PROTECTED

[Veritas-bu] Status code 28 (failed trying to fork a process) NBU 6.5.1 o

Here you go. Before attempting to use Netbackup with HP-UX 11.31 a customer should first install the HP-UX 11.31 patch bundle from March 2008 and then apply HP-UX 11.31 patch PHKL-37455. Hope that helps you. +-- |This was sen

[Veritas-bu] Status code 28 (failed trying to fork a process) NBU 6.5.1 o

I believe the problem there is an issue with that OS. The last I heard is that HP is working on the process forking issue, and think they have it fixed. I don't know which OS patch is required to fix it though. +-- |This was se

Re: [Veritas-bu] Netbackup Manual Backup - can't see restore - OFFTOPIC

Symantec changed standard client to Windows some time ago. Its called BackupExec. :^) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lightner Sent: Thursday, May 01, 2008 2:53 PM To: Martin, Jonathan; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [V

Re: [Veritas-bu] Best setup for NetBackup in 2 sites across theWANlink

There is no such thing as a Master Server License, never has been to my knowledge(after 3.11). There are only Mediaservers. Any Enterprise Media server can be a master. Mediaservers are tiered by OS (windows, linux, Unix) and Manufacture Model #. Symantec determines which tier a Model is in. San Me

Re: [Veritas-bu] lto4 fc bottleneck

Or to put it another way. The backplane of your switch is the limiting factor. If the switch is oversubscribed(too many devices) it could become a bottleneck. jim -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Friday, March 21, 2008 4:38