Re: [Veritas-bu] MS-Sql server
Hi Kevin If you use INSTANCE $ALL and DATABASE $ALL NetBackup will automatically try and backup every DB and Instance on the server. You can either logon to the server as has been described and use the SQL client GUI to check the client progress log. An easier method is to just remotely look at the log file generated which is used to display the job status in the sql gui. You can just connect to the server $ share as opposed to having to log on and then launch the client gui The path would be /install_path\veritas\netbackup\logs\user_ops\mssql\logs There will be a file for each job in that folder with the bottom of the file summarising the failures and successes. BTW - Are your SQL clients on 6.5.6 too? Pre 6.5.6 there was a bug in the sql agent which caused some databases to be skipped from backup and not reported on when using $ALL Regards, Tal From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon (external) Sent: 24 September 2010 07:13 To: Baumann, Kevin; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] MS-Sql server Hi Kevin There is normally a Parent Job that kicks off. After this, there should be child jobs for each Database. Was the .bch file configured with the ALL$ command? Also, to clarify, goto the Backup, Archive, Restore tool, specify the client machine and the policy type, in your case MS-SQL-Server. You would run this BAR tool on the Master Server (assuming its a client). Hope this helps Simon From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Baumann, Kevin Sent: Thursday, September 23, 2010 7:41 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] MS-Sql server All, My Windows team has asked me if I can see what databases have been backed up on a particular Windows server. It is running MS-SQL, and when the master server kicks off the backup it looks at a .bch script on that server. It looks to me like the backups work, but I cannot find a way to say what actual databases were backed up. Is there an easy way to do that? And can I assume that if I get a status 0, that all the databases in the .bch file get backed up? Linux master/media server, 6.5.6. Client is Windows 2003 server (r2) running MS-Sql server. Thanks. -Kevin This email (including any attachments) may contain confidential and/or privileged information or information otherwise protected from disclosure. If you are not the intended recipient, please notify the sender immediately, do not copy this message or any attachments and do not use it for any purpose or disclose its content to any person, but delete this message and any attachments from your system. Astrium disclaims any and all liability if this email transmission was virus corrupted, altered or falsified. -o- Astrium Limited, Registered in England and Wales No. 2449259 Registered Office: Gunnels Wood Road, Stevenage, Hertfordshire, SG1 2AS, England ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Device Recognition in RHEL5/NBU7
Did you by any chance zone the devices into multiple HBA ports in the new config but not the old? Perhaps you had powerpath, DMP or some kind of multipath software installed before? By the way - there shouldn't be any problems with seeing multiple devices and NB will only use the ones configured and it shouldn't actually go an configure 16 robots and 400 drives. The device config wizard will know that some are the same devices - atleast it does in my environment. Have you let the device config wizard finish - what does it actually configure after detecting all the devices? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Heathe Yeakley Sent: 23 September 2010 15:39 To: NetBackup Mailing List Subject: Re: [Veritas-bu] Device Recognition in RHEL5/NBU7 To clarify my question: I currently have a live NetBackup environment where the master server is a Dell 2950 and I have two media servers that are solaris boxes running RHEL 4. My department wants to decommission the older boxes and move NetBackup to newer boxes, and I wanted to upgrade to 7.0 anyway, so I decided to kill two birds with one stone and build 1 new master and 2 new media, install NBU 7 on the new environment and then zone my existing libraries into the new environment and then point all the servers I'm backing up to the new environment. On my live NetBackup environment (the RHEL4 one), when I go into the NBU hardware configuration wizard and scan for devices, the wizard comes back and says it sees 3 libraries and 92 drives (which is the number I expect to see). When I shut down my live environment and bring up the NBU 7 environment and run the hardware wizard, it sees like 16 robots and 400 drives. I'm trying to figure out why my NBU 6.0/RHEL4 environment is able to see one device file per robot/tape drive, but my NBU 7/RHEL5 environment thinks each path is 1 device. I'm not sure where to begin researching this issue. I'm in the process of skimming through the NBU 7 device configuration manual, the HBA documentation and Red Hat's storage documentation. Any light that can be shed on this will be greatly appreciated. - HKY ___ 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] Device Recognition in RHEL5/NBU7
As far as the zoning in the old environment, I've gone over both with a fine tooth comb and it looks like I've zoned both environments exactly alike. As far as multipath software, I have device mapper multipath configured on both environments. As far as letting the wizard finish, I decided to try that and about halfway through the wizard, NetBackup realized it's all the same devices and presented me with 3 robots and 92 drives (the correct number). I'm still confused why my 6.0 environment sees 3 robots and 92 drives after the first scan on the 2nd page of the Hardware configuration wizard whereas my 7.0 environment has to go about halfway through before it sees all the devices as 3 robots and 92 drives But hey, at least it's working now. - HKY On Fri, Sep 24, 2010 at 5:39 AM, Shekel Tal tal.she...@uk.fujitsu.com wrote: Did you by any chance zone the devices into multiple HBA ports in the new config but not the old? Perhaps you had powerpath, DMP or some kind of multipath software installed before? By the way - there shouldn't be any problems with seeing multiple devices and NB will only use the ones configured and it shouldn't actually go an configure 16 robots and 400 drives. The device config wizard will know that some are the same devices - atleast it does in my environment. Have you let the device config wizard finish - what does it actually configure after detecting all the devices? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Heathe Yeakley Sent: 23 September 2010 15:39 To: NetBackup Mailing List Subject: Re: [Veritas-bu] Device Recognition in RHEL5/NBU7 To clarify my question: I currently have a live NetBackup environment where the master server is a Dell 2950 and I have two media servers that are solaris boxes running RHEL 4. My department wants to decommission the older boxes and move NetBackup to newer boxes, and I wanted to upgrade to 7.0 anyway, so I decided to kill two birds with one stone and build 1 new master and 2 new media, install NBU 7 on the new environment and then zone my existing libraries into the new environment and then point all the servers I'm backing up to the new environment. On my live NetBackup environment (the RHEL4 one), when I go into the NBU hardware configuration wizard and scan for devices, the wizard comes back and says it sees 3 libraries and 92 drives (which is the number I expect to see). When I shut down my live environment and bring up the NBU 7 environment and run the hardware wizard, it sees like 16 robots and 400 drives. I'm trying to figure out why my NBU 6.0/RHEL4 environment is able to see one device file per robot/tape drive, but my NBU 7/RHEL5 environment thinks each path is 1 device. I'm not sure where to begin researching this issue. I'm in the process of skimming through the NBU 7 device configuration manual, the HBA documentation and Red Hat's storage documentation. Any light that can be shed on this will be greatly appreciated. - HKY ___ Veritas-bu maillist - veritas...@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] Real World NBU Buffer settings Win2k3
The 64k limit was due to a tcp/ip stack limitation I have always found larger buffers (256k) generally provide the best performance. Only if you had lots of small files would I recommend anything less Flashbackup will definitely improve your performance as the data will not need to be uncompressed prior to passed to the backup device. The only factor to consider is that flashbackup will also backup the blocks on the drive which are empty - so you backup the entire volume. I am going to guess you wont see much performance going to disk as you issue is probably not at the backup target as you have a collection of LTO4 drives. A single LTO4 should be able to backup that entire volume in 6 hours easy - even if the SAN is running at 2GB. Can you share any info about your disk config? Is it SAN or internal storage? How many disks are in the config? If you run Windows perfmon how are your disk queues looking? Also - how many split I/O's are you getting? - ensuring proper file system / volume partition can make a decent difference Do you have bad disk fragmentation? All things that can make a difference . . . . From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Nic Solomons Sent: 16 September 2010 14:44 To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Real World NBU Buffer settings Win2k3 Also worth noting that for 2003+, if you don't have specific RTOs for individual files, you can do volume based backups with your standard licensing (but no individual file restore). http://seer.entsupport.symantec.com/docs/275912.htm Which should give you the same performance boost as flash backup. Make sure you use VSS though - not VSP (why they left the screenshot like that, no idea). Cheers, Nic From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Martin, Jonathan Sent: 16 September 2010 14:23 To: WEAVER, Simon (external); William Brown; veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Real World NBU Buffer settings Win2k3 Windows is a piece of cake. Install the client. Select Policy Type: Flashbackup-Windows Setup Selection List: \\.\R file:///\\.\R : (change drive letter as required) Run Policy Enjoy monumentally faster backups (on compressed volumes) You cannot backup the system drive (C:) or System State with Flashbackup. I normally run these in a 2nd OS policy. Be sure to test a restore. You can do entire volume restores, which are just as fast as backups. Or, you can restore individual files. -Jonathan From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of WEAVER, Simon (external) Sent: 15 September 2010 19:00 To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Real World NBU Buffer settings Win2k3 Hi All Anyone got any real world experience on buffer settings: scenarion: Win2k3 San Media, connected to 2GB Fabric attached 8 LTO4 Drives. Due to drive availability, Multiplexing onto one drive. Main problem: One volume (1,7tb in size) takes over 4 days to fully complete. Got the Tuning Guide and Technote 244602, but I tried some settings, only to find the backup would not even mount tape correctly. So back to no settings at the mo. Volume are generic files/folders, mixture of large and small sizes. But 1.7TB's in my view should be done quicker. Also Data is compressed. Regards Simon The information contained in this e-mail and its attachments is confidential. It is intended only for the named address(es) and may not be disclosed to anyone else without Attenda's consent. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Device Recognition in RHEL5/NBU7
I know that the version I am on 6.5.5 see's the multiple paths you have described. It could just be a change in behaviour from within NB? Could be worth asking Symantec support the question . . . . -Original Message- From: Heathe Yeakley [mailto:hkyeak...@gmail.com] Sent: 24 September 2010 14:08 To: Shekel Tal Cc: NetBackup Mailing List Subject: Re: [Veritas-bu] Device Recognition in RHEL5/NBU7 As far as the zoning in the old environment, I've gone over both with a fine tooth comb and it looks like I've zoned both environments exactly alike. As far as multipath software, I have device mapper multipath configured on both environments. As far as letting the wizard finish, I decided to try that and about halfway through the wizard, NetBackup realized it's all the same devices and presented me with 3 robots and 92 drives (the correct number). I'm still confused why my 6.0 environment sees 3 robots and 92 drives after the first scan on the 2nd page of the Hardware configuration wizard whereas my 7.0 environment has to go about halfway through before it sees all the devices as 3 robots and 92 drives But hey, at least it's working now. - HKY On Fri, Sep 24, 2010 at 5:39 AM, Shekel Tal tal.she...@uk.fujitsu.com wrote: Did you by any chance zone the devices into multiple HBA ports in the new config but not the old? Perhaps you had powerpath, DMP or some kind of multipath software installed before? By the way - there shouldn't be any problems with seeing multiple devices and NB will only use the ones configured and it shouldn't actually go an configure 16 robots and 400 drives. The device config wizard will know that some are the same devices - atleast it does in my environment. Have you let the device config wizard finish - what does it actually configure after detecting all the devices? -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Heathe Yeakley Sent: 23 September 2010 15:39 To: NetBackup Mailing List Subject: Re: [Veritas-bu] Device Recognition in RHEL5/NBU7 To clarify my question: I currently have a live NetBackup environment where the master server is a Dell 2950 and I have two media servers that are solaris boxes running RHEL 4. My department wants to decommission the older boxes and move NetBackup to newer boxes, and I wanted to upgrade to 7.0 anyway, so I decided to kill two birds with one stone and build 1 new master and 2 new media, install NBU 7 on the new environment and then zone my existing libraries into the new environment and then point all the servers I'm backing up to the new environment. On my live NetBackup environment (the RHEL4 one), when I go into the NBU hardware configuration wizard and scan for devices, the wizard comes back and says it sees 3 libraries and 92 drives (which is the number I expect to see). When I shut down my live environment and bring up the NBU 7 environment and run the hardware wizard, it sees like 16 robots and 400 drives. I'm trying to figure out why my NBU 6.0/RHEL4 environment is able to see one device file per robot/tape drive, but my NBU 7/RHEL5 environment thinks each path is 1 device. I'm not sure where to begin researching this issue. I'm in the process of skimming through the NBU 7 device configuration manual, the HBA documentation and Red Hat's storage documentation. Any light that can be shed on this will be greatly appreciated. - HKY ___ Veritas-bu maillist - veritas...@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] 7.0.1 UNIX/Linux clients backups
I saw the same messages when I was on 6.5.x. I have a AIX master. Don't know if they just fixed that for Linux in 7 (maybe they missed that before) All it is telling you is that it is backing up / (root) and in doing so it sees that /u01 is a separate file system, and it knows you are doing multiply jobs, so it will not backup /u01 with root but will do it as a separate job. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jorge Fábregas Sent: Friday, September 24, 2010 7:48 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] 7.0.1 UNIX/Linux clients backups Hello everyone, I finally upgraded our master/media server from 6.5.3 to 7.0 (and then quickly applied 7.0.1). All seems to be working fine but noticed some new informational messages on our Standard policies for our Linux jobs. These messages appear on the details tab for the job. Here is an example (the jobs exits with a 0 status): Info bpbrm(pid=4240) from client dbsrv33: TRV - /u01 is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /var is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /dev is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /proc is on file system type PROC. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /u02 is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /boot is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /sys is in a different file system from /. Skipping I have ALL LOCAL DRIVES for this policy and the cross mount-points option set. As I mentioned, the job exits successfully and when I check if the other filesystems were backed up (/u01, /var, /u02) they were indeed backed up. Don't you think these informational messages are misleading? I was worried while the job was running (when I saw these messages) thinking the job was indeed skipping all these other filesystems. Of course, I don't worry about /sys, /proc, /dev etc (.I already had them on the exclude_list). I'll appreciate your comments. Best regards, Jorge ___ 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] 7.0.1 UNIX/Linux clients backups
This is why we prefer to use exclude files for our UNIX/Linux OS policies and tell them to backup / instead of ALL LOCAL DRIVEs. We can exclude any filesystem we want (especially things that won't backup like /proc and /sys) then create a separate policy for environment backups (e.g. we might exclude /database from the OS backup then have a separate policy to backup /database itself - usually run at a point the database is down.) Using exclude files also can help you avoid policies that end in status 1 for things they can't backup - at one job I had management wasn't willing to accept the idea that a status 1 was (mostly) successful. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Friday, September 24, 2010 10:29 AM To: jorge.fabre...@gmail.com; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] 7.0.1 UNIX/Linux clients backups I saw the same messages when I was on 6.5.x. I have a AIX master. Don't know if they just fixed that for Linux in 7 (maybe they missed that before) All it is telling you is that it is backing up / (root) and in doing so it sees that /u01 is a separate file system, and it knows you are doing multiply jobs, so it will not backup /u01 with root but will do it as a separate job. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Jorge Fábregas Sent: Friday, September 24, 2010 7:48 AM To: VERITAS-BU@mailman.eng.auburn.edu Subject: [Veritas-bu] 7.0.1 UNIX/Linux clients backups Hello everyone, I finally upgraded our master/media server from 6.5.3 to 7.0 (and then quickly applied 7.0.1). All seems to be working fine but noticed some new informational messages on our Standard policies for our Linux jobs. These messages appear on the details tab for the job. Here is an example (the jobs exits with a 0 status): Info bpbrm(pid=4240) from client dbsrv33: TRV - /u01 is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /var is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /dev is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /proc is on file system type PROC. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /u02 is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /boot is in a different file system from /. Skipping. Info bpbrm(pid=4240) from client dbsrv33: TRV - /sys is in a different file system from /. Skipping I have ALL LOCAL DRIVES for this policy and the cross mount-points option set. As I mentioned, the job exits successfully and when I check if the other filesystems were backed up (/u01, /var, /u02) they were indeed backed up. Don't you think these informational messages are misleading? I was worried while the job was running (when I saw these messages) thinking the job was indeed skipping all these other filesystems. Of course, I don't worry about /sys, /proc, /dev etc (.I already had them on the exclude_list). I'll appreciate your comments. Best regards, Jorge ___ 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 Proud partner. Susan G. Komen for the Cure. Please consider our environment before printing this e-mail or attachments. -- CONFIDENTIALITY NOTICE: This e-mail may contain privileged or confidential information and is for the sole use of the intended recipient(s). If you are not the intended recipient, any disclosure, copying, distribution, or use of the contents of this information is prohibited and may be unlawful. If you have received this electronic transmission in error, please reply immediately to the sender that you have received the message in error, and delete it. Thank you. -- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Windows Client install blows up during the install....
I'm trying to install NBU 6.5 Client on a Windows server. 5.1 used to be on the box but it stopped working long ago. During the install of the 6.5 client, I see Installing Veritas NetBackup Client. It runs for a bit more and then I get The Veritas NetBackup Client install was interrupted before it could be completed and that's as far as I can go. I removed the old 5.1 client to install 6.5 clean. The old 5.1 client wasn't working any more and we have upgraded all our boxes to 6.5.6 and I was just trying to upgrade this Windows box. We are primarily a Unix/Linux shop...so this Windows stuff has me all strung out. [Wink] Someone has mentioned before that it could be a WMI issue (for whatever that is) and I'm coming here to see what the collective minds have to say here. Master server and media servers are 6.5.6 and running on Solaris 10 boxes. ACSLS 7.1 and backups run to DSSU or VTL or to T10K tape drives. I just want to install NBU 6.5 and patch it on this Winders box.please help if you can. +-- |This was sent by dpe...@acxiom.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Windows Client install blows up during the install....
Hello Judy, I am running the install from the Windows Console. The software to be installed in on the local machines E:\ drive and the old client was installed in the C:\ drive. I've even had one of the domain admins try and install it for me and he got the same exact error I did. Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of judy_hinchcli...@administaff.com Sent: Friday, September 24, 2010 1:40 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: Re: [Veritas-bu] Windows Client install blows up during the install 2 options. First, try right click and run as administrator If that does not work. Copy the install files to the c drive and do the install from a local drive. -Original Message- From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Dennis Peacock Sent: Friday, September 24, 2010 1:38 PM To: VERITAS-BU@MAILMAN.ENG.AUBURN.EDU Subject: [Veritas-bu] Windows Client install blows up during the install I'm trying to install NBU 6.5 Client on a Windows server. 5.1 used to be on the box but it stopped working long ago. During the install of the 6.5 client, I see Installing Veritas NetBackup Client. It runs for a bit more and then I get The Veritas NetBackup Client install was interrupted before it could be completed and that's as far as I can go. I removed the old 5.1 client to install 6.5 clean. The old 5.1 client wasn't working any more and we have upgraded all our boxes to 6.5.6 and I was just trying to upgrade this Windows box. We are primarily a Unix/Linux shop...so this Windows stuff has me all strung out. [Wink] Someone has mentioned before that it could be a WMI issue (for whatever that is) and I'm coming here to see what the collective minds have to say here. Master server and media servers are 6.5.6 and running on Solaris 10 boxes. ACSLS 7.1 and backups run to DSSU or VTL or to T10K tape drives. I just want to install NBU 6.5 and patch it on this Winders box.please help if you can. +-- |This was sent by dpe...@acxiom.com via Backup Central. |Forward SPAM to ab...@backupcentral.com. +-- ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Windows Client install blows up during theinstall....
Wayne, Thank you. I did open a ticket and have the server rebooted after the NBU 5.1 was uninstalled. I'll go try the run as administrator but I don't think that that will matter any since I'm on the box as an admin. I'll also try the turning off of the A/V stuff. Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Friday, September 24, 2010 2:45 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Windows Client install blows up during theinstall Judy's recommendation to run as administrator is a good one. That an older version was uninstalled makes the hair on the back of my neck tingle ... because of the uninstall, I recommend a Windows reboot before installing 6.5 ... and if anything NBUish happens on the reboot, reboot again. Turn Anti-Virus off temporarily and try the install again. (I don't have a lot of Windows machines either, but these (3) actions have allowed the NBU 6.5 install to complete for me (when it didn't on the machine owner's first try). I've had it suggested from someplace that defining a policy for the client and opening the vnetd port (13724) first is needed, but that has NOT been true for my cases (I usually open the firewalls after install and define an NBU policy after that). Cheers, Wayne *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Windows Client install blows up duringtheinstall....
Windows 2003 SP1 Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) From: Martin, Jonathan [mailto:jmart...@intersil.com] Sent: Friday, September 24, 2010 2:56 PM To: Peacock Dennis - dpeaco; w...@maine.edu; VERITAS-BU@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Windows Client install blows up duringtheinstall Run as Administrator is only applicable to 2008/2008R2. Even if you have the administrator privilege, you don't use it automatically in Windows 2008 by default. (This behavior can be turned off.) Which OS version is this client? -Jonathan From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Peacock Dennis - dpeaco Sent: Friday, September 24, 2010 3:48 PM To: w...@maine.edu; VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Windows Client install blows up duringtheinstall Wayne, Thank you. I did open a ticket and have the server rebooted after the NBU 5.1 was uninstalled. I'll go try the run as administrator but I don't think that that will matter any since I'm on the box as an admin. I'll also try the turning off of the A/V stuff. Thank You, Dennis Peacock EBCA Acxiom Corporation 501-342-6232 (office) From: veritas-bu-boun...@mailman.eng.auburn.edu [mailto:veritas-bu-boun...@mailman.eng.auburn.edu] On Behalf Of Wayne T Smith Sent: Friday, September 24, 2010 2:45 PM To: VERITAS-BU@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Windows Client install blows up during theinstall Judy's recommendation to run as administrator is a good one. That an older version was uninstalled makes the hair on the back of my neck tingle ... because of the uninstall, I recommend a Windows reboot before installing 6.5 ... and if anything NBUish happens on the reboot, reboot again. Turn Anti-Virus off temporarily and try the install again. (I don't have a lot of Windows machines either, but these (3) actions have allowed the NBU 6.5 install to complete for me (when it didn't on the machine owner's first try). I've had it suggested from someplace that defining a policy for the client and opening the vnetd port (13724) first is needed, but that has NOT been true for my cases (I usually open the firewalls after install and define an NBU policy after that). Cheers, Wayne *** The information contained in this communication is confidential, is intended only for the use of the recipient named above, and may be legally privileged. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please resend this communication to the sender and delete the original message or any copy of it from your computer system. Thank You. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
