OK. This is getting stranger... :-)
I logged into the server with the local admin account (which I NEVER do) and
all the files show up. My own account that I was logging in with is a DA
account. I tried adding my account directly to the local administrators
group. Still only see half the files.

Obviously a perms issue, but why? Even an elevated Explorer window doesn't
show all the files...

***********************
Charlie Kaiser
[email protected]
Kingman, AZ
***********************  

> -----Original Message-----
> From: Kennedy, Jim [mailto:[email protected]] 
> Sent: Thursday, January 14, 2010 11:03 AM
> To: NT System Admin Issues
> Subject: RE: Backup Exec 12.5 file restore missing a bunch of files
> 
> 
> Does the account running the BE service have the same perms 
> as the account doing the folder right clicking and checking? 
> I think the right clicking account is lacking some perms on 
> the target drive.
> 
> 
> 
> -----Original Message-----
> From: Charlie Kaiser [mailto:[email protected]]
> Sent: Thursday, January 14, 2010 1:01 PM
> To: NT System Admin Issues
> Subject: Backup Exec 12.5 file restore missing a bunch of files
> 
> File server migration project. Old file server W2K3. New file 
> server W2K8 SP2. Backup server also W2K8 SP2 running BE 12.5.
> Rather than using robocopy et al, decided to try a backup restore.
> 
> Backed up current file server "\Public" folder (Note: not an 
> Exchange PF; just file structure), backup successful. Total 
> volume ~80 Gigs.
> 
> Performed redirect restore (including perms), completed 
> successfully, job log shows ~80 gigs restored minus a few 
> insignificant exceptions.
> 
> Went to new file server selected properties of restored 
> folder. Imagine my surprise when the total size of \public 
> was only 40g. Some quick checking shows files missing from a 
> variety of folders.
> Original folder props: 267,572 Files, 55,373 folders New 
> folder props: 160,009 files, 43,339 folders.
> 
> Nothing significant in event log or BE job log.
> 
> Any ideas? My next step is to blow away the new folder and 
> restore again, this time with destination auditing in place. 
> If that doesn't work, a call to Symantec.
> 
> But I'm wondering if it's a W2K8 issue. Perms, etc?
> 
> TIA.
> 
> ***********************
> Charlie Kaiser
> [email protected]
> Kingman, AZ
> *********************** 
> 
> 
> ~ Finally, powerful endpoint security that ISN'T a resource 
> hog! ~ ~ 
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
> 
> ~ Finally, powerful endpoint security that ISN'T a resource 
> hog! ~ ~ 
> <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~
> 


~ Finally, powerful endpoint security that ISN'T a resource hog! ~
~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/>  ~

Reply via email to