Shares Changed Drive Letter of the Shared Folder after a Reboot on Windows 2003


hi,

i have file server running windows server 2003 standard edition patches upto 5/30/12. server connected storage array via scsi , has 8
folders being shared. drive letter volume "s:\". folder called "xyz" shared folder "s:\xyz"

we have volume has drive letter "t:\" attached via local storage. we conducted a dr test, took full backup of "s:\" , restored "t:\" using netbackup. test successful , restore. had "s:\" , "t:\" have identical data except "s:\" production , has shares on it. never rebooted server our test , data stayed on 24 days no issues.

on june 1st rebooted server part of our monthly maintenance , after reboot shares hosted on "s:\" drive changed drive letter "t:\" "xyz" folder went "s:\xyz" "t:\xyz". the shares security , permissions intact so when users accessed shared folder, date was24 days old.

the correlation find reboot couldn’t find else change drive letter. checked on array , looked healthy , there no errors reported nor there errors scsi cards or system hardware.

can provide me guidance why drive letter change occurred. if need additional info please let me know. thanks



so found root cause why drive letter got changed. when used netbackup restore t drive used existing backup set of s. in simpler terms, took full backup of s drive , restored data onto t drive. netbackup preserves security , shares of files , folders. netbackup before backup checks , gets aware of folder structure , shares these folders have. when did restore shares put backup because told netbackup preserve settings. going thru backup logs saw warning messages tells, "the 'server' service needs restarted in order shares take affect." since never rebooted server, normal should server waiting on pending "server" service restarted move shares over. once reboot done shares on t drive went in affect. change drive letter. 


--alex abraham



Windows Server  >  File Services and Storage



Comments

Popular posts from this blog

Edit Group Policy

Hyper-V VM not reaching OS 'Logon' screen

DNS question...