Re: [Veritas-bu] image cleanup process - run time
My experience has shown that as soon as NetBackup starts for the first time it runs a cleanup. Then, it will run a cleanup based on the bpconfig value for DB Cleanup Interval, which is 12 by default. So, assuming default value of 12, if you start NetBackup at 2:15pm, the next cleanup will run at 2:15am, then 2:15pm, etc. We have the ability to force many parts of the cleanup process, but I have not yet gotten a good single command to run the whole cleanup process in its entirety. -Rob Thelen. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Bobby R Windle Sent: Friday, November 12, 2010 11:40 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] image cleanup process - run time I understand Netbackup does a cleanup process on a regular bases when a job fails or ends etc. Also I understand a nightly cleanup process runs to expire images on disk etc.. What time does this nightly cleanup job kick off or better yet, how do I change this job to run at a specific time? Thanks for the help. Bobby Windle | W.L. Gore associates, Inc. Backup / Disaster Recovery Admin work: 302 292 4026 cell : 302 588 7374 bwin...@wlgore.com | http://www.gore.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] NBU 6.5.6 restore for a SAN Client
I was able to get my restores working, finally. It turns out that NUMBER_DATA_BUFFERS_FT only works for backups. I had this set to 32, but when the restores ran, they were using 64 buffers (from NUMBER_DATA_BUFFERS_RESTORE). So I had to change that touchfile from 64 to 32, and then the restores magically started working again. I think that the restores should have used the NUMBER_DATA_BUFFERS_FT touchfile for both backups and restores, but that was not the case here. I have updated my documentation internally, so hopefully this will no longer become an issue for us. -Rob Thelen. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of THELEN, ROBERT M (ATTSI) Sent: Tuesday, October 26, 2010 9:26 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] NBU 6.5.6 restore for a SAN Client It's too bad that this thread didn't happen a few weeks ago, as now I am committed to delivering a SAN Client solution for a client that is incomplete. We are running NBU 6.5.4, and no restores have worked yet at all, with SAN Client enabled. Unfortunately, we are deploying SAN Client specifically because the client does not have any more ports available to use for backup. Restoring the backups over the LAN is really not an option in this case. I will be opening a case with Symantec about this, and I will see about having it linked with your case. -Rob Thelen. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ch1waner Sent: Monday, October 25, 2010 9:21 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 6.5.6 restore for a SAN Client The SAN client is not working correctly since it came out. (It took Symantec until 6.5.4 to remove the fragment issue that i did report with version 6.5.1) I'm working on a case since Netbackup 6.5.1 and still restores are failing most of the times. Fell free to link your case with my case number (410-654-721). The more customers report this unacceptable situation the more pressure for Symantec to fix this issue. For me it worked to set the SAN client to never under device section - this switched to LAN and the restores worked always this way. To permanently disable i would recommend: bpclntcmd -sanclient 0 Stop (windows) or kill (Unix/Linux) the nbftclnt service process on the client You should now be able to delete the client from the GUI (SAN Clients in Devices) Best Regards, Ernst +-- |This was sent by wanner.er...@synthes.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] NBU 6.5.6 restore for a SAN Client
It's too bad that this thread didn't happen a few weeks ago, as now I am committed to delivering a SAN Client solution for a client that is incomplete. We are running NBU 6.5.4, and no restores have worked yet at all, with SAN Client enabled. Unfortunately, we are deploying SAN Client specifically because the client does not have any more ports available to use for backup. Restoring the backups over the LAN is really not an option in this case. I will be opening a case with Symantec about this, and I will see about having it linked with your case. -Rob Thelen. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of ch1waner Sent: Monday, October 25, 2010 9:21 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] NBU 6.5.6 restore for a SAN Client The SAN client is not working correctly since it came out. (It took Symantec until 6.5.4 to remove the fragment issue that i did report with version 6.5.1) I'm working on a case since Netbackup 6.5.1 and still restores are failing most of the times. Fell free to link your case with my case number (410-654-721). The more customers report this unacceptable situation the more pressure for Symantec to fix this issue. For me it worked to set the SAN client to never under device section - this switched to LAN and the restores worked always this way. To permanently disable i would recommend: bpclntcmd -sanclient 0 Stop (windows) or kill (Unix/Linux) the nbftclnt service process on the client You should now be able to delete the client from the GUI (SAN Clients in Devices) Best Regards, Ernst +-- |This was sent by wanner.er...@synthes.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] need help with mass tape copy
IN order to do that quickest, you would want to have a media server or two that is configured to see both 9940 and LTO4 drives. Then, setup those media servers to read and write to the itself and let it run. If you use one media to read 9940 media and then duplicate to another media server with LTO4 drives, then the data will travel the network. You do not want this to happen. This will cause the duplications to take a very very very long time to complete. -Rob Thelen. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of X_S Sent: Thursday, September 23, 2010 11:00 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] need help with mass tape copy we are using nb 6.5.5 on windows 2003 platform with vault. we need to copy a few hundred 9940 tapes to LTO4 media and am looking for the best and most efficient way to copy the tapes. my other question is, can i use one media server to read the 9940 tapes and have them duplicated to another media server that has the LTO4 drives attached? thanks +-- |This was sent by xsp...@yahoo.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ 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] Policy kicking off again after a successful backupandgetting 196 errors.
I have seen Calendar based backups do this when the backup window is open for a long time. The Window is really to be used for frequency based backups – The backup will happen sometime during that window, based on the frequency. However, for calendar based backups, the start of the backup window is when the backup is set to run. If the backup runs and completes during the window, and it is still the same calendar day, then the backup will run again, until the backup window closes, with some respect for the frequency (but not much). I solved this in the past by either shrinking the backup window or inflating the frequency. With your backup windows starting at 7am and running all day through 10pm, I would guess that some of these backups might even run more than once per day. -Rob Thelen. From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour, Wayne Sent: Tuesday, September 21, 2010 7:39 AM To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Policy kicking off again after a successful backupandgetting 196 errors. It’s calendar based, daily is a Cumulative Incremental that runs Monday through Saturday, backup window 07:00:00 à 22:00:00. The weekly / monthly is a Full, runs on Sunday with the same window. It has happened on the weekly and daily runs. Wayne BeDour Unix System Administrator PH: 248-447-1739 Internet: wbed...@lear.com From: WEAVER, Simon (external) [mailto:simon.wea...@astrium.eads.net] Sent: Tuesday, September 21, 2010 8:28 AM To: BeDour, Wayne; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Policy kicking off again after a successful backup andgetting 196 errors. Wayne What is the frequency set for in this policy (within the schedule). Simon From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of BeDour, Wayne Sent: Tuesday, September 21, 2010 1:07 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Policy kicking off again after a successful backup andgetting 196 errors. Our environment, HP-UX 11-31 currently running one master and media server running NetBackup 6.5.2. Running mostly unix / Linus backups and a couple windows b/u’s thrown in for good measure. I’ve been modifying a few policies, splitting out mount points, changing the volume pool etc. On a couple of the policies that I’ve modified, they successfully run to completion and then they kick off again and error out with a 196. When they attempt to run after the successful run, they are still in the backup window even though they shouldn’t have kicked off again. Doesn’t make much sense to me, anyone ever see this before? Thanks in advance…. Wayne BeDour Unix System Administrator PH: 248-447-1739 Internet: wbed...@lear.com ** ** LEGAL DISCLAIMER ** ** This E-mail message and any attachments may contain legally privileged, confidential or proprietary information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this E-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this E-mail message from your computer. 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. -o- Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ** ** LEGAL DISCLAIMER ** ** This E-mail message and any attachments may contain legally privileged, confidential or proprietary information. If you are not the intended recipient(s), or the employee or agent responsible for delivery of this message to the intended recipient(s), you are hereby notified that any dissemination, distribution or copying of this E-mail message is strictly prohibited. If you have received this message in error, please immediately notify the sender and delete this E-mail message from your computer. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
