Sponsored Content
Full Discussion: Sun Solaris10
Operating Systems Solaris Sun Solaris10 Post 302094228 by DukeNuke2 on Thursday 26th of October 2006 05:43:40 AM
Old 10-26-2006
which dumps?
 

10 More Discussions You Might Find Interesting

1. Solaris

help,win2003 and solaris10 in a pc?

sorry,my english is poor. who can install win2003 and solaris10 in one pc ? my win2000server in hda1 so frist install win2003 in hda5 second install solaris10 in hda2 but after install over,the win2003 can't logon in. alway let me press<ctrl>+<alt>+<del>. why? (1 Reply)
Discussion started by: keyi
1 Replies

2. IP Networking

Detecting NIC in Solaris10

I have an E420 server that has a TPE Slot / NIC installed. However there is no interface file installed eg /etc/hostname.hme0 or equivalent. I have placed a private ip entry int the hosts file to accompany the loop back entry i.e. 127.0.0.1 localhost 172.16.0.10 loghost se420 ... (1 Reply)
Discussion started by: jimthompson
1 Replies

3. UNIX for Dummies Questions & Answers

Inst. Solaris10

I just download solaris 10, from sun.com, I have them ziped in my HD, How can I install them, so I can run solaris10, my present os is RH9; THANKS (5 Replies)
Discussion started by: mxlst14
5 Replies

4. Solaris

CMOS settings on SUN V20Z from Solaris10

Hello Guys, and good day to everybody. I am battling to redirect console on this V20Z 'beast', and would really like to know if it's possible to 'see' CMOS settings from Solaris10 point of view. Machine is remote and I can't easily go and reboot the box and press F2 etc... So is there a... (3 Replies)
Discussion started by: mponjevic
3 Replies

5. Solaris

Re: Crontab in solaris10

Hi all, I wrote a small shell (bash) script and it was executing well. I'm getting problem when I use this in crontab. My script is: #!/usr/bin/bash mkdir `date '+%m-%d-%y'` cd `date '+%m-%d-%y'` cvs co -r br_name module cd dir1/dir2/dir3 bash build.sh this is doing well... (7 Replies)
Discussion started by: gullapalli
7 Replies

6. Solaris

SUN Solaris10 DVD

Hello All, Please let me know how to order free sun sloaris10 dvd from sun microsystem? Prashant (1 Reply)
Discussion started by: prashant_ohol
1 Replies

7. Solaris

Using mailx under solaris10

Hello all. I am a new user Solaris10, on a sunblade100. And I need help. How to send an e-mail on command line under solaris 10 ? I try mailx-s "subject" snacks@yahoo.fr without success. I would like to know why? What files do I configure? Thank you in advance. best regards. (3 Replies)
Discussion started by: SnackS
3 Replies

8. Solaris

Solaris10

Hi All How can we verify if any of the parameters we have change in Solaris10 after reboot. Like is there any command? Please advice Thanks (3 Replies)
Discussion started by: imran721
3 Replies

9. Solaris

Msktutil on Solaris10

Technical Prose: Solaris integration with Active Directory - Part I follow this guide,install solarisgcc,and dev libraries required. But after configure i get checking for res_search... yes checking for krb5_init_context in -lkrb5... yes checking for ldap_initialize in -lldap... yes... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies

10. Solaris

Solaris10 and pxeLinux

I want to run solaris10 with my pxelinux server i put on pxelinux.cfg/default this LABEL solaris 10 kernel mboot.c32 append -solaris solaris/boot/platform/i86pc/kernel/unix -v -m verbose install dhcp nowin nfs://192.168.0.2/jumpstart/config.tar -B install_media=192.168.0.2:/solaris... (0 Replies)
Discussion started by: Linusolaradm1
0 Replies
BACKUP_DELETEDUMP(8)					       AFS Command Reference					      BACKUP_DELETEDUMP(8)

NAME
backup_deletedump - Deletes one or more dump records from the Backup Database SYNOPSIS
backup deletedump [-dumpid <dump id>+] [-from <date time>+] [-to <date time>+] [-port <TC port offset>] [-groupid <group ID>] [-dbonly] [-force] [-noexecute] [-localauth] [-cell <cell name>] [-help] backup dele [-d <dump id>+] [-fr <date time>+] [-t <date time>+] [-p <TC port offset>] [-g <group ID>] [-db] [-fo] [-n] [-l] [-c <cell name>] [-h] DESCRIPTION
The backup deletedump command deletes one or more dump records from the Backup Database. Either use the -dumpid argument to specify the dump ID number of one or more dumps, or use the -from and -to arguments to delete the records for all regular dumps created during the time period bracketed by the specified values. Use this command to remove dump records that are incorrect (possibly because a dump operation was interrupted or failed), or that correspond to dumps that are expired or otherwise no longer needed. CAUTIONS
The only way to remove the dump record for an appended dump is to remove the record for its initial dump, and doing so removes the records for all of the initial dump's associated appended dumps. The only way to remove the record for a Backup Database dump (created with the backup savedb command) is to specify its dump ID number with the -dumpid argument. Using the -from and -to arguments never removes database dump records. Removing records of a dump makes it impossible to restore data from the corresponding tapes or from any dump that refers to the deleted dump as its parent, directly or indirectly. That is, restore operations must begin with the full dump and continue with each incremental dump in order. If the records for a specific dump are removed, it is not possible to restore data from later incremental dumps unless the deleted records are restored by running the backup scantape command with the -dbadd flag. If a dump set contains any dumps that were created outside the time range specified by the -from and -to arguments, the command does not delete any of the records associated with the dump set, even if some of them represent dumps created during the time range. OPTIONS
-dumpid <dump id>+ Specifies the dump ID of each dump record to delete. The corresponding dumps must be initial dumps; it is not possible to delete appended dump records directly, but only by deleting the record of their associated initial dump. Using this argument is the only way to delete records of Backup Database dumps (created with the backup savedb command). Provide either this argument or the -to (and optionally -from) argument. -from <date time>+ Specifies the beginning of a range of dates; the record for any dump created during the indicated period of time is deleted. Omit this argument to indicate the default of midnight (00:00 hours) on 1 January 1970 (UNIX time zero), or provide a date value in the format mm/dd/yyyy [hh:MM]. The month (mm), day (dd), and year (yyyy) are required. The hour and minutes (hh:MM) are optional, but if provided must be in 24-hour format (for example, the value "14:36" represents 2:36 p.m.). If omitted, the time defaults to midnight (00:00 hours). The -to argument must be provided along with this one. -to <date time>+ Specifies the end of a range of dates; the record of any dump created during the range is deleted from the Backup Database. Provide either the value "NOW" to indicate the current date and time, or a date value in the same format as for the -from argument. Valid values for the year (yyyy) range from 1970 to 2037; higher values are not valid because the latest possible date in the standard UNIX representation is in February 2038. The command interpreter automatically reduces any later date to the maximum value. If the time portion (hh:MM) is omitted, it defaults to 59 seconds after midnight (00:00:59 hours). Similarly, the backup command interpreter automatically adds 59 seconds to any time value provided. In both cases, adding 59 seconds compensates for how the Backup Database and backup dumpinfo command represent dump creation times in hours and minutes only. For example, the Database records a creation timestamp of "20:55" for any dump operation that begins between 20:55:00 and 20:55:59. Automatically adding 59 seconds to a time thus includes the records for all dumps created during that minute. Provide either this argument, or the -dumpid argument. This argument is required if the -from argument is provided. Caution: Specifying the value "NOW" for this argument when the -from argument is omitted deletes all dump records from the Backup Database (except for Backup Database dump records created with the backup savedb command). -localauth Constructs a server ticket using a key from the local /etc/openafs/server/KeyFile file. The backup command interpreter presents it to the Backup Server, Volume Server and VL Server during mutual authentication. Do not combine this flag with the -cell argument. For more details, see backup(8). -cell <cell name> Names the cell in which to run the command. Do not combine this argument with the -localauth flag. For more details, see backup(8). -help Prints the online help for this command. All other valid options are ignored. OUTPUT
At the conclusion of processing, the output lists the dump IDs of all dump records deleted in the following format: The following dumps were deleted: dump ID 1 dump ID 2 etc. EXAMPLES
The following command deletes the dump record with dump ID 653777462, and for any appended dumps associated with it: % backup deletedump -dumpid 653777462 The following dumps were deleted: 653777462 The following command deletes the Backup Database record of all dumps created between midnight on 1 January 1997 and 23:59:59 hours on 31 December 1997: % backup deletedump -from 01/01/1997 -to 12/31/1997 The following dumps were deleted: 598324045 598346873 ... ... 653777523 653779648 PRIVILEGE REQUIRED
The issuer must be listed in the /etc/openafs/server/UserList file on every machine where the Backup Server is running, or must be logged onto a server machine as the local superuser "root" if the -localauth flag is included. SEE ALSO
backup(8), backup_dumpinfo(8), backup_scantape(8) COPYRIGHT
IBM Corporation 2000. <http://www.ibm.com/> All Rights Reserved. This documentation is covered by the IBM Public License Version 1.0. It was converted from HTML to POD by software written by Chas Williams and Russ Allbery, based on work by Alf Wachsmann and Elizabeth Cassell. OpenAFS 2012-03-26 BACKUP_DELETEDUMP(8)
All times are GMT -4. The time now is 08:33 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy