Welcome! » Log In » Create A New Profile

How to tell which clone job is writing to which device?

Posted by Michael Leone 
Michael Leone
How to tell which clone job is writing to which device?
May 08, 2019 02:59PM
Something I would really like to be able to determine. I have a number of
clone jobs running, more than I have tape drives for the job to write to.
But using NMC, I can't tell which clone job is writing to which tape
drive. And I can't go by the duration listing of the running job, since a
job could be in a running state for hours, before a tape drive freed up
for it to write to. So a job could actually have a run duration for 4
hours, but has only actually been writing to a device for 5 minutes.

Is there any way to tell that? I can't think of any. Can you?

Michael Leone
Network Administrator, ISM
Philadelphia Housing Authority
2013 Ridge Ave
Phila, PA 19121-4113
Hours: 8AM - 4PM EST
Tel: 215-684-4180
Cell: 215-252-0143

This list is hosted as a public service at Temple University by Stan Horwitz
If you wish to sign off this list or adjust your subscription settings, please do so via http://listserv.temple.edu/archives/emc-dataprotection-l.html
If you have any questions regarding management of this list, please send email to owner-emc-dataprotection-l@listserv.temple.edu
This message was imported via the External PhorumMail Module
No you can't ... unless you assign a tape drive to a specific pool.
The idea behind that is that NW should be able to move to the next device ... if your have one assigned to that pool.

What we did was that we used our DD to store the backups on multiple DD Boost devices/media.
By using scripted cloning we then started a clone job for the new save sets on each disk device.
Such allowed us to optimally clone these save sets.

But even more important:
- cloning is running independently from backup
- you always have unmultipled backups on tape - optimal for restores

Of course you need a (DD Boost) disk for the backup.
Sorry, you do not have permission to post/reply in this forum.