Tape is not appendable despite having alot of free space available.
I am new to BackupExec but we are running into an issue with our tapes. We have a few servers doing a full backup to disk once a week, then the full backup gets duplicated to tape. When the Duplicate job comes up, it prompts to insert over writable media instead of just appending to the existing tape. So far only 2.4TB is used of 8TB available however, it will not append. The OPP is set to one year and the APP is set to Infinite allow append. So I don't know what would be blocking the append. Do the disk backups have to be in the same media set as the tape backups? Currently, backups on the disk are only protected for 1 week whereas they are protected for 1 year on tape. Let me know if there is more info needed.
Restore from LTO-6 tape
Greetings, everyone... I am puzzled if I will be able to restore from old LTO-6 tape after upgrading to the new environment. My old environment was: Windows Server 12 R2, using BE15, backup to IBM LTO-6 tape drive I am planning to upgrade to: Windows Server 2022 with the latest BE22, backup to new new LTO-8 tape drive In case I need to restore from old LTO-6 tape, is it supported restore from BE22 while it was backed up by BE15? And should the Inventory and Catalog operations done first before the restore? https://veritas.com/support/en_US/article.100042698Using Media Vault for Tape Management
We have several backup jobs that run just on the weekend that capture full vmWare guest servers. We run these to a Media Set that has two tapes. Recently we've ran into an issue where the first tape is almost full when another job kicks off and appends to it. Well, the data from that job is too much to fit onto that first tape, so it reaches the end of the job then just sits there prompting to import blank or scratch media. Well, we have a second tape available as part of the media set, but since it has other jobs on it, the job that is "hung" cannot append itself to another tape (read that this is by design). So I was thinking of using a Media Vault to export the first tape to after the 2nd to last job runs so that the final job doesn't get hung up after filling the rest of tape 1, instead, if tape 1 is exported to the media vault prior to the final job running, then tape 2 should be the only media available and it has plenty of space for the final job to write to. Can the Media Vault be used in this scenario? When tape media is exported to it at the end of the job, the media isn't available again until an inventory is ran against the slot, correct?
BACKUP EXEC 2014
Hello, We have backupexc 2014 installed on windows 2012 R2 server and we are backing up several physical servers which Includes Exchange Server and SQL servers. The backup server first takes the backup on the storage and then duplicates to the HP LTO 7 Tape drive. We have created a media group and added a tape to it. The problem is after 2 or 3 days the backupexec server adds a random tape from the tape drive and starts the backing up on that tape instead the tape which we have defined, I am also adding a screenshot to checkBackup Exec Not Recognizing Tape Media
I'm new to Backup Exec and am having trouble getting our backups working. We use NDMP to backup NetApp to a robotic tape library. Under the Media Properties of the tape drive it states "There is no media in the drive." When I try to run a job it gets stuck on "Active: Queued - Backup Scan" This is on Backup Exec 20.5. I've tried restarting the tape library and server, manually loading tapes to the drive, adjusting the overwrite protection, and inventories are completed succussfully. Any suggestions?
How to implement tape rotation with BE 21.0.1200
Hi, I am currently testing Backup Exec V21.0.1200. I would like to implement a data backup on tape and therefore have an LTO-4 tape drive, unfortunately without a tape changer. This means that I have to change the tape manually every day. No problem at first, if I knew which tape would be requested next, especially because I wanted to rotate the tapes according to the grandfather strategy. Unfortunately, I don't find an approach for this in this version. I'm grateful for every tip. Kind regards, UlrichBE 20.4 - 'reserve' 1 'concurrent operation' for DeDup to Tape
Hi everyone - On a client's installation I have a problem with keeping 'duplicate DeDup-backup to Tape'-jobs running without waiting for ending of a 'VM-backup to DeDup'-job. Sample: Active jobs: B2DD-4,B2DD-5,DD2T-2 and B2DD-6 (3 x backup to DeDup-store and one duplicate to tape - in total 4 concurrent operations (but setup for max 3)). When the job DD2T-2 has ended, the tape-storage is in-active until one of the backup-jobs has finished. ------- How do we configure BE's job-/queue-manager to 'always start next DD2T-job' when tape-storage (LTO) is idle and there are jobs waiting for this storage/device ? /JanMox
Duplicating a hardware encrypted tape to an unencrypted tape
I have an LTO5 tape that has been backed up with hardware encryption. It has a variety of different types of backup sessions (flat files, MS SQL servers, MS Exchange) and I've been given the passphrase, so I've re-created the key and can pull off the flat files without any issue. The client has asked me to create an unencrypted version of the tape (they wish to use various 3rd party tools to extract the SQL and MS Exchange backups), and I've tried doing this with the duplication function, but I can't get it to work. I have a second tape drive in which I've mounted a freshly erased and labelled LTO5. When I try duplicating the original sessions from the encrypted tape onto it, I'm given the option of types of encryption (I chose none) but BE is switching on hardware encryption on the target drive anyway. This is regardless of whether I use DirectCopy, or choose to actually have encryption (which then gives me the option of choosing which key to use). Any ideas? Is there some option or other hidden deep in the bowels of BE that's telling it to encrypt everything it writes to tape by default?Slow backup to tape
Hi, We're having some trouble backing up virtual and physical servers to tape. We're not getting the speed it should get and it takes up a lot of time to back up the environment. 2,63TB of data takes up more than 24 hours. Information about job, tape & tape drive: Tape type: HPE LTO Ultrium 6 6,25TB MP RW Tape Drive: MSL 2024 Compression: Hardware Encryption: None Verify: Yes These backups are going through the internal network within the domain. The average backup speed is 4,300MB/m (which is way to slow) When we backup locally on the backup server (for example the D:\ drive where the incremental disk backups are saved on the backup server) it gets to a speed of 10500MB/m. Which is understandable considering it's a straight connection to the tape drive. What did we do to try and resolve it: * Checked the compression * Checked encryption * Replaced tapes for new tapes * Resetted the tape drive * Updated Tapedrive firmware * Checked out the network for inconsistencies (not found), file transfers via other apps around 126mbs from server to server) * Job from VM on hyper-visor to tape (around 2,900 MB/m) * Local disk to tape (between 10500MB/M and 13500MB/M) * VM to disk on the backup server (Around 6200MB/M) Help would be appreciated.Tape Backups
So I was put in charge of our tape backups that were not working and I pretty much had to redo everything from scratch. I have the backups working but I don't understand backing up to tape. How do I implement a tape rotation strategy in backup exec? ZI feel like everything is just backing up to whatever random tape. One of my tapes are full, now what do I do with it? Thanks