I second this.
>From experience using CommVault Simpana which includes this
functionality to suspend/resume backups and copies (clones) I've found
this to be very useful for maintenance tasks.
Jeff Morton
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Werth, Dave
Sent: Wednesday, September 29, 2010 12:58 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NetWorker 7.6 SP1
Skip,
One feature I would love to see in NetWorker cloning is the ability for
it to be interrupted then continued. For example we have some clones
that occasionally run well into the work day and sometimes we've had to
kill them in order to do a critical restore. It would be great if we
could suspend the clone for a time then continue it from where it left
off.
Thanks, Dave
Dave Werth
Garmin AT, Inc.
Salem, Oregon
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Skip Hanson
Sent: Tuesday, September 28, 2010 8:27 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] NetWorker 7.6 SP1
Mathew,
This is excellent feedback, thank you. This is exactly the kind of
information I am looking for.
We knew when we implemented schedule cloning that it would only be the
beginning of the feature. In my research I found that there is no limit
as to how our customers are scripting cloning today. So we boiled it
down to the top 80 % or nsrclone options as a starting point.
Anyone who upgrades to 7.6.1 and has options or features they would
like to see in schedule cloning or any other area of NetWorker. Please
either post it here or send me an email directly at
networker_usability AT emc DOT com.
That is how this feature made it into the product in the first place.
Cheers,
Skip Hanson
NetWorker Usability
On 9/28/10 5:46 PM, "Mathew Harvest"
<Mathew.HARVEST AT COMMUNITIES.QLD.GOV DOT AU>
wrote:
> Just installed 7.6.1 in a sandpit this morning, and had a bit of a
> play
>
> The scheduled cloning look like it could be a useful feature -
> although I think the functionality is a little limited for use in my
> environment 1. I think it would be nice to be able to limit the number
> of clone jobs running at any one time, so you don't potentially
> consume all of you available tape drives with cloning jobs.
> 2. Not having the ability to filter clone jobs based on source device
> I think is a major omission, this means that you are potentially going
> to have multiple clone jobs with savesets spread across multiple file
devices.
> Potentially causing clone jobs to wait until file devices become
> available from other clone jobs 3. having the ability to limit a clone
> job to a specific size or number of savesets, so you can control the
> amount of time a file device is locked up by a cloning job
>
> Interestingly it appears that
> 1. it doesn't appear that you can run a scheduled clone job from the
> command line - not sure if this would really be useful 2. An empty
> scheduled clone (ie nothing to clone) job does not log anything to the
> daemon log file 3. An empty scheduled clone results in the scheduled
> clone reporting as failed (big red X next to it)
>
> I'm making a bit of an assumption here, but I would have thought that
> people who tend to use scripted cloning, probably also use scripted
> cleanup scripts - rather than staging policies??? I'm still trying to
> get my head around if you were to make the move to scheduled cloning
> whether you would then also then want to use staging policies to
> recover space from your file devices, or still stick with scripted
> saveset removal. I guess it might be nice to see something like a
> staging policy, but instead of a clone and remove process when a
> high-water mark is reached it just removes savesets that meet certain
> criteria, for me this would just be just if the saveset has been
> cloned x number of times
>
> Anyway just my initial thoughts and observations ... also wondering
> how this is just a point point release with all the new functionality
> and bugfixes
>
> Mat
>
> -----Original Message-----
> From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU]
> On Behalf Of Preston de Guise
> Sent: Saturday, 25 September 2010 6:36 AM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] NetWorker 7.6 SP1
>
> On 25/09/2010, at 02:10 , Eric Carter wrote:
>
>> Those binaries will appear later today. You'll have to wait a bit
>> longer for the vStorage support. It is not in the SP1 release.
>> Here's some more info for the VADP integration
>> https://community.emc.com/thread/100259 and there is a call for beta
>> testing help on the vStorage API integration release here if you at
all can help:
>> https://community.emc.com/message/498740
>>
>
> With the binaries now available for download, I've published my review
> of some of the key updates in NetWorker 7.6 SP1 from a core
functionality perspective.
> (I didn't personally have much to do with the Data Domain integration
> testing
> - other colleagues of mine handled that and were pretty happy with
> it.)
>
> The review is available on the NetWorker Blog for those who are
interested:
>
> http://nsrd.info/blog/2010/09/25/networker-7-6-sp1-2/
>
> Cheers,
>
> Preston.
>
> --
> Preston de Guise
>
> http://nsrd.info/blog NetWorker Blog
> http://www.enterprisesystemsbackup.com "Enterprise Systems Backup and
> Recovery: A corporate insurance policy"
>
>
>
>
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
this list.
> You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
> Tomorrow's Queensland: strong, green, smart, healthy and fair -
> www.towardQ2.qld.gov.au
>
>
> ********************************* DISCLAIMER
> *********************************
>
> The information contained in the above e-mail message or messages
> (which includes any attachments) is confidential and may be legally
> privileged. It is intended only for the use of the person or entity to
> which it is addressed. If you are not the addressee any form of
> disclosure, copying, modification, distribution or any action taken or
> omitted in reliance on the information is unauthorised. Opinions
> contained in the message(s) do not necessarily reflect the opinions of
> the Queensland Government and its authorities. If you received this
> communication in error, please notify the sender immediately and
> delete it from your computer system network.
>
> To sign off this list, send email to listserv AT listserv.temple DOT edu and
> type "signoff networker" in the body of the email. Please write to
> networker-request AT listserv.temple DOT edu if you have any problems with
this list.
> You can access the archives at
> http://listserv.temple.edu/archives/networker.html or via RSS at
> http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
>
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient. If you are not the intended
recipient, please be aware that any disclosure, copying, distribution or
use of this e-mail or any attachment is prohibited. If you have received
this e-mail in error, please contact the sender and delete all copies.
Thank you for your cooperation.
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or via RSS at
http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
NOTICE OF CONFIDENTIALITY: Information included in and/or attached to this
electronic mail transmission may be confidential. This electronic mail
transmission is intended for the addressee(s) only. Any unauthorized
disclosure, reproduction, or distribution of, and/or any unauthorized action
taken in reliance on the information in this electronic mail is prohibited. If
you believe that you have received this electronic mail transmission in error,
please notify the sender by reply transmission, or contact Support AT multiplan
DOT com, and delete the message without copying or disclosing it.
______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email
______________________________________________________________________
To sign off this list, send email to listserv AT listserv.temple DOT edu and
type "signoff networker" in the body of the email. Please write to
networker-request AT listserv.temple DOT edu if you have any problems with this
list. You can access the archives at
http://listserv.temple.edu/archives/networker.html or
via RSS at http://listserv.temple.edu/cgi-bin/wa?RSS&L=NETWORKER
|
