[Veritas-bu] Netbackup Processes
Does anyone know of a document detailing the Netbackup 6.5.2a processes that run on startup and during normal runtime, and a detailed description of what they do? We just spent a over a week with support to find out that our issue was with a process that should have been running, but wasn't. Thanks Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Netbackup Processes
Thank you! I also found that the Netbackup Administration Guide for Unix and Linux Volume 1 pages 62 - 68 give pretty good detail on every Netbackup process as well. http://seer.entsupport.symantec.com/docs/290201.htm -Eric From: Baumann, Kevin [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 11:47 AM To: Hillman, Eric; veritas-bu@mailman.eng.auburn.edu Subject: RE: [Veritas-bu] Netbackup Processes Check out the 6.5 Troubleshooting guide, around page 591. http://seer.entsupport.symantec.com/docs/290230.htm Hope that helps. -Kevin From: Hillman, Eric [mailto:[EMAIL PROTECTED] Sent: Wednesday, September 17, 2008 11:12 AM To: veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Netbackup Processes Does anyone know of a document detailing the Netbackup 6.5.2a processes that run on startup and during normal runtime, and a detailed description of what they do? We just spent a over a week with support to find out that our issue was with a process that should have been running, but wasn't. Thanks Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Encrypted Sybase restore giving Status Code 40
For some reason when I try to do a redirected restore of an encrypted Sybase database backup I immediately get STATUS 40: network connection broken. A redirected restore of a db not backed up using encryption works fine. The keyfile has been setup with the same passphrase and the encryption libraries have been copied. Any help would be greatly appreciated. -Eric Hillman THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Encrypted Sybase restore giving Status Code 40 - RESOLUTION
When restoring to an alternate server, the alternate server's CLIENT_NAME setting in the bp.conf must reflect the name of the original server the database was backed up from. This ONLY applies to encrypted backup restores. Found this in the following article: http://support.veritas.com/docs/248263 http://support.veritas.com/docs/248263 The article refers to Oracle, but it apparently applies to Sybase as well. From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hillman, Eric Sent: Thursday, December 07, 2006 1:29 PM To: Veritas-bu@mailman.eng.auburn.edu Subject: [Veritas-bu] Encrypted Sybase restore giving Status Code 40 For some reason when I try to do a redirected restore of an encrypted Sybase database backup I immediately get STATUS 40: network connection broken. A redirected restore of a db not backed up using encryption works fine. The keyfile has been setup with the same passphrase and the encryption libraries have been copied. Any help would be greatly appreciated. -Eric Hillman THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] Client Hostnames
Thanks for all of your replies. This has been a very interesting and helpful thread. I may have found one issues when using aliases however. Can anyone confirm that you CANNOT use an alias of the server name when backing up an Exchange server/cluster? From what I'm reading, the netbackup client needs to reference the Exchange application using the actual hostname used when installing Exchange in order to successfully access the specified storage groups. This would mean that the actual hostname of the box needs to be added to the Netbackup Policy and not a -backup hostname. Hopefully, this would be the only case that an alias cannot be used. Thanks! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of David Rock Sent: Thursday, September 28, 2006 11:19 AM To: veritas-bu@mailman.eng.auburn.edu Subject: Re: [Veritas-bu] Client Hostnames * Bobby Williams [EMAIL PROTECTED] [2006-09-28 05:47]: About the FQN's, we don't use them. Why type all of those extra characters? Our DR strategy is to carry our offsite tapes to one of our other sites and do our recovery. Without using FQN's, we just bring a development box back up as a lost production box and put it in the domain of the DR site. Depends on environment. We have a shared NBU infrastructure that backs up multiple client environments, therefore we have the potential problem of two different clients with the same short name. -- David Rock [EMAIL PROTECTED] ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. ___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Client Hostnames
Title: Client Hostnames We have public and backup networks. All clients have a public network which is typically 100Mb and some clients (larger clients) have a backup network which is typically GbE. This seems to be pretty typical in larger organizations. Given the above scenarios, my question is in Netbackup what do you name your clients with backup nic's? Option #1: Add a dns entry of the client name with a -backup suffix and assign it's backup ip. Do the same with the Master/Media server and add their -backup hostnames as additional servers from within the netbackup client software Option #2: Instead of using dns, simply add the -backup hostname client alias to the local hosts file on the Netbackup Master/Media servers and assign the backup ip. Do the same with the Master/Media server and add their -backup hostnames as additional servers from within the netbackup client software Option #3: Simply override the actual client's hostname IP with it's backup ip by adding it to the local hosts file on the Netbackup Master/Media server. Do the same with the Master/Media server in the client's hosts file and leave the non -backup hostnames as servers in the netbackup client software. This alternate method would overwrite the DNS record of the actual client and Master/Media hostnames with the hosts backup IP. Also, is it best practice to use FQDN's, or no? Thanks -Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Database backup restarts
Title: Database backup restarts We have a problem whereas if a database (Sybase) job is spawned using the standard netbackup script and half way through the backup (maybe 25 out of 50 databases) the parent job failes, Netbackup restarts the parent job and ALL databases attempt to backup all over again. This is a big problem since we use DSSU's. The DSSU fills up before the 2nd go around finishes. Is there a way to edit the backup script to restart only the missed databases and not ALL databases when these jobs fail? Thanks! Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] How to only stop new disk to tape jobs from starting
Title: How to only stop new disk to tape jobs from starting We use disk staging in NBU 5.0 MP5. Our backups to disk were greatly delayed last night and are now contending with the disk to tape jobs. We've manually killed all duplication jobs, but new ones keep starting based on the schedule we set. Does anyone know of a way besides stopping bprd to stop only the Duplication jobs from starting? Thanks! -Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
Re: [Veritas-bu] How to only stop new disk to tape jobs from starting
Title: How to only stop new disk to tape jobs from starting I ended up administratively downing all tape drives. Not sure why I didn't think about that sooner. Thanks for all of your replies! From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hillman, EricSent: Thursday, June 08, 2006 10:14 AMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] How to only stop new disk to tape jobs from starting We use disk staging in NBU 5.0 MP5. Our backups to disk were greatly delayed last night and are now contending with the disk to tape jobs. We've manually killed all duplication jobs, but new ones keep starting based on the schedule we set. Does anyone know of a way besides stopping bprd to stop only the Duplication jobs from starting? Thanks! -Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.___ Veritas-bu maillist - Veritas-bu@mailman.eng.auburn.edu http://mailman.eng.auburn.edu/mailman/listinfo/veritas-bu
[Veritas-bu] Windows FS backing up more drives than specified
Title: Windows FS backing up more drives than specified This is a known bug that was supposed to be fixed pre-MP5 that seems to still be happening. We have a Windows policy pointing to a virtual cluster hostname backing up 5 drives with Allow Multiple Data Streams turned on. The first job starts and fails. The 2nd stream not only backs up it's assigned drive letter, but continues to backup every other drive letter specified in the policy even though the other streams are either queued or are running themselves. This is a huge pain. Anyone know of a fix? Thanks, Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
RE: [Veritas-bu] Windows FS backing up more drives than specified
Title: Windows FS backing up more drives than specified I'm sorry. I'm using Netbackup 5.0 MP5 on the server and client From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Hillman, EricSent: Wednesday, May 17, 2006 2:28 PMTo: veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] Windows FS backing up more drives than specified This is a known bug that was supposed to be fixed pre-MP5 that seems to still be happening. We have a Windows policy pointing to a virtual cluster hostname backing up 5 drives with Allow Multiple Data Streams turned on. The first job starts and fails. The 2nd stream not only backs up it's assigned drive letter, but continues to backup every other drive letter specified in the policy even though the other streams are either queued or are running themselves. This is a huge pain. Anyone know of a fix? Thanks, Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof. THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
[Veritas-bu] Iron Mountain Vault Report File Issue
Title: Iron Mountain Vault Report File Issue We are in the process of switching our rotation procedure from using some Iron Mountain application to simply uploading the Netbackup Vault IM report file to inform Iron Mountain of the tapes that are getting sent to them that day. One issue that we're seeing is that when Vault runs, some tapes are still being written to. If these tapes hold valid images, Vault tries to eject them, and fails. The Picking List for Robot vault report shows these tapes as **Not Ejected**, but the IM file still adds it to it's list of outgoing tapes. When the file is FTP'd, Iron Mountain thinks it's receiving the tape and later generates an exception email stating that a tape was not received. Does anyone know if it's possible to have these **Not Ejected** media removed from the IM report files? Thanks! -Eric THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
RE: [Veritas-bu] What command cleans out DSSU's?
Title: What command cleans out DSSU's?
Booby,
Thank you! It's actually not the valid images
that automaticatlly get removed that I am trying to clean. It's the
invalid image files that get left on disk when jobs fail that I need to find and
clean. The only way I know of is to wait until I get error code 190's when
manually running archival to tape and then finding all *.F1 files without a
corresponding .ds extention. Then I can remove all of those image files
that belong to that invalid image.
From: Bobby Williams
[mailto:[EMAIL PROTECTED] Sent: Saturday, May 13, 2006 7:07
AMTo: Hillman, Eric;
veritas-bu@mailman.eng.auburn.eduSubject: RE: [Veritas-bu] What
command cleans out DSSU's?
First, look at your global setting of "maximum
copies". If it is higher than 2, this will give you more
copies.
Also, go to the storage units area of the GUI and manually
run the staging to make sure that you are up to date.
On the dssu, there are files (all less than 2GB) named
{system_name}_{utime}_F$$ and there are files of "0" size named the same but
with "ds" at the end.
The file with the "ds" at the end are files that NB thinks
it has put on disk. The other files are the backup images named (in the
above format) as the backupid and the fragment number (dsu and dssu are limited
to 2GB fragments).
All NB is doing on the dssu is duplicating the images to
tape. Copy 1 is on disk, copy 2 (thru ...) is on tape. When the
duplication process completes successfully (the way it is designed anyway), the
backupid_fragment.ds file is created to let NB that it can be purged if
necessary.
You can check each file that ends in F1 (fragment 1) and
use bpimagelist to see how many copies you have. If the ds file version of
the file exists, you should show copy 1 or primary to be on the DSSU and copy 2
to be on tape (or wherever you stage to).
If you can verify that you have 2 copies, you can use
"bpexpdate -d 0 -copy 1 -backid {backupid} -force" to expire the copy that is on
disk.
That will clear up the DSSU.
Bobby Williams
2205 Peterson
Drive Chattanooga, Tennessee 37421 423-296-8200
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] On Behalf Of Hillman,
EricSent: Friday, May 12, 2006 2:55 PMTo:
veritas-bu@mailman.eng.auburn.eduSubject: [Veritas-bu] What command
cleans out DSSU's?
We use Disk Staging Storage Units in our Netbackup
5.0 MP5 environment. When jobs fail for whatever reason, the image files
created up to that point still stay on disk. At some point, they get
removed by Netbackup, but it's not immediate. This used to be a huge
problem pre mp5. In MP5, Veritas added better cleanup processes, but they
don't go into detail as to how it works. Can someone tell me what process
goes through DSSU's looking for invalid images to remove and when that process
runs? Also, is it possible to run that process manually at
will?
Thanks in advance for any help! THE
INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED,
CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader
of this message is not the intended recipient, you are hereby notified that any
dissemination, distribution, copying or use of this message and any attachment
is strictly prohibited. If you have received this message in error, please
notify us immediately by replying to the message and permanently delete it from
your computer and destroy any printout thereof.
THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
[Veritas-bu] Planned Network Outage - What should I do about backups?
Title: Planned Network Outage - What should I do about backups? We start weekly backups every Friday night. They run through Sunday. There is a scheduled network outage on Saturday morning between 5am and noon. This will disconnect clients from the backup servers and the media servers from the master servers. Can anyone recommend the best way to pause these jobs? Here are the choices I'm considering: 1. Stop Netbackup daemons on all master and media servers Friday night and restart them after the network outage is done. I believe this will not allow all backups enough time to finish by Sunday night when our next backup window starts 2. Don't do anything. I'm not sure what will happed to jobs that are running including User database backups which get sent to the master server and run on a media server when the communication between those servers is gone. Also DSSU archival to tapes may experience problems when communication is cut between the master server who is sending the list of backup images to the media server to archive to tape. 3. Login immediately prior to the network outage and kill all backup jobs, stop Netbackup deamons and restart deamons after the network is back up. This has never ended cleanly. There's always jobs that don't stop. I almost always need to do some kill -9's to get the job processes to die and the rest of the daemons to stop. Also, partial images will be left on DSSU's which won't get removed. When jobs get restarted, they'll eventually run out of disk space because Netbackup left those partial images. Does anyone know of an easy way of cleaning out partial images on DSSU's? Any recommendations are helpful. Thanks! THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
[Veritas-bu] What command cleans out DSSU's?
Title: What command cleans out DSSU's? We use Disk Staging Storage Units in our Netbackup 5.0 MP5 environment. When jobs fail for whatever reason, the image files created up to that point still stay on disk. At some point, they get removed by Netbackup, but it's not immediate. This used to be a huge problem pre mp5. In MP5, Veritas added better cleanup processes, but they don't go into detail as to how it works. Can someone tell me what process goes through DSSU's looking for invalid images to remove and when that process runs? Also, is it possible to run that process manually at will? Thanks in advance for any help! THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
[Veritas-bu] How to determine the size of a restore
Title: How to determine the size of a restore How can you determine the size of a restore if the restore includes 1 parent folder with thousands of sub-directories and files within those sub-directories? I would think that this would be possible somehow, but Veritas Support states that there is no way to do it? Thanks! THE INFORMATION CONTAINED IN THIS MESSAGE AND ANY ATTACHMENT MAY BE PRIVILEGED, CONFIDENTIAL, PROPRIETARY OR OTHERWISE PROTECTED FROM DISCLOSURE. If the reader of this message is not the intended recipient, you are hereby notified that any dissemination, distribution, copying or use of this message and any attachment is strictly prohibited. If you have received this message in error, please notify us immediately by replying to the message and permanently delete it from your computer and destroy any printout thereof.
