Re: [Veritas-bu] VSP in 6.x
Another cause of large cache, is when the AV is not configured correctly - this also makes the file become larger than required, use all disk space, and then report to NetBackup that the snap shot failed (156 status). Again, fine tuning the AV, or turning it off can be of some assistance.. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Martin, Jonathan Sent: Monday, October 29, 2007 5:22 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x If I'm not mistaken VSS is only available on Windows 2003. Windows 2000 users are kind of up the creek. If you want the software installed the same way every time I'd recommend creating a .mst or modifying Symantec's .msi so it can only be installed one way. Software deployment FTW. =) I've found with 200+ windows machines that its only certain boxes that have trouble with VSP files and for those I either disable VSP on the master or switch to VSS if Windows 2003. I think its 6 servers right now. That's not bad for 200+. As far as disabling VSP all together, I'd rather have more Windows 2000 files backed up via VSP and deal with the headaches when it infrequently breaks, than turn it off altogether and miss all that data all the time. -Jonathan _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Monday, October 29, 2007 12:53 PM To: Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Use VSS, not VSP and you won't have the issues in 6.0. We've instructed our Windows admins to always do a custom install and disable the VSS installation and let Windows do the snapshots. No more cache files. Now getting the Windows admins to actually follow the installation instructions and do a custom install - that's a challenge all by itself. Whenever they complain to us (Storage) about a large cache file, we tell them to read the install docs and get it right this time. .../Ed On 10/29/07, Major, Rusty [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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] VSP in 6.x
VSS is fine for Win2k3, but you will need VSP for earlier versions of windows. Common issue the old cache... there are tools to use to remove the lock, which is very simple to do. Sysinternals is worth a look around. I have used the standard install, and to be honest not had that many issues with large cache files. Again, there are documents to tune this, or if you want, simply turn it off. The snap shot option is there for a reason - again, rather than turn off, check to see what it can offer your environment. Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Monday, October 29, 2007 4:53 PM To: Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Use VSS, not VSP and you won't have the issues in 6.0. We've instructed our Windows admins to always do a custom install and disable the VSS installation and let Windows do the snapshots. No more cache files. Now getting the Windows admins to actually follow the installation instructions and do a custom install - that's a challenge all by itself. Whenever they complain to us (Storage) about a large cache file, we tell them to read the install docs and get it right this time. .../Ed On 10/29/07, Major, Rusty [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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
[Veritas-bu] Error status 129 - DiskStaging Unit is full - NetBackup 6.0
Hello I'm using 6.0 with a diskstaging unit on 1Tb. Now I get a lot of 129 errors that says the staging unit is full. The problem is that is not full. Its abou 325Gb og free space. Does anybody have any suggestions? +-- |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] Error status 129 - DiskStaging Unit is full -NetBackup 6.0
I've never seen an error 129 when there is plenty of space for backups. Are you sure the system has 325GB free at the time of the error? If you are running (for example) a 500GB backup, it will fill up the drive, give you the error 129 then remove the 325GB of 500GB it has already backed up. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of osonder Sent: Tuesday, October 30, 2007 5:15 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0 Hello I'm using 6.0 with a diskstaging unit on 1Tb. Now I get a lot of 129 errors that says the staging unit is full. The problem is that is not full. Its abou 325Gb og free space. Does anybody have any suggestions? +-- |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] Error status 129 - DiskStaging Unit is full - NetBackup 6.0
Hello Jonathan You may have a point. Because this happens in the middle of the night. So I'm not here when this happens. I just looked at the DSSU at the morning and noticed a free space of 325Gb. +-- |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] BackupExec -- NBU Migration
Does anyone know if there is a BackupExec -- Netbackup migration path? I know you can import the media into Netbackup, but if I've got a live BE 10d environment and I want to upgrade it to Netbackup is there any way to preserve that catalog information and import it into the fresh Netbackup install? -Jonathan ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0
Nothing worse than backing up 800GB of data and having it fail at 799GB because of low / no disk space. If you enable checkpoint backups it will retain the backed up bit back to the last 15 or 30 minutes or whatever you configure. That way you can restart the backup after you clear disk space. Its better than starting over from scratch. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of osonder Sent: Tuesday, October 30, 2007 9:12 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0 Hello Jonathan You may have a point. Because this happens in the middle of the night. So I'm not here when this happens. I just looked at the DSSU at the morning and noticed a free space of 325Gb. +-- |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] VSS
Has anyone else experienced significant slowdown of backups using VSS? Our environment is 5.1 MP6 running on Suse 9.2 Linux and HPUX 11.11 with W2k3 or Suse 9.2 Linux media servers. -- George Herbert|Platform Solutions - Storage Solutions|SunTrust Banks http://www.suntrust.com/ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, October 30, 2007 3:19 AM To: 'Ed Wilts'; Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x VSS is fine for Win2k3, but you will need VSP for earlier versions of windows. Common issue the old cache... there are tools to use to remove the lock, which is very simple to do. Sysinternals is worth a look around. I have used the standard install, and to be honest not had that many issues with large cache files. Again, there are documents to tune this, or if you want, simply turn it off. The snap shot option is there for a reason - again, rather than turn off, check to see what it can offer your environment. Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Monday, October 29, 2007 4:53 PM To: Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Use VSS, not VSP and you won't have the issues in 6.0. We've instructed our Windows admins to always do a custom install and disable the VSS installation and let Windows do the snapshots. No more cache files. Now getting the Windows admins to actually follow the installation instructions and do a custom install - that's a challenge all by itself. Whenever they complain to us (Storage) about a large cache file, we tell them to read the install docs and get it right this time. .../Ed On 10/29/07, Major, Rusty [EMAIL PROTECTED] wrote: Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] 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 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSS
Well thing to do, is turn off VSS, or any I/O disk activity software, or possibly the AV while the backup runs. To be honest, its hard to know what your problem is, without knowing the spec of the Server, the type of files you have, network speeds, port configuration, ect Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Herbert.George [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 1:41 PM To: WEAVER, Simon (external); Ed Wilts; Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: VSS Has anyone else experienced significant slowdown of backups using VSS? Our environment is 5.1 MP6 running on Suse 9.2 Linux and HPUX 11.11 with W2k3 or Suse 9.2 Linux media servers. -- George Herbert|Platform Solutions - Storage Solutions|SunTrust Banks http://www.suntrust.com/ _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of WEAVER, Simon (external) Sent: Tuesday, October 30, 2007 3:19 AM To: 'Ed Wilts'; Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x VSS is fine for Win2k3, but you will need VSP for earlier versions of windows. Common issue the old cache... there are tools to use to remove the lock, which is very simple to do. Sysinternals is worth a look around. I have used the standard install, and to be honest not had that many issues with large cache files. Again, there are documents to tune this, or if you want, simply turn it off. The snap shot option is there for a reason - again, rather than turn off, check to see what it can offer your environment. Thanks Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Monday, October 29, 2007 4:53 PM To: Major, Rusty Cc: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Use VSS, not VSP and you won't have the issues in 6.0. We've instructed our Windows admins to always do a custom install and disable the VSS installation and let Windows do the snapshots. No more cache files. Now getting the Windows admins to actually follow the installation instructions and do a custom install - that's a challenge all by itself. Whenever they complain to us (Storage) about a large cache file, we tell them to read the install docs and get it right this time. .../Ed On 10/29/07, Major, Rusty [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] wrote: Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] mailto:[EMAIL PROTECTED] 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 LEGAL DISCLAIMER The information transmitted is intended solely for the individual or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of or taking action in reliance upon this information by persons or entities other than the intended recipient is prohibited. If you have received this email in error please contact the sender and delete the material from any computer. SunTrust and Seeing beyond money are federally registered service marks of SunTrust Banks, Inc. [ST:XCL] 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
Re: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0
I had the same issue. This is what I got from my SUN/Symantic Support: I did hear back from Symantec. The level 4 engineer at Symantec identified the issue as an instance of a defect that will be resolved in 6.0 MP6. I've filed Sun Change Request (CR) 6623137 fo document this problem. The Symantec issue was described as, backup jobs to disk would end in a status 129 when the disk was full. The DSSU's would fill up, the backups writing to it would exit with a status 129, then the images would subsequently be cleaned up and the backups run fine. The fixes (to bptm and bpdm) should pause backups writing to full dssu's, clean up old images and then resume backups. The tentative expectation is that 6.0 MP6 will be available in January to February, 2008. Symantec has tested a hot fix on a Linux platform at a customer site, and can generate Solaris binaries, if you require a hot fix. I explained to our contact at Symantec that my greatest concern was a misidentification of the issue, as there has been difficulty explaining this issue up till now. She has reviewed the logs and other data provided from your site, and is confident that this issue the issue they addressed for one or two other sites and documented as the bug cited here. Steve On 10/30/07, Martin, Jonathan [EMAIL PROTECTED] wrote: Nothing worse than backing up 800GB of data and having it fail at 799GB because of low / no disk space. If you enable checkpoint backups it will retain the backed up bit back to the last 15 or 30 minutes or whatever you configure. That way you can restart the backup after you clear disk space. Its better than starting over from scratch. -Jonathan -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of osonder Sent: Tuesday, October 30, 2007 9:12 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0 Hello Jonathan You may have a point. Because this happens in the middle of the night. So I'm not here when this happens. I just looked at the DSSU at the morning and noticed a free space of 325Gb. +-- |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 maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSP in 6.x
Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSP in 6.x
exclude .tmp files then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 2:35 PM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. 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] VSP in 6.x
So they changed the extension in 6.X??? How tricky can these guys get? Is that the client binary change (I would assume) that changes the extension? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 10:35 AM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSP in 6.x
Yes, I think that it would be a Very Great Idea to exclude from virus scanning all files on all systems for which I do backups of all files with the file extension .tmp. I'm sure that the Security Officer will think that's a great idea too. (No. That's not an option, of course. Which was my point.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 10:42 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x exclude .tmp files then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 2:35 PM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. 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
[Veritas-bu] Error status 129 - DiskStaging Unit is full
If you are using 6.0 MP4 or 6.0MP5 the status 129's are most likely happening when the dssu fills up. What is supposed to happen is that NetBackup pauses the backups, stages the data and then cleans up the images, then the backup proceeds. What happens at 6.0MP4 and 6.0MP5 is that the backup is paused, staging occurs, but the images are not immediately removed - resulting in a status 129. Regular cleanup will remove the staged files and then the space is cleaned up. This is due to be resolved in 6.0MP6. A work around would be to set up manual staging policies (if this is already done - you might want to run it more frequently.) D __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSP in 6.x
If there was a change in 6.x, it was *to* using a .vsp extension, not from it. (I don't have any 6.x environments handy to check.) See http://seer.entsupport.symantec.com/docs/270127.htm -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Bobby Williams [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 10:42 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x So they changed the extension in 6.X??? How tricky can these guys get? Is that the client binary change (I would assume) that changes the extension? Bobby Williams 2205 Peterson Drive Chattanooga, Tennessee 37421 423-296-8200 _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 10:35 AM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Error status 129 - DiskStaging Unit is full -NetBackup 6.0
This is a instance of defect? It looks like to me 6.0 MP5 already does cleanup of old images when the DSU gets filled up during the backup process. I just had one DSU filled up last night and here are the logs I captured: The backup job log from the Admin console: 10/29/2007 22:18:20 - begin writing 10/29/2007 22:19:05 - Warning bpdm (pid=5419) storage unit ee03dbp- disk47 is full: processing disk full condition 10/29/2007 22:19:22 - Critical bpdm (pid=5419) storage unit /data/ bk47 is full 10/29/2007 22:19:22 - Critical bpdm (pid=5419) bp_sts_open_image failed: error 31 10/29/2007 22:19:23 - end writing; write time: 0:01:03 Disk storage unit is full (129) Here is the bpdm log showing it was trying to clean up old images: 22:19:05.159 [5419] 4 write_backup: successfully wrote backup id rptprd-data-vip.prod.advertising.com_1193710548, copy 1, fragment 4, 2000128 Kbytes at 49402.954 Kbytes/sec 22:19:05.175 [5419] 16 ee03dbp-data: STSBasicDisk: Caught exception in STSBasicDisk::CreateImage, FILE=STSBasicDiskIma geInfo.cpp, FUNCTION=, LINE=260, ERROR=STS_ENOSPC 22:19:05.175 [5419] 32 bp_sts_open_image: sts_create_image failed: error 31 22:19:05.176 [5419] 4 db_getSTUNIT: EMM interface already initialized (using cached master name s01-inf-bkpvip.prod.ro ot). 22:19:05.279 [5419] 2 vnet_vnetd_service_socket: vnet_vnetd.c.2034: VN_REQUEST_SERVICE_SOCKET: 6 0x0006 22:19:05.280 [5419] 2 vnet_vnetd_service_socket: vnet_vnetd.c.2048: service: bpdbm 22:19:05.284 [5419] 2 logconnections: BPDBM CONNECT FROM 192.168.9.107.61767 TO 10.100.9.50.13724 22:19:05.599 [5419] 8 process_diskfull: storage unit ee03dbp-disk47 is full: processing disk full condition 22:19:05.614 [5419] 2 make_space_STANDARD: Acquired exclusive use of bpdm disk cleanup lock (ee03dbp-disk47 1092188) 22:19:05.620 [5419] 2 ds_logger: libsts openp() 07/10/29 22:19:05: opening module /usr/openv/lib/libstspibasicdisk.so 22:19:07.269 [10540] 2 vnet_vnetd_service_socket: vnet_vnetd.c. 2034: VN_REQUEST_SERVICE_SOCKET: 6 0x0006 22:19:07.270 [10540] 2 vnet_vnetd_service_socket: vnet_vnetd.c. 2048: service: bpdbm 22:19:07.274 [10540] 2 logconnections: BPDBM CONNECT FROM 192.168.9.107.61775 TO 10.100.9.50.13724 22:19:07.353 [5419] 4 ds_logger: found 0 of 523 images 22:19:07.359 [5419] 2 bpdm: firstloop, no candidates, no delay on lock --- returning disk full 22:19:07.360 [5419] 2 bpdm: updating EMM with FINAL freespace = 7855583232 22:19:07.360 [5419] 4 db_modifySTUNIT: EMM interface already initialized (using cached master name s01-inf-bkpvip.prod .root). 22:19:07.425 [5419] 2 db_modifySTUNIT: 22:19:07.426 [5419] 2 make_space_STANDARD: Released bpdm disk cleanup lock (ee03dbp-disk47 1092188) 22:19:07.427 [5419] 2 process_diskfull: disk is full, calling diskfull_notify script 22:19:07.427 [5419] 2 notify_call: executing - /usr/openv/netbackup/ bin/diskfull_notify bpdm /data/bk47/rptprd-data-vi p.prod.advertising.com_1193710548_C1_F5 /dev/null /dev/null 2/dev/ null 22:19:07.496 [5419] 2 diskfull_corral: DSU IS FULL (0KB written) 22:19:07.516 [5419] 2 diskfull_corral: Released diskfull cleanup lock Rongsheng On Oct 30, 2007, at 10:17 AM, Steve Fogarty wrote: I had the same issue. This is what I got from my SUN/Symantic Support: I did hear back from Symantec. The level 4 engineer at Symantec identified the issue as an instance of a defect that will be resolved in 6.0 MP6. I've filed Sun Change Request (CR) 6623137 fo document this problem. The Symantec issue was described as, backup jobs to disk would end in a status 129 when the disk was full. The DSSU's would fill up, the backups writing to it would exit with a status 129, then the images would subsequently be cleaned up and the backups run fine. The fixes (to bptm and bpdm) should pause backups writing to full dssu's, clean up old images and then resume backups. The tentative expectation is that 6.0 MP6 will be available in January to February, 2008. Symantec has tested a hot fix on a Linux platform at a customer site, and can generate Solaris binaries, if you require a hot fix. I explained to our contact at Symantec that my greatest concern was a misidentification of the issue, as there has been difficulty explaining this issue up till now. She has reviewed the logs and other data provided from your site, and is confident that this issue the issue they addressed for one or two other sites and documented as the bug cited here. Steve On 10/30/07, Martin, Jonathan [EMAIL PROTECTED] wrote: Nothing worse than backing up 800GB of data and having it fail at 799GB because of low / no disk space. If you enable checkpoint backups it will retain the backed up bit back to the last 15 or 30 minutes or whatever you configure. That way you can restart the backup after you clear disk space. Its better than starting over from scratch. -Jonathan -Original Message- From: [EMAIL PROTECTED]
Re: [Veritas-bu] VSP in 6.x
who said ALL files ? exclude the name.tmp ! :-) For example, depending on your AV, something like *_vxfiVSPCacheFile_*.tmp Sure you can figure it out.. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Rosenkoetter, Gabriel [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 2:43 PM To: WEAVER, Simon (external); Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x Yes, I think that it would be a Very Great Idea to exclude from virus scanning all files on all systems for which I do backups of all files with the file extension .tmp. I'm sure that the Security Officer will think that's a great idea too. (No. That's not an option, of course. Which was my point.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 10:42 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x exclude .tmp files then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 2:35 PM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. 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 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] VSP in 6.x
My original point here was that Symantec AntiVirus precisely fails to permit exclusions of the sort you describe. (It's not the only AntiVirus product out there, but it's also not the only one with a broken exclusion methodology, and it is one of the more popular. And comes from, ahem, the same vendor as NetBackup.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 11:07 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x who said ALL files ? exclude the name.tmp ! :-) For example, depending on your AV, something like *_vxfiVSPCacheFile_*.tmp Sure you can figure it out.. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: Rosenkoetter, Gabriel [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 2:43 PM To: WEAVER, Simon (external); Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x Yes, I think that it would be a Very Great Idea to exclude from virus scanning all files on all systems for which I do backups of all files with the file extension .tmp. I'm sure that the Security Officer will think that's a great idea too. (No. That's not an option, of course. Which was my point.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 10:42 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x exclude .tmp files then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 2:35 PM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. 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
Re: [Veritas-bu] Error status 129 - DiskStaging Unit is full
Do not completely agree with this statement. Images are indeed immediately removed. WHAT you have to take care of is that NO CATALOG BACKUP is running at the same time a cleanup is required !! Bernard Tel. (32 2 22) 85459 // 0477 390 211 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] From: d w [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 3:50 PM To: VERITAS-BU@mailman.eng.auburn.edu; [EMAIL PROTECTED] Subject: [Veritas-bu] Error status 129 - DiskStaging Unit is full If you are using 6.0 MP4 or 6.0MP5 the status 129's are most likely happening when the dssu fills up. What is supposed to happen is that NetBackup pauses the backups, stages the data and then cleans up the images, then the backup proceeds. What happens at 6.0MP4 and 6.0MP5 is that the backup is paused, staging occurs, but the images are not immediately removed - resulting in a status 129. Regular cleanup will remove the staged files and then the space is cleaned up. This is due to be resolved in 6.0MP6. A work around would be to set up manual staging policies (if this is already done - you might want to run it more frequently.) D __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com = = = = = = = = = = = = = = = = = = = = = = = = = Fortis disclaimer : http://www.fortis.be/legal/disclaimer.htm Privacy policy related to banking activities of Fortis: http://www.fortis.be/legal/privacy_policy.htm = = = = = = = = = = = = = = = = = = = = = = = = = ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Status 83 cannot open file E:\\VERITAS\NetBackup\db\media\tpreq/0269L3
Hello After a botched install of MP6 and uninstall of it. I keep getting status 83, in the details of the job there is entries like cannot open file E:\\VERITAS\NetBackup\db\media\tpreq/0269L3 Have tried to shut down the backup server through the RAC interface, to be sure there wasn't any hanging process Hope that you guys have some ideas Regards Michael ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] disaster recovery best practices.
We're currently running Netbackup 5.1 MP4 on our Solaris Master server. We're looking at replacing the server hardware and since the server doesn't have enough local disk, we're going to present SAN space to the sever. We're looking at using SRDF to replicate the data on the SAN lun to a remote site in the event of a disaster. I was wondering what the best practice is forgetting data out to a remote site. Should I just put the /netbackup/db/images on the San lun and leave everything else on Local disk, or should I install everything on the SAN. We are looking at upgrading to 6.5 once the hardware replacement is finished. Don Klebba Quicken Loans Storage Management Team [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] phone: (734)805-7791 cell: (734)634-7486 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Backup and Vault Performance
Does a whitepaper exist that explains the relationship between using multiple write drives/multiple streams and the effect it has on i/o performance? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] VSP in 6.x
good job I dont use Symantec AV then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Rosenkoetter, Gabriel [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 3:27 PM To: WEAVER, Simon (external); Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x My original point here was that Symantec AntiVirus precisely fails to permit exclusions of the sort you describe. (It's not the only AntiVirus product out there, but it's also not the only one with a broken exclusion methodology, and it is one of the more popular. And comes from, ahem, the same vendor as NetBackup.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 11:07 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x who said ALL files ? exclude the name.tmp ! :-) For example, depending on your AV, something like *_vxfiVSPCacheFile_*.tmp Sure you can figure it out.. Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: Rosenkoetter, Gabriel [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 2:43 PM To: WEAVER, Simon (external); Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x Yes, I think that it would be a Very Great Idea to exclude from virus scanning all files on all systems for which I do backups of all files with the file extension .tmp. I'm sure that the Security Officer will think that's a great idea too. (No. That's not an option, of course. Which was my point.) -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 30, 2007 10:42 AM To: Rosenkoetter, Gabriel; Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] VSP in 6.x exclude .tmp files then :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: mailto:[EMAIL PROTECTED] [EMAIL PROTECTED] -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rosenkoetter, Gabriel Sent: Tuesday, October 30, 2007 2:35 PM To: Rockey Reed; Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Um, Rocky... you're aware that the file extension for VSP files is .tmp, right? -- gabriel rosenkoetter Radian Group Inc, Unix/Linux/VMware Sysadmin / Backup Recovery [EMAIL PROTECTED], 215 231 1556 _ From: Rockey Reed [mailto:[EMAIL PROTECTED] Sent: Monday, October 29, 2007 4:56 PM To: Major, Rusty; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] VSP in 6.x Rusty, Make sure you virus scan is set to ignore .VSP file. VSP will be required of W2K servers; whereas, VSS should be used on W2K3. Thanks, Rockey J. Reed You're not obligated to win. You're obligated to keep trying to do the best you can every day. Marian Wright Edelman _ From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Major, Rusty Sent: Monday, October 29, 2007 11:45 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] VSP in 6.x Has NBU 6.0 or 6.5 fixed the issue with the VSP Cache file becoming locked and not cleaning up after itself? This remains a common problem for me in 5.1 so we try not to use it. Thanks, Rusty Major, MCSE, BCFP Sr. Data Assurance Engineer (281) 584-4693 VeriCenter, Inc. 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 This email (including any attachments) may contain confidential and/or privileged information or information
