|
|
Repository management tools are handled through any Web browser, as shown in "VPN Console: File Menu." Additionally, you can run dbBackup from the command line to back up your repository, as shown in the "Backup from the Command Line" section, or to back up a repository using a third party backup program, as shown in the "Backup from Third Party Backup Program" section. Also, you can grant access permission to the Repository Management tools (see "Access Permission to Repository Management Tools" section).
This section provides the description and syntax for the dbBackup command that can be run from the command line to back up a repository.
The dbBackup command backs up a repository from the command line. You can run dbBackup from <MPLS VPN Directory>/bin/solaris.
dbBackup -db <dbpath> -dest <destDir> [-tar|-compress] [-v] [-log] [-help]
where:
-db <dbpath> is the path to the repository you wish to back up.
-dest <destDir> is the existing destination directory into which to place the backed up repository.
-tar indicates to tar the backed up repository into the existing destination directory.
-compress indicates to tar and compress the backed up repository into the existing destination directory.
-v indicates to supply verbose log output.
-log indicates to send information to log output.
-help indicates to print this message.
This section provides the description and syntax for the dbBackup command that can back up a repository using a third party backup program that is running with the same user ID as the VPN software.
The dbBackup command backs up a repository using a third party backup program. You can run dbBackup from <MPLS VPN Directory>/bin/solaris.
When you execute the dbBackup command, it automatically does the following:
1. Locks the repository
2. Executes your backup program
3. Unlocks the repository.
dbBackup -db <dbpath> -p "<progname -parameters>"
where:
-db <dbpath> is the path to the repository you wish to back up.
-p "<progname -parameters>" is the backup program name and all its parameters.
This section includes the following categories:
This feature allows you to specify which machines have access permission to the Repository Management tools. Without an access permission file, every machine has permission to use the Repository Management tools.
In UNIX, create a file in your install directory called SecureAccess.id. For example, if your install directory is My_Install_Directory, create the following file:
My_Install_Directory/etc/SecureAccess.id
Within this file, define the machines to which you want to permit and deny access permission, as specified in the section "Syntax of the Access Permission File." Then restart the httpd server by issuing the following command: wdclient restart httpd.
{permit | deny} {<IPaddress> | <MachineName> | <SubnetAddress>}
where:
You must choose one of the following two arguments:
permit gives access permission to the Repository Management tools.
deny denies access permission to the Repository Management tools.
You must choose one of the following three arguments:
<IPaddress> is the IP address of the machine.
<MachineName> is the name of the machine.
<SubnetAddress> is the address of the subnet of multiple machines.
The following example of an access permission file, SecureAccess.id, gives permission to the machine with the IP address 171.71.227.170 and the machine with the name machine1.company1.com to use the Repository Management tools. This example also denies permission to the machine with the name machine2.company1.com and the machines in the subnet 171.71.227.0/24 to use the Repository Management tools.
# start of the id file#
#
#
# end of the comment block
permit 171.71.227.170
permit machine1.company1.com
deny machine2.company1.com
deny 171.71.227.0/24
# end of the id file
Posted: Thu Apr 20 16:31:34 PDT 2000
Copyright 1989 - 2000©Cisco Systems Inc.