Re: [Veritas-bu] NBU6.5 Win Client Installation
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, August 27, 2008 2:09 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU6.5 Win Client Installation Hi, I've run the .msi installer and it gives me the below error message Error 1723, There is a problem with this window installer package. A DLL required for this install to complete could not be run. Is there something wrong with the OS? Regards +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. - Astrium Limited, Registered in England and Wales No. 2449259 REGISTERED OFFICE:- Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disc Staging Area Full
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@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Disc Staging Area Full I run several scripts that manually prune my DSSUs and DSUs of unwanted images. Forget the catalog, just run bpexpdate with the image switch and use the server_image num directly on any file you find on the drive. Make sure you drop the extension. All my scripts parse the directory directly, I don't even bother querying the catalog first. You will get an error something like entry does not exist if you try to expire an image that does not exist in the catalog. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Crowey Sent: Tuesday, August 26, 2008 2:12 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Disc Staging Area Full Thanks fellas. I tried the catalogue method first - and while it did return some images, nowhere near as many as I know are in the disc staging areas. But nonetheless, I expired those. As I mentioned earlier, this came about through a synthetic backup snafu - and first stage of fixing the problem I just cancelled the differential job writing to disc; this couldn't have orphaned the images on disc could it? Or do I have to now manually find/identify the old images and use bpexpdate as suggested? +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] job retries per client
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 an oracle RMAN script to initiate a backup from oracle RAC back through the netbackup oracle agent to policies configured. Within the bpstart script i have captured the exit status from the RMAN script and if it is other than 0 it causes bpstart script to fail so we know there has been a problem. What seems to have happened is there has been a fail somewhere and then the job has ran again. This has caused a second RMAN script to run which has caused problems. I have increased the bpstart time out per client but i would like to be able for it only to try a job once within 12 hours. That possible? Netbackup 6.0Mp4 Solaris9/10 Cheers ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] bpstart timeout not honoured
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 = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpstart timeout not honoured
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 client. You also need to have it set the same or greater on the media server. Ken Zufall Technical Analyst D660C The Goodyear Tire Rubber Company Dave Markham [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 08/28/2008 07:00 AM Please respond to [EMAIL PROTECTED] To veritas-bu@mailman.eng.auburn.edu veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] bpstart timeout not honoured 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 = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpstart timeout not honoured
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 time i have put the following into bp.conf on the client that initiates the bpstart CLIENT_READ_TIMEOUT = 24000 BPSTART_TIMEOUT = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] scheduled backups fail to launch
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 didn't notice this, and we went through one backup cycle that way. Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine. The only hint I can find is the bpsched log contains messages like this: log_in_errorDB: skipping backup of client bsd3, policy HD Q-Stand, schedule 2years because it has exceeded the configured number of tries I assume somewhere NB mis-remembers it did that backup (in the future). Where would it keep that information, and how can I reset it. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Master Server number of copies - unique setting for just one client?
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 short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Master Server number of copies - unique setting for just one client?
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 that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] scheduled backups fail to launch
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 skip it since it's been less than the timer requires. So - don't panic until you see that 2X hours have passed without an automatic run. If this has happened, post your bplllist pol_name -U output to this list. -M -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chad Sent: Thursday, August 28, 2008 12:27 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] scheduled backups fail to launch 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 didn't notice this, and we went through one backup cycle that way. Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine. The only hint I can find is the bpsched log contains messages like this: log_in_errorDB: skipping backup of client bsd3, policy HD Q-Stand, schedule 2years because it has exceeded the configured number of tries I assume somewhere NB mis-remembers it did that backup (in the future). Where would it keep that information, and how can I reset it. +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] scheduled backups fail to launch
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 that the NTP daemon refused to correct it. The repair dude didn't notice this, and we went through one backup cycle that way. Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine. The only hint I can find is the bpsched log contains messages like this: log_in_errorDB: skipping backup of client bsd3, policy HD Q-Stand, schedule 2years because it has exceeded the configured number of tries I assume somewhere NB mis-remembers it did that backup (in the future). Where would it keep that information, and how can I reset it. The quick hack that *might* work would be to shut NetBackup down, rename /usr/openv/netbackup/db/images/$CLIENT/STREAMS to something else, and restart NetBackup. It will then reset the timers for that client - your schedules will start over. Alternatively, you could edit the STREAMS file and put in a timestamp you like - that's even more of a hack and if you break it, you get to keep both pieces. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Status 96
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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] BMR 6.5.1 on a SOLARIS 9
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:
1000 Mbps FDX Link up
Requesting Internet Address for 0:3:ba:18:b1:45
1000 Mbps FDX Link up
krtld: load_exec: fail to expand cpu/$CPU
krtld: error during initial load/link phase
panic - boot: exitto64 returned from client program
Program terminated
{1} ok
+--
|This was sent by [EMAIL PROTECTED] via Backup Central.
|Forward SPAM to [EMAIL PROTECTED]
+--
___
Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu
http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Master Server number of copies - unique settingfor just one client?
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] 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 that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] scheduled backups fail to launch
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 but I'll wait until tomorrow when Friday's backups would be Full backups anyway. Thanks, Randy From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Thursday, August 28, 2008 11:29 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] scheduled backups fail to launch 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 that the NTP daemon refused to correct it. The repair dude didn't notice this, and we went through one backup cycle that way. Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine. The only hint I can find is the bpsched log contains messages like this: log_in_errorDB: skipping backup of client bsd3, policy HD Q-Stand, schedule 2years because it has exceeded the configured number of tries I assume somewhere NB mis-remembers it did that backup (in the future). Where would it keep that information, and how can I reset it. The quick hack that *might* work would be to shut NetBackup down, rename /usr/openv/netbackup/db/images/$CLIENT/STREAMS to something else, and restart NetBackup. It will then reset the timers for that client - your schedules will start over. Alternatively, you could edit the STREAMS file and put in a timestamp you like - that's even more of a hack and if you break it, you get to keep both pieces. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Log Files - .log files
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 those files? Thanks in advance, Randy From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Thursday, August 28, 2008 2:22 PM To: Tim Hoke Cc: nbu Subject: Re: [Veritas-bu] Master Server number of copies - unique settingfor just one client? 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] 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 that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Log Files - .log files
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 attempting that, I would read the Netbackup Troubleshooting Guide for the latest release. There is a section specifically about the unified logs and how to properly delete, reduce in number, or change location of these files. Current version = ftp://exftpp.symantec.com/pub/support/products/NetBackup_Enterprise_Server/290230.pdf Look at page 82 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 those files? Thanks in advance, Randy From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Thursday, August 28, 2008 2:22 PM To: Tim Hoke Cc: nbu Subject: Re: [Veritas-bu] Master Server number of copies - unique settingfor just one client? 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] 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 that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Log Files - .log files
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: Thursday, August 28, 2008 4:21 PM To: nbu Subject: [Veritas-bu] Log Files - .log files 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 those files? Thanks in advance, Randy From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Scott Jacobson Sent: Thursday, August 28, 2008 2:22 PM To: Tim Hoke Cc: nbu Subject: Re: [Veritas-bu] Master Server number of copies - unique settingfor just one client? 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]mailto:[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 that is in two Vault process and do to the retention periods of their copies, their expiration periods overlap for a short period of time. During that time there will be a Vault that will run in which because the maximum copies is set to 2, a copy is not made. Thanks, Scott J. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edumailto:Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] bpstart timeout not honoured
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? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Dave Markham Sent: Thursday, August 28, 2008 4:01 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] bpstart timeout not honoured 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 = 2400 After some investigation it seems a job has exited with status 74 after 11000 seconds saying bpstart failed to complete. It then causes the script to run again as i have retries per 12 hours set to 2. Anyone any idea why the time out is not being honoured for the client? Cheers Dave ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Storage Lifecycle Policies
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 policies? 2) Assuming I can ever get he ability to create them how does this feature compare with say Vault? Just to give you some background the plan would be to use VTLs on site and have the images duplicate to a remote facility over our SAN's WDM connection. Steven Steven Stewart NC State University OIT/Provisioning ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Storage Lifecycle Policies
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 stage to disk, destage from disk, duplicate to disk or tape, etc. all from a single SLP and apply it to multiple policies. Kind of nice really, but disappointing that in order to use this feature you pretty much have to buy expensive hardware or add-on products. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Steven Stewart Sent: Thursday, August 28, 2008 5:28 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Storage Lifecycle Policies 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 policies? 2) Assuming I can ever get he ability to create them how does this feature compare with say Vault? Just to give you some background the plan would be to use VTLs on site and have the images duplicate to a remote facility over our SAN's WDM connection. Steven Steven Stewart NC State University OIT/Provisioning ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] scheduled backups fail to launch
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 run comes around again, it'll skip it since it's been less than the timer requires. So - don't panic until you see that 2X hours have passed without an automatic run. We are using calendar based scheduling, so the frequency is grayed out. -Original Message- From: veritas-bu-bounces at mailman.eng.auburn.edu [mailto:veritas-bu-bounces at mailman.eng.auburn.edu] On Behalf Of Chad Sent: Thursday, August 28, 2008 12:27 AM To: VERITAS-BU at mailman.eng.auburn.edu Subject: [Veritas-bu] scheduled backups fail to launch 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 didn't notice this, and we went through one backup cycle that way. Since then, the backups on the remote media server do not start as scheduled. If kicked off manually they work just fine. The only hint I can find is the bpsched log contains messages like this: log_in_errorDB: skipping backup of client bsd3, policy HD Q-Stand, schedule 2years because it has exceeded the configured number of tries I assume somewhere NB mis-remembers it did that backup (in the future). Where would it keep that information, and how can I reset it. +-- |This was sent by clarson at eldocomp.com via Backup Central. |Forward SPAM to abuse at backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu at mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu[/quote] +-- |This was sent by [EMAIL PROTECTED] via Backup Central. |Forward SPAM to [EMAIL PROTECTED] +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] scheduled backups fail to launch
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 it going to try to run a Full backup? If so, it will still work but I'll wait until tomorrow when Friday's backups would be Full backups anyway. Yup - like I said, your schedules will start over just like it was a new policy so you'll get fulls. .../Ed *From:* [EMAIL PROTECTED] [mailto: [EMAIL PROTECTED] *On Behalf Of *Ed Wilts *Sent:* Thursday, August 28, 2008 11:29 AM *To:* VERITAS-BU@mailman.eng.auburn.edu *Subject:* Re: [Veritas-bu] scheduled backups fail to launch On Thu, Aug 28, 2008 at 1:26 AM, Chad [EMAIL PROTECTED] wrote: -- Ed Wilts, Mounds View, MN, USA [EMAIL PROTECTED] If I've helped you, please make a donation to my favorite charity at http://firstgiving.com/edwilts The quick hack that *might* work would be to shut NetBackup down, rename /usr/openv/netbackup/db/images/$CLIENT/STREAMS to something else, and restart NetBackup. It will then reset the timers for that client - your schedules will start over. Alternatively, you could edit the STREAMS file and put in a timestamp you like - that's even more of a hack and if you break it, you get to keep both pieces. .../Ed Ed Wilts, RHCE, BCFP, BCSD, SCSP, SCSE [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
