(CEP-19129) Security Administration Dashboard
Interaction Date:June 18 - June 28, 2024 Interaction Type:Q&A Interview / Interactive Research Session The Veritas Research Team is conducting an interactive research session about the security administration dashboard. This two part session will focus on understanding your definition and triage of theats, and the second part will focus on walkthrough of some security dashboard the design team is creating to get your feedback. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.
Netbackup incorrectly assigning MediaIDs at first but corrects when deleted & re-scanned.
Netbackup v10.2.0.1 - We're importing & cataloging (P1/P2) 1000s of tapes and we've got a script that does inventory (vmupdate) when the tapes are loaded for multiple media agents. The MediaID generation rule are applied, for few random tapes it does not add the initials eg.: NS is not added for tape NS1234 but it is updated as 1234L6 (default inventory) which fails the import jobs as it cannot find the tape. The same tapes [updated as 1234L6] when deleted from console and re-scanned manually from console gets the correct barcode NS1234. It is random & intermittent (but happens atleast once in 2 days) so I was hoping to get more details from Logs when it happens. It will be good to know which logs are required apart from bptm on media agents and if there are any other robot/inventory specific logs with higher debug ? Thank you.
[Snapshot Manager] Inconsistency between Cloud and Storage sections
Hello! Looking for help, please. My situation is the following: I was faced with an enviroment with an old CloudPoint server that failed on upgrading, resulting in the loss of the images and configuration. Upon fresh installation of a new VM of the Snapshot Manager 10.3, i promptly configured the Cloud Section of the Web UI Primary server and added the provider configuration (Azure). All the permissions have been granted to the Snapshot Manager regarding Azure. Protection Plans created, protected assets selected. Problem is, even thou the jobs are coming through with status 0, i am unable to find any recovery points for the assets. Also, upon investigation, i found on the Storage -> Snapshot Manager section, that the Primary Server is configured as a Snapshot Server, with the old version (10.0). This was done on the old configuration and i have no idea as to why it is present there. Trying to connect does not work, error code 25 as well as retrieving version information. Trying to add the new Snapshot Manager will result in Entity alredy exists error message. Could this storage configuration be related? If so, any suggestions as how to fix it? (I am also unable to delete the old Cloudpoint from the Web UI, but it is disabled) Primary server version is 10.3 New Snapshot Manager is 10.3 Old Cloudpoint was 10.0, already decomissioned. Thank you!
(CEP-19116) NetBackup Web UI & Tape Library Storage
Interaction Date:May 13 - June 7, 2024 Interaction Type:Q&A Interview / Research Interviews The Veritas Customer Experience team is interested to have a discussion with participants about the NetBackup Web UI's tape library functionality. If you are interested in getting more details about this opportunity or in participating in other exciting interactions and are not currently a member of our CPEP program, you can register here:https://cpep.veritas.comthencontact us atcustomer.engagement@veritas.com.
MS SQL VADP Application State Capture (ASC) Backups are Fully Recoverable in NetBackup 10.4
Starting with NetBackup 10.4, VMware VADP Microsoft SQL full backups can be configured for complete application restoration. Before this release, users had just copy-only full backups combined with differential and incremental transaction log backups to restore their MS SQL applications. Copy-only full backups perform ASC, but do not allow for complete application recoveries. Also, copy-only can’t recover the transaction logs on top of those style backups like the new style full backups can. Now users have the option to configure their VMware MS SQL data protection two different ways as shown in the policy and protection plan figures below: The new Microsoft Transact-SQL (T-SQL) full backups configured for full application recoveries. Subsequent differential backup benchmarks are reset so differential backups don’t grow to become the size of fulls The traditional copy-only full backups with incremental and transaction log backups in separate schedules NetBackup 10.4 and onward makes this is possible because MS-SQL full backups are now cataloged as assets in the NetBackup Web UI. Users can now select MS SQL recovery points in the Web UI from either type of backup displayed in the MS SQL assets as shown in the figure below.So, restores work the same way they always have, just with the option of T-SQL full recovery points. Incremental and transaction log backups continue to use the NetBackup client agent. There are a few important notes to consider when using the new fully recoverable MS SQL full backups: This new full backup takes advantage of the T-SQL snapshot feature that begins in MS SQL 2022 but does so in compliance with that snapshot feature’s limitations. Those limitations include that no earlier MS-SQL versions are allowed, or that more than sixty-four (64) databases are included in a snapshot. Microsoft will most likely increase the sixty-four-database limit in the future This new full backup is an “opt in” feature and not the default full. The traditional copy-only full method is offered with the option to use the T-SQL snapshot as an alternative. Neither the “Truncate logs” or “Enable T-SQL snapshots” option are enabled by default Selecting the T-SQL option in a VMware (VADP) policy automatically sets snapshot handling to “Stop the backup if any snapshots exist.” This is a Microsoft requirement to ensure that the database is not in a suspended or inoperable state during the backup All NetBackup servers involved in T-SQL full backups or restores must be at version 10.4 or higher
