Enterprise Vault OWA Setup Wizard
Updated: May 6, 2015 Currently the OWA configuration wizard is undergoing maintenance. Please subscribe to this forum post for updates on the tools availability. We would like to apologize for any inconvenience this has caused. Customers can check back to the Forum post or subscribe to HOWTO75066 for the latest updates. ------------ Here is a wizard which guides you through the steps to configure OWA for Enterprise Vault. This wizard includes five steps that will help you install packages, configure external access, and verify functionality. A sixth step will provide an opportunity to learn more about OWA. Check it out!1.2KViews13likes3CommentsSharepoint archiving - re-indexing crawl in Sharepoint
Hi everyone. I just wanted to pick everyone's brain about something. Say we archive a few TB worth of Sharepoint documents and they all get replaced by shortcuts. My understanding is that during its re-indexing crawl, the Sharepoint server will reach to every archived document on EV and bring it over to be indexed (I am not talking about EV indexing but rather SP indexing). I guess an incremental crawl is not a big deal, but every once in a while Sharepoint needs to perform a full crawl, which means a few TB worth of data will be pulled from EV and dragged across the network back to the Sharepoint server for indexing purposes. I can't see how this is feasible. The full crawl will take weeks and may kill the network.Solved510Views13likes2CommentsHow to backup one file that changes filenames daily?
Hey there, I'm wondering if it is possible to create a selection list that backs up a single file in a directory, that changes its filename every day. Example, I want to backup a text file located at: \example\test1.txt - but tomorrow the file is going to be named test2.txt and in that folder, test1.txt and test2.txt will exist. Hopefully this makes sense, and hopefully it is possible to do this. Thanks in advance for any help and/or suggestions!1.1KViews12likes6CommentsHow to - Backing up Hyper-V and VMware environments
Are you are looking to find information on the most common tasks related to backing up Hyper-V and VMware environments using Symantec Backup Exec 2012? Here are the two consolidated articles - Hyper-V and VMware that lists out: - Top Knowledge Base articles - Top Videos - Top Getting Started Articles - Top Troubleshooting Articles - Symantec Backup Exec 2012 Administrator's Guide Check them out!1.3KViews11likes12CommentsMailbox Analysis Tool
All, When I used to admin the Symantec Enterprise Vault environment, I had the need to analyse users mailboxes to determine why things where not being archived ect, ect. Someone “thanks Karl” wrote me a small command line tool that allowed me to do this. We have had the need to do this for someone else but decided to make a new tool with a new nice UI to give a better overall analysis of a mailbox. If you think this would be a useful tool, please let me know then we can get it packaged up and offered as a totally free tool. Any comments / suggestions welcome.2.6KViews11likes38CommentsArchive Leavers
As an Enterprise Vault Administrator you may often be asked on to handle company leavers. The question is: "How should archives and mailboxes be handled in the leavers process?" ArchiveLeavers will help you manage this process. When the tool is called to run against a specified mailbox the tool will connect to the mailbox, archive all non-archived items, remove them, and then delete all existing shortcuts. The end result is that you will have an empty mailbox, which is disabled from Enterprise Vault archiving. Optionally you can also convert the archive to a structured shared archive. For further information on how to get this tool, please see: http://www.quadrotech-it.com/products/evtools/free/archive-leavers/1.3KViews11likes9CommentsHow-To: Downgrade Backup Exec 2012 to 2010 R3
Two months ago I decided to upgrade our backup environment to Backup Exec 2012. I have upgraded Backup Exec in the past and always had relatively few issues during the upgrade process. I had tried to find some detailed information about Backup Exec 2012 but all I could find was some vague descriptions of what was new. I figured I would give it a shot(totally going against my own if it aint broke don't fix it policy). After the relatively smooth upgrade process my jaw dropped at the interface. I thought it was terrible. But I thought I would give it a chance. I eventually got used to the interface although after two months I still preferred the old interface. My problem was the bugs. Maybe it was because I upgraded rather than installed fresh. But over the course of two months I ran into numerous bugs. The application would randomly quit with exception errors. Sometimes during the middle of my jobs it would just stop backing up and I could not perform any jobs (inventory, erase, etc) without restarting the services. It was terrible. I was having to babysit the thing constantly and still not having reliable backups. After working with Support and them telling my to just "repair" the installation and having the same problems, I decided to take matters into my own hands and downgrade. Luckily before I upgraded I made a copy of my Catalog and Data folders that are located in the Backup Exec program files folder. I would like to preface by saying the intro to this article is not meant to start a discussion about the fallacies of BE 2012 - there are plenty of forums for that - just giving a little background on why I chose to downgrade. The following are the steps I used to downgrade my installation. 1. Locate your backed up Data and Catalogs folders.Hopefully, you backed up your Data and Catalogs folder before you upgraded. If you didn't then this article doesn't apply to you. 2. Uninstall BE 2012 choosing to remove everything when asked. 3. After uninstall is complete reboot the server. 4. Install BE 2010 and select the options you need during the wizard, choose to use a new SQL Express instance. 5. After installation run Live Update and update to R3. 6. Reboot the server. It doesn't prompt you to reboot but if you try opening the application it tells you that you need to so go ahead. 7. Stop all the BE services. 8. Navigate to C:\Program Files\Symantec\BackupExec\ and rename the Data folder to Data.new and the Catalogs folder to Catalogs.new 9. Copy your backed up Data and Catalogs folder to the directory in Step 8. VERY IMPORTANT STEP - WILL NOT WORK IF NOT PERFORMED 10. Run thebeutility.exefound in the location from Step 8. Ignore the warning message that pops up when you open it. 11. Select All Media Servers in the left pane. 12. Select your media server in the right-pane and right-click. 13. Select Copy Database. 14. Navigate to the .mdf database file that is located in your Data folder that you copied over in Step 9. 15. Do the same thing for the .ldf log file located in the same location. 16. Press OK. It will run through stopping services re-attaching the database and starting the services again/ NOTE: The first time I did this I didnt do steps 10-16 and the BE services would not start correctly. Thanks to owner ofthis blogI was able to follow their steps and get it going. Big shoutout. 17. You now have an almost fully-restored BE 2010 installation again. It will be running in trial mode. You will still need to contact Symantec Licensing (1-800-721-3934) to get your license keys donwgraded to BE 2010. But at least you can run backups now for 60-days. Now the time-consuming part...This will vary depending on how many servers you are backing up. After I restored my BE 2010 installation I edited my policies and checked my selection list. The first thing I noticed was I was not able to select anything other than user shares on each server. I then proceeded to check my resource credentials. They all failed stating the agent was not installed or the credentials were invalid. I was sure the service account I was using was valid but just to make sure I went ahead and logged into another machine succesfully using it. After I confirmed it wasnt the service account, I knew it was most likely the newer agents I had installed for using BE 2012. I tried to install the BE 2010 agents through the BE 2010 interface. It said they installed correctly but I was still getting the same error. Here is what I did to get the agents going again. 1. Log into each server you are backing up. (I used RDP, but console would work also) 2. Navigate to the backup exec program files unc path located on your media server. ex: \\servername\c$\program files\symantec\backupexec\agents 3. You will see RAW32 and RAW64. These obviously are the Windows installation agents for 32-bit version and 64-bit. 4. Select the appropiate folder for your server architecture and run setup.exe 5. Select the Uninstall option (repair doesnt work - I tried). 6. After the uninstall is complete, run setup.exe and this time install. NOTE: You could also just run the uninstall on all your servers and then re-install the agents using the BE 2010 interface. Actually this would have been my preferred method but I didn't think about it until after I installed all the agents. 7. Most of my servers did not require a reboot but if you get an error about a missing file after the install - uninstall again, but this time reboot after the uninstall and re-install after the server reboots. 8. Go back to your media server and test your resource credentials and selection lists. They should all pass and you should be able to see and select all the drives, SQL database, and Exchange IS'. You are done! I would say for a ~20 server environment this process might take around two hours to complete. It took me much, much longer but I was figuring things out as I went. Like I said the most time consuming part was the agent installs and this will greatly affect how long it takes in your environment. I hope this helps someone out. Again, I'm sure BE2012 is right for someone but for us, we'll stick with 2010 as long as we can. We already bought Avamar and will be moving to that in the next 30 days but we still have to keep BE for at least 7 years2.3KViews10likes6CommentsNetbackup VMware Backup - Windows Change Journal
If I am backing up VMware VM's using the FLASHBACKUP-WINDOWS policy type, with an OFF-HOST VMware type of backup (VRAY), then I assume the use of Windows Change Journal on the VM itself is of no benefit ? Any comments ? I am using CBT for the VM's, and performing FULL & DIFFERENTIAL backups. I have 'lots' of files on this server, and am looking to get the shortestbackup window possible. I am using a VMware Mount Host which is SAN attached to the datastore LUNs of the ESX5 servers. NBU 7104. Any Comments ? AJ708Views10likes3CommentsEnterprise Vault Issus with outlook
hi, here i am posting two snap shots for outlook error with enterprise vault. EV 9 with Exchange 2010 i created a new mailbox in exchange and then configure it to outlook 2010 and then i just install HTTP Only add-in and installed with no errors, but when click any option in Enterprise Vault add in tab its appears an option for yes or no and whn i click yes it gives an error both snapshot are attached for refference.Solved819Views10likes5Comments