[90:114] Cannot unload medium, target slot (255) appears to be occupied

[Warning] From: BMA@linuxsrv155.com "ESL01_D17"  Time: 2/9/2015 1:13:44 PM
[90:54]   /dev/nst1
Cannot open device (Unit not ready.)

[Major] From: BMA@linuxsrv155.com "ESL01_D17"  Time: 2/9/2015 1:13:55 PM
[90:114]   By: UMA@mediasrv01.com@/dev/rchgr/autoch3
Cannot unload medium, target slot (255) appears to be occupied

Solution:

> The above error is due to DP couldn't unload the media from where it was actually loaded to the drive during backup/restore.

> Move the tape manually from the drive to any free slot using UMA by following the steps below. 

> Login to the media server from where the tape library/autoloader is connected.

>> run devbra-dev, the output will be the drives and exchanger detected from the device manager.

>> copy the scsi path of exchanger (here it is /dev/rchgr/autoch3)
>> execute the below command and move the media to any empty slot.
>uma -ioctl /dev/rchgr/autoch3

/dev/rchgr/autoch3> move D17 S13

> If there are no empty slots available, eject full media to I/O slots and move the media stuck in drive to free slot.
> Then retry the backup, which should be successful.

Hope this helps!

[81:52] Not a valid mount point => aborting.

[Critical] From: VBDA@winsrv01 "winsrv01 [/G]"  Time: 5/26/2014 9:28:58 AM
[81:52]  /G
                Not a valid mount point => aborting.

An attempt to backup the specific drive (G:/ in this example) connected to the DP client machine was failed and no data will be backed up by DP.

In Windows :

• Login to the windows client machine and check if the drive is accessible.
• Check if the drive is local drive or zoned drive and the zoning still exists.

In case the zoned drive no more exists, you can exclude it in the backup spec. 

If the drive exists on the server and it is accessible, try deleting the \tmp folder on the windows client machine and rerun the backup.

Default path to tmp folder for windows 2003/NT/XP:

C:\Program Files\OmniBack\tmp

Default path to tmp for windows 2008:

"C:\ProgramData\Omniback\tmp"

Hope this helps!!!

[Major] Host for device "ESL01_D01" not found.

[Normal] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:27 PM

 Backup session 2014/03/21-104 started.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D01 not found.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D02 not found.

[Major] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Host for device ESL01_D03 not found.

[Normal] From: BSM@cellsrv01.in.com "Backupspec_win1"  Time: 3/21/2014 6:04:32 PM

 Backup Statistics:

         

  Session Queuing Time (hours)         0.00      

  -------------------------------------------    

  Completed Disk Agents ........          0        

  Failed Disk Agents ...........          7        

  Aborted Disk Agents ..........          0        

  -------------------------------------------    

  Disk Agents Total  ...........          7        

  ===========================================    

  Completed Media Agents .......          0        

  Failed Media Agents ..........          0        

  Aborted Media Agents .........          0        

  -------------------------------------------    

  Media Agents Total  ..........          0        

  ===========================================    

  Mbytes Total .................       0 MB      

  Used Media Total .............          0        

  Disk Agent Errors Total ......          0  

This error occurs when the backup device wasn't removed from the devices context following the media server deletion/migration to other cell.

In other words, the media server could have moved to another cell server or might have been decommissioned and by mistake the devices were not removed from the devices list.

Check the media server's existence, if available;

Check the cell server name, it is pointing to;

Mostly, if the orphan device entry is removed, this error will disappear.

[61:2051] All mountpoints on host \"winsrv01.in.com\" are excluded.

Error:

[Major] From: BSM@cellsrv01.in.com \"win2008bck_spec1\"  Time: 06/09/14 19:09:47
[61:2051] All mountpoints on host \"winsrv01.in.com\" are excluded.
Nothing will be backed up.

Reason:

>> This is something related to Inet error (which was discussed Here), but not necessarily be due to network disruptions. This could also be due to platform side issue.

Analysis:

>> Try to ping and telnet the windows server using default port number from cell server or any other server on the same network.

>> In this case, the server was pretty slow and non-responsive. Telnet to the default port was hung, so requested wintel team for server optimization which must fix the error.

>> Double-check by expanding the server's objects from the backup specification (which would hung as well).

Have a Great Day :)

TSM Insufficient system resources exist to complete the requested service

Error:

ANS9999E ntrc.cpp(928): Received Win32 RC 1450 (0x000005aa) from FileRead(): ReadFile '\\xxxx\. Error description: Insufficient system resources exist to complete the requested service.

Solution:

>> Edit the dsm.opt file by adding the param "MEMORYEFFICIENTBACKUP YES".

>> Save it.

>> Try a manual backup and check if the backup completes.

If not, this error needs attention from platform end.

>> Windows OS has the paging file space memory that needs attention. 
>> Issue can be resolved by adding/modifying "PoolUsageMaximum & PagedPoolSize" in registry

For more info, please refer the article from microsoft.

http://support.microsoft.com/kb/304101

Your backup should be successful, once this is fixed.

Have a nice Day!!

[90:801] Active Removable Storage Manager (RSM) service found on local system.

[Normal] From: BMA@mediasrv01.in.com "MSL2024_D02"  Time: 3/23/2014 2:57:16 PM

 STARTING Media Agent "MSL2024_D02"

[Warning] From: BMA@mediasrv01.in.com "MSL2024_D02"  Time: 3/23/2014 2:57:16 PM

[90:801]  Active Removable Storage Manager (RSM) service found on local system.

 [Warning] From: UMA@mediasrv01.in.com "MSL2024"  Time: 3/23/2014 2:57:18 PM

[90:59]   Changer0:0:0:0

 Cannot open exchanger control device ([2] The system cannot find the file specified. )

[Warning] From: UMA@mediasrv01.in.com "MSL2024"  Time: 3/23/2014 2:57:18 PM

 The device "MSL2024" could not be opened ("Device could not be accessed") 

[Normal] From: UMA@mediasrv01.in.com "MSL2024"  Time: 3/23/2014 2:57:18 PM

 Starting the device path discovery process. 

[Warning] From: UMA@mediasrv01.in.com "MSL2024"  Time: 3/23/2014 2:57:19 PM

[90:59]   Changer0:0:0:0

 Cannot open exchanger control device ([2] The system cannot find the file specified. )

[Normal] From: BMA@ mediasrv01.in.com "MSL2024"  Time: 3/23/2014 2:57:21 PM ABORTED Media Agent " MSL2024_D02"

Solution:

Removable Storage Manager (RSM) service on MS Windows 2003 might cause device issues in backup environment.

It is recommended to stop and disable the RSM service on all MS Windows 2003 systems.

RSM Service in Started status

[90:63] Cannot load exchanger medium (Medium error.)

[Normal] From: BMA@winsrv01.in.com "MSL_D01"  Time: 3/24/2014 10:53:43 PM

 By: UMA@winsrv01.in.com@Changer0:0:0:0

 Loading medium from slot 9 to device Tape0:0:0:0

[Major] From: BMA@winsrv01.in.com "MSL_D01"  Time: 3/24/2014 11:03:16 PM

[90:63]   By: UMA@winsrv01.in.com@Changer0:0:0:0

 Cannot load exchanger medium (Medium error.)

[Normal] From: BMA@winsrv01.in.com "MSL_D01"  Time: 3/24/2014 11:03:16 PM

 ABORTED Media Agent "MSL_D01"

[Normal] From: BMA@winsrv01.in.com " MSL_D02"  Time: 3/24/2014 11:03:21 PM

 STARTING Media Agent " MSL_D02"

[Normal] From: BMA@winsrv01.in.com " MSL_D02"  Time: 3/24/2014 11:03:26 PM

 By: UMA@winsrv01.in.com@Changer0:0:0:0

 Loading medium from slot 9 to device Tape1:0:0:0

[Major] From: BMA@winsrv01.in.com " MSL_D02"  Time: 3/24/2014 11:13:10 PM

[90:63]   By: UMA@winsrv01.in.com@Changer0:0:0:0

 Cannot load exchanger medium (Medium error.)

[Normal] From: BMA@winsrv01.in.com " MSL_D02"  Time: 3/24/2014 11:13:10 PM

 ABORTED Media Agent " MSL_D02"

Solution:

Exchanger medium is failing while handling media from particular slot (here it is slot 9). The media has errors that is residing slot 9.

Move to 'Devices & Media' context -> Click Library -> Click Slot -> move to Slot 9.

--- Check the status of media in slot 9.

--- It was poor media. Isolate the media by moving it to separate media pool and unload it from library. Wait for the media to expire and reformat it. If the status is still shows poor even after formatting, it is not advisable to use it henceforth.

--- Clean the affected drives with good cleaning tape and run a test backup. They should be good for backups.

[70:24] A system error occurred when starting the target script or an agent module.

Problem:

Backup of client machine (Win 2003) fails with the following errors.

[Critical] From: INET_thread_vbda.exe@winclient01.in.com \"winclient01.in.com\"  Time: 03/04/14 08:46:39

[70:24] A system error occurred when starting the target script or an agent module. 

The system error code reported is 2 and the message resolves to [2] The system cannot find the file specified.

Solution:

>> Uninstall & re-install DP client. 
>> Import the DP client in the cell server using GUI [or] add the entry in the cell_info file.
>> Start the backup of DP client which should be successful.