One of the things we've done, just for restore purposes, is to keep the
indexes for an infinite time frame.  If we want an old restore, we
simply do a nsrck -L7 -t mm/dd/yyyy clientname, and it rebuilds the
index to that date.  Depending on the size of the index, it takes
anywhere from just a few minutes to up to 20-30 minutes for a 30-40GB
index file. 

After that, the restore is pretty simple, and can be done within
minutes, most of the time.  Of course, restore time might be in hours,
depending on how big the restore is. 

Just a thought. 

David M. Browning Jr.
IT Project Coordinator Enterprise Backups and Help Desk

 
-----Original Message-----
From: EMC NetWorker discussion [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On
Behalf Of Goslin, Paul
Sent: Friday, June 13, 2008 3:14 PM
To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
Subject: Re: [Networker] Upgrade from 7.2 - 7.4 question

Since it takes the better part of an 8 hour day to re-scan a tape and
re-build the index, I'm trying to avoid having to do that... Besides our
Networker 'downtime' is continually shrinking due to ever increasing
demands for backup capacity..(it's now less than 6 hours per day). If
they request data and we tell them it's going to take two days (per
tape) to get it... They won't be as happy as if we can simply restore
and produce it in one day..

People don't realize that yes maybe disk space is really cheap now, but
the capacity to back it up is not always cheap and is finite ...

> -----Original Message-----
> From: EMC NetWorker discussion
> [mailto:NETWORKER AT LISTSERV.TEMPLE DOT EDU] On Behalf Of Fazil Saiyed
> Sent: Friday, June 13, 2008 3:54 PM
> To: NETWORKER AT LISTSERV.TEMPLE DOT EDU
> Subject: Re: [Networker] Upgrade from 7.2 - 7.4 question
>
> Hello,
> Two things you can do in an hurry
> 1.      Not sure if legal hold required you to keep file index on a
> client, they should be happy that you can keep the backup
> tapes, you can always  rebuild indexes with scanning again or
> restoring individual files from saveset with recover file option.
> 2.      If you have iscsi in your environment or fc, just assign a
> suitable lun to the windows server, during networker
> downtime, copy all
> data from D     drive to new partition say ( F-Drive) ,
> rename partitions,
> do your conversion\update of networker  & then reverse the
> process, take
> back the        lun. ( You can use secure copy to make speedy
> copy between
> the drives)
> HTH
>
> 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

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