Netbackup Tape writing behaviour
Hello All, I have a question about tape retention. The question may be stupid and /i think i know the answer, but I am not sure. In a situation where netbackup is writing a frontend(client to tape) or SLP driven deduplication backup (disk to tape).. and for some reason the backup fails. What happens to the data that has already been written on the tape? Is it retained as per the policy schedule retention that is defined or is it discarded? Also what happens to such a tape where the backup that was writing to it failed before it could complete? Is there a way of identifying such tapes? Maybe erasing them and putting them i nthe scratch pool? Any help is fully appreciated. Kind Regards, Jay
Simple Tape rotation question
I just took over the Backup Exec environment and had a simple question about tapes and rotating them through the system. We do a monthly backup and those tapes are kept for 2 years per our retention rules. So I have older tapes that are cycling out of the retention period that I would like to reuse. For the backups we use a Monthly backup media set. What would be the best operation for reusing these tapes in the monthly backup media set?
failed to change retention of backup image using bpexpdate
[root@PMLPMSDPINF01 ~]# /usr/openv/netbackup/bin/admincmd/bpexpdate -recalculate -backupid PROD-PCDC_1622446947 -d 05/31/2022 Are you SURE you want to recalculate expiration dates on all images that meet the following criteria: backupid PROD-PCDC_1622446947 to expire on Tue 31 May 2022 12:00:00 AM PS Continue?(y/n)y unexpected message receivedWhat is the retention period for Annual backup
Dear Support, What is the retention period I need to set for my Yearly backup to Tape. (Media set propeties please see the screenshot attached). Retention perid/ overwrite protection period / Append period. Please note this a one time backup only. Backup to Tape drive (LTO6) The purpose of this backup is to keep every year a copy of that year's backup in a seperate LTO Tape. (This is not going to overwrite). This is only for future use in case management needed any files from previous years. I need a proper retention policy to keep for these kind of backups. Thank you.
An “American Style” eDiscovery Trap
The eDiscovery frenzy that has gripped the American legal system over the past decade has largely eluded our European counterparts. This is due in large part to the broad and fastidious protections of European privacy laws. Another reason is found in Europe’s narrower discovery rules, which forbid categorical document requests authorized by the Federal Rules of Civil Procedure
Retroactively Changing Retention and deleting expired items
Hello, Running EV 11.0.1. I have to deal with a situation where storage is getting filled up and the company wants to remove a lot of the oldest archived items (specfics yet to be determined). All Provisioning Groups are linked to a retention category "Business" that is set to hold items forever (from what I've been told, this was how Enteprise Vault was setup originally so all items should have been archived with that retention category tag). Now, I know that custom retention categories can have their retention period modified and this will enforce retroactively, correct? So, if I change if from "Forever" to 7 years, archived items older than 7 years become expired and eligible for deletion? The problem is that we need to audit the data first and decide what is a good retention period, so as not to delete too much. I know I can run the expiry report and check the number of items eligible for deletion (as described here:https://www.veritas.com/support/en_US/article.000080850) but is there a more detailed report that can assess how much actual space/how many users/etc. will be processed? Second, once the changes to the retention categories are implemented and the reports ran, these will need to be assessed, which will take a week. The problem is that the Vault Site has a scheduled Storage Expiry every weekend. I attempted to set it to "Never" run but VAC throws off an error that "PST Holding Folder location is not available or not configured" and reverts back to the schedule. Isn't the PST Holding Folder used for PST migrations? Do I need to set it up before I can set the Storage Expiry to never run? The reason for this is we want to avoid a scheduled expiry task running over the weekend and deleting anything before we've fine tuned and decided what the best retention period to put in place. Sorry for the long post, would appreciate advice on this?
