NT Backup and Buffulo NAS
We deployed a NAS drive on a customer's network a few weeks ago because they had filled the data partition on a Windows 2003 Server.
After some trial and error to get access to the share folder on the NAS drive (must be mapped to a static IP and not the FQDN which worked fine for the first week), things seem to work OK except for the backup. We schedule NTBackup to do a full backup to USB drives on Monday and a differential backup to Iomega REV 35 GB disks Tuesday through Friday.
The share directory on the NAS drive (G: is mapped to \\static_IP_Adress\Share) will not back up. All other server resources back up fine (C: drive (System), Z: drive (Data) and system state). I'm assuming that since there is no full backup of the NAS share directory, there will be no differential backup of that data.
What can be done to back up this data. It is there company information and hasn't been back up since the NAS drive was installed.
After some trial and error to get access to the share folder on the NAS drive (must be mapped to a static IP and not the FQDN which worked fine for the first week), things seem to work OK except for the backup. We schedule NTBackup to do a full backup to USB drives on Monday and a differential backup to Iomega REV 35 GB disks Tuesday through Friday.
The share directory on the NAS drive (G: is mapped to \\static_IP_Adress\Share) will not back up. All other server resources back up fine (C: drive (System), Z: drive (Data) and system state). I'm assuming that since there is no full backup of the NAS share directory, there will be no differential backup of that data.
What can be done to back up this data. It is there company information and hasn't been back up since the NAS drive was installed.
armitdept
Try backing this data up right to the root. Without any sub folders. I have had this problem and that has worked. You can then move the .bkf to the subfolder so the data does not get over written.
Are you usre that BE has all the latest patches ?
have you checked that the NAS has the latest firmware ?
Have you checked your DNS ?
Why did the FQDN work for a week and stop ?
Were backups OK during the first week ?
I hope this helps !
have you checked that the NAS has the latest firmware ?
Have you checked your DNS ?
Why did the FQDN work for a week and stop ?
Were backups OK during the first week ?
I hope this helps !
ASKER
I ran a manual backup yesterday evening and it worked OK. It seems just the scheduled backups don't want to back up the G: drive (the NAS mapped drive).
I am not sure why the drive has to be mapped using a static IP and users cannot access the share folder using NAS (FQDN).
The Buffalo support tech had us apply the latest patches, assign a static IP and map to it to fix the folder access problem.
When I ran the Buffalo setup utility, the drive did appear in DNS with the correct IP.
I am not sure why the drive has to be mapped using a static IP and users cannot access the share folder using NAS (FQDN).
The Buffalo support tech had us apply the latest patches, assign a static IP and map to it to fix the folder access problem.
When I ran the Buffalo setup utility, the drive did appear in DNS with the correct IP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I am not sure what you mean by 'correct user context/permissions.'
I used the same user name and password to create the scheduled backup as I used to run the manual backup. The only difference that I can see is the scheduled backup will run and back up the c: (system) and Z (data) drives and the system state. The G (NAS) does not appear in the bkf file. When I ran a manual backup, the C: (system), Z (data) and G (NAS) drives and the system state all appear in the bkf file.
I restored a folder from the G (NAS) to an alternate location and the data was there.
I used the same user name and password to create the scheduled backup as I used to run the manual backup. The only difference that I can see is the scheduled backup will run and back up the c: (system) and Z (data) drives and the system state. The G (NAS) does not appear in the bkf file. When I ran a manual backup, the C: (system), Z (data) and G (NAS) drives and the system state all appear in the bkf file.
I restored a folder from the G (NAS) to an alternate location and the data was there.
ASKER
I scheduled a differential backup to the REV 35 GB disk last evening and ran it manually. The backup performed without a problem. I let the backup run on schedule and still no NAS data. The G: drive (mapped to the static IP of the NAS) does not appear in the backup report.
So it seems that only the scheduled backups are failing to find the NAS drive.
So it seems that only the scheduled backups are failing to find the NAS drive.
1) In the batch file that is scheduled for NTBACKUP, I would first check to see if the G: mapped drive exists,
If not, I would map it as part of the scheduled task ( you may need to use another drive letter )
The issue may simply be that the scheduled task does not see the mapped drive.
I hope this helps !
If not, I would map it as part of the scheduled task ( you may need to use another drive letter )
The issue may simply be that the scheduled task does not see the mapped drive.
I hope this helps !
ASKER
I am still experiencing this issue. When I schedule a backup, the Buffalo NAS Share data (G: drive) is not backed up. When I right click on the scheduled task and select Run, the NAS drive is included in the backup.
This happens in with Full (Monday) and Differential (Tuesday-Friday) backups.
I'm not sure where to proceed from here.
Any help would be greatly appreciated.
This happens in with Full (Monday) and Differential (Tuesday-Friday) backups.
I'm not sure where to proceed from here.
Any help would be greatly appreciated.
The problem may be that the mapping only appears in the Logged in user context.
Set the scheduled task to use the same login, and test again.
The machine needs to be logged in with the same user as the scheduled task.
Set the scheduled task to use the same login, and test again.
The machine needs to be logged in with the same user as the scheduled task.
ASKER
SysExpert,
First, thank you for keeping up with this problem and making suggestions to solve it.
I not sure I understand what you are getting at here. The entire backup system is set up using the administrator user name and password which a member of the Domain Admins group. I use the 'Schedule Jobs' tab in the NTBackup application to set up all backups.
The problem appeared again on Friday. The Differential backup is scheduled to run at 7 PM on Friday and usually takes about a half hour. When I logged on remotely to the server to check the NTBackup report, no NAS drive data was backed up. I opened Scheduled Tasks, right click on the Backup job that is set up (in this case Friday2), select run and the NAS drive data is backed up. I check the report and the G:\ drive appears there (mapped to \\NAS\Share). I select the file backup on the Restore tab of the NTBackup utility and the data is there ready to be restored.
Thanks for any input.
First, thank you for keeping up with this problem and making suggestions to solve it.
I not sure I understand what you are getting at here. The entire backup system is set up using the administrator user name and password which a member of the Domain Admins group. I use the 'Schedule Jobs' tab in the NTBackup application to set up all backups.
The problem appeared again on Friday. The Differential backup is scheduled to run at 7 PM on Friday and usually takes about a half hour. When I logged on remotely to the server to check the NTBackup report, no NAS drive data was backed up. I opened Scheduled Tasks, right click on the Backup job that is set up (in this case Friday2), select run and the NAS drive data is backed up. I check the report and the G:\ drive appears there (mapped to \\NAS\Share). I select the file backup on the Restore tab of the NTBackup utility and the data is there ready to be restored.
Thanks for any input.
1) You use the administrator User and PW to set up these scheduled tasks ?
2) Is the computer normally logged in with the Same Administrator account.
If not, then test it with it logged in as the Same admin accout that is used in the scheduled task..
I hope this helps !
2) Is the computer normally logged in with the Same Administrator account.
If not, then test it with it logged in as the Same admin accout that is used in the scheduled task..
I hope this helps !
ASKER
Yes, the administrator user and PW are used to set up the scheduled tasks.
I log on remotely using RDP using the same credentials (administrator user and PW).
I log on remotely using RDP using the same credentials (administrator user and PW).
Forced accept.
Computer101
EE Admin
Computer101
EE Admin