[Veritas-bu] Restoring from Multiplexed Backup
Curtis, You mean to say if i start 5 restore all 5 of them will start writing at the same time. +-- |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] Restoring from Multiplexed Backup
That is exactly what I'm saying -- even if they're multiplexed together. Curtis Preston | VP Data Protection GlassHouse Technologies, Inc. T: +1 760 710 2004 | C: +1 760 419 5838 | F: F: +1 760 710 2009 [EMAIL PROTECTED] | www.glasshouse.com Infrastructure :: Optimized -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of NBU Sent: Sunday, August 03, 2008 10:55 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Restoring from Multiplexed Backup Curtis, You mean to say if i start 5 restore all 5 of them will start writing at the same time. +-- |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 and any files transmitted with it are confidential and intended solely for the use of the individual or entity to whom they are addressed. If you have received this email in error please notify the system manager. This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put this info out there in case anyone else is moving towards ZFS. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu National Australia Bank Ltd - ABN 12 004 044 937 This email may contain confidential information. If you are not the intended recipient, please immediately notify us at [EMAIL PROTECTED] or by replying to the sender, and then destroy all copies of this email. Except where this email indicates otherwise, views expressed in this email are those of the sender and not of National Australia Bank Ltd. Advice in this email does not take account of your objectives, financial situation, or needs. It is important for you to consider these matters and, if the e-mail refers to a product(s), you should read the
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
In general exclude lists work for directories as well as files so I'm not sure why you stated they don't work for the former. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Glazerman Sent: Monday, August 04, 2008 8:53 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put this info out there in case anyone else is moving towards ZFS. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential, are intended solely for the use of the addressee, and may be legally privileged. If you have received this email in error please notify the sender immediately, and do not copy or forward it. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu National Australia Bank Ltd - ABN 12 004 044 937 This email may contain confidential information. If you are not the intended recipient, please immediately notify us at [EMAIL PROTECTED] or by replying to the sender,
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
Jeff, I didn't say that Exclude lists don't work for directories. I said that Include lists don't work for directories. We have Exclude lists in place on each server so that the filesystem backups don't back up archive and redo logs which are backed up separately by RMAN. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 8:46 AM To: Mark Glazerman; [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks In general exclude lists work for directories as well as files so I'm not sure why you stated they don't work for the former. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Glazerman Sent: Monday, August 04, 2008 8:53 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put this info out there in case anyone else is moving towards ZFS. Mark Glazerman Enterprise Storage Administrator Spartech Corporation Desk: 314-889-8282 Fax: 314-854-8282 Cell: 618-520-3401 [EMAIL PROTECTED] mailto:[EMAIL PROTECTED] http://www.spartech.com http://www.spartech.com/ P please don't print this e-mail unless you really need to This e-mail and any files transmitted with it are confidential,
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
My apologies. You mentioned exclude lists multiple times so I guess my brain interpreted the final sentence as exclude rather than include. From: Mark Glazerman [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 9:53 AM To: Jeff Lightner; [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Jeff, I didn't say that Exclude lists don't work for directories. I said that Include lists don't work for directories. We have Exclude lists in place on each server so that the filesystem backups don't back up archive and redo logs which are backed up separately by RMAN. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: Jeff Lightner [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 8:46 AM To: Mark Glazerman; [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks In general exclude lists work for directories as well as files so I'm not sure why you stated they don't work for the former. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Mark Glazerman Sent: Monday, August 04, 2008 8:53 AM To: [EMAIL PROTECTED] Cc: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Domink, The problem with exclude lists is that if you start having a different exclude list for each server, it quickly becomes a nightmare keeping those lists current and up to date. Also, because ALL_LOCAL_DRIVES doesn't recognize the ZFS filesystems, the only way to have them included was to start listing the mountpoints in the backup selections tab of the policy. We tried looking at include lists also but those only work for individual files, not whole directories. This brought us to our workaround where we had to specify every possible zfs mountpoint in the backup policy and then make sure that each of those directories existed on every server (to avoid the 71's). That has worked like a charm over the weekend so will have to do until there is a release of NBU which includes ZFS under the ALL_LOCAL_DRIVES backup selection Thanks Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Monday, August 04, 2008 1:17 AM To: Mark Glazerman Subject: Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks You couldn't use exclude lists ??? Mark Glazerman [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 01/08/2008 11:34 PM To Veritas-bu@mailman.eng.auburn.edu cc Subject [Veritas-bu] ZFS Filesystem Backups - Tips and tricks Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. We have a number of Sun boxes which have various test and development oracle instances which are housed inside ZFS file systems. We blew away one of these test instances the other day (after doing a full OS backup and the required RMAN backups) but when we went to restore the data from the ZFS filesystems, NBU didn't have anything under the uppermost directory. A quick check of other systems with ZFS showed the same issue.We spent the better part of 2 days playing around with the include_list's and exclude_list's but nothing worked. In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. This fix was also confirmed by Symantec support who were also happy to tell me that ZFS isn't officially supported by NBU yet. This on its own should work great if you have a single policy backing up a single server with all it's ZFS under the same parent directory. However, if like us, you have a backup policy which backs up multiple servers, each with their own uniquely named ZFS file systems, you need to get a bit creative. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. Now when the policy runs, it sees each directory (as listed in the backup selection) on each server and doesn't moan about anything. Perhaps not the neatest of fixes but it works. Apologies for the wordy post, just thought I'd put
[Veritas-bu] Removing 6.5.2 and going back to 6.5.1
Symantec Tech Support says that since there were changes in the database when upgrading to 6.5.2, I will need to restore the catalog from 6.5.1. +-- |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] ZFS Filesystem Backups - Tips and tricks
Incase anyone is considering implementing any ZFS in their environment which they want to back up using NetBackup we found out yesterday that ALL_LOCAL_DRIVES as the backup selection does NOT cover ZFS filesystems. [...] In order to backup ZFS file systems you must explicitly add the ZFS directories into the backup selections of the backup policy. Catching up on mail; apologies if these bits have already been addressed. As others have pointed out, 6.5.2 has the fix for A_L_D and ZFS. I got an engineering binary for bpmount (depends on the Solaris version, IIRC) for your clients that works just fine. You may need to blow away the STREAMS file to deal with auto-discovered streaming mode. The policy in question backs up 15 Sun boxes with a total of 6 differently named ZFS file systems spread amongst them. If you just list the file systems in the backup selections, NBU looks for each of those different filesystems on each server and spits out an error code 71 (None of the files in the file list exist) for every directory it can't find. The only way we could work out to avoid these errors (and there were a lot of them) was to create every missing directory on every server and then touch a tiny file inside each of these directories. [...] Others pointed out that turning off allow_multiple_data_streams avoids a stat 71, but you need simultaneous backups rather than going through all the filesystems on a client sequentially. Been there, done that. This may strike you as a kludge, but for situations where A_L_D isn't what I need, but a single policy has to handle servers with different selection list entries, the simplest way is to put all the selections in the policy and frame each with NEW_SERVER and a file guaranteed to be on the host (/etc/hosts or c:/windows/system32/drivers/etc/hosts). Allow multiple streams and you're good without having to create anything on the clients. Now, adding the dummy file to a stream works just fine, but if you have to manually edit hundreds of mount points and you're going to get that EEB in a day or two, it may be an option to just keep A_L_D and let the stat 71s happen. Depending on your procedures, of course, unless your environment has chronic 71 problems (how rare is _that_?), significant numbers of failure statuses which need investigation/remediation nightly or you have automated systems that generate unpleasantness for every non-success status, Operations can filter the 71s, be sure they are from these systems and ignore them for a day or so. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Removing 6.5.2 and going back to 6.5.1
What? Restore the catalog just to back out a patch? That's crazy! The 6.0 releases can undo database changes when backing out a patch. Either your support rep is bonkers or Symantec is being lazy with their patch uninstall procedure. ...becoming more and more disillusioned with Symantec and NetBackup Jack L. Forester, Jr. UNIX Systems Administrator, Stf Lockheed Martin Information Technology (304) 625-3946 -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of mconner1201 Sent: Monday, August 04, 2008 10:50 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] Removing 6.5.2 and going back to 6.5.1 Symantec Tech Support says that since there were changes in the database when upgrading to 6.5.2, I will need to restore the catalog from 6.5.1. +-- |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] FW: no jobs on activity monitor after hardware migration
Yes, this happened to us as well. Job history is probably not backed up in the catalog backup. Jack L. Forester, Jr. UNIX Systems Administrator, Stf Lockheed Martin Information Technology (304) 625-3946 From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Asiye Yigit Sent: Saturday, August 02, 2008 7:29 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] FW: no jobs on activity monitor after hardware migration Hi All, I have a question. We have migratede netbackup master server to the new box. After migration, in the new master activity monitor, there are no jobs related past. It starts from the scratch. Is it normal? ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Bpschedreq in 6.5
I would be interested as well. Please send it. Thank you On Thu, Jul 31, 2008 at 3:59 PM, schmaustech [EMAIL PROTECTED] wrote: I wrote a Perl scriot that allows you to determine which policies and schedules will kick off on a given day. It also can display a histogram of how many jobs per hour are kicked off. Let me know if interested. +-- |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] Status 23: socket read failed _ on 6.5.2 W2K3 Master
Check the client attributes settings on the Master server for this particular client. You would need to see if that something to do with the snapshoting either VSP or VSS if it is Windows 2003 client. On Thu, Jul 31, 2008 at 9:47 AM, Eagle, Kent [EMAIL PROTECTED]wrote: Recently upgraded our test environment Master server from 6.0MP5 to 6.5MP2 Now receiving intermittent errors. From Job Details: Status 23: socket read failed 7/29/2008 6:07:51 PM - Info bpdbm(pid=2812) deleted 1 expired records, compressed 0, tir removed 0, deleted 0 expired copies socket read failed(23) From All Log Entries report: 7/29/2008 6:07:52 PM Media ServerXYZ ClientXYZ Error 0 GeneralCould not build host list: database system error Nothing interesting in the .evt logs during the affected timeframe. Any ideas? Thank you, Kent Eagle [EMAIL PROTECTED] Visit our website at www.wilmingtontrust.com Investment products are not insured by the FDIC or any other governmental agency, are not deposits of or other obligations of or guaranteed by Wilmington Trust or any other bank or entity, and are subject to risks, including a possible loss of the principal amount invested. This e-mail and any files transmitted with it may contain confidential and/or proprietary information. It is intended solely for the use of the individual or entity who is the intended recipient. Unauthorized use of this information is prohibited. If you have received this in error, please contact the sender by replying to this message and delete this material from any system it may be on. ___ 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] duplication failed (failed accessing daemon lock file(158)
Hello all, During a bpduplicate command i get the following error message; 4-8-2008 13:03:02 - Error bpduplicate(pid=5976) Could not lock backupid: .._1217834851, copy 3; duplicate of image in progress 4-8-2008 13:03:02 - Error bpduplicate(pid=5976) Duplicate of backup id .._1217834851 failed, failed accessing daemon lock file (158). Anyone an idea what can have caused this error? Thanks _ Your PC, mobile phone, and online services work together like never before. http://clk.atdmt.com/MRT/go/108587394/direct/01/___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ZFS Filesystem Backups - Tips and tricks
I didn't say that Exclude lists don't work for directories. I said that Include lists don't work for directories. [...] No. Include lists work exactly the same way as exclude lists; directories and/or files are valid. Reference the Veritas NetBackup System Administrator's Guide, Vol I for syntax rules. This misunderstanding might be attributed to way the *_list rules are applied. Note that an exclude list can only exclude items that are in the policy's selection list (obviously). And that an include list can only include items that were excluded by an exclude list. (Perhaps that's the logic in Symantec renaming the include list to exceptions to the exclude list.) Stated another way, the selection list defines the universe of data to be backed up. Excludes subtract from the universe. Includes reinstate only items from the set of excluded items. You can see the processing steps in the client's bpbkar log. Logging level 0 will show each directive as it is encountered; level 1 and higher will show the process more clearly via the PrintFile lines. From that I can infer the reason the rules are as they are (above): bpbkar processes the selection list and only mentions exclude_list items when they match its current path; include_list entries are only mentioned when they match the current exclude_list item. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] ZFS backup problems
I have two servers that I've configured with ZFS filesystems but I haven't had a chance to test them with NetBackup yet. Do ZFS filesystems that are mounted via the /etc/vfstab versus the ZFS mounting facility file back up properly with the ALL_LOCAL_DRIVES directive? Jamie ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] ZFS backup problems
I'm sure someone will correct me if I'm wrong but I believe that traditionally NBU uses the mnttab to check for mounted filesystems. We tried tricking the vfstab to see the filesystems but didn't have any luck. All of our filesystems are mounted via the built in ZFS process (whatever that is called) and as we found out, this was not enough for NBU to see them and back them up. However, from replies to my earlier posts, it sounds like if you are running a version of NBU older than 6.5 you might still be ok with using ALL_LOCAL_DRIVES. Mark Glazerman Desk: 314-889-8282 Cell: 618-520-3401 P please don't print this e-mail unless you really need to From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of JAJA (Jamie Jamison) Sent: Monday, August 04, 2008 7:04 PM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] ZFS backup problems I have two servers that I've configured with ZFS filesystems but I haven't had a chance to test them with NetBackup yet. Do ZFS filesystems that are mounted via the /etc/vfstab versus the ZFS mounting facility file back up properly with the ALL_LOCAL_DRIVES directive? Jamie ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
