Sounds like it could be that you're spawning more than
1 archive session each time you're performing an
archive via maxsession parameter on the client. Also
depending upon what stgpool you're using for archives
do you have more that 1 resource for that stgpool (ie
does that stgpool contain only 1
Hello, can everyone help :
I start an archive schedule on a client. After the end of archiving the client
has two sessions : the first is Run and a second with status IdleW and I must
cancel this sessions over the adminconsole. The archiving process is finished
succesful without failurs.
