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
Virtual Machine Backups Suddenly Got Slow
Hello, In December, our backups of VMWare full virtual machines suddenly slowed way down. At that time a staff admin recreated datastores and bumped the VMFS version from 5 to 6. There were no other changes that I'm aware of. Agent based backups run fine. Only Virtual machine backups run poorly now. It doesn't matter whether I backup to disk or tape, they never achieve a rate above 300 MB/min. Ideas on where the bottleneck is? Something is limiting the communication from Backup Exec to vCenter. I have a case open with support, but they are not figuring it out. I run BE 21.4 on a physical Windows 2016 server. Backup targets are NAS appliances and direct attached SAS tape drives. The server has teamed NIC that connect to three VLAN's: data to servers, second to NAS appliances, and third to underlying SAN appliances that host our VMWare environment. Our VMWare is old: 6.5. Thanks for your help. Ray
Backup Exec 15 Restore from Disk performance issues
Hi, We are having problems with performance when restoring from disk on backup exec 15. We're running an ESXI 5.1 cluster and several servers got hit with ransomeware. We are restoring our fileserver first from a datadomain (Current software 6.0.0.9-544198) target for backup to disk and when restoring it starts at 1468 MB/Minute restore and then drops down to somwehre between 40 and 68 MB per minute. We have over a terabyte to restore in all and cannot afford the extended time to restore. We ensured that the network for restore and connection is set to 9000 MTU and rebooted but still unable to get better speed. Most searches either returns information for restores from tape or backup performance tuning. Until the ransomware, backups were working just fine with no known performance issues.
VMWare restore not restoring nsx security tag
NB 773 Master and media servers VSphere/vcenter 6.5 After performing full restore of vm (vmware/vadp) vmdk the nsx security tag is not associated. The rest of the tags were restored. It was an overwrite full vm restore with same network, etc. Any ideas how to get it to restore the nsx security tag?
