Re: [Veritas-bu] Veritas reporting
You should also look at APTARE Storage Console. www.Aptare.com John Trainer David Rock [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 12/15/2005 09:36 PM Please respond to David Rock [EMAIL PROTECTED] To veritas-bu@mailman.eng.auburn.edu cc Subject Re: [Veritas-bu] Veritas reporting * Geordie Wardman [EMAIL PROTECTED] [2005-12-15 14:22]: I'm looking for something that sends pretty graphs of all my backups, which ones were successful, and which ones failed. Preferably in a .pdf bar chart or something. That is my main concern. I use bpdbjobs to send a .csv file, and it is fine for me, but not for Sr. Mgt. If you aren't afraid of rolling your own, there are a few open source plotting packages that would probably suit your needs; gnuplot, matplotlib are a couple that come to mind off the top. -- David Rock [EMAIL PROTECTED] [attachment attsfncn.dat deleted by John Trainer/IT/CF/CCI]
[Veritas-bu] Disk volume layout question
We are in the early stages of migrating from Legato NetWorker to Veritas NetBackup 5.1. As part of our migration, we are adding enough disk space to hold one week worth of backups before they are staged to tape. When configuring our disk (approximately 9.6TB before RAID in a Sun StorEdge 3511 SATA array. NetBackup server is a Sun E450 running Solaris 10) are there any recommendations for how it should be separated out into volumes? Is it better to have one large volume? Many small volumes? What are the advantages and disadvantages to the given volume sizes from a NetBackup perspective? Thank you, Eric Johnson Service Technologist Tel: (204)925-3404 Email: [EMAIL PROTECTED] MTS Allstream ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disk volume layout question
On Fri, Dec 16, 2005 at 12:52:05PM -0500, Johnson, Eric K wrote: We are in the early stages of migrating from Legato NetWorker to Veritas NetBackup 5.1. As part of our migration, we are adding enough disk space to hold one week worth of backups before they are staged to tape. When configuring our disk (approximately 9.6TB before RAID in a Sun StorEdge 3511 SATA array. NetBackup server is a Sun E450 running Solaris 10) are there any recommendations for how it should be separated out into volumes? Is it better to have one large volume? Many small volumes? What are the advantages and disadvantages to the given volume sizes from a NetBackup perspective? With 5.1, a job will fail if the DSSU fills up. There are no mechanisms to throw a bunch of volumes at it and let NetBackup chose. With 6.0, this problem is supposed to go away. For now, I'd think that you would want to create a single large array. All of this assumes that all backups are created equally. If there is some stuff that you need to guarantee stays on disk for a week, you may need to set up individual DSSUs for that stuff (we're doing this for some Oracle databases). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Disk volume layout question
Veritas says to create a different filesystem for Full and Incrementals, due to the backup sizes generally involved and how many files have to get deleted for each when cleaning a DSSU. Future versions of NetBackup sound like they'll do a much better job of handling staging disks. Some light reading for you: http://seer.support.veritas.com/docs/270101.htm http://seer.support.veritas.com/docs/270079.htm http://seer.support.veritas.com/docs/268777.htm http://seer.support.veritas.com/docs/265305.htm http://seer.support.veritas.com/docs/278169.htm http://seer.support.veritas.com/docs/273532.htm Depending on what you're using for back-end storage, EMC also has a pair of whitepapers/briefs you can get on running backups to disk. They should be available from their webpage somewhere. Effective Write Bandwidth with CLARiiON ATA Disk Drives and RAID 3: Backup-to=Disk and Streaming Media EMC Backup Storage Solutions: Backup-to-Disk Guide with VERITAS NetBackup Have fun. =) - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Friday, December 16, 2005 10:51 AM To: Johnson, Eric K Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Disk volume layout question On Fri, Dec 16, 2005 at 12:52:05PM -0500, Johnson, Eric K wrote: We are in the early stages of migrating from Legato NetWorker to Veritas NetBackup 5.1. As part of our migration, we are adding enough disk space to hold one week worth of backups before they are staged to tape. When configuring our disk (approximately 9.6TB before RAID in a Sun StorEdge 3511 SATA array. NetBackup server is a Sun E450 running Solaris 10) are there any recommendations for how it should be separated out into volumes? Is it better to have one large volume? Many small volumes? What are the advantages and disadvantages to the given volume sizes from a NetBackup perspective? With 5.1, a job will fail if the DSSU fills up. There are no mechanisms to throw a bunch of volumes at it and let NetBackup chose. With 6.0, this problem is supposed to go away. For now, I'd think that you would want to create a single large array. All of this assumes that all backups are created equally. If there is some stuff that you need to guarantee stays on disk for a week, you may need to set up individual DSSUs for that stuff (we're doing this for some Oracle databases). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[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] 4.5 to 5.1 upgrade
The upgrade is going rather well. Just a few nits. There is one we have not figured out. One of our 2 exchange servers is failing with a status 59. When attempting to do the client properties or connect from the master we receive "server not allowed access" this is the same from bpgetconfig -M svrmailgate The master is a sun box running solaris 9 Not sure what to check on the client to correct this problem
RE: [Veritas-bu] Disk volume layout question
In NB 5.0, i have noticed that one DSSU(a) can't delete the contents of another DSSU(b) if it needs more space. example: /export/dsu is a single partition /export/dsu/daily all information has been duplicated to tape /export/dsu/monthend needs more space, but can't/won't ask /export/dsu/daily to delete some information. Currently, your better splitting off a slice for each DSSU. Which leads to wasted space. Maybe that has changed under 6.0. Karl [EMAIL PROTECTED] wrote on 12/16/2005 01:20:42 PM: Veritas says to create a different filesystem for Full and Incrementals, due to the backup sizes generally involved and how many files have to get deleted for each when cleaning a DSSU. Future versions of NetBackup sound like they'll do a much better job of handling staging disks. Some light reading for you: http://seer.support.veritas.com/docs/270101.htm http://seer.support.veritas.com/docs/270079.htm http://seer.support.veritas.com/docs/268777.htm http://seer.support.veritas.com/docs/265305.htm http://seer.support.veritas.com/docs/278169.htm http://seer.support.veritas.com/docs/273532.htm Depending on what you're using for back-end storage, EMC also has a pair of whitepapers/briefs you can get on running backups to disk. They should be available from their webpage somewhere. Effective Write Bandwidth with CLARiiON ATA Disk Drives and RAID 3: Backup-to=Disk and Streaming Media EMC Backup Storage Solutions: Backup-to-Disk Guide with VERITAS NetBackup Have fun. =) - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Ed Wilts Sent: Friday, December 16, 2005 10:51 AM To: Johnson, Eric K Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Disk volume layout question On Fri, Dec 16, 2005 at 12:52:05PM -0500, Johnson, Eric K wrote: We are in the early stages of migrating from Legato NetWorker to Veritas NetBackup 5.1. As part of our migration, we are adding enough disk space to hold one week worth of backups before they are staged to tape. When configuring our disk (approximately 9.6TB before RAID in a Sun StorEdge 3511 SATA array. NetBackup server is a Sun E450 running Solaris 10) are there any recommendations for how it should be separated out into volumes? Is it better to have one large volume? Many small volumes? What are the advantages and disadvantages to the given volume sizes from a NetBackup perspective? With 5.1, a job will fail if the DSSU fills up. There are no mechanisms to throw a bunch of volumes at it and let NetBackup chose. With 6.0, this problem is supposed to go away. For now, I'd think that you would want to create a single large array. All of this assumes that all backups are created equally. If there is some stuff that you need to guarantee stays on disk for a week, you may need to set up individual DSSUs for that stuff (we're doing this for some Oracle databases). .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[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] 5.1 MP4
From the MP4 readme: Etrack Incident = ET313352 Description: Disk staging only submits one duplication job at a time so it was unable to make use of idle tape drives. Additional Notes: Up to four bpduplicate jobs are submitted at a time. The duplication jobs contain images grouped into jobs of 25 Gigabytes. By creating files named MAX_STAGING_JOBS and STAGING_JOB_KB_LIMIT in the NetBackup directory on the master server, these defaults can be adjusted as needed. For the STAGING_JOB_KB_LIMIT, the value is in kilobytes and the default is 26214400 (25 gigabytes). A smaller value causes more jobs to be submitted, but there will only be MAX_STAGING_JOBS running at a time. It's not a bug, it's a feature. I've also seen those bid files present under 5.1 MP3a so it's nothing new anyway. I haven't seen hundreds either so I'm pretty sure NB is cleaning up after itself at some point. - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geyer, Gregory Sent: Friday, December 16, 2005 3:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 5.1 MP4 We've upgraded to 5.1 MP4 and are now experiencing issues with Disk staging. We've got a ticket open but interested to see if anyone else has experience these issues: The disk staging process now automatically takes 4 tape drives per DSSU when going off to tape. This is a problem if you have 6 DSSUs and only 15 tape drives, not to mention those drives are needed for other media servers. It is now also creating these files on the DSSU media servers in /usr/openv/netbackup: root@hostname:/usr/openv/netbackup# ll bid* -rw-rw-rw- 1 root root 1984 Dec 15 13:20 bid_file_bladestore_oracle0 -rw-rw-rw- 1 root root 530 Dec 16 13:08 bid_file_bladestore_oracle_1_15240 -rw-rw-rw- 1 root root 1219 Dec 16 13:08 bid_file_bladestore_oracle_2_15240 -rw-rw-rw- 1 root root18 Dec 16 13:08 bid_file_bladestore_oracle_3_15240 -rw-rw-rw- 1 root root 293 Jul 1 2004 bid_file_bladestore_staging_1TB0 -rw-rw-rw- 1 root root 4375 Dec 15 10:04 bid_file_bladestore_unix0 SNIP In the files are a listing of images to get backed up. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Disk volume layout question
On Fri, Dec 16, 2005 at 02:23:10PM -0600, [EMAIL PROTECTED] wrote: In NB 5.0, i have noticed that one DSSU(a) can't delete the contents of another DSSU(b) if it needs more space. Maybe that has changed under 6.0. You can have a group of DSSUs in 6.0. If dssu1 fills during a backup run, NBU can automatically start using dssu2. We're not at 6.0 yet here, but that's what I've heard. .../Ed -- Ed Wilts, Mounds View, MN, USA mailto:[EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] 5.1 MP4
John, GREAT INFORMATION! Now, to investigate whether MAX_STAGING_JOBS is per DSSU or altogether (ie, if DSSU#1 kicks off first and grabs all the jobs, what does DSSU#2 do?) Thanks again, the list rocks. G. -Original Message- From: Nardello, John [mailto:[EMAIL PROTECTED] Sent: Friday, December 16, 2005 4:26 PM To: Geyer, Gregory Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] 5.1 MP4 From the MP4 readme: Etrack Incident = ET313352 Description: Disk staging only submits one duplication job at a time so it was unable to make use of idle tape drives. Additional Notes: Up to four bpduplicate jobs are submitted at a time. The duplication jobs contain images grouped into jobs of 25 Gigabytes. By creating files named MAX_STAGING_JOBS and STAGING_JOB_KB_LIMIT in the NetBackup directory on the master server, these defaults can be adjusted as needed. For the STAGING_JOB_KB_LIMIT, the value is in kilobytes and the default is 26214400 (25 gigabytes). A smaller value causes more jobs to be submitted, but there will only be MAX_STAGING_JOBS running at a time. It's not a bug, it's a feature. I've also seen those bid files present under 5.1 MP3a so it's nothing new anyway. I haven't seen hundreds either so I'm pretty sure NB is cleaning up after itself at some point. - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geyer, Gregory Sent: Friday, December 16, 2005 3:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 5.1 MP4 We've upgraded to 5.1 MP4 and are now experiencing issues with Disk staging. We've got a ticket open but interested to see if anyone else has experience these issues: The disk staging process now automatically takes 4 tape drives per DSSU when going off to tape. This is a problem if you have 6 DSSUs and only 15 tape drives, not to mention those drives are needed for other media servers. It is now also creating these files on the DSSU media servers in /usr/openv/netbackup: root@hostname:/usr/openv/netbackup# ll bid* -rw-rw-rw- 1 root root 1984 Dec 15 13:20 bid_file_bladestore_oracle0 -rw-rw-rw- 1 root root 530 Dec 16 13:08 bid_file_bladestore_oracle_1_15240 -rw-rw-rw- 1 root root 1219 Dec 16 13:08 bid_file_bladestore_oracle_2_15240 -rw-rw-rw- 1 root root18 Dec 16 13:08 bid_file_bladestore_oracle_3_15240 -rw-rw-rw- 1 root root 293 Jul 1 2004 bid_file_bladestore_staging_1TB0 -rw-rw-rw- 1 root root 4375 Dec 15 10:04 bid_file_bladestore_unix0 SNIP In the files are a listing of images to get backed up. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] 5.1 MP4
Take a look at the following TechNote for a really good write-up on this subject... http://support.veritas.com/docs/280398 Also this one for 6.0: http://support.veritas.com/docs/280067 -Tim On Dec 16, 2005, at 5:53 PM, Geyer, Gregory wrote: John, GREAT INFORMATION! Now, to investigate whether MAX_STAGING_JOBS is per DSSU or altogether (ie, if DSSU#1 kicks off first and grabs all the jobs, what does DSSU#2 do?) Thanks again, the list rocks. G. -Original Message- From: Nardello, John [mailto:[EMAIL PROTECTED] Sent: Friday, December 16, 2005 4:26 PM To: Geyer, Gregory Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] 5.1 MP4 From the MP4 readme: Etrack Incident = ET313352 Description: Disk staging only submits one duplication job at a time so it was unable to make use of idle tape drives. Additional Notes: Up to four bpduplicate jobs are submitted at a time. The duplication jobs contain images grouped into jobs of 25 Gigabytes. By creating files named MAX_STAGING_JOBS and STAGING_JOB_KB_LIMIT in the NetBackup directory on the master server, these defaults can be adjusted as needed. For the STAGING_JOB_KB_LIMIT, the value is in kilobytes and the default is 26214400 (25 gigabytes). A smaller value causes more jobs to be submitted, but there will only be MAX_STAGING_JOBS running at a time. It's not a bug, it's a feature. I've also seen those bid files present under 5.1 MP3a so it's nothing new anyway. I haven't seen hundreds either so I'm pretty sure NB is cleaning up after itself at some point. - John Nardello Your backups are only as good as your restores. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geyer, Gregory Sent: Friday, December 16, 2005 3:14 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] 5.1 MP4 We've upgraded to 5.1 MP4 and are now experiencing issues with Disk staging. We've got a ticket open but interested to see if anyone else has experience these issues: The disk staging process now automatically takes 4 tape drives per DSSU when going off to tape. This is a problem if you have 6 DSSUs and only 15 tape drives, not to mention those drives are needed for other media servers. It is now also creating these files on the DSSU media servers in /usr/openv/netbackup: root@hostname:/usr/openv/netbackup# ll bid* -rw-rw-rw- 1 root root 1984 Dec 15 13:20 bid_file_bladestore_oracle0 -rw-rw-rw- 1 root root 530 Dec 16 13:08 bid_file_bladestore_oracle_1_15240 -rw-rw-rw- 1 root root 1219 Dec 16 13:08 bid_file_bladestore_oracle_2_15240 -rw-rw-rw- 1 root root18 Dec 16 13:08 bid_file_bladestore_oracle_3_15240 -rw-rw-rw- 1 root root 293 Jul 1 2004 bid_file_bladestore_staging_1TB0 -rw-rw-rw- 1 root root 4375 Dec 15 10:04 bid_file_bladestore_unix0 SNIP In the files are a listing of images to get backed up. ___ 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] netbackup client on windows
Can I manage the netbckup installed on a solaris 880 box through its windows client installed on my desktop? I am running windws XP. Thanks in advance. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
RE: [Veritas-bu] Veritas reporting
Title: Re: [Veritas-bu] Veritas reporting File xport from the activity monitor - save as .txt then open with .xlsxcell - works great for graphs- Dua - I have diags from 1999 doing this From: [EMAIL PROTECTED] on behalf of David RockSent: Thu 12/15/2005 9:36 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: Re: [Veritas-bu] Veritas reporting * Geordie Wardman [EMAIL PROTECTED] [2005-12-15 14:22]: I'm looking for something that sends pretty graphs of all my backups, which ones were successful, and which ones failed. Preferably in a .pdf bar chart or something. That is my main concern. I use bpdbjobs to send a .csv file, and it is fine for me, but not for Sr. Mgt.If you aren't afraid of rolling your own, there are a few open sourceplotting packages that would probably suit your needs; gnuplot,matplotlib are a couple that come to mind off the top.--David Rock[EMAIL PROTECTED]
