Backup Exec 2012 Keygen Onlyl
Janae Nowinski
my question is around configuration we would ideally like to be able to do restores ad hoc as such library has 2 tape drives in the device however the backup job will use both drives, we would ideally like to specify one drive for backups and one for restores - aware backups may take longer however often when needed the technicians in location are stopping full job as it has not finished to allow the restore to take place.
I have not tested this myself but this might do what you are after.
Target every backup job to the tape drive itself and not the library. Obviously all backup jobs to the same tape drive.
Let us know if that does what you after for the benefit of others.
NOTE: Having said the above, it's possible that some issues are unique to my environment (that is, my network, my Active Directory domain, etc...). Many of these problems have been observed across domains, and all of them have been observed across multiple backup servers, but I won't rule out the possibility that some of these are unique to my domain (if that's possible).
You cannot use the Search wizard to search the backup sets for granular data. However, you can browse the backup sets. If you want to restore granular data from the backup sets, Backup Exec browses the backup sets for granular data as you browse for items that you want to restore. If you select this option, the time to browse granular data at the time of restore is slightly longer.
Select this option to run the full catalog operation immediately after a backup job finishes. The catalog operation runs as a separate job. This option is the default setting for GRT-enabled backup jobs.
For Exchange and SharePoint Agent for Windows based backups, the full catalog operation runs immediately after all full backups. It runs once every 24 hours for all incremental backups and differential backups.
Before the full catalog operation completes, instead of using the Search wizard, you must browse the backup sets to select the individual items that you want to restore. The Search wizard is available after the full catalog job is complete.
If you schedule the full catalog operation, it runs only for the most recent backup set since the last catalog operation. In this situation, only the most recent backup set since the last catalog operation can be used for granular recovery.
This was a defect we discovered prior to BE 15 FP4, and depends on the "Delayed Catalog" option you had selected for the backup job and the timing of you trying to restore the incremental backup. If you had selected the option "Delay the full operation" and run the restore from the incremental backup job, this used to fail if the catalog operation didn't complete. This has been fixed in BE 15 FP4 and now you can restore from incremental backup jobs at all times post backup completion.
However If I completely select the volume the backup does run. But I do not want to run a backup of the complete volume. There are around 70 directories and I just want to select some 20 to 25 directories.
So it's day one with your new Isilon cluster and you go to backup the unit using NDMP as you would a NetApp. Your hoping to select the device and start browsing through subdirectories and select any file or folder you wish, as you would with a NetApp...well...no so fast. For some reason Backup Exec only lets you select the root volume and nothing else. An Isilon cluster by design will only have a single root volume that continues to grow as you add more nodes, so selecting the root volume of 400TB to backup when you're only looking for a subfolder with 20GB's is unacceptable.
I cannot speak for the nightmare Symantec calls Backup Exec 2012, but in 2010 R3 I finally figured out how to back up individual folders using NDMP on an EMC Isilon unit. Here's a quick tutorial for all of those users out there that are just as frustrated as I was. I'll explain how I'm currently backup individual directories and files along with using wildcard searches and exclusions. This may or may not work in your environment but I figured I'd post this out here since there isn't much documentation found on the topic.
My Isilon looks like so, I've got a root /ifs/ volume with 4 main sub directory shares for each department in my organization. I want to backup 2 folders underneath the Processing directory called "Folder A" and "Folder B".
When the Isilon submenu appears under Variable Name select the Value under FILES and put in the following syntax based on your directory path. REMEMBER Isilon is Linux based, so if you have folders or files with spaces in the name you must put a "\" before every space in the name. Each new subdirectory you wish to backup needs to be separated with a space like I have below.
"Note: Backup Exec allows you to browse to the individual file level ; however individual files cannot be selected for backup, only folder level selection is available but during restore file level selection is available."
Second question -- I have 9 tapes in the device. Right now, only one has actually been used by Backup Exec for backups. I want to make another full backup on one of the unused tapes and then move that tape somewhere off site. I've created the backup job and it's backing up right now to my designated tape. My question is, what do I have to in Backup Exec before I remove that tape from the library? Is there like an "unload" button or procedure that I need to follow so I don't damage anything?
In Backup Exec you can define media sets. These are named 'folders' with defined overwrite protection and append periods. Each backup job is configured to target a specific media set. When these jobs start, the chosen tape is allocated to the media set. Usable tapes that are not allocated should live in the built-in Scratch Media set.
Now this kind of makes sense as DFS abstracts your shares so they look like regular shares so the folders are perhaps links to the DFS areas on the disk, but seriously - as Backup exec knows that a folder is DFS replicated, why on earth is it not automatically selected and dealt with rather than presenting you with a fake list for you to choose from so you think that you are keeping backups when you are not?
You can back up your data to virtual tapes, archive the tapes, and manage your virtual tape library (VTL) devices by using Veritas Backup Exec. In this topic, you can find basic documentation needed to perform backup and restore operations using the following versions of Backup Exec:
The procedure for using these versions of Backup Exec with a Tape Gateway is the same. See the Veritas support website for detailed information about how to use Backup Exec, including how to create secure backups with Backup Exec, software and hardware compatibility lists, and administrator guides for Backup Exec.
Tape Gateway provides 10 tape drives. However, your Backup Exec license agreement might require your backup application to work with fewer than 10 tape drives. In that case, you must deactivate tape drives in the Backup Exec robotic library to leave only the number of tape drives allowed by your license agreement actuvated. For instructions, see Deactivating a Tape Drive in Backup Exec .
Veritas Backup Exec software requires the Tape Gateway medium changer type. If the medium changer type listed under Robotic library is not Tape Gateway, you must change it before you configure storage in the backup application. For information about how to select a different medium changer type, see Selecting a Medium Changer After Gateway Activation.
When you import tapes into the robotic library, the tapes are stored in slots instead of tape drives. Therefore, the tape drives might have a message that indicates there is no media in the drives (No media). When you initiate a backup or restore job, the tapes are moved into the tape drives.
You write data to a Tape Gateway virtual tape by using the same procedure and backup policies you do with physical tapes. For detailed information, see the Backup Exec Administrative Guide in the documentation section in the Backup Exec software.
0aad45d008