List Scratch Tapes from Standalone and send a report
Dear Experts, I am planning to automate Scratch request of Standalone tapes to be recalled from DR. I use the below query to fetch the Scratch from Standalone. vmquery -pn Scratch -b | grep "NONE" The Output lists Media Id but We need Barcode of all these media as our media Id and Barcodes are not similar, how can i achieve this.844Views0likes1CommentUpgrading from Netbackup 8.1.1 to 8.2
I am in the midst of upgrading from 8.1.1 to 8.2. We have 2 Windows masters communicating through AIR SLP's. Each master is a Windows cluster. We are also using 4 Veritas 5240 appliances. What is the suggested order of upgrading the Netbackup environment (master server, media servers, appliances, clients) ?Solved2.4KViews0likes3CommentsSlow 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.1.8KViews0likes2CommentsFujitsu selects Veritas Access as their next-gen storage infrastructure to support K5
Have you read today’s news? FujitsuLimited(Minato-ku, Tokyo) has selectedVeritas TM Access,a software-defined scale-out network-attached storage (NAS) solution, as the premier storage infrastructure for theFujitsu Cloud Service K5. Fujitsu selected Veritas Access due to the following key benefits: Scale-out architecture that enables the cluster’s hardware to be added or replaced without taking systems off-line Flexibility in supporting multiple protocols and the ability to seamlessly interface with different types of storage Control and efficiency Advanced technology with proven record of supporting global mission critical systems Read the press release and share your thoughts by commenting below.1.8KViews0likes0CommentsVeritas16 /Backup Exec 15
Here is the Issue: I am using Backup exec 15 (14.2) V-Ray edition and using agentless methodology to take backup of my virtual infrastructure on Hyper-V platform. I am taking backup of virtual machines (11) splitting them in different in jobs with GRT enabled and agent installed on windows machine. I amusing Full backup and Increment strategy to keep 1-3 month data having full every month or every 3 months. I have SQL, SharePoint, Terminal and File Server in my environment. Issue s incremental backup I am receiving for these virtual machines are very high like for SQL 120-150 GB every incremental (Tried disabling and enabling SQL GRT no difference but if I disable file folder GT backup size reduces significantly but restore time increase due to compression but I need file folder GRT for my servers). I tried agent base backup for SQL and result was same despite checking taking SQL backup log after backup job feature enabled or not. For share point VM size is 80 GB and actual data is 40 GB but incremental is 20-30 GB (only file folder GRT enabled) and same applies to terminal servers like 10 GB incremental and File Server which is also AD is creating 40-50GB incremental. I thought may be there is some issue with tool and I upgraded it from BE 15 (14.2) to veritas 16 Trial and issue remain same. I hold backups by veritas and used another tool agent base backup and I was wondering hat backup size for full and incremental was very small like for SQL full only 70GB as compare to BE 15/Veritas 400 GB and Incremental 10GB as compare to 150 GB same applies to other servers. I am wondering should I go for upgrade or simply move away from BE/Veritas as other product is working very fine. Note: I have virtual infrastructure so I prefer to have VM base backups as it’s easy to manage and recover incase of any issue.2.1KViews0likes6CommentsThe Impact of Hyperconverged Infrastructures on IT
The emergence of hyperconverged infrastructures (HCI) over the last five years has coincided with IT teams needing greater simplicity in supporting specific workloads while providing appropriate levels of processing and storage performance and capacity based on application mix and user needs. By definition, hyperconverged infrastructures combine compute processing, storage, and networking (as required) within a single managed physical system. The HCI surge has been led by Nutanix, whose Nutanix Enterprise Cloud along with its Prism interface have ushered in new levels of simplicity and productivity for IT teams, especially for finely “prescribed” workloads like virtual desktop infrastructure (VDI). By prescribed, I’m talking about creating pre-configured amounts of processing power, storage type/capacity, and networking ideal for a specific workload type and making that pre-configured solution easy to order, install, and operate. The end result is a complete system that is extremely easy to procure and stand up, while also being very efficient for the targeted workload(s) by offering required performance without over-configuring (thus over-spending on) too much processing or storage. From the Veritas viewpoint, we’ve seen increasing numbers of customers deploying hyperconverged workloads on the Nutanix platform. As the global leader in data protection, we know from experience that many organizations cannot offer a new service (app/app mix) to their users unless they know they can protect it. By now supporting Nutanix on Veritas NetBackup 8.1 with NetBackup Parallel Streaming, organizations can benefit from the simplicity and efficiency of Nutanix hyperconverged infrastructure solutions with full confidence that all of their data associated with those workloads can be fully protected. In addition, NetBackup CloudCatalyst allows backups of Nutanix-based workloads to execute up to three times faster than alternative backup solutions. And finally, Veritas CloudPoint now enables organizations to execute “snapshots” between Nutanix Enterprise Cloud virtual machines using the Acropolis hypervisor and a variety of public, private, or hybrid clouds. The Veritas-Nutanix partnership is still in its early stages yet we’ve already seen extensive integration between our respective solutions. This portends even more jointly-derived capabilities targeted at making our common customers even more efficient and effective, while ensuring that their data remains safe – wherever it resides. To learn more about how Veritas and Nutanix are partnering to help advance the digital transformation of our joint customers, read the press release, and view the virtual webcast event, “Is Your Data Center Multi-Cloud Ready?” at https://www.veritas.com/form/webinar/data-center-multi-cloud-ready .2.5KViews0likes0CommentsBackup Exec 16 - Temporary VMware folders are not cleaned from the Backup Exec data directory
HI All, So we started with Backup Exec 14 few years back and I've updated to BE 16 last week with latest patch due to following issue when Symantec could not resolve it. Issue: When backup up VM's, there are lot of Temporary folders been created in folder C:\Program Files\Symantec\Backup Exec\Data. (Folders name include VM's name and date ), and number of folders been created keep growing everyday. Troubleshoot done: I've logged a call with Symantec and for a week they did troubleshooting and today an Advanced tech called me and advised that this is a known issue and only work-around is to delete these folders manually ? Now I have had the same above issue while we were on BE 15, with all the patches installed, hence why I quickly upgraded to BE 16 to see if that resolve the issue. Symantec advance support tech directed me to this article ( https://www.veritas.com/support/en_US/article.000023219 ) which is according to the article was an issue on BE 2014. So I don't believe that Backup Exec 16 will have this now, will it ? And I can't accept an answer been deleting these folder manually every day as a solution. Does anyone experienced this kind of issue ? Cheers3.3KViews0likes3Comments