How 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!
How 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!
How-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 years
HOW TO install BackupExec 2010 agent on Debian (RALUS)
I hope this post will be useful to many people (please vote for it or mark it as solution if it helps you). Installing directly RALUS on Debian will not always work. First problem : ../perl/Linux/bin/perl: No such file or directory Second problem : at the end "was not successfully installed" and "impossible to add VRTSralus to (server)" And some others that will get solved when following my solution This is a simple way to install it and avoid these (and other) problems : 1. (optional) Create a folder to keep all RALUS files and copy the archive into it : mkdir /root/BE mkdir /root/BE/RALUS2010 mv RALUS_RMALS_RAMS-2896.9.tar.gz /root/BE/RALUS2010/ cd /root/BE/RALUS2010 2. Unpack the archive provided by Symantec tar xzf RALUS_RMALS_RAMS-2896.9.tar.gz 3. Stop the RALUS service if it is already installed and runnig /etc/init.d/VRTSralus.init stop 4. Very important, if you are under a 64 bit Linux you have to this Extract debian package : tar xzf RALUS64/pkgs/Linux/VRTSralus.tar.gz Install debian package : dpkg -i VRTSralus-13.0.2896-0.x86_64.deb Start installation : ./RALUS64/installralus 5. But if you are under a 32 bit Linux you have to this (I didn't tested under 32 bits) : Extract debian package : tar xzf pkgs/Linux/VRTSralus.tar.gz Install debian package : VRTSralus-13.0.2896-0.i386.deb Start installation : ./RALUSx86/installralus or ./installralus 6. Be sure to answer all questions correctly especially the one about the host server (XXX.XXX.XXX.XXX), you must give the IP of the Backup Exec server. 7. Do a restart of the RALUS Backup Exec agent, and it should say "[ OK ]" /etc/init.d/VRTSralus.init start I hope it will help ! Send me questions if you have other problems... Denis P.S. Tested with Debian 5.0.3 P.P.S. If you still have some problems : A) If you get "ERROR: VXIF_HOME is invalid. It must point to the root of VxIF. Exiting ...", simply edit ./RALUS64/installralus, and change line 3 : from : VXIF_HOME=../;export VXIF_HOME to : VXIF_HOME=/root/BE/RALUS2010/;export VXIF_HOME B) If you get "./RALUS64/installralus: line 50: ../perl/Linux/bin/perl: No such file or directory", simply edit ./RALUS64/installralus, and change line 50 : from : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ../installralus.pl $* to : ../perl/$OS/bin/perl -I.. -I$PATH -I$VXIF_HOME -I../perl/$OS/lib/$PERL_VER ./installralus.pl $* or to : perl -I.. -I$PATH -I$VXIF_HOME ./installralus.pl $* (to be clear, remove one dot in front of"/installralus.pl", keep only one dot instead of two) C) If the installation is sucessful but VRTSralus refuses to start, launch /opt/VRTSralus/bin/beremote –-log-console to see the error. If you get error while loading shared libraries: libstdc++.so.5: cannot open shared object file: No such file or directory you simply need to install the package : Under Debian 6.0.3 : apt-get install libstdc++5 (Thanks to RockwellMuseum)Restoring files to QNAP
Hi, I'm getting strange errors when trying to do a restore from tape to a QNAP. We're backing up our Vm's to the QNAP using VEEAM and then taking a weekly backup of the QNAP using BAckup exec 2010. All of the above works fine. However I've just come to do our first test restore from tape and on trying to restore to a separate folder on the QNAp (with exactly the same permissions as the fodler that is being backed up) I am geting an error saying that the directory or file was not found. Both the folder that the backup is from and the folder i'm trying to write to are added as custom selections in the format \\QNAP\restoretest The job does get as far as creating the folder into which the restore should placed so I don't think it's a permissions thing. I'm a bit stumped as to what to try next though... Does anyone have a similar setup / advice? ThanksTop 20 Technotes: BEWS
Your question might already have an answer. Check these top 20 Technotes before you post. Else, try looking into the Knowledge Base. How to troubleshoot issues with a Robotic Library or Tape Drive in Backup Exec for Windows Servers. "Corrupt data encountered" (a000fe36 HEX or e000fe36 HEX) is reported when a backup job fails. When attempting to run a backup job "Physical Volume Library Drive not available" Error occurs Backup Exec 12.5 for Windows Servers revision 2213 Hotfix 319699 Symantec Backup Exec (tm) 10.1 (10d) for Windows Servers revision 5629 - Service Pack 3 - Includes Critical Security Updates Symantec Backup Exec (tm) 10.1 (10d) for Windows Servers revision 5629 - Service Pack 4 - Includes Critical Security Updates Backup fails with the error "AOFO: Initialization failure on: "\\\Shadow?Copy?Components". Advanced Open File Option used: Microsoft Volume Shadow Copy Service (VSS). Snapshot provider error (0x8007000E): Ran out of memory" How to backup Exchange 2007 with Backup Exec for Windows Servers (BEWS) Backup of a Microsoft Exchange Information Store fails with error "V-79-57344-33928 - Access Denied. Cannot backup directory mailbox database and its subdirectories" How to troubleshoot the error "A failure occurred querying the Writer status" (a000fed1 HEX or e000fed1 HEX or 0xfffffed1 HEX) using VSSADMIN Backup job fails with the error message " Final error: 0xe00084af - The directory or file was not found, or could not be accessed " Job Engine service crashes when the backup job is targeted to the tape drive. Backup job to tape fails with error "Final error: 0xe0000f16 - The operation failed to acquire the minimum number of drives and media needed." How to perform a local installation of the Backup Exec Remote Agent for Windows Servers or the Advanced Open File Option Granular Restore Technology (GRT) Backup of an Exchange Information Store fails with error "Cannot log on to MAPI with the specified credentials" Symantec Backup Exec (tm) 10d rev. 5629 for Windows Servers Installation Files Backup Exec 12.5 for Windows Servers revision 2213 hotfix 318328, Device Driver Installer DDI20090215 (February 15th, 2009) - 32bit download. Backup Exec 11.0 revision 7170 Service Pack 4 - 32bit download "Job failed running its test run. See log file for details" (a0008703 HEX or e0008703 HEX) No devices found to run job is reported when running a "Test Run" Backup Exec for Windows Servers - Snapshot provider error (0xE000FED1) A failure occurred querying the Writer status when backing up Exchange 2007.
How to use external hard-disks and rotate them
Are you thinking of using external USB or eSata hard-disks for your backups and you also want to rotate them? If you do not know how, read my articles For BE 2012 - https://www-secure.symantec.com/connect/articles/how-rotate-external-harddisks-be-2012 For BE 2010 and earlier versions of BE - https://www-secure.symantec.com/connect/articles/how-rotate-external-harddisks
