Backup Exec log files 38GB
We've had an issue with our server due to lack of free space. We've examined the contents of the drive and "C:\Program Files\Symantec\Backup Exec\Logs\" is taking up 38GB of space. Can you tell me why it would take up this much space please? More importantly how do i cap it at say 10GB? We are using Backup Exec 2010 R3 on a windows 2007 sbs server. All our backups are backup to disk folders on removable drives and we backup also backup exchange and SQL. Thanks, your help is appreciated ThanksSolved12KViews1like4CommentsSeeking SQL query returning per-user count of (non-legal hold) items to be expired from EV
Hi all, Long-time listener, first-time caller. Our customer is looking to turn on expiry in their environmentfor the first time.They use EV in a non-traditional manner, so of 32MM+ items, upwards of 2/3 (maybe even 9/10)are on legal hold via DA. Effectively the only items not on legal hold are from cases thatwere active but have since been closed, removing the holds. Many of the holds overlap, as well. We have successfully tested expiry in a near-duplicateQA EV environment and removed about 2MM items without incident. After presenting that result, the customer's IT team has requested that we add an additional step to present to legal before advancing into Production. They'd like as granular a report as possible of what will be removed so they can confirm the data to be expired should be expired. Criteria are below: Asimplecount of items to be removed per user would be the bare minimum. A better solution would include retention categories The perfect query would provide: Granular item-by-item reporting (for at least some users) Ameans by which at least a subset of physical savesets could belocated and presented After digging around the forums for quite some time, I've tested versions ofJesusWept3's query (which looks like it should do exactly what I need) but: In my lab (which does not have DA) I need to remove any references to the holdsaveset table or else it returns no results I'm considering adding DA to my lab to test it, but I have little doubt thatJesusWept3knows his stuff. I'm confident that it will work. In the QA environment, looking at just one of three vault stores, I stopped it after about 36 hours of execution, made some modifications and was unable to make it work more efficiently. I started it again and it has still not completed running after anotherhours.Even if it does conclude after, say, 48 hours, this is not likely to be an acceptable option to management. Please let me know if you have any tweaks, experience or advice to offer6KViews0likes10CommentsHaving problem on MSSQL agent backup
Hello Everyone, I'm new here and this is my first post!! :D I want to ask experts here about error from backup MSSQL using online agent. I use NBU extension GUI to create backup script to full backup all DB in default instance. When the schedule completed the parent job got status 1. Then I look for detailed page and found 1 of my DB cannot backup. ###error messages appear in Job status on NBU extention GUI ### INFO Error in GetConfiguration: 0x80770003. INFO The api was waiting and the timeout interval had elapsed. ###cut from dbclient log### 12:07:32.258 [8532.6572] <16> writeToServer: ERR - send() to server on socket failed: 12:07:32.258 [8532.6572] <16> dbc_RemoteWriteFile: ERR - could not write progress status message to the NAME socket 12:07:32.258 [8532.6572] <4> dbc_RemoteWriteFile: INF - RemoteWriteFile status = 0 12:07:32.258 [8532.6572] <16> CDBbackrec::InitDeviceSet_Part2(): ERR - Error in GetConfiguration: 0x80770003. error messages don't make any sense to me. I tried google and KB but no work. has anyoneexperience this before? please help me D: PS. sorry for my bad english.Solved5.9KViews2likes9CommentsDMP, MPIO, MSDSM, SCSI-3 and ALUA configuration settings
Ok, I'm somewhat confused and the more I read the more confused I think I'm getting. I'm going to be setting up a 4 node active/active cluster for SQL. All of the nodes will have 2 seperate fiber channel HBAs connecting through 2 seperate switches to our NetApp. The NetApp supports ALUA, so the storage guy wants to use it. It is my understanding that I need to use SCSI-3 to get this to work. Sounds good to me so far. My question is, do I need to use any of Microsoft's MPIO or MSDSM? This is on Win 2008 R2. Or does Veritas take care of all of that? Also, I read that in a new cluster set up, only connect 1 path first and then install and then connect the 2nd path and let Veritas detect it and configure it. Is that accurate? Any info or directions you can point me will be greatly appreciated. Thanks!SolvedErrors Changing SQL Collation
We currently run Enterprise Vault 9.0.2 and are looking at upgrading to 9.0.3. For the last couple of upgrades we've been seing the 'mismatched collation' errors in the Deployment Scanner but have not had the opportunity to take the time out to resolve it and it has not prevented the upgrades. As I currently have a period of down-time due to an unrelated issue I have been trying to correct the SQL Collation errors prior to upgrading to 9.0.3 by following the usual technote: http://www.symantec.com/business/support/index?page=content&id=TECH55063&actp=search&viewlocale=en_US&searchid=1329133685543. For most Databases this has been working fine but for a couple of databases some unusual errors have been thrown up. I'll need to retry following a restore on the Audit and Directory databases but I have the errorlog from one of the Vault Store DB's. I followed the process of copying the first part of the programmability script and executed that, then ran the change_collation.sql (We're using SQL 2005) in report mode and it came back operation successful. After clearing down the TempDB tables I then executed the script in normal mode and after running for just under an hour it completed with the error: Msg 547, Level 16, State 0, Line 1 The ALTER TABLE statement conflicted with the FOREIGN KEY constraint "FK_SavesetIdentity_SavesetProperty". The conflict occurred in database "EVExchangeArchiveStore1", table "dbo.Saveset", column 'SavesetIdentity'. I now don't know if the whole script completed or whether it has stopped after the error during the -- CREATE FK CONSTRAINTS section of the script. Has anyone seen this issue before? The script seems to be running fine against the other Vault Store DB's. I'm going to try and re-run the script again tomorrow following a DB Restore but would appreciate any advice or comments on what could have caused this. Thanks CraigSolved4.2KViews0likes5CommentsSQL Backup Failed with Error code 59
From the last couple of days my SQL backup is getting failed with error code 59. I have checked all the communication between master server and media server and client there was no issue but still my backup is getting failed. Any idea what will be the issue. Regards SaqibSolved3.9KViews0likes10CommentsRestore encrypted SQL database on another server
Hi folks! Recently we applied TDE (Transparent Data Encryption) on some of our SQL databases on an SQL server. Netbackup policies keep working troublefree both for Full and Incremental Backups. Now, we need to perform a restore of one of these databases onto another SQL server where the TDE has been applied as well. I try to make the restore but I got the error with status 2828. Can someone guide me on how to do the restore? Thank you all in advance for the support.Solved3.4KViews0likes3CommentsSQL batch file with BATCHSIZE being ignored
I have a customer running a SQL environment on Windows 2008 with 7.5.0.6 client (unsupported, yes) into a 7.7.3 master server which sends backups on their way any available media server and onto a DataDomain (disk) appliance. A batchfile on the Windows host is configured as follows: OPERATION BACKUP DATABASE $ALL EXCLUDE Conversion_XX EXCLUDE Conversion_YY EXCLUDE Conversion_ZZ EXCLUDE dpa_repository EXCLUDE DBA EXCLUDE master EXCLUDE msdb EXCLUDE tempdb SQLHOST "CLUSTERNAME" BROWSECLIENT "NODENAME2" NBSERVER "NBUMASTER" MAXTRANSFERSIZE 6 BLOCKSIZE 7 BATCHSIZE 20 STRIPES 1 POLICY PTC_DB_SQL_BACKUP003 NBSCHED Daily OBJECTTYPE TRXLOG NUMBUFS 1 ENDOPER TRUE ... and is being called from within SQL as expected. Backups complete successfully and are recoverable. So, that's good. Here's what's weird: the databases continue to peel off the SQL host one at a time, even though BATCHSIZE is set to 20. I've advised our customer to request an upgrade of that 7.5.0.6 client to 7.7.2, but I've meanwhile searched through this forum as well as Veritas' KB articles without finding anything that indicates this to be a bug. Has anyone else experienced this ? Thanks! tySolved3.3KViews0likes6Comments