First thing you notice after installing Backup Exec 12 and setting up your first job, is that you can't select anything but "Keep Data Infinitely - Do Not Allow Overwrite". Great :-\
"Help" and Google tells you to manually erase the media, relabel it (which effectively erases it), or move the media to scratch. But if you're looking to continuously overwrite your media, this is a big pain. I think I have it figured out, though:
I went to Tools > Options > Media Management and set the Media overwrite protection level to "None" and no Prompting.
Then I went to "Media" and right-clicked on "Keep Data Infinitely - Do Not Allow Overwrite", went to "Properties" and set the overwrite protection to 3 days.
Neither of the above immediately gave me the ability to choose "Overwrite" on the backup job, but after the job ran for the first time it now gives me the "Overwrite" option. -I guess I'll have to wait and see if it actually works next week. What an odd piece of software...
Showing posts with label computers. Show all posts
Showing posts with label computers. Show all posts
Thursday, April 03, 2008
Backup Exec 12 install
I've just finished upgrading our backup software from Backup Exec 9 to Backup Exec 12 and I must say that the documentation, for all it's length (over 1600 pages in the pdf!), it wasn't much help. If this gets any google juice, maybe it'll let someone else avoid reading and re-reading the docs over again because Symantec decided to leave out some key information:
1. Grab the CD (or download folder) and run the Browser
2. Run the Environment Check or Start the Install (the install runs the Environment Check, so if you're ready to install, just run the install).
3. Fix any issues the Environment Check finds -mine warned me about using Terminal Services for the install, but I had no issues with it. As long as you are not using a mapped drive you should be good. Also, it'll warn you about Symantec Endpoint Protection & Endpoint Protection Manager -we ignored those as well as we didn't need whatever functionality they provide. YMMV.
4. Enter all your license numbers -all of them. Including any agents you've purchased such as SQL or Exchange.
5. Complete the install. In the process you'll have to decide on an existing or new account for Backup Exec to use that has privileges to all the resources you're planning to backup.
6. If necessary, UNinstall any old Remote Agents on the machines you'll be backing up.
7. Install the Remote Agent on the machines you plan to back up. You can either push it out from within Backup Exec (in the "Tools" menu) or run the install from each server from the CD or download folder by clicking on "Browser", then selecting "Start the Backup Exec Remote Agent Installation".
Now here's the issue I have with the doc's. They don't tell you that there's no separate agent needed for Exchange or SQL. By installing the Remote Agent, you'll have access to all the functionality of the Exchange and SQL agents (and whatever other ones there are) as long as the licenses for them are installed on the backup server.
So, once that generic "Remote Agent" is installed on all the machines you plan to back up, you're pretty much done.
The remote agent install does not require a reboot, but one of my servers prompted for a reboot after UNinstalling the old Backup Exec 9 Remote Agent.
We moved from one backup server to another, so we didn't actually upgrade -it was more like a new install, so I'm not sure if you were to install 12 on the same server as you had previously had 9 on, if you'd still have access to your old jobs, etc.
1. Grab the CD (or download folder) and run the Browser
2. Run the Environment Check or Start the Install (the install runs the Environment Check, so if you're ready to install, just run the install).
3. Fix any issues the Environment Check finds -mine warned me about using Terminal Services for the install, but I had no issues with it. As long as you are not using a mapped drive you should be good. Also, it'll warn you about Symantec Endpoint Protection & Endpoint Protection Manager -we ignored those as well as we didn't need whatever functionality they provide. YMMV.
4. Enter all your license numbers -all of them. Including any agents you've purchased such as SQL or Exchange.
5. Complete the install. In the process you'll have to decide on an existing or new account for Backup Exec to use that has privileges to all the resources you're planning to backup.
6. If necessary, UNinstall any old Remote Agents on the machines you'll be backing up.
7. Install the Remote Agent on the machines you plan to back up. You can either push it out from within Backup Exec (in the "Tools" menu) or run the install from each server from the CD or download folder by clicking on "Browser", then selecting "Start the Backup Exec Remote Agent Installation".
Now here's the issue I have with the doc's. They don't tell you that there's no separate agent needed for Exchange or SQL. By installing the Remote Agent, you'll have access to all the functionality of the Exchange and SQL agents (and whatever other ones there are) as long as the licenses for them are installed on the backup server.
So, once that generic "Remote Agent" is installed on all the machines you plan to back up, you're pretty much done.
The remote agent install does not require a reboot, but one of my servers prompted for a reboot after UNinstalling the old Backup Exec 9 Remote Agent.
We moved from one backup server to another, so we didn't actually upgrade -it was more like a new install, so I'm not sure if you were to install 12 on the same server as you had previously had 9 on, if you'd still have access to your old jobs, etc.
Monday, February 25, 2008
Shopping: LTO Tape Drive
Our LTO tape library took a dump a couple weeks ago, so I need to find a replacement. These are my notes while I look into the drives available to see what I'll recommend:
First, I started with a search for all LTO tape libraries sorted by lowest price first on CDW.com.
My requirements (in no particular order):
First, I started with a search for all LTO tape libraries sorted by lowest price first on CDW.com.
My requirements (in no particular order):
- At least 100GB/200GB capacity
- Backward compatible with our Ultrium 1 100GB/200GB tapes (in case we need to restore data from them)
- We have about 12 hours to back up about 250GB of data, so we need a minimum of 6MB/sec but we'll double that to make room for expansion, so 12MB/sec. -Shouldn't be hard.
- It's a small company, so price is a factor.
- Our old library had a Ultra 160 connection, so that'd be the easiest to go with this time around although it (does/does not) have room for a (what kind?) card if we want to go with something better/faster.
- Holds at least 7 or 8 tapes at a time.
- HP StorageWorks 1/8 G2 Tape Autoloader Ultrium 232:
- Ultra320 SCSI
- 100GB/200GB Ultrium 1 tapes
- web interface to manage the drive remotely
- 16/32 MBps
- $2,895.99, or $3,099.00 -for the bundle which includes the rack mount kit, 8 tapes, and a jumpered power cord.
- HP StorageWorks 1/8 G2 Tape Autoloader Ultrium 448:
- Ultra320 SCSI
- 200GB/400GB LTO Ultrium 2 tapes
- backward compatible with Ultrium 1 tapes
- web interface for management
- 24/48 MBps
- $3,049.00, or $3,049.00 -for the bundle which includes the rack mount kit, 8 tapes, and a jumpered power cord.
- The rest of the models aren't backward compatible with our Ultrium 1 tapes, so I guess our decision will be between these two.
Monday, April 02, 2007
Outlook 0x8007000E and 0x8004010F errors
In an Exchange 2000 environment, I had one user reporting that she could send emails, but she was not receiving new emails. When a Send/Receive was initiated, the following Outlook 2003 error occurred:
Taking Outlook out of Cached Exchange mode allowed her to receive emails, but she was still getting the following error in Outlook when a Send/Receive was initiated:
...the problem ended up being a corrupt email message. I found it by creating a .pst file on her desktop and attempting to export her entire mailbox to it. I got an error saying the "operation failed". From there, I had to figure out where the corrupt message was, so I re-exported her mailbox one folder at a time. I got lucky, it was in her Deleted Items folder, which was both near the top, and easy to fix. Rather than search through the 386 messages she had in the folder, I simply backed up the folder and then emptied it.
Afterwards I did a Send/Receive and it was successful. I tested it a few more times, it was successful each time (it was failing 100% of the time before), so I declared victory and gave the user back her computer.
This page has some other good suggestions of things to try if you are getting the 0x8004010F error: http://forums.msexchange.org/m_140040800/mpage_1/tm.htm
Error message when you send or receive e-mail messages in Outlook: "Sending and Receiving reported error (0x8007000E): Out of memory or system resources"
Taking Outlook out of Cached Exchange mode allowed her to receive emails, but she was still getting the following error in Outlook when a Send/Receive was initiated:
Task 'Microsoft Exchange Server' reported error (0x8004010F): 'The operation failed. An object could not be found.'
...the problem ended up being a corrupt email message. I found it by creating a .pst file on her desktop and attempting to export her entire mailbox to it. I got an error saying the "operation failed". From there, I had to figure out where the corrupt message was, so I re-exported her mailbox one folder at a time. I got lucky, it was in her Deleted Items folder, which was both near the top, and easy to fix. Rather than search through the 386 messages she had in the folder, I simply backed up the folder and then emptied it.
Afterwards I did a Send/Receive and it was successful. I tested it a few more times, it was successful each time (it was failing 100% of the time before), so I declared victory and gave the user back her computer.
This page has some other good suggestions of things to try if you are getting the 0x8004010F error: http://forums.msexchange.org/m_140040800/mpage_1/tm.htm
Wednesday, December 29, 2004
Stop Complaining About Dell's Tech Support!
I got through Christmas, but here's a taste of what I have to put up with.
Cousin Jan: "Erica, you know computers. What kind should I get?"
Me: "Uh, don't know. What will you be doing with it?"
Cousin Jan: "Just writing resume's, going on the internet."
Me: "Okay. No high-end games or anything like that?"
Cousin Jan: "No. No, I just need something simple. Cheap."
Me: "Okay, well you can get just about anything then. Check out Dell, they're good. As long as you've heard of the brand you're usually okay."
Then everyone jumps in and starts talking about the bad experiences that they, their co-worker, or their dog had with Dell tech support.
Cousin Frank: "Yeah, every time I call them up I get some dot-head on the phone. I ask over and over for someone who speaks english, but I guess they can't understand me so I just hang up."
Cousin Debbie: "I've called them several times and when I hear that accent I ask for someone who speaks english. They're usually very suprised, but I don't give up until someone who speaks english comes to talk to me."
I agree, it can be frustrating, but I call Dell tech support all the time as part of my job, and although I have to ask them to repeat themselves once in awhile, I've gotten my issue resolved 95% of the time. There have been times, yes, when the issue wasn't resolved or took much more effort on my part than it should have. For instance, once, I called about a bad power supply, and the tech told me to "open it up and see if there are any loose wires". I about hit the floor. I assume he thought I was calling the computer itself a "power supply", but if I had "opened up" the REAL power supply I could have easily electrocuted myself! But, this is one problem in several hundred phone calls in my carreer.
See, the real problem (if there is one) lies with you -the consumer. Everyone wants as good a computer as they can get for as cheap as they can get it. No matter who you pick these days, you're tech support will be outsourced overseas because any computer company that doesn't do that can't compete anymore. So shut up! You've got that extra $100 in your pocket -here's where you pay for it (with time). If you want better support, but still want a cheap computer check your local (or smaller chain) computer stores. There's a chain by us (Microcenter) who had a computer, monitor, and printer combo on sale for $350 right before Christmas. Even Dell can't beat that! The only downside might be that you'll have to bring the computer in for repair, you may not get phone support (or it might not be 24 hour), and if they go out of business before your warranty is up you're out of luck.
Remember: Treat people the way you'd like to be treated. Why resort to hate? (Do you know a second language well enough to work tech support for another country?)
Cousin Jan: "Erica, you know computers. What kind should I get?"
Me: "Uh, don't know. What will you be doing with it?"
Cousin Jan: "Just writing resume's, going on the internet."
Me: "Okay. No high-end games or anything like that?"
Cousin Jan: "No. No, I just need something simple. Cheap."
Me: "Okay, well you can get just about anything then. Check out Dell, they're good. As long as you've heard of the brand you're usually okay."
Then everyone jumps in and starts talking about the bad experiences that they, their co-worker, or their dog had with Dell tech support.
Cousin Frank: "Yeah, every time I call them up I get some dot-head on the phone. I ask over and over for someone who speaks english, but I guess they can't understand me so I just hang up."
Cousin Debbie: "I've called them several times and when I hear that accent I ask for someone who speaks english. They're usually very suprised, but I don't give up until someone who speaks english comes to talk to me."
I agree, it can be frustrating, but I call Dell tech support all the time as part of my job, and although I have to ask them to repeat themselves once in awhile, I've gotten my issue resolved 95% of the time. There have been times, yes, when the issue wasn't resolved or took much more effort on my part than it should have. For instance, once, I called about a bad power supply, and the tech told me to "open it up and see if there are any loose wires". I about hit the floor. I assume he thought I was calling the computer itself a "power supply", but if I had "opened up" the REAL power supply I could have easily electrocuted myself! But, this is one problem in several hundred phone calls in my carreer.
See, the real problem (if there is one) lies with you -the consumer. Everyone wants as good a computer as they can get for as cheap as they can get it. No matter who you pick these days, you're tech support will be outsourced overseas because any computer company that doesn't do that can't compete anymore. So shut up! You've got that extra $100 in your pocket -here's where you pay for it (with time). If you want better support, but still want a cheap computer check your local (or smaller chain) computer stores. There's a chain by us (Microcenter) who had a computer, monitor, and printer combo on sale for $350 right before Christmas. Even Dell can't beat that! The only downside might be that you'll have to bring the computer in for repair, you may not get phone support (or it might not be 24 hour), and if they go out of business before your warranty is up you're out of luck.
Remember: Treat people the way you'd like to be treated. Why resort to hate? (Do you know a second language well enough to work tech support for another country?)
Subscribe to:
Posts (Atom)