[Veritas-bu] BMR on 6.5.3

Greetings all, I am testing BMR with 6.5.3 on a AIX 5.3 client. My SRT and my client are patched to the same level. The entire restore process moves like it should, but the bosboot doesn't succeed at the end, and the log gives me this error: 0301-154 bosboot: missing proto file:

Re: [Veritas-bu] Windows Mount points ALL_LOCAL_DRIVES

Hi All Thanks to all who responded. bpmount only picked up C: and D: The solution is indeed ALL_LOCAL_DRIVES with Cross Mount Points. http://seer.entsupport.symantec.com/docs/315351.htm http://seer.entsupport.symantec.com/docs/307881.htm Regards Marianne From:

Re: [Veritas-bu] Making use of 6.5.2+ default priorities in the presence of pre-existing policy priority settings

And we have a winner. The default priorities (ie, JOB_PRIORITY in bp.conf) control at what priority some types of jobs will spawn, but where priority is a saved configuration knob (especially, policies, but probably see also duplications under Vault and SLP) it is checked at the time that

Re: [Veritas-bu] help in pushing to a MAC server.

There is no ROOT on a Mac, you have to use a regular account and sudo or an account with Administrator level access may give you the permissions you need. On 2/6/09 11:03 AM, veritas-bu-requ...@mailman.eng.auburn.edu veritas-bu-requ...@mailman.eng.auburn.edu wrote: help in pushing to a MAC

Re: [Veritas-bu] Real time failure notification

That's hard to do, too Say you have a retry interval of once per 2 hours but you have a backup schedule with an 8 hour window. You could get four different tries in that time. If you window is just 4 hours, then, of course, it's half that. I'm not sure you get new job numbers or a try

[Veritas-bu] Upgrading to 6.5.3

Folks, I'm not finding documentation on Symantec's web site regarding the clients upgrade to 6.5.3 (Master Server just got upgraded to 6.5.3). I've got several Windows clients on 5.1 MP6.., can I go straight to 6.5.3? Also, for new clients, I'm assuming I can just install 6.5.1 and

Re: [Veritas-bu] NOM VCB

Not much experience with NOM, but I believe it is intended for immediate reporting/alerting. It is not intended for historical reporting/trending - that's where VBR (or Aptare) would come in. If you're looking for something more historical in nature, this question has been asked many times on

Re: [Veritas-bu] Upgrading to 6.5.3

On Fri, Feb 6, 2009 at 1:04 PM, Leidy, Jason D leidy.ja...@con-way.comwrote: I'm not finding documentation on Symantec's web site regarding the clients upgrade to 6.5.3 (Master Server just got upgraded to 6.5.3). I've got several Windows clients on 5.1 MP6……, can I go straight to

Re: [Veritas-bu] Upgrading to 6.5.3

For new clients, you have to install the base, 6.5.0, and then your patch. I'm pretty sure with the 5.16.5 upgrade, the clients have to have the same procedure. NetBackup has always been this way, but that doesn't mean it's the best way. Rusty Major, MCSE, BCFP, VCS ▪ Sr. Storage Engineer ▪

Re: [Veritas-bu] NOM VCB

On Thu, Feb 5, 2009 at 6:03 PM, Justin King jk...@hnl.bcm.edu wrote: 1. Is anyone using NOM that can give feedback on its value as a reporting tool? It's okay at what it does - a short term Operations Manager. It's essentially an admin console with a bit more intelligence. It has no value

[Veritas-bu] NOM vs VCB

Justin I will chime in for Aptare. We evaluated NOM and found it to be of little use in our environment. Aptare gives you historical data, and NBConsole gives current status, and some historical info on backup status. Not to mention that is was unstable at the time we evaluated is a couple of

Re: [Veritas-bu] NOM VCB

Hi Justin. Regarding the 229 error that you are getting, are you performing file level backups (snapshot method 0), vmdk backups (snapshot method 1 or 2), or are your performing vmdk full and file level incrementals (snapshot method 3)? -George Winter -Original Message- From: