Appliance 5230 file system showing read only
Hi Friends, I am facing an issue file system read only with appliance 5230 and cannot login on appliance via putty and getting below error. Pleas help me. Appliance.Support> Maintenance <!-- Maintenance Mode --!> Error in tempfile() using /tmp/errfile_XXXXXX: Could not create temp file /tmp/errfile_qQQ3H4: Read-only file system at /opt/NBUAppliance/scripts/nbu_runcmd.pm line 266 ************************************************************************** *************** Regards, Priyeranjan1.7KViews3likes4CommentsWhen too much process on appliance, randomly some of database backup fails at the middle of process
Hello, Firstly, this is a big company, nearly 20-25 TB data is backedup as weekly full backup. I think the problem occurs when i have duplication and backup processes at the same time. Randomly some db backup fails with 6 errors at the middle of job. Sometimes i make rebase is off and these errors are lower than to rebaseon. After a fail, i retry to job and it mostly finishes successfully. i dont exactlyknow which logs are needed. i try to explain my envoirement. Master -> 7.5.0.7, windows 2008r2 Media -> 5220 appliance, 2.5.4 Clients ->windows 2008r2, sql2008 i found some link about the issue, but i dont know exactly these changes work or not. http://www.symantec.com/connect/forums/interrupt-when-backup-large-sql-databases http://www.symantec.com/connect/forums/5220-limits?page=0#comment-10092541 Thanks a lotSolved1.4KViews3likes6CommentsAIR replication is failing
Hi All, I have master server on windows 2008 datacentre x64 and two 5230 Netbackup appliances. Main Site : One windows master server and one Netbackup 5230 appliance as media server DR site : One Netbackup 5230 appliace as media server. I am configuring AIR between main site windows master server and DR site Netbackup Appliance 5230 as master server. I have configured the aAIR as per standard configuration. I am facing an issue during replication. Please see the below replication job detail and help me. Thank you... ========================================================================================================== Logs : 9/10/2014 2:43:31 PM - requesting resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week 9/10/2014 2:43:31 PM - granted resource LCM_*Remote*Master*:msdp_sql_dc_to_dr_2_week 9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) Suspend window close behavior is not supported for nbreplicate 9/10/2014 2:43:31 PM - Info nbreplicate(pid=6296) window close behavior: Continue processing the current image 9/10/2014 2:43:31 PM - started process RUNCMD (6296) 9/10/2014 2:43:32 PM - requesting resource @aaaae 9/10/2014 2:43:32 PM - reserving resource @aaaae 9/10/2014 2:43:32 PM - reserved resource @aaaae 9/10/2014 2:43:32 PM - granted resource MediaID=@aaaae;DiskVolume=PureDiskVolume;DiskPool=dp_disk_dc-nbmedia01;Path=PureDiskVolume;StorageServer=dc-nbmedia01;MediaServer=dc-nbmedia01 9/10/2014 2:47:39 PM - Error nbreplicate(pid=6296) ReplicationJob::Replicate: Replication failed for backup id sqlf02_1410349007: media write error (84) 9/10/2014 2:47:39 PMReplicate failed for backup id sqlf02_1410349007 with status 84 9/10/2014 2:47:39 PM - end operation 9/10/2014 2:48:31 PM - Info bpdm(pid=206039) started 9/10/2014 2:48:31 PM - started process bpdm (206039) 9/10/2014 2:48:34 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 1 KB, CR sent over FC: 0 KB, dedup: 75.0%, cache disabled 9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Using OpenStorage to replicate backup id sqlf02_1410349007, media id @aaaae, storage server dc-nbmedia01, disk volume PureDiskVolume 9/10/2014 2:48:35 PM - Info dc-nbmedia01(pid=206039) Replicating images to target storage server dr-nbmaster, disk volume PureDiskVolume 9/10/2014 2:52:35 PM - Critical bpdm(pid=206039) Storage Server Error: (Storage server: PureDisk:dc-nbmedia01) async_get_job_status: Replication started but failed to complete successfully: Error occured during replication. Look at the replication logs on the source storage server for more information. V-454-105 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) wait failed: error 150 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) <async> cancel failed: error 2060001: one or more invalid arguments 9/10/2014 2:52:35 PM - Error bpdm(pid=206039) copy cancel failed: error 174 9/10/2014 2:52:35 PM - Info dc-nbmedia01(pid=206039) StorageServer=PureDisk:dc-nbmedia01; Report=PDDO Stats for (dc-nbmedia01): scanned: 4 KB, CR sent: 0 KB, CR sent over FC: 0 KB, dedup: 100.0%, cache disabled no images were successfully processed(191)3.7KViews3likes4CommentsSymantec 5230 Appliance - Disk Space Warning Message
I am receiveing an emailalert (Warning) each morning relating to disk space utilisation on the de-dup pool in my 5230 Appliance (which is at 80%) and wish to raise the threshold for the warning to 85%. The appliance is sitting steady at 80% so I am not too concerned. Where can I change the limit ? Thanks, AJSolved1.6KViews3likes3CommentsSNMP configuration for 5020-DeDupe appliance & 5220-MSDP
Is there any way to add a query to MIB list to recive an alert in trap reciever(SNMP server) fromDeDupe appliance & 5220-MSDP, whenever entire pool goes down(Situation when backup fails with status 2074). How can I change the priority for MIB lists ???? Regards, BharathSolved655Views3likes1CommentCancel retrying (AIR) Import job on 5200 master
I have configured one of my 5200's as a master server and put it in our dr site. Im am using AIRand import SLP's to replicate the data to the DR appliance. SinceI upgraded mydatacenters netbackup to 7.5 importsfor my cataloge backups are failing. Support has already confirmed thisis a bug and will befixed in the next release (7.5)of the appliance. SoI have stopped replication of the cataloge backups. But... My issue is the originalfailing imports will not stop retrying. This has been going on for weeks and i cant seem to figure out how to stop them on the appliance. I've ran commands in the past for my windows NBU master serve to get jobs to start but this is my first go around with an appliance. Does any one know how to kill these jobs? Each one shows the same info in them and theyhave been retryingfor weeks now. Thanks.Solved1.7KViews3likes3Comments5220 as master/media, logs, ESX San method
Hi all, I'm testing this configuration to backup VM on SAN method. My 5220's is configured as Master/Media. Zoning is OK and appliance have access to datastore lun. When I run Vmware policy, i've see VMWare snapshot create but, Netbackup can't retrieve it. Status 6/23 appears in Admin Console. So I've setting loglevel in appliance for VxMS, to 7 but logs aren't very explicit. It seems to rest in log level 1... : Begin VxMS Session... Logmask set to 0x04000000 Current Environment Variables VFM_ROOT = /usr/openv VFM_PRIVATE_ROOT = /usr/openv VFM_MAP_API_LIB = NULL VFM_MAP_DIR = NULL VFM_UTIL_LIB = NULL 08/21/2015 14:33:41 : vdOpen:VixInterface.cpp:480 <ERROR> : VixDiskLib_Open() error: 13 08/21/2015 14:33:41 : vixMapObjCtl:VixCoordinator.cpp:976 <ERROR> : Returning: 23 08/21/2015 14:33:41 : vix_map_objctl:libvix.cpp:1206 <ERROR> : Returning: 23 Do you explain me if my debugg method is correct ? PS : NBD method is functionnal. ThanksSolved1.2KViews2likes8CommentsNetBackup failures to write to Windows Event Log
Ok so the gist of it is we have a NetBackup Appliance that is Linux and most if not all servers being backed up are Windows. We want to be able to use the Application log in Windows Event Viewer to determine if a backup has failed with our monitoring software. Problem is any information I have found to enable Windows Event logging, only applies to a Windows OS Media/Master server for NetBackup. Is there a way to have a Linux Media/Master server and still have backup failures write to a Windows Event log? It can either be a main Windows servers or to each Windows server running netbackup.1.4KViews2likes5CommentsRunning DataCollect.sh fails with MegaRAID
Acting on instructions from support, I'm attempting to run/opt/NBUAppliance/scripts/DataCollect.sh This fails with the following error: ================================ERROR============================================= MegaRAID_CLI Symlink does not exist or not a executable file, please Check your system. MegaRAID_CLI Symlink should be in the '/opt/MegaRAID/' directory and it should point to either MegaCli64 or CmdTool2 depending on hardware. ================================================================================== This is new install of a NetBackup 5220 appliance with one storageshelf. I updated the box to 2.5.2 a couple of weeks ago. The cache battery appears to have failed, hence the support case. I've reverted the question to support, but I thought I'd ask here as well.566Views2likes4CommentsNetBackup Appliances: Best Practices, Known Issues, Installation, Configuration, and Troubleshooting tips, Documentation and Downloads
Don't Miss This!!! This article gives you a single point of access for help with NetBackup Appliance known issues, best practices, and troubleshooting tips for common Appliance problems such installation and configuration. The Symantec Technical Support team has found these KB articles to be especially helpful to NetBackup Appliance customers. Links to NetBackup downloads and documentation are also included. Let us know if you have any comments or questions! https://www-secure.symantec.com/connect/articles/netbackup-appliances-best-practices-known-issues-installation-configuration-and-troubleshoo420Views2likes0Comments