Login or Register to Ask a Question and Join Our Community


Filesystems, Disks and Memory

Veritas HSM not releasing tapes

Login to Discuss or Reply to this Discussion in Our Community

 
Thread Tools Search this Thread
Special Forums Hardware Filesystems, Disks and Memory Veritas HSM not releasing tapes
# 1  
Old 09-08-2009
Veritas HSM not releasing tapes
I have a volume managed by Veritas Storage Migrator 6.0 running on Solaris 10. It has one managed volume and one tape robot it shares with netpackup (separate volume pools). When I check the process tree I am not seeing any migration processes running, but when I check the panel on the tape robot under media managers control it still has a the tape in a drive from the last job. On the Net Backup Activity Monitor, a job with a tape from a finished migration job is still showing active. This is interfering with other jobs such as backups managed by Net Backup. Any ideas?

---------- Post updated 09-08-09 at 12:44 AM ---------- Previous update was 09-07-09 at 07:10 PM ----------

I was able to solve my own problem. I appreciate those who took the time to read my post.
Login or Register to Ask a Question

Previous Thread | Next Thread

10 More Discussions You Might Find Interesting

1. UNIX for Beginners Questions & Answers

PLINK from Windows not releasing job

Hi all, I would greatly appreciate some help with this. I may not even be on the right path but I think I am close. I have a Synology NAS that I am running rsync jobs on to offload to USB3. These work fine. I have backup software on our Windows Server 2008R2 that I have now realized can... (2 Replies)
Discussion started by: stefshuuj
2 Replies

2. UNIX for Beginners Questions & Answers

How to extend a disk in veritas volume manager in veritas cluster?

Hi Experts, I wanted to extend a veritas file system which is running on veritas cluster and mounted on node2 system. #hastatus -sum -- System State Frozen A node1 running 0 A node2 running 0 -- Group State -- Group System Probed ... (1 Reply)
Discussion started by: Skmanojkum
1 Replies

3. AIX

AIX 6.1: Releasing Memory and Page Space

Hi everyone, i have a question about the Memory Management in AIX 6.1. I have - 128 GB RAM and - 70 GB Page Space. The application i am running on this machine is doing some operations in perl. These are done only once a day and uses both memory and paging space. My problem... (1 Reply)
Discussion started by: Haichao
1 Replies

4. AIX

Releasing a Port

Hey Guys, I need a help, After I upgraded my server to AIX 6.1.4 the port 80 is occupied by a Java process bash-3.00# netstat -Aan | grep "*.80" f1000700007d7bb0 tcp 0 0 *.80 *.* LISTEN bash-3.00# rmsock f1000700007d7bb0 tcp usage: rmsock Addr... (2 Replies)
Discussion started by: kkeng808
2 Replies

5. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (4 Replies)
Discussion started by: Paarth
4 Replies

6. Solaris

Releasing the swap space Solaris

Hi Guys ! I have found this problem many times that the swap space (/tmp space more precisely )of my Server becomes full specially when i run a complete back up of the server . once the /tmp space is full I am not able to run simple commands as i get error like : fork no space on... (6 Replies)
Discussion started by: Paarth
6 Replies

7. Programming

Posix Semaphore Use - Releasing all resources?

I am attempting to write a program with multiple POSIX threads. I want to ensure all threads are released at the same time. I am (trying to) use a semaphore to accomplish this. Without too much irrelevant information, I declare my semaphore with 0 of 25 resources available. Is there a way... (7 Replies)
Discussion started by: snowbarr
7 Replies

8. Linux

ext3 file system not releasing space

Hi all i am facing a problem with ext3 file system df -h is showing 19gb is used even if there is not a single file on the mount point /dev/mapper/vg01-archive 55G 19G 33G 36% /archive_log OS == Linux cdrsvr 2.6.9-55.ELsmp #1 SMP Fri Apr 20 17:03:35 EDT 2007... (1 Reply)
Discussion started by: ajays
1 Replies

9. Solaris

Checking/ Releasing File Locks in Solaris

Hi, One of my prod jobs using Ab Initio (which is Solaris Based) returned this error: ========= Error from Reformat_3.000 on f7j21-01.xxxx3.com ========= Failed opening file for flow: Resource temporarily unavailable Flow = "Flow_11.000" connected to output port "out0" of "Reformat_3.000"... (0 Replies)
Discussion started by: teenu18
0 Replies

10. Programming

Problem with releasing semaphore lock

Hi, I am trying to write stuff to a shared memory using a writer, and reading the corresponding stuff using a reader. I am facing problems while releasing the lock, as a result of which I am having segmentation faults. The code is as follows... /********** writer.c ***********/ ... (1 Reply)
Discussion started by: jacques83
1 Replies
Login or Register to Ask a Question

LEARN ABOUT HPUX

vxinstall

vxinstall(1M)															     vxinstall(1M)

NAME

       vxinstall - menu-driven Veritas Volume Manager initial configuration procedure

SYNOPSIS

       vxinstall

DESCRIPTION

       The  vxinstall utility provides a menu driven interface to configure Veritas Volume Manager (VxVM).  If you install the Veritas Volume Man-
       ager software package using the operating system's package administration commands, you can run vxinstall to configure VxVM for initial use
       on your system.

       Note: If you use the Veritas software installation scripts, do not run this utility.

OPERATIONS

       Licensing
	    vxinstall  first asks if you want to view the Veritas licenses already installed on the system.  Answering "yes" is equivalent to exe-
	    cuting the vxlicrep command (see vxlicrep(1)).

	    You are then asked if you want to add licenses for other Veritas products.	Answering "yes" is equivalent  to  running  the  vxlicinst
	    command (see vxlicinst(1)).  and entering a license key.

       Enclosure-Based Naming
	    You  can choose whether you want to use disk access names that are based on the device names assigned by the operating system, or that
	    are based on names that you assign to enclosures.

       System-Wide Default Disk Group
	    You can enter the name for the default disk group (defaultdg).  This is an alias for the disk group name that should be assumed if the
	    -g	option is not specified to a command, or if the VXVM_DEFAULTDG environment variable is undefined.  By default, defaultdg is set to
	    nodg (that is, no disk group).

NOTES

       From release 4.0 of VxVM, it is no longer necessary to run vxinstall to configure the rootdg disk group.  Disks	and  disk  groups  may	be
       added  to  VxVM	by  running  commands such as vxdiskadm(1M) or by using the graphical user interface without first running vxinstall.  The
       operation of VxVM does not require any disk groups to have been configured, and a disk group named rootdg does not need to  be  present	on
       the system.  Any disk group may be configured as the default disk group that is to be used with VxVM commands.  Any disk group named rootdg
       has no special significance to VxVM. See the vxdg(1M) manual page for further details.

SEE ALSO

       vxdctl(1M), vxdg(1M), vxdiskadm(1M), vxintro(1M), vxlicinst(1), vxlicrep(1)

VxVM 5.0.31.1							    24 Mar 2008 						     vxinstall(1M)