Managing Backup Policies (Classes)
39
3
In our example client list, mercury is a server and has a large amount of
data. To avoid excessively long backup times, we put mercury in a separate
class called S1 and the workstations in a class called WS1. Later, we may
find that we need more than one class to back up mercury, but we will
evaluate other factors first. For now, the classes are as follows:
3. Create classes to accommodate special storage requirements.
The storage unit and volume pool settings apply to all files that are backed
up by the class. If files have special storage unit and volume pool
requirements, create separate classes for them, even if other factors, such as
schedules, are the same.
In our example (see below), we create a separate class (S2) for
D:\h002\R&D
and
D:\h002\Desdoc
on mercury because those files go on
DLT tape. Other files on mercury go on 8 mm tape. If it is necessary to keep
backups for some files on separate media, create a class that specifies a
unique volume pool for those backups. Then, add the media for that
volume pool as explained in the Media Manager Administrator’s Guide -
Windows NT Server.
Class
Clients
S1
mercury (file server)
WS1
mars
jupiter (workstations)
neptune
pluto
Class
Clients
Files
Desired
Storage
S1
mercury
C:\
D:\User
D:\h001
E:\h002\Projects
8 mm
S2
mercury
mercury
E:\h002\R&D
E:\h002\Desdoc
dlt
NetBackup 3.2 System Administrator's Guide for Windows NT
NetBackup 3.2 System Administrator's Guide for Windows NT
