In NetWorker software releases 7.1 and later, if a VSS client license is present (for all Windows operating systems except Vista, which does not require a VSS client license), NetWorker software uses VSS technology to create snapshot backups of volumes and exact copies of files, including all open files. For example, databases and files that are open due to operator or system activity are backed up during a volume shadow copy. In this way, files that have changed during the backup process are copied correctly. Shadow copy (snapshot) backups ensure that: ◆ Applications can continue to write data to the volume during a backup. ◆ Open files are no longer omitted during a backup. ◆ Backups can be performed at any time, without locking out users.
ntuser.dat is the registry data for the locally signed in user - it should be backed up as part of the full registry backup in the relevant system saveset backup so not a worry. You should try to ensure people get in the habit of logging out of servers that they use. pst files may be more of a problem - it depends on your mail system what these are; my guess is probably that it is someone who has left themselves logged in and is archiving their mail to a server folder overnight. If that is the case the relevant mail data should be backed up as part of your Exchange backups and the pst will back up next time it is not locked open, but we would need more information to give a definite answer.
For locked files to be backed up you can use VSS, I'm not too sure if OFM is still around, it is pretty old technology and last I had anything to do with it was at least 6 years ago. However, these files look like SQL Server files - you have two options here, firstly you can purchase the Networker for MS SQL Server module which will enable you to do a "hot backup" which means you don't stop the database to back it up which is useful if your database is active around the clock. You can then create a directive to skip the database files. The other option is to stop the database prior to backing it up then restart it after the backup completes - to do this you would use the savepnpc (save pre and post processing command) backup command and have a script (and resource file) locally on the client that takes care of this - if this is what you choose to do check the manual and come back to us with any questions.
HabibG2
455 Posts
0
June 3rd, 2009 05:00
See note from Network Admin guide below.
In NetWorker software releases 7.1 and later, if a VSS client license is present (for all
Windows operating systems except Vista, which does not require a VSS client
license), NetWorker software uses VSS technology to create snapshot backups of
volumes and exact copies of files, including all open files. For example, databases and
files that are open due to operator or system activity are backed up during a volume
shadow copy. In this way, files that have changed during the backup process are
copied correctly. Shadow copy (snapshot) backups ensure that:
◆ Applications can continue to write data to the volume during a backup.
◆ Open files are no longer omitted during a backup.
◆ Backups can be performed at any time, without locking out users.
HabibG2
455 Posts
0
June 3rd, 2009 06:00
DavidHampson
2 Intern
•
1.1K Posts
0
June 3rd, 2009 07:00
pst files may be more of a problem - it depends on your mail system what these are; my guess is probably that it is someone who has left themselves logged in and is archiving their mail to a server folder overnight. If that is the case the relevant mail data should be backed up as part of your Exchange backups and the pst will back up next time it is not locked open, but we would need more information to give a definite answer.
DavidHampson
2 Intern
•
1.1K Posts
0
June 3rd, 2009 07:00
However, these files look like SQL Server files - you have two options here, firstly you can purchase the Networker for MS SQL Server module which will enable you to do a "hot backup" which means you don't stop the database to back it up which is useful if your database is active around the clock. You can then create a directive to skip the database files. The other option is to stop the database prior to backing it up then restart it after the backup completes - to do this you would use the savepnpc (save pre and post processing command) backup command and have a script (and resource file) locally on the client that takes care of this - if this is what you choose to do check the manual and come back to us with any questions.
jarady
2 Intern
•
132 Posts
0
June 14th, 2009 23:00
VSS, stands for what?
HabibG2
455 Posts
0
June 15th, 2009 02:00
Whilst we are happy to help, often to save yourself time, its worth google thing like this. Use the forum for more complex problem.