精华内容
下载资源
问答
  • Expiry date feature

    2020-12-02 20:22:54
    m implementing this in a pharmacy and their drugs has expiry date which they want to get notified when adding them. Does this feature exist? </p><p>该提问来源于开源项目:opensourcepos/...
  • Allow empty Expiry Date

    2020-12-02 10:16:30
    <div><p>I have a need to import a blank expiry date, however, Craft will automatically add the current timestamp if a null value is passed to the expiryDate field. <p>To overcome this I made a ...
  • Players expiry date

    2020-12-26 11:19:07
    <div><p>A suggestion from a client, a way to auto remove users who have been inactive for a length of time.</p><p>该提问来源于开源项目:PEXPlugins/PermissionsEx</p></div>
  • Gift Voucher expiry date

    2020-12-08 20:03:07
    <div><p>Normally Gift Vouchers would not be valid forever, normal is ...Thus the Gift Vouchers would need a option for setting the expiry date.</p><p>该提问来源于开源项目:arastta/arastta</p></div>
  • tape expiry is for the physical media. Think of it as shelf life. If you have a new tape and you do not want to use it after it is 3 years old then set the tape expiry to 3 years. After 3 years NetBac

    tape expiry is for the physical media. Think of it as shelf life. If you have a new tape and you do not want to use it after it is 3 years old then set the tape expiry to 3 years. After 3 years NetBackup will no longer write to it. Images that are on it may or may not have expired. If they have not expired then they can still be used for a restore.

    Image retention is how long the image written to the tape can be used to do a restore.

    if you have a tape that has a 3 year tape expiry and an image on it with a 7 year retention then the tape will no longer be able to be written to after 3 years and the image can no longer be used for a restore after 7 years.

     

    "Data expiration [or image expiration]: the date when the backups [images] on the volume [tape] expire"

    "Volume expiration [or tape expiration]: Indicates the age of the volume [tape]. If the volume expiration date is reached, the volume is considered too old to be reliable and no further mounts in write mode are allowed. NetBackup can mount the volume in read mode but writes a message to the system application log that the expiration date has been reached. If the column is blank, the volume has no expiration date.Note: This is the expiration date for the media itself not the expiration of any images stored on the media

     

    bpexpdate — change expiration date of backups in image catalog and media in media catalog

    bpexpdate -mmedia_id -ddate | 0 | infinity [-hostname] [-force] [-nodelete] [-notimmediate] [-Mmaster_server,...]

    DESCRIPTION

    NetBackup maintains catalogs, which are internal databases with backup image and media information. The image record in the image catalog contains an expiration date. The media ID in the media catalog also contains an expiration date. The expiration date is the date and time when NetBackup removes the record for a backup or a media ID from the corresponding catalog.

    The bpexpdate command allows the expiration date and time of backups to be changed in the NetBackup image catalog. The command is also used to change the expiration of removable media in the NetBackup media catalog. If the date is set to zero, bpexpdate immediately expires backups from the image catalog or media from the media catalog. When a media ID is removed from the NetBackup media catalog, it is also removed from the Enterprise Media Manager Database. It is removed regardless of the media's previous state (FROZEN, SUSPENDED, and so on).

    You can change the expiration on a media ID basis or on an individual backup ID basis. When you change the expiration date of a media ID, the expiration date of all backups on the media are also changed.bpexpdate also provides the following options:

    • Remove media from the media catalog if they no longer contain valid backups.

    • Recalculate the expiration date to base it on the configured or a supplied retention level.

    Any authorized user can run this command.

    For more information about NetBackup authorization, refer to theNetBackup Security and Encryption Guide.

    OPTIONS

    The different formats of the command are as follows:

    -backupid

    Changes the expiration of a single backup. If the date is zero, the backup is removed from the image catalog. If the backup is on removable media and the-d expiration is greater than the current media ID expiration, the media catalog expiration also changes. The change affects all copies of a backup, unless the-copy option is used. The-copy option causes only the specified copy to be affected.

    -deassignempty

    Searches the catalog for the removable media that no longer contain valid backups. It removes the media from the media catalog and removes the media IDs in the Media Manager catalog. The media is then available to use again. You can use the NetBackup Images on Media report to determine if the assigned media no longer contain valid backups.

    -m

    Changes the expiration date or removes the media ID from the media catalog and associated backups from the NetBackup catalog. A separate expiration date is maintained in the image catalog for each copy of a backup. When this format is used, only the expiration of the copy on the media is affected. If you remove the media ID from the media catalog by specifying a zero date, you also remove it in the Enterprise Media Manager Database.

    -recalculate

    Allows the expiration date of backups to be changed based on the specified retention level, or you can specify a new expiration date. When the expiration changes according to retention level, the new date is based on the creation date of the backup plus the retention level value. The expiration can be changed for a single backup, or for all backups for a particular client, policy, or schedule type.

    If the backup is on removable media, the expiration in the media catalog changes if the command expiration is greater than the current expiration.

    -stype server_type

    A string that identifies the storage server type. Possible values are AdvancedDisk, OpenStorage (vendorname), and PureDisk.

    OPTIONS

    -clientname

    Specifies the client name for the-backupid and-recalculate operations.

    For the backupid operation, this option causes NetBackup to first search for the backup ID for the specified client. This option is useful if the client name has changed.

    For recalculate, this option causes NetBackup to recalculate the expiration date to be based on the retention level for all the specified client backups.

    -copy number

    Expires or changes the expiration date of the specified copy number and is valid only with the-backupid and-recalculate options. Valid values are1 through 10.

    If the primary copy is expired, the other copy becomes the primary copy. If this option is not specified, the expiration affects both copies of the backup.

    -d date

    Specifies the expiration date and time. date can be any one of the following:

    • mm/dd/yy hh:mm:ss

    • 0 - the backup or media expires immediately

    • infinity - the backup never expires

    The required date and time values format in NetBackup commands varies according to your locale. The/user/openv/msg/.conf file (UNIX and Linux) and theinstall_path\VERITAS\msg\LC.CONFfile (Windows) contain information such as the date-time formats for each supported locale. The files contain specific instructions on how to add or modify the list of supported locales and formats.

    More information is available about the locale of your system.

    See the "Specifying the locale of the NetBackup installation" topic in theNetBackup Administrator's Guide, Volume II.

    -deassignempty

    Expires the removable media from the media catalog when that media no longer contain valid backups. It also deassigns the media ID in the Media Manager catalog.

    -dp disk_pool_name -dv disk_volume

    Specifies the disk pool and, optionally, the disk volume for the expiration date operation to be performed.

    -force

    Before you run the specified operation,bpexpdate queries before it starts the operation. This option forces thebpexpdate command to carry out the operation without querying the user.

    -host name

    Note:

    For the NetBackup server, this option is not required because only one server (the master) exists. If you do use the option, specify the host name of that server.

    Specifies the host name of the server to which the media is assigned. This option should be used only with the-mmedia_id option, and then only if the following is true: The master has remote media servers and the volume was not written on the server where you runbpexpdate.

    For example, assume that you have   a master server named whale and a media server named eel. You run the following command on whale to remove media ID BU0001 manually from the media catalog and all corresponding backups from the image catalog:

    bpexpdate -m BU0001 -d 0 -host eel

    You can use the NetBackup Media List report to determine which server's media catalog has the volume.

    -m media_id

    Specifies the media ID that the expiration date change affects. The expiration dates of the backups on the media ID also change. The-d option must be included with this option.

    This option can also be used when the -deassignempty option is specified to check if valid backups exist on this particular media ID. In this case, do not include the-d option.

    The media ID must be six or fewer characters and must be in the NetBackup media catalog.

    -M master_server [,...]

    Specifies the master server that manages the media catalog that has the media ID. If this option is not specified, the default is one of the following: For NetBackup server :

    NetBackup server  supports only one server (the master) with no remote media servers. Therefore, the default in this case is always the master server where you run the command.

    For NetBackup Enterprise Server:

    If the command is run on a master server, then that server is the default. If the command is run on a media server that is not the master, then the master for that media server is the default.

    -nodelete

    Deletes the backup from the image catalog but does not delete it from the disk storage. Use this option when you unimport a disk group from one master server and import the disk group to a different master server.

    -notimmediate

    Inhibits the call that bpexpdate makes to thenbdelete command after it expires an image on disk. If you intend to delete many images at the same time, use-notimmediate to avoid the overhead of multiple job creation fornbdelete to process. You can then run thenbdelete command later.

    -policy name

    Specifies the policy name and is valid with the-recalculate option. When the policy name is specified, the expiration is recalculated based on the retention level for all backups that are created in this policy.

    -recalculate

    Recalculates the expiration of backups that are based on the retention level or you can specify a new expiration date. You can include other options to change the expiration for a single backup, or for the following: All backups for a specific client name, policy name, or schedule type. Either the-d or-ret option must be specified with this option.

    -ret retention_level

    Specifies the retention level to use when you recalculate expiration dates and is valid with the-recalculate option. Levels range from 0 to 24. The new expiration date is the backup's creation date plus this retention level. You must specify either-backupid or-policy with this option.

    -sched type

    Specifies the schedule type and is valid with the-recalculate option. When the type is specified, the expiration is recalculated based on the retention level for all backups that are created with this schedule type. Enter a numeric value for type as follows:

    0 = Full

    1 = Differential Incremental

    2 = User Backup

    3 = User Archive

    4 = Cumulative Incremental

    The -policy option must be specified with-sched.

    NOTES

    Some options in large environments can take a significant amount of time to complete. Changes that cause backups or media to expire are irrevocable. You may be required to import backups or recover previous versions of the catalogs if you make mistakes by using this command.

    EXAMPLES

    Example 1 - The following command runs on the master server and removes media ID BU0002 from the media catalog. It deassigns the media ID in the media manager catalog. It also expires associated image records in the image catalog.

    # bpexpdate -m BU0002 -d 0

    Example 2 - Change the expiration of copy 2 of backupid eel_0904219764. It does not affect the expiration of copy 1 of the backup.

    # bpexpdate -backupid eel_0904219764 -d 12/20/2010 08:00:00 -copy 2

    Example 3 - Remove the backup from the image catalog. Since the-copy option is not specified, all copies are removed.

    # bpexpdate -backupid eel_0904219764 -d 0

    Example 4 - Check for media in the media catalog of hostcat that is still assigned, but no longer contain valid backups. The command removes any such media from the catalog and deassigns them in the media manager catalog.

    # bpexpdate -deassignempty -host cat

    Example 5 - Recalculate the expiration date of backup ID 1234 to the date 10/31/2010.

    # bpexpdate -recalculate -backupid 1234 -d 10/31/10

    Example 6 - Recalculate the expiration date of backup ID 1234 based on a retention level. The new retention level is 4 which is two months (default value). Backup ID 1234 is now scheduled to expire in 2 months.

    # bpexpdate -recalculate -backupid 1234 -ret 4 

     

     

    -------------------------------------------------------------

    Netbackup tips

     

    Starting and Stopping Netbackup

    Stopping Netbackup

    • /usr/openv/netbackup/bin/K77netbackup    --> graceful shutdown
    • /usr/openv/netbackup/bin/bpps -a   --> check for any remaining processes
    • /usr/openv/netbackup/bin/goodies/bp.kill_all   --->  kills all remaining netbackup processes, not necessarily graceful
    • /usr/openv/netbackup/bin/bpps -a   --> check for any remaining processes
    • kill -9 <pid>  for any remaining.   NOTE:  unkillable processes may require a reboot

    Starting Netbackup

    • /usr/openv/netbackup/bin/S77netbackup  --> after bp.kill_all, to restart

     

    Common Tasks

    Starting the Administration GUI

    • java from the windows client
    • x-windows from the server - /usr/openv/netbackup/bin/xnb &

    Checking Backup Status

    • Activity Monitor or
    • /usr/openv/netbackup/bin/admincmd/bpdbjobs -report

    Cleaning a tape manually

    • Identify the drive name to be cleaned
      • tpclean -L
    • Manually clean the drive:
      • tpclean -C <drive name>

    Determining what tapes were used for a backup

    • GUI
      • Backup and Restore --> Find the file system --> Preview Media Button
    • CLI
      • Find the correct backup images
        • bpimagelist -U -client <CLIENT> -d <STARTDATE> -e <ENDDATE>
      • Find the media used for those images
        • bpimagelist -U -client <CLIENT> -d <STARTDATE> -e <ENDDATE> -media

    Listing the files in a backup

    Find the tape(s) used (above procedure using bpimagelist)
    cd /usr/openv/netbackup/db/jobs/done
    Run the following script and redirect it's output to a text file:
            for file in `grep MOUNTING *|grep <MEDIA_ID>|awk '{print $1}'|sed 's/:MOUNTING//'`
            do
            echo $file
             grep PATH_WRITTEN $file|awk '{print $3}'
            echo " "
            echo "==========================================End of Image======================================"
            echo " "
            done


    This process works for NBU V3.4:

    • cd /usr/openv/netbackup/db/images/<CLIENT>
    • ls -ltr  -->  this will identify the directory with the proper date
    • verify directory with "bpdbm -ctime <Unixtime>
    • cd <Unixtime>
    • ls -ltr --> lists all of the backups for this client on this date
    • cat <POLICY>_<Unixtime>_<BU Type>.f | awk '{print $10}'  --> this prints out the files in the backup


    For NBU > V3.4

    • bpflist  --help   --> undocumented netbackup command to list files from a binary .f file



    Inventory the Robot

    • Inventory Robot  -->  /opt/openv/volmgr/bin/vmcheckxxx -rt robot_type -rn robot_number -list  (where robot_type is tld, acs, . . .)
    • Inventory Robot and Update Configuration -->  /opt/openv/volmgr/bin/vmupdate -rt robot_type -rn robot_number -list  (where robot_type is tld, acs, . . .)

    Listing Properties of the Volume Pools

    • vmpool -listall

    Scratch Tapes

    • Count scratch tapes:  /usr/openv/volmgr/bin/vmquery -pn Scratch | grep -c "robot slot"
    • Moving tapes to the scratch pool
      • If Needed - Expire the tape
        • bpexpdate -ev <TAPE ID> -d 0 -force -host <Media Manager>
      • Move the tape
        • vmchange -p 2 -m <TAPE ID>

    Checking Drive Usage

    • /usr/openv/volmgr/bin/vmoprcmd

    Taking a drive down or up

    • /usr/openv/volmgr/vmoprcmd -down <drive index>
    • /usr/openv/volmgr/vmoprcmd -up <drive index>


    Performing a Restore

    • From the GUI
      • user backup & restore --> configuration --> client
      • user backup & restore --> configuration --> client to restore
      • directory to search
      • directory depth
      • date range
      • file --> browse backups for restore

    Adding New Tapes to the Library

    • Using the GUI
      • Media Management --> Actions --> New --> Single Volume . .  -->
      • Media Type (ie DLT)
      • Robot Type (ie TLD)
      • Media ID (from Inventory)
      • Slot Number (from Inventory)
      • Robot Number (ie 0)
      • Volume Group
      • Volume Pool (ie Scratch)
    • Using the CLI
      • vmadd -m <media id> -mt <tape type> -verbose -rt <robot type> -b <barcode> -rn <robot number> -rc1 <slot> -p <pool number> -mm <max mounts>
        • vmpool -listall  --> lists all pools, both name and number
      • For example:  vmadd -m 000151 -mt dlt -verbose -rt tld -b 000151 -rn 0 -rc1 8 -p 2 -mm 0

    Re-using Tapes from other systems or older Netbackups

    • Expire the media
      • bpexpdate -ev MEDIA_ID -d 0 -force -host HOST
    • Deassign the media
      • vmquery -deassignbyid MEDIA_ID 4 0
    • Move to the scratch pool
      • vmchange -m MEDIA_ID -p POOL#
    • Relabel the media
      • bplabel -ev CIM572 -d dlt -p Scratch

    Changing the attributes of media

    • Changing the barcode
      • vmchange -barcode CYM100D -m CYM100
    • Changing the Volume Pool
      • vmchange -m MEDIA_ID -p POOL#


    To expire media

    • bpexpdate -ev <medai id> -d 0 -force -host <media server>

    To unfreeze media

    • List the frozen media
      • /usr/openv/netbackup/bin/goodies/available_media | grep -i FROZEN
    • Unfreeze the media
      • bpmedia -unfreeze -ev <media id> -h <media server>

    To relabel a tape

    • bplabel -ev <media id> -d <tape density> -p <pool name>
    • bplabel -ev 000687 -d dlt -p TriVrgt_OFFSITE

    To remove media from the Netbackup database

    • Verify that there are no images on the tape
      • bpimmedia -mediaid 000687 -L
    • Expire the tape
      • bpexpdate -ev 000687 -d 0 -host scorpius -force
    • Get the status and pool number of the tape
      • vmquery -m 000687
    • Deassign the tape
      • vmquery -deassignbyid <media id> <pool number> <status code from vmquery -m>
      • vmquery -deassignbyid 000687 4 0x0
    • Delete the tape
      • vmdelete -m 000687


    Installing the Netbackup Client

    • /update_clients -ForceInstall -ClientList /tmp/clients.lst
      • requires that TMPDIR and TEMPDIR be set correctly

    Excludng files from backup on a client

    • Create /usr/openv/netbackup/exclude_list
    • Put the file specifications of the files/directories to be excluded
      • /mnt/directory/*

    Displaying Information about a Tape

    • vmquery -m <media id>   --> Displays attributes about a particular tape
    • bpmedialist -U -mcontents -ev 000687   --> Displays media contents
    • bpmedialist -U -mlist  --> List of all media
    • bpmedialist -U -mlist -ev CYM966  --> Listing of a particular media id
    • bpimmedia -mediaid 000687 -L   --> Listing of images on a tape

    Robtest Commands

    • Starting robtest
      • robtest
      • 1  --> to select TLD 0
    • Getting help
      • ?
    • Looking at contents of the tape drives
      • s d
    • Looking at the contents of the library
      • s s
    • Moving a tape from a drive to a library slot
      • s d  --> to identify drive number that has tape (Contains Cartridge = yes, Barcode=XXXXXX)
      • s s  --> to identify an empty slot in the tape library (Netbackup will need to be re-inventoried)
      • m d# s#  --> from from drive # to slot #
      • s d  --> verify the tape drive is empty
      • s s --> verify the library slot has the tape



     

    Configuration Files

    /usr/openv/netbackup/bp.conf

    • configuration file, sets backup server and backup clients
    • force statement must be correct
    • client to browse from
    • client to restore to

    /usr/openv/volmgr/vmconf

    Logfiles

    To utilize logfiles, create the corresponding directory in /usr/openv/netbackup/logs

    Server Logfile directories:

    • admin - adminstrative commands
    • bpbrm - backup and restore manager
    • bpcd - client daemon
    • bpdbjobs - database manager program process
    • bpdm - disk manager process
    • bpjava-msvc - Java application server authentication service
    • bpjava-usvc - process that services Java requests
    • bprd - request daemon process
    • bpsched - scheduler process that runs on master servers
    • bptm - tape/optical media management process
    • user-ops - required directory for use by Java programs
    • xbpadm - X based administration utility
    • xbpmon - X based job monitor process

    Client Logfile directories:

    • bp - client user interface process
    • bparchive - archive program
    • bpbackup - backup program
    • bpbkar - program that generates golden images
    • bpcd - client daemon
    • bpjava-msvc - Java application server authentication service
    • bpjava-usvc - process that services Java requests
    • bplist - program that lists backed up and archived files
    • bpmount - program that determines local mountpoints  and wildcard expansion for multiple streams
    • bphdb - Oracle database backup program start process
    • db_log - database specific extension log
    • tar - tar process log during restores
    • user_ops

    Media Manager logging automatically goes to the system log using syslogd logging facility

    .Logging will only occur if these directories are created.  These directories will generate a lot of data and should be deleted when no longer necessary.

    To increase the amount of logging information set VERBOSE=2 in /usr/open/netbackup/bp.conf  (default is VERBOSE=1)

    Processes

    ltid
    acsd
    vmd


    Useful Commands


    bpcllist - list classes
    bpclinfo <class> -L   --> displays info about a class
    vmpool - volume pools
    vmpool -listall
    vmpool -listscratch
    bplabel -ev <media id> -d hcart
    bpbackup db  --> backs up the catalog
    bpclclients <policy>  --> lists the clients for a particular policy (class)

    Troubleshooting

    bperror -statuscode   <-- displays information about the  netbackup error.

    No Backups are running:

    • Check system log file for error messages
    • Stop and restart all the netbackup processes
    • Look for a downed drive
      • /usr/openv/volmgr/bin/vmoprcmd
      • /usr/openv/volmgr/bin/vmoprcmd -up 0   --> this will bring up drive 0 if it's control shows as down
    • Look for pending requests
      • /usr/openv/volmgr/bin/vmoprcmd or gui --> device management
      • If there is a pending request either re-assign it to a drive, or deny the request

    Downed drive does not come back up or does not stay up

    • Check for a hardware problem by looking for messages on the tape library
    • Make sure there is not a tape stuck in the drive
      • Use robtest (described above) to look at the drives
        • If there is a tape stuck in the drive, try to remove it using robtest
        • If robtest fails, then you must manually remove it.

    Verify the Client is communicating properly:

    • bpclncmd -ip  <ip address>  --> from both client and server
    • bpclntcmd -hn <hostname>  --> from both client and server
    • bpclntcmd -pn    -->  from client only


     

    Device Actions

    Device Management --> info about tape drives

    • dlt
    • hcart (ultrium)

    Media Actions

    Media id must agree with # of the tape
    Create a media id

    • actions -->new-->single volume-->dlt cart (not dlt2)
    • put it into the "netbackup" volume pool

    Netbackup Client


    To check things out do this:

    It could be a couple things.  Mostly DNS, bp.conf, or something stupid.  On
    the client run this command

    /usr/openv/netbackup/bin/bpclntcmd -pn

    /usr/openv/netbackup/bin/bpclntcmd -server "server name"

    /usr/openv/netbackup/bin/bpclntcmd ip "ip_address"

    -----------------------------------------


    tpclean” Command

    Runing the “tpclean –L” command from the master server will provide the information regarding whether or not a drive needs cleaning and what the accumulated mount time is. In the following example you can see that drive  IBM.ULTRIUM-TD3.008     needs cleaning. It should be automatically cleaned after 360 hours of accumulated mount time but as you can see it still has not been cleaned. The issue may be there are no appropriate cleaning tapes in the library or there are zero remaining cleanings. Correcting this situation will result in the drive being automatically cleaned.

    bash-2.05$ sudo ./tpclean -L

    Password:

    Drive Name              Type      Mount Time  Frequency   Last Cleaned         Comment

    **********              ****      **********  *********   ****************     *******

    IBM.ULTRIUM-TD3.006     hcart3*   315.9       360         08:55 06/07/2011

    IBM.ULTRIUM-TD3.007     hcart3*   0.0         360         11:53 06/28/2011

    IBM.ULTRIUM-TD3.008     hcart3*   526.4       360         17:14 05/21/2011     NEEDS CLEANING

    ----------------------------------

    netbackup commands

     

    NetBackup Command Guide

    Submitted by Igor on December 27, 2009 – 7:17 pm4 Comments

    NetBackup is an enterprise-level distributed backup and recovery application. The environment consists of the master server, media server, storage library, networking hardware, and client agents. NetBackup supports a wide variety of Unix, Linux, VMS, and Windows systems. The original backup solution was developed by Control Data Corp., later acquired by Openvision, which gave the product its “NetBackup” name. NetBackup was then bought by Veritas and is currently owned and supported (poorly) by Symantec.

    Daemons and Processes

    On the master server there are four NetBackup daemons started in sequence:

    1. bprd – the request daemon started during system boot
    2. bpsched – the scheduler daemon started by bprd
    3. bpdbm – the NetBackup database manager started by bpsched
    4. bpjobd – the job monitor daemon started by bpdbm

    One the media server, there are up to nine NetBackup daemons:

    1. bpcd – communications daemon started during system boot
    2. bpbrm - backup and restore manager started by bpcd
    3. bptm - tape manager started by bpbrm
    4. bpdm - disk manager started by bpbrm
    5. ltid - media manager started during system boot
    6. avrd - bar code reader daemon started by ltid
    7. vmd - volume manager daemon started by ltid
    8. tldd - robotic tape library daemon started by ltid
    9. tldcd - robotic tape library control daemon started by ltid

    One the client side, there is one NetBackup daemon started during system boot:

    1. bpcd – the client daemon, which starts the bpbkar processes for each active backup or restore job

    Logs and Configuration Files

    Version and patch levels

    1. NetBackup and patch versions: /opt/openv/netbackup/bin/version
    2. Patch level history: /opt/openv/netbackup/patch/patch.history
    3. Media version: /opt/openv/volmgr/version

    Configuration Files

    1. NetBackup configuration: /opt/openv/netbackup/bp.conf
    2. Media manager configuration: /opt/openv/volmgr/vm.conf
    3. Buffer size: /opt/openv/netbackup/db/config/SIZE_DATA_BUFFERS
    4. Number of buffers: /opt/openv/netbackup/db/config/NUMBER_DATA_BUFFERS
    5. Network buffer size: /opt/openv/netbackup/NET_BUFFER_SZ (default is 32)
    6. Catalog type: /opt/openv/netbackup/db/config/cat_format.cfg

    Access control

    1. Java GUI authorization: /opt/openv/java/auth.conf

    Troubleshooting

    1. Corrupt database images: /opt/openv/netbackup/db.corrupt

    (The following is the corrected and expanded information found at http://www.datadisk.co.uk/html_docs/veritas/veritas_netbackup_cs.htm)

    Server Commands

    Check license details /opt/openv/netbackup/bin/admincmd/get_license_key
    Start Netbackup netbackup start

    /opt/openv/netbackup/bin/initbprd  (master)
    /opt/openv/volmgr/bin/vmd (media)

    Stop Netbackup (does not disconnect GUI sessions) netbackup stop

    /opt/openv/netbackup/bin/admincmd/bprdreq -terminate  (master)
    /opt/openv/netbackup/bin/bpdbm -terminate (master)

    Stop Netbackup and kill all GUI sessions /opt/openv/netbackup/bin/goodies/bp.kill_all
    Start the GUI /opt/openv/netbackup/bin/jnbSA
    Scan for tape devices sgscan (solaris)
    ioscan (HPUX)
    Display all Netbackup processes bpps -a
    lists servers errors

    bperror -U -problems -hoursago
    bperror -U -backstat -by_statcode -hoursago

    display information on a error code bperror -statuscode [-recommendation]
    Reread bp.conf file without stopping Netbackup bprdreq -rereadconfig
    Check database consistency bpdbm -consistency 1
    bpdbm -consistency 2

    Check for the below lines:
    Bad image header
    Does not  exist

    Netbackup Recovery
    Device catalog is intact bprecover -l -m -d dlt  (listing)
    bprecover -r -m -d dlt (recovering)
    Device catalog is gone or corrupted bprecover -l -tpath (listing)
    bprecover  -r -tpath (recovering)
    Disk backups bprecover -l -dpath (listing)
    bprecover  -r -dpath (recovering)

    Catalog Commands

    Master Server
    Information about backed-up files image – /opt/openv/netbackup/db
    Storage Unit, Global Configuration, Catalog backup configuration. config – /opt/openv/netbackup/db
    Backup Policy information class – /opt/openv/netbackup/db
    Job status information jobs – /opt/openv/netbackup/db
    Netbackup logs with error and status information error – /opt/openv/netbackup/db
    Information on volumes, volume pools, scratch pool and volume  groups volume – /opt/openv/volmgr/database
    Media Server
    Tracks assigned volumes (media that has data them) media – /opt/openv/netbackup/db
    Information about devices managed by the media server device – /opt/openv/volmgr/database

    Volume Commands

    Tape Drive and Inventory Commands
    List drive status, detail drive info and pending requests vmoprcmd
    List the tape drive status vmoprcmd -d ds
    List the pending requests vmoprcmd -d pr
    Control a tape device vmoprcmd [-reset][-up][-down]
    List all changes in the robot(but do not update) vmupdate -recommend -rt tld -rn 0

    vmcheckxxx -rt tld -rn 0 -recommend

    Empty the robot and re-inventory (using barcodes) vmupdate -rt tld -rn -rh -vh -nostderr -use_barcode_rules -use_seed  -empty_ie
    Tape Media Commands
    List all pools vmpool -listall -bx
    List tapes in pool vmquery -pn -bx
    List all tapes in the robot vmquery -rn 0 -bx |grep ‘TLD’ | sort +4
    List cleaning tapes vmquery -mt dlt_clean -bx
    List tape volume details vmquery -m
    Delete a volume from the catalog vmdelete -m
    Change a tapes expiry date vmchange -exp 12/31/06 23:59:58 -m
    Change a tape’s media pool vmchange -p -m

    Media Commands

    List the storage units bpstulist -U
    Freeze or unfreeze media bpmedia [-freeze][-unfreeze] -ev
    List media details bpmedialist -ev
    List media contents bpmedialist -U mcontents -m
    List backup Image Information bpimagelist -backupid
    Expire client images bpimage -cleanup -allclients
    Expire a tape bpexpdate -d 0 -ev -force
    List all netbackups jobs bpdbjobs -report [-hoursago]
    Move media from one media server to another bpmedia -movedb -newserver   -oldserver

    Tape/Robotic Library Commands

    List tape drives tpconfig -d
    List cleaning times on drives tpclean -L
    clean a drive tpclean -C
    change a drives cleaning frequency tpclean -F
    set a drives cleaning time to zero tpclean -M
    Move tapes within robot using robtest robtest

    commands that can be used are as follows:

    s s       (show slots)
    s  d       (show drives)
    s i       (show load port)
    m s250 d5 (move tape from  slot 250 into drive 5)
    uload d5  (unload tape from drive 5)
    m d5 s250  (move tape from drive 5 to slot 250)
    m s250 i1 (move tape from slot 250 to  load port 1)

    List load port tapes echo “s i q” | tldtest -r /dev/sg/c0t4l0
    List all slot contents echo “s s q” | tldtest -r /dev/sg/c0t4l0
    List tape drive contents echo “s d q” | tldtest -r /dev/sg/c0t4l0
    Move a tape in s100 to drive 1 echo “m s100 d1″ | tldtest -r /dev/sg/c0t4l0
    Move a tape to load port 1 echo “m s100 i1″ | tldtest -r /dev/sg/c0t4l0

    Archiving Commands

    list archive info bpcatlist -client all -before Jul 01 2006
    bpcatlist -client all -before  Aug 01 2006
    archive and remove images bpcatlist -before Jul 01 2006 | bpcatarc | bpcatrm
    restore archive files bpcatlist -before Jul 01 2006 | bpcatres

    Client Commands

    test client connectivity bpclntcmd [-ip ]
    bpclntcmd [-hn  ]
    bpclntcmd [-pn]
    bpclntcmd [-sv]

     

     

    展开全文
  • <p>Also see from 9 months ago: <a href="https://wordpress.org/support/topic/listing-expiry-date-isnt-working-correctly/">Listing Expiry Date isn't working correctly</a></p>该提问来源于开源项目&#...
  • <p>I saw you deleted the optionnal argument expiry date on the keyword : add cookie. <p>Is there any way to add this option again? I want to add an expiry date on my cookie. <p>Thanks</p><p>该提问...
  • <div><p>Some gateways accept the expiry date as MM/YY only. But the form takes MM/YYYY too and this is causing transactions to fail because of if people enter the full year our gateway send back an ...
  • Adding expiry date to items

    2020-12-02 13:19:48
    <div><p>I added the expiry date attribute to the item, it can be very useful for those who has to manage even the expiry dates. </p><p>该提问来源于开源项目:opensourcepos/opensourcepos</p></div>
  • <div><p>Once expiry date field is set and save it is not possible to leave it blank. Even cleaning and saving it will keep last expiry date set. <p>Reproducing this issue: Settings > Announcements...
  • ve tried, the expiry date seems to be ignored. There appears to be nothing helpful in the log indicating a failed attempt to detect expiry, but maybe that's simply because there is no such log ...
  • Expiry date is not showing

    2020-12-27 18:20:40
    <div><p>The old (0.98 version) of Certify displayed the expiry date. Not so in 2.x alpha version.</p><p>该提问来源于开源项目:webprofusion/certify</p></div>
  • Expiry date is nil

    2020-12-28 06:33:40
    <div><p>Hi, <p>After decoding any JWT token, I would always get a <code>nil</code> value for <code>expiresAt</code> and <code>false</code> for <code>expired</code>. I managed to make it work by ...
  • <p>The date from the Listing Expiry Date field gets the current date when trying to edit the date <h4>Steps to Reproduce the Bug <ol><li>Add a listing through the front-end;</li><li>Go to dashboard ...
  • s expiry date, you need to remove the key, and re-upload it with the new expiry-signatures. <p>It would be nice if the keyserver would detect these signatures, and update the key accordingly. User ...
  • Expiry date is one day off

    2020-12-06 19:07:05
    <div><ol><li>Create a new key</li><li>Set expiry date to 3. feb 2014</li><li>save</li><li>open key again, expiry is 2. feb 2014</li></ol>该提问来源于开源项目:open-keychain/open-keychain</p></...
  • Set user account expiry date

    2012-10-25 16:41:00
    One useful feature of AD is that we can set an expiry date on an account – very useful for temporary workers or if we know someone is leaving at on particular date. The expiry date is stored in AD as...

    One useful feature of AD is that we can set an expiry date on an account – very useful for temporary workers or if we know someone is leaving at on particular date. The expiry date is stored in AD as the number of  100 nanosecond intervals since 1st January 1601 – this is stored as a 64 bit integer

    $date = Get-Date             
    $ou = "OU=England,DC=Manticore,DC=org"            
                
    "`nMicrosoft"            
    $name = "UserA"            
    $exp = $date.Adddays(30)            
    Get-ADUser -Identity $name |            
    Set-ADAccountExpiration -DateTime $exp            
                
    "`nAD provider"            
    $name = "UserB"            
    $dn = "cn=$name,$ou"            
    $exp = $date.Adddays(60).ToFileTime()            
    Set-ItemProperty -Path AD:\$dn  -Name accountExpires -Value $exp -Force            
                
    "`nQuest"            
    $name = "UserC"            
    $exp = $date.Adddays(90)            
    Get-QADUser -Identity $name |            
    Set-QADUser -AccountExpires $exp            
                
    "`nScript"            
    $name = "UserD"            
    $dn = "cn=$name,$ou"            
    $exp = $date.Adddays(120).ToShortDateString()            
    $user = [adsi]"LDAP://$dn"            
                
    $user.AccountExpirationDate = $exp            
    $user.SetInfo()

    In all cases I’ve added a number of days to todays date to give the expiry date. it would be just as easy to specify a particular date.

    The Microsoft cmdlets use Set-AdAccountExpiration and a datetime object

    The Quest cmdlets and script accept a date in short date format.

    The provider expects an integer – we can can convert the date using ToFileTime() method

    Notice the different attribute names between the script and the provider

    转载于:https://www.cnblogs.com/ahjxxy/archive/2012/10/25/2739113.html

    展开全文
  • <p>I have this issue since V1.9.6 which always showed the renewal dates in letsencrypt.exe one month after the expiry date of the certificate. <p>Now with the new win-acme version 1.9.10 it turned ...
  • Can't recognize expiry date

    2020-11-30 06:27:02
    scanIntent.putExtra(CardIOActivity.EXTRA_REQUIRE_EXPIRY, true); startActivityForResult(scanIntent, CreditCardActivity.SCAN_CARD_REQUEST_CODE)</code></p> <p>Both card number and the expire date of the ...
  • <p>i need to implement a feature that would notify the user that his password will expire soon and then expire when it reaches a certain date. <p>need this for more security reasons, is there a chance...
  • s Number or expiry date is being scanned which is invalid for Card B. <p>So as per my analysis, this is card.io limitation. If anyone is facing same issue kindly share your's thought.</p><p>该提问...
  • while some other are often travelling, so they may need very different configuration related to notification of upcoming tip expiry time.</p><p>该提问来源于开源项目:globaleaks/GlobaLeaks</p></...
  • In iOS, 05/30 is cut off expiry date. 14 years, 11 months, 24 days including the end date. <p>But in Android, 12/30 is valid expiry date. In Android, Cut off date is 01/31. Difference is 15 years, 6...
  • <div><p>嗨 Jrohy 数据库通过导出 再导入后提示 expiryDate 数值为 Null 看了下是原来没有设置逾期日期的项目(就是原默认无限制)需要手动填写数据库数值后才能 面板刷新才看到数据,要不就一直...
  • m only missing a lifetime setting / expiry date for the cached data. Even when querying a regularly changing database a ("short", e. g. 1 day) cache time would be greatly appreciated. But when...
  • # HELP probe_ssl_earliest_cert_expiry Returns earliest SSL cert expiry in unixtime # TYPE probe_ssl_earliest_cert_expiry gauge probe_ssl_earliest_cert_expiry 1.590835718e+09 # HELP probe_success ...
  • <p>When clients enter their card number to make a payment, some clients with card expiry month on October "10" can not proceed to payment. The problem occurs because when the choose the expiry...
  • <p>Move expiry date to flyout, with a clock icon <img alt="flyoutexpiry" src="https://img-blog.csdnimg.cn/img_convert/f62461180fbe813c60a83f1f7169858c.png" /></p> </li></ol> <p>Sketch file: ...
  • <p>The native checkout pass the card validation even if the card is expired (expiry date in the past). However the validation works for card number <p>Card details: Card name: any string Card number: ...
  • <div><p>Example throws an InvalidCreditCardException</p><p>该提问来源于开源项目:thephpleague/omnipay</p></div>

空空如也

空空如也

1 2 3 4 5 ... 20
收藏数 1,348
精华内容 539
关键字:

dateexpiry