Re: [Veritas-bu] Mac OS-X client install - how?
Use the CD - All Unix Clients in the MAC itself and run Vrts_pack.install -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Chris Freemantle Sent: Thursday, March 08, 2007 7:39 AM To: Veritas List Cc: [EMAIL PROTECTED] Subject: [Veritas-bu] Mac OS-X client install - how? Netbackup 5.1 MP4 with the server running under Windows. I need to install a client on an Intel based Macintosh running OS 10.4 Support have said that I need to install a unix server (Solaris in my case) and push the client to the Mac. I don't have a Solaris server licence and the Windows licence (unsurprisingly) doesn't work. I am also told that there is only one Mac client which is used for all versions of the Macintosh. I have been referred to my sales rep for a unix licence key, but it seems a bit extreme to have to use a server just to distribute client software. I find all of this hard to believe. Can anyone confirm this, or give me some ideas of a better way of doing things. thanks -- --- REMEMBER- There is only one certainty about storage systems - they *will* fail ! This includes backup and archiving systems. If you want to be paranoid, make your own backups as well. For FIL computer support issues, please email [EMAIL PROTECTED] rather than individual team members Chris Freemantle Data Manager Wellcome Trust Centre for Neuroimaging Tel. +44 (0)20 7833 7472 reception Tel. +44 (0)20 7833 7496 direct Fax +44 (0)20 7813 1420 Home Page: http://www.fil.ion.ucl.ac.uk ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu This message (including any attachments) is intended for the sole use of the individual to whom it is addressed and may contain confidential information. You are hereby notified that any dissemination, distribution, or duplication of this message by someone other than the intended addressee or their designated agent is strictly prohibited. Information included in this message that does not relate to the specified business of Worknet shall be understood as neither given by nor endorsed by Worknet or its employees. Any cost estimates or estimated quotes included in this message are considered non-binding estimates only and must not be considered final costs unless contained within an official proposal document. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Mac OS-X client install - how?
Hi Chris Normally you don't need to push the client, it can usually be installed directly from a CD or from a file-image, at least this have been possible on all the unix/linux machines I have worked with. The license is another issue, but you should just need a unix client license and not a server license Regards Michael On Thu, 8 Mar 2007 13:38:59 +, Chris Freemantle wrote Netbackup 5.1 MP4 with the server running under Windows. I need to install a client on an Intel based Macintosh running OS 10.4 Support have said that I need to install a unix server (Solaris in my case) and push the client to the Mac. I don't have a Solaris server licence and the Windows licence (unsurprisingly) doesn't work. I am also told that there is only one Mac client which is used for all versions of the Macintosh. I have been referred to my sales rep for a unix licence key, but it seems a bit extreme to have to use a server just to distribute client software. I find all of this hard to believe. Can anyone confirm this, or give me some ideas of a better way of doing things. thanks -- --- REMEMBER- There is only one certainty about storage systems - they *will* fail ! This includes backup and archiving systems. If you want to be paranoid, make your own backups as well. For FIL computer support issues, please email [EMAIL PROTECTED] rather than individual team members Chris Freemantle Data Manager Wellcome Trust Centre for Neuroimaging Tel. +44 (0)20 7833 7472 reception Tel. +44 (0)20 7833 7496 direct Fax +44 (0)20 7813 1420 Home Page: http://www.fil.ion.ucl.ac.uk ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu -- Cybercity Webhosting (http://www.cybercity.dk) ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Virus Scanning and NBU
This is rediculous. Re-read the knowledgebase article. It specifically says: The C2 crash has been found to be caused by Veritas BackupExec or NetBackup VSP.SYS version 1.2 or earlier VSP.SYS is the same anyway, no matter which product its in. And trust me, I'm very well aware that this issue does apply since we could reproduce it at will. -Original Message- From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 1:06 AM To: Trotman, Kevin [CCC-OT_IT]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU But Kevin, the technote refers to VSP for Backup Exec !! Also, look at the date of the Technote http://seer.support.veritas.com/docs/264490.htm Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Trotman, Kevin [CCC-OT_IT] [mailto:[EMAIL PROTECTED] Sent: 07 March 2007 16:14 To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU In spite of your success, there is a knowledgebase article. ;) https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKCdocType=kc; externalId=KB40024sliceId=SAL_PublicdialogID=1057330stateId=0%200%2010559 15 The article deals with a bluescreen issue prevalent in v.8.0i/8.5i with VSP.sys versions through 1.2.0. Version 1.3 of vsp.sys was first shipped in Netbackup 5.1MP4. And, of course, you don't *have* to exclude anything from scan. Like everything else in the IT world, the original question was just a matter of managing risk factors. Kevin -Original Message- From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 12:48 AM To: Trotman, Kevin [CCC-OT_IT]; Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU We run 8.5 and we don't exclude any of the files! During the backup window however, the services are turned off the Windows boxes! I have never seen a problem with 8,5 and NBU 5.1 MP2 and MP5 yet Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Trotman, Kevin [CCC-OT_IT] [mailto:[EMAIL PROTECTED] Sent: 06 March 2007 22:13 To: Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Virus Scanning and NBU You don't mention the NB version, but 8.5 has some issues with client versions below 5.1MP4, so be aware. For windows platform, you should exclude bpinetd.exe. Just to be safe, I would also avoid tar32.exe, tracker.exe, vopied.exe, and vnetd.exe on client platforms. bprd.exe, bpjobd.exe, bptm.exe, oprd.exe, rdevmi.exe, avrd.exe, acsd.exe, and tl*.exe for server platforms. Depending on your robot type, any of then can be open at any given time. Been to LW for a summer program. Very nice. Many, many, many...years ago. ;) Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brooks, Jason Sent: Tuesday, March 06, 2007 10:00 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Virus Scanning and NBU We are preparing to push McAfee 8.5 to our servers and in conjunction with that, I'm compiling a list of NBU processes that McAfee should avoid scanning. What I have so far is as follows: bpcd.exe bpbkar32.exe bpbrm.exe bmrdb.exe bpdbm.exe Others that I've missed? Thanks, Jason Brooks Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2034 fax - (434) 395-2035 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 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
Re: [Veritas-bu] Upgrade/Migrate master server from 5.0/Linux to6.0/Solaris
Catalog format from linux to solaris is compatible, but from 5.x to 6.x is not. Migrate from linux to Solaris maintaining V5.x, then upgrade to 6.x Paul -- -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Rongsheng Fang Sent: March 7, 2007 4:53 PM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Upgrade/Migrate master server from 5.0/Linux to6.0/Solaris Some said that the catalog format was compatible between 5.x and 6.0, and some said it's not. Can somebody confirm this? La version française suit le texte anglais. This email may contain privileged and/or confidential information, and the Bank of Canada does not waive any related rights. Any distribution, use, or copying of this email or the information it contains by other than the intended recipient is unauthorized. If you received this email in error please delete it immediately from your system and notify the sender promptly by email that you have done so. Le présent courriel peut contenir de l'information privilégiée ou confidentielle. La Banque du Canada ne renonce pas aux droits qui s'y rapportent. Toute diffusion, utilisation ou copie de ce courriel ou des renseignements qu'il contient par une personne autre que le ou les destinataires désignés est interdite. Si vous recevez ce courriel par erreur, veuillez le supprimer immédiatement et envoyer sans délai à l'expéditeur un message électronique pour l'aviser que vous avez éliminé de votre ordinateur toute copie du courriel reçu. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Backing up ZFS snapshots
Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/.zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. How do you do that? Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Have you tried a symlink into the snapshot dir? Karl [EMAIL PROTECTED] wrote on 03/08/2007 10:27:42 AM: Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/. zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. How do you do that? Alexander Skwar ___ 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] Log User Activities in NBU GUI?
Is there a way to log user activities in the NBU Windows Admin GUI? Can you also log commands that are run from the command line? Thanks! Jason Ellis Technical Consultant, Data Protection Team IndyMac Bank, La Mirada Datacenter Phone: (714) 520-3414 Mobile: (714) 889-8734 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Upgrade/Migrate master server from 5.0/Linux to6.0/Solaris
Thank you Paul! That's good news. Do you know if the databases (like the ones under /usr/openv/netbackup/db and /usr/openv/volmgr/database) are compatible between Linux and Solaris if they both run NBU 5.x? Thanks, Rongsheng Paul Keating wrote: Catalog format from linux to solaris is compatible, but from 5.x to 6.x is not. Migrate from linux to Solaris maintaining V5.x, then upgrade to 6.x Paul ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
You can control whether the .zfs directory for snapshots is visible or not woth the zfs set snapdir=visible filesyste option. From the zfs manpage: snapdir=hidden | visible Controls whether the .zfs directory is hidden or visi- ble in the root of the file system as discussed in the Snapshots section. The default value is hidden. Eric -Original Message- From: Alexander Skwar [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 10:28 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Backing up ZFS snapshots Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/.zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. How do you do that? Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] 5.1 DST Job Scheduling Bug
Did this just come out yesterday? I could swear when I looked into this last month this wasn't an issue? The document says updated March 7th. http://seer.entsupport.symantec.com/docs/286772.htm -J Known scheduling issues for NetBackup 5.x and prior releases: There is a known scheduling issue with daylight Savings Time with NetBackup 5.x and prior releases. This scheduling issue has been confirmed for the NetBackup 4.5 release. No official testing has been done for any prior releases. This occurs only with the spring forward transition from DST. To be affected by this issue, all of the following conditions must apply to a backup policy: The NetBackup master server must be running a version previous to NetBackup 6.0 *AND* the policy must be configured with a schedule that is frequency-based *AND* the schedule must be configured with a frequency value that is an exact multiple of 24 hours *AND* the schedule must be configured with a backup window that must start between 00:00 and 01:00 on the spring forward day *AND* the schedule must become due to run within its window at some time after 01:59 on the spring forward day If all of the above conditions are met, then this policy/schedule combination will erroneously be considered not due for the duration of the backup window. The next time this backup window opens, this policy/schedule combination will run. This issue is scheduled to be fixed in the NetBackup 5.0 Maintenance Pack 8 (MP8) and the NetBackup 5.1 Maintenance Pack 7 (MP7) releases. These fixes were originally scheduled for the NetBackup 5.0 MP7 and the NetBackup 5.1 MP6 releases. However issues found while testing prevented them from being released as scheduled. A workaround for the scheduling issue is listed below and can be used until these fixes are available. To download these NetBackup 5.x releases, once they become available, visit the Support Web site at: http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143 Symantec Corporation has acknowledged that the above-mentioned issue is present in the NetBackup 4.5 release. Symantec Corporation is committed to product quality and satisfied customers. The NetBackup 4.5 release has reached End Of Life (EOL). There are currently no plans to address this issue by way of a patch or hotfix in the NetBackup 4.5 release at the present time. The workaround listed below can be used until the NetBackup environment can be upgraded to a supported release. To work around the known scheduling issue perform the following steps: 1. Identify any backup schedules with a backup window that begins between 00:00 and 01:00 on a Sunday. This can be done by running the bppllist -allpolicies -U command from the master server and redirecting the output to a file. The resulting file can be scanned for any policies that contain an entry for Sunday under the Daily Windows: section of the policy. 2. Write down the names of any policies and schedules that are affected by this issue. 3. Change the backup window to open at 01:10 or later. This should prevent any scheduling issues from appearing on the spring forward day of daylight savings time. 4. On March 12th, the backup window can be changed back. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Mike L. Varney schrieb: NetBackup would happily backup the symlink as if it were an individual file. It would not follow the link. Exactly. What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Alexander Skwar -- If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Johnson, Eric schrieb: You can control whether the .zfs directory for snapshots is visible or not woth the zfs set snapdir=visible filesyste option. I know - but how does that solve the problem? If .zfs were visible, wouldn't this make even more problems? Suppose I'd backup /pool, this would cause the original /pool/Teamcenter and also the snapshot underneath /pool/Teamcenter/.zfs/snapshot/backup to be stored on tape. That's absolutely not what I want - I do not want to store the (more or less) same content twice - I don't work at Imation, or any other tape vendor, you know ;) Alexander Skwar -- If I want your opinion, I'll ask you to fill out the necessary form. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
I would think you could specify the hidden directory on the command line to back up the snapshot directory. It wouldnt be the matter of the backup client not getting access to the directory; the hidden directory just doesn't show up when the client is iterating thru the filesystem. -- M Alexander Skwar [EMAIL PROTECTED] Sent by: [EMAIL PROTECTED] 03/08/2007 04:54 PM Please respond to veritas-bu@mailman.eng.auburn.edu To cc veritas-bu@mailman.eng.auburn.edu Subject Re: [Veritas-bu] Backing up ZFS snapshots Mike L. Varney schrieb: NetBackup would happily backup the symlink as if it were an individual file. It would not follow the link. Exactly. What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Alexander Skwar -- If you remove stricture from a large Perl program currently, you're just installing delayed bugs, whereas with this feature, you're installing an instant bug that's easily fixed. Whoopee. -- Larry Wall in [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] Backing up ZFS snapshots
What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Since the client knows the snapshot involved, it could give the correct name to the process (/fs/.zfs/snapshot/name). Also, you can rename snapshots. A script could make sure that the most recent snaphot is always called 'current' or something. You place that name on the backup list of the profile. Then when it's time to rotate, the script could rename 'current' to a timestamp and create a new 'current'. Or maybe rotate like netapp 'daily.0' - 'daily.1' etc... -- Darren Dunham [EMAIL PROTECTED] Senior Technical Consultant TAOShttp://www.taos.com/ Got some Dr Pepper? San Francisco, CA bay area This line left intentionally blank to confuse you. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Bprecover
Target master server name is the same as the restore server name Solaris 9 This is what I get using the GUI to recover from a HOT backup Images seem to have recovered successfully and then Starts to restore the database and I get ... 6:09:59 (36.001) INF - Beginning restore from server calmp1 to client calmp1. 16:10:00 (36.001) /mp1_data/staging/EMM_DATA.db 16:10:02 (36.001) /mp1_data/staging/EMM_INDEX.db 16:10:04 (36.001) /mp1_data/staging/NBDB.db 16:10:04 (36.001) /mp1_data/staging/NBDB.log.1 16:10:04 (36.001) /mp1_data/staging/databases.conf 16:10:04 (36.001) /mp1_data/staging/server.conf 16:10:04 (36.001) /mp1_data/staging/vxdbms.conf 16:10:04 (36.001) INF - TAR EXITING WITH STATUS = 0 16:10:04 (36.001) INF - TAR RESTORED 7 OF 7 FILES SUCCESSFULLY 16:10:04 (36.001) INF - TAR KEPT 0 EXISTING FILES 16:10:04 (36.001) INF - TAR PARTIALLY RESTORED 0 FILES 16:10:05 (36.001) Status of restore from image created Thu Mar 08 09:59:35 2007 = the requested operation was successfully completed 16:10:07 INF - Server status = 0 16:10:09 (36.xxx) INF - Status = the requested operation was successfully completed. 16:10:11 INF - Database recovery started 16:10:11 INF - Recovery not successfully completed 16:10:11 ERR - Failed to recover NBDB on calmp1 (13) 16:10:16 INF - attempting to freeze media used in recovery Any ideas .how to fix seems like it has restored the Eustace Fernandes Technical Support mailto:[EMAIL PROTECTED] voice (403) 237-1534 ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
On 3/8/2007 10:27 AM, Alexander Skwar wrote: Hello. On one of the servers which are backed up with NBU 6.0 MP4, we're using Solaris 10 and also ZFS. To keep the backup window as short as possible, I'm creating ZFS snapshots just before the backup policy gets run. I do that manually with a script, eg. like this: zfs snapshot pool/[EMAIL PROTECTED]. This creates a snapshot, which is accessible over /pool/Teamcenter/.zfs/snapshot/backup. The .zfs directory is completely invisible: [EMAIL PROTECTED] /opt $ sudo zfs snapshot pool/[EMAIL PROTECTED] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/ total 116 drwxr-xr-x 22 root root 22 Feb 27 14:33 . drwxr-xr-x 5 root sys5 Mar 8 17:15 .. drwxr-xr-x 2 root root 12 Nov 14 15:51 TT_DB drwxrwxr-x 21 dev1 pdmusers 62 Jan 11 20:11 dev1 [...] [EMAIL PROTECTED] /opt $ ls -la /pool/Teamcenter/.zfs total 3 dr-xr-xr-x 3 root root 3 Jan 12 18:50 . drwxr-xr-x 22 root root 22 Feb 27 14:33 .. dr-xr-xr-x 2 root root 2 Jan 12 18:50 snapshot How do you guys actually backup ZFS snapshots? I don't really want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup to the Backup Selections of a policy, as this would mean, that the Backup Selections would have to be updated, when a new zfs is created. I don't like this. I haven't used zfs, but what happens if the policy specifies /pool/*/.zfs ? Enable cross mount-points and does the right thing happen? Try a bpdir from the master using that directory spec and see if your files are listed. .../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 DST Job Scheduling Bug
Just as an FYI... It's my understanding that this scheduling problem is NOT a result of the DST changes that start this year. This risk of a missed backup job existed last spring, and the spring before that, and the spring before that... So it's nice that it's finally going to be fixed. (even if it's not in time for this sunday night...) HTH rob On Mar 8, 2007, at 1:52 PM, Martin, Jonathan ((Contractor)) wrote: Did this just come out yesterday? I could swear when I looked into this last month this wasn't an issue? The document says updated March 7th. http://seer.entsupport.symantec.com/docs/286772.htm -J Known scheduling issues for NetBackup 5.x and prior releases: There is a known scheduling issue with daylight Savings Time with NetBackup 5.x and prior releases. This scheduling issue has been confirmed for the NetBackup 4.5 release. No official testing has been done for any prior releases. This occurs only with the spring forward transition from DST. To be affected by this issue, all of the following conditions must apply to a backup policy: The NetBackup master server must be running a version previous to NetBackup 6.0 *AND* the policy must be configured with a schedule that is frequency-based *AND* the schedule must be configured with a frequency value that is an exact multiple of 24 hours *AND* the schedule must be configured with a backup window that must start between 00:00 and 01:00 on the spring forward day *AND* the schedule must become due to run within its window at some time after 01:59 on the spring forward day If all of the above conditions are met, then this policy/schedule combination will erroneously be considered not due for the duration of the backup window. The next time this backup window opens, this policy/schedule combination will run. This issue is scheduled to be fixed in the NetBackup 5.0 Maintenance Pack 8 (MP8) and the NetBackup 5.1 Maintenance Pack 7 (MP7) releases. These fixes were originally scheduled for the NetBackup 5.0 MP7 and the NetBackup 5.1 MP6 releases. However issues found while testing prevented them from being released as scheduled. A workaround for the scheduling issue is listed below and can be used until these fixes are available. To download these NetBackup 5.x releases, once they become available, visit the Support Web site at: http://www.symantec.com/enterprise/support/downloads.jsp?pid=15143 Symantec Corporation has acknowledged that the above-mentioned issue is present in the NetBackup 4.5 release. Symantec Corporation is committed to product quality and satisfied customers. The NetBackup 4.5 release has reached End Of Life (EOL). There are currently no plans to address this issue by way of a patch or hotfix in the NetBackup 4.5 release at the present time. The workaround listed below can be used until the NetBackup environment can be upgraded to a supported release. To work around the known scheduling issue perform the following steps: 1. Identify any backup schedules with a backup window that begins between 00:00 and 01:00 on a Sunday. This can be done by running the bppllist -allpolicies -U command from the master server and redirecting the output to a file. The resulting file can be scanned for any policies that contain an entry for Sunday under the Daily Windows: section of the policy. 2. Write down the names of any policies and schedules that are affected by this issue. 3. Change the backup window to open at 01:10 or later. This should prevent any scheduling issues from appearing on the spring forward day of daylight savings time. 4. On March 12th, the backup window can be changed back. ___ 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] Virus Scanning and NBU
Well its not re-produced here :-) And that's good for us ... Bad for you :-) Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Trotman, Kevin [CCC-OT_IT] [mailto:[EMAIL PROTECTED] Sent: 08 March 2007 15:57 To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU This is rediculous. Re-read the knowledgebase article. It specifically says: The C2 crash has been found to be caused by Veritas BackupExec or NetBackup VSP.SYS version 1.2 or earlier VSP.SYS is the same anyway, no matter which product its in. And trust me, I'm very well aware that this issue does apply since we could reproduce it at will. -Original Message- From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Thursday, March 08, 2007 1:06 AM To: Trotman, Kevin [CCC-OT_IT]; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU But Kevin, the technote refers to VSP for Backup Exec !! Also, look at the date of the Technote http://seer.support.veritas.com/docs/264490.htm Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Trotman, Kevin [CCC-OT_IT] [mailto:[EMAIL PROTECTED] Sent: 07 March 2007 16:14 To: WEAVER, Simon (external); veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU In spite of your success, there is a knowledgebase article. ;) https://knowledge.mcafee.com/SupportSite/search.do?cmd=displayKCdocType=kc; externalId=KB40024sliceId=SAL_PublicdialogID=1057330stateId=0%200%2010559 15 The article deals with a bluescreen issue prevalent in v.8.0i/8.5i with VSP.sys versions through 1.2.0. Version 1.3 of vsp.sys was first shipped in Netbackup 5.1MP4. And, of course, you don't *have* to exclude anything from scan. Like everything else in the IT world, the original question was just a matter of managing risk factors. Kevin -Original Message- From: WEAVER, Simon (external) [mailto:[EMAIL PROTECTED] Sent: Wednesday, March 07, 2007 12:48 AM To: Trotman, Kevin [CCC-OT_IT]; Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Virus Scanning and NBU We run 8.5 and we don't exclude any of the files! During the backup window however, the services are turned off the Windows boxes! I have never seen a problem with 8,5 and NBU 5.1 MP2 and MP5 yet Regards Simon Weaver 3rd Line Technical Support Windows Domain Administrator EADS Astrium Limited, B23AA IM (DCS) Anchorage Road, Portsmouth, PO3 5PU Email: [EMAIL PROTECTED] -Original Message- From: Trotman, Kevin [CCC-OT_IT] [mailto:[EMAIL PROTECTED] Sent: 06 March 2007 22:13 To: Brooks, Jason; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Virus Scanning and NBU You don't mention the NB version, but 8.5 has some issues with client versions below 5.1MP4, so be aware. For windows platform, you should exclude bpinetd.exe. Just to be safe, I would also avoid tar32.exe, tracker.exe, vopied.exe, and vnetd.exe on client platforms. bprd.exe, bpjobd.exe, bptm.exe, oprd.exe, rdevmi.exe, avrd.exe, acsd.exe, and tl*.exe for server platforms. Depending on your robot type, any of then can be open at any given time. Been to LW for a summer program. Very nice. Many, many, many...years ago. ;) Kevin -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Brooks, Jason Sent: Tuesday, March 06, 2007 10:00 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Virus Scanning and NBU We are preparing to push McAfee 8.5 to our servers and in conjunction with that, I'm compiling a list of NBU processes that McAfee should avoid scanning. What I have so far is as follows: bpcd.exe bpbkar32.exe bpbrm.exe bmrdb.exe bpdbm.exe Others that I've missed? Thanks, Jason Brooks Jason Brooks Computer Systems Engineer IITS - Longwood University voice - (434) 395-2034 fax - (434) 395-2035 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 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.
[Veritas-bu] Alternative Media Manager restore
Hi all, I have here in my backup infra one master server and 6 media managers. If I have a situation when I backed up a server in a robot that is attached to one media manager and I need to restore some files but all the tapes in this robot are busy. What is the steps that I need to follow to put the required tape or tapes in another robot, of the same infra, and inform Netbackup to use it for this restore? Thanks, Julio ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Backing up ZFS snapshots
Darren Dunham [EMAIL PROTECTED]: What if you started the backup as a User Backup from the client at the end of your script which created the snapshot? Hm, interesting idea. What should the client then specify to backup? I mean, which directory? Since the client knows the snapshot involved, it could give the correct name to the process (/fs/.zfs/snapshot/name). Okay. But what would I have to add to the Backup Selections properties of the Policy? Also, you can rename snapshots. A script could make sure that the most recent snaphot is always called 'current' or something. The snapshot currently is called backup. So, that's already a static name. You place that name on the backup list of the profile. Nah, that's exactly the route, that I do NOT want to go. To quote my OP: | I don't really | want to go the route of having to add /pool/Teamcenter/.zfs/snapshot/backup | to the Backup Selections of a policy, as this would mean, that | the Backup Selections would have to be updated, when a new | zfs is created. I don't like this. Or did I misunderstand you? Thanks, Alexander Skwar ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
