SoftwareTipsPalace.com: Newsletter | YouTube Channel | Write for Us | RSS/XML

 

advertisement
Home Windows Apple/Mac Linux Reviews Guides/Tips How-To Techs/Tests Web 2.0 Downloads Videos Blogs/News Forums
Windows Vista | Windows XP | Windows 98 | Windows 95 | Windows Forums | Windows News
{feature}
+ Advanced Search
+ Suggest a website
advertisement

read also
Incremental Backups
Professional Backup Programs for Windows 95/NT
Using Options with NT Backup for More Versatility
Using the Windows NT Schedule Service and the AT Command to Automate Backups
Configuring a Screen Saver in Windows 95/NT

 

 » More Win. 95 resource
» Windows 95 Forums
» Windows Services
» Windows Glossary
» Windows Run Commands
» Interface & Visual
» System
» Other Guides/Tips
» View all Guides/Tips

 

 

Limitations of Windows NT Backup

By: Staff
Date: October 08, 2006
Level: All

The three most pressing limitations of Windows NT Backup are:

  • Windows NT Backup will not back up files (including hidden files) or directories that you do not own or whose access has been restricted. To ensure a full backup, make sure you are a member of the Backup Operators group. Members of this group can back up items even if they do not have direct ownership or the other specific permissions. They cannot read the files, but they can back them up.
  • The best and most important example of this is home directories for users on the network. Access to those directories is restricted to every user (including the network administrator) except the owner of the directory. Unless the user who is logged on is a member of the Backup Operators group, only the directories will be backed up, not the files inside.
  • Ensure that the user who will be backing up the files is added (by the network administrator) to the Backup Operators group in User Manager for Domains.
  • Windows NT Backup cannot be used to back up registries on remote computers.
  • Windows NT Backup has no scheduling capabilities of its own. It has to be run from the command prompt unless an outside scheduler is used. With an outside scheduler, it only launches the application or batch file. Even if there is a problem or failure during the backup, the schedule has already been completed just by the launch of the application. With an internal scheduler, the schedule is reset only when the application completes its task. Imagine your chagrin if you assumed the backup went as planned, but it had failed. You might get a message in the Event Viewer, but you might not.

 

email this to a friend | forum discuss
{feature}
{feature}
logo SoftwareTipsPalace.com : Newsletter | Email Signup | Guides, Tips, Tricks | YouTube Channel | subscribe to our rss

WebSite Links: Home | Forums | Blog | Web Mail | Windows | Software Reviews | How-To Features | Techs & Tests | Web 2.0 Reviews | Downloads

About Us | Privacy Policy | Terms of Use | Advertising Info | Contacts | FAQ's | Write for Us

{feature}