Re: [Veritas-bu] NBU6.5 Win Client Installation

2008-08-28 Thread WEAVER, Simon (external)
I tend not to use the msi file extension, but rather the .exe file itself. Is that not present? Cant be the OS if its running ok - any other error messages in the event log itself? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of dy018 Sent: Wednesday,

Re: [Veritas-bu] Disc Staging Area Full

2008-08-28 Thread Esson, Paul
Jonathan, Could you share your scripts? I have little scripting knowledge at the moment but am learning and some reference scripts would be of use. Regards, Paul Esson Redstor LTD -Original Message- From: Martin, Jonathan [mailto:[EMAIL PROTECTED] Sent: 26 August 2008 13:41 To:

[Veritas-bu] job retries per client

2008-08-28 Thread Dave Markham
Guys i know there is the global attribute on the master server for n tries within x hours ( currently set at 2 per 12 hours ) but does anyone know if this can be tailored anywhere per client or ideally per client and policy? The situation is we have a bpstart script on a management box which runs

[Veritas-bu] bpstart timeout not honoured

2008-08-28 Thread Dave Markham
Guys i have a bpstart script on a client which initiates an RMAN backup (i just emailed about it 2 mins ago for a different reason). As the RMAN backup takes some time i have put the following into bp.conf on the client that initiates the bpstart CLIENT_READ_TIMEOUT = 24000 BPSTART_TIMEOUT =

Re: [Veritas-bu] bpstart timeout not honoured

2008-08-28 Thread ken_zufall
Dave, Looks like you have a typo below, but that's not important. What is is that regardless of what the bpstart timeout is set to on the client, it has to be set to the same or greater on the master server...if master server timeout is less than client, master will get honored before the

Re: [Veritas-bu] bpstart timeout not honoured

2008-08-28 Thread Michael Graff Andersen
Hi For netbackup RMAN backups we also set CLIENT_CONNECT_TIMEOUT Regards Michael 2008/8/28, Dave Markham [EMAIL PROTECTED]: Guys i have a bpstart script on a client which initiates an RMAN backup (i just emailed about it 2 mins ago for a different reason). As the RMAN backup takes some

[Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Chad
We have NB 4.5 running on two Linux servers (master and slave). Around the first of the month, we had to replace the motherboard in the master. Unfortunately the CMOS clock on the new board was set way in the future, far enough that the NTP daemon refused to correct it. The repair dude

[Veritas-bu] Master Server number of copies - unique setting for just one client?

2008-08-28 Thread Scott Jacobson
The default setting for the number copies is 2. Can a setting of say 3 be configured for just one client? I don't want to over complicate the explanation but I have a client that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a

Re: [Veritas-bu] Master Server number of copies - unique setting for just one client?

2008-08-28 Thread Tim Hoke
Scott, That's a global parameter. -Tim On Thu, Aug 28, 2008 at 10:14 AM, Scott Jacobson [EMAIL PROTECTED]wrote: The default setting for the number copies is 2. Can a setting of say 3 be configured for just one client? I don't want to over complicate the explanation but I have a client

Re: [Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Mark.Donaldson
As you test, it's important to remember that you tests count against the timers. Manual backups are not special in this regard. So, if you see that a backup didn't run and manually initiate them, and it's less that X hours, your schedule interval, when the automatic run comes around again, it'll

Re: [Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Ed Wilts
On Thu, Aug 28, 2008 at 1:26 AM, Chad [EMAIL PROTECTED]wrote: We have NB 4.5 running on two Linux servers (master and slave). Around the first of the month, we had to replace the motherboard in the master. Unfortunately the CMOS clock on the new board was set way in the future, far enough

[Veritas-bu] Status 96

2008-08-28 Thread Piotr
Hello amure1, it seems that I have exactly the same issue. Have you resolved it ? Please let me know !! +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED]

[Veritas-bu] BMR 6.5.1 on a SOLARIS 9

2008-08-28 Thread jcconsulting
Have anyone been successful in performing a BMR of a sun box? I am having issues running a prepare to discover on desimiliar disk. I get this error: Rebooting with command: boot net2 Boot device: /[EMAIL PROTECTED],70/[EMAIL PROTECTED] File and args:

Re: [Veritas-bu] Master Server number of copies - unique settingfor just one client?

2008-08-28 Thread Scott Jacobson
Tim, Yes, it is a Global Parameter. I'm wondering if anyone has found a way to change this uniquely for just one client. Thanks, Scott Tim Hoke [EMAIL PROTECTED] 8/28/2008 9:20 AM Scott, That's a global parameter. -Tim On Thu, Aug 28, 2008 at 10:14 AM, Scott Jacobson [EMAIL PROTECTED]

Re: [Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Randy Samora
Ed, If I create a new policy (and obviously a new schedule) the job will always run a Monthly backup first or a Weekly or whatever Full schedule you have that contains the longest retention. If I do what you suggested below, is it going to try to run a Full backup? If so, it will still work

[Veritas-bu] Log Files - .log files

2008-08-28 Thread Randy Samora
What are the .log files (51216-163-99657920-080822-00.log) that are populating my \Netbackup\logs folder on my Windows media server? It looks like it's rolling over after 30 days or a month but they're taking up a lot of room. I delete them and they come back. What setting is creating

Re: [Veritas-bu] Log Files - .log files

2008-08-28 Thread savil_chacko
Welcome to the world of Unified Logging... so the quick answer is that for new Netbackup processes, rather than creating a directory for the process as in the legacy method, they now create log file(s) per process in this directory. These can be configured with the vxlogcfg command, but before

Re: [Veritas-bu] Log Files - .log files

2008-08-28 Thread Len Boyle
These are the new format logs for netbackup. They are written up in the troubleshooting guide. From the nblog.conf file in the /usr/openv/netbackup directory. 163.L10nResource=nbsvcmon 163.OIDNames=nbsvcmon From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Randy Samora Sent:

Re: [Veritas-bu] bpstart timeout not honoured

2008-08-28 Thread Najim,Nabil A - JHS-5
Hi dave, Hope you found the answer, but if not, my best guess would be the global setting 'backup start notify timeout' setting on the Admin Console Netbackup Management Host properties master server properties timeout. Is this overriding the other timeout setting in bp.conf?

[Veritas-bu] Storage Lifecycle Policies

2008-08-28 Thread Steven Stewart
I've been trying to play with a few of the newer features in 6.5 and was looking at storage lifecycle policies. I've been playing with a test bed of 2 RHEL 4 with netbackup 6.5.2 1) Has anyone see the error Intermittent connectivity lost with server. Please... with creating said lifecycle

Re: [Veritas-bu] Storage Lifecycle Policies

2008-08-28 Thread Clausen, Matt R [EQ]
SLPs can essentially mimic all the functionality of vault without the nice reports that vault can generate. Though in order to use them, you have to have intelligent hardware (VTLs, AdvancedDisk, Tape Libraries, etc.) instead of dumb hardware (BasicDisk). You can pretty much craft the SLP to

[Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Chad
Mark.Donaldson wrote: As you test, it's important to remember that you tests count against the timers. Manual backups are not special in this regard. So, if you see that a backup didn't run and manually initiate them, and it's less that X hours, your schedule interval, when the automatic

Re: [Veritas-bu] scheduled backups fail to launch

2008-08-28 Thread Ed Wilts
On Thu, Aug 28, 2008 at 2:58 PM, Randy Samora [EMAIL PROTECTED]wrote: If I create a new policy (and obviously a new schedule) the job will always run a Monthly backup first or a Weekly or whatever Full schedule you have that contains the longest retention. If I do what you suggested below, is