Re: [Veritas-bu] Windows Server and Linux Clients

Hi James, The colon and the backslashes in this path: can’t create file: usr:\local\pathname\to\file (WIN32 3:The system cannot find the path specified.) have me concerned. AFAIK, this is not a valid path in Linux and I would expect to see something like /usr/local/pathname/to/file instead.

Re: [Veritas-bu] NBU 5 client backing up to NBU 7 Master Media

Symantec supports the current and two major revisions back of the client. So, in your case, 7.0.x will support 7.0 clients, 6.5 clients and 6.0 clients. This isn't to say this will not work, and even Symantec states that though it's not supported, it still may work just fine. In fact, if it's

[Veritas-bu] Error code 48: client hostname could not be found.

Hi All, The first question I have is where could the client hostname not be found. The scenario: NetBackup 7.0.1 Solaris 10(both client (sparc) and master(x64)) Two physical hosts in an active/passive cluster Either system can be backed up by its physical name. If I try to use a logical

Re: [Veritas-bu] strange disk usage

Just a shot in the dark, but have you enabled image compression? We have servers with millions of tiny files that produce huge images files (5GB+) and compressing those into a .tgz might chew up a fair amount of space before the original image gets deleted. -Jonathan From:

Re: [Veritas-bu] Server OS and NBU upgrades

James You would need to uninstall the patch on the Master, and potentially, reapply a Catalog backup from your environment that was not patched. But if its one client causing a problem, dont update the client, rather than goto the effort of rolling back? Or have I missed something. Simon

Re: [Veritas-bu] strange disk usage

You're a good shot when it's dark! yes, I see the Compress Catalog Interval checked and set for 2 days. This doesn't happen every two days, though; makes me wonder if it may happen after some many backups, or a set amount backed up... Thanks From: Martin,

Re: [Veritas-bu] strange disk usage

Regarding disk usage: Run this command sequence: # To list values for logging for i in `vxlogcfg -l -p 51216| grep -v ist` do echo $i /tmp/current.vxlog.config vxlogcfg -l -p 51216 -o $i /tmp/current.vxlog.config done Review what is in the /tmp/current.vxlog.config file

Re: [Veritas-bu] strange disk usage

That's the only thing I can think of, too (other than logs, but that would be more of a gradual increase than all at once, I would think). Keep in mind that catalog compression will keep the catalog compressed until someone needs to search that data, such as for a restore or bplist. The image

Re: [Veritas-bu] Error code 48: client hostname could not be found.

Hi Patrick We have a bp.conf in the oracle users home directory with the logical name as the CLIENT_NAME on our AIX powerha clusters And is using NB_ORA_CLIENT= logical name in the rman scripts Hope this helps Regards Michael 2011/4/1 Patrick netbac...@whelan-consulting.co.uk Hi All,

Re: [Veritas-bu] strange disk usage

Thanks for the tips... I've got the regular logging set to minimum, but will check... -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of David McMullin Sent: Friday, April 01, 2011 11:12 AM To:

[Veritas-bu] NDMP differentials of Netapp path backups

Hello everyone- Looking for assistance on the configuration required got differential incremental backups of our Netapp volumes (NDMP) setup. I have been able to get what appears to be cumulative dumps/backups of our NDMP paths by setting the SET UPDATE = Y entry at the beginning of the policy