Sponsored Content
Operating Systems Solaris What is an Ideal Backup Strategy Post 62169 by Phantom on Saturday 12th of February 2005 04:59:25 AM
Old 02-12-2005
Quote:
Originally Posted by una
What is an Ideal Backup Strategy
depends on:

1. Size of data (you already indicated 300 GB). What data out this is most important and should be recovered first if data disaster occurs ? Categorize your data.
2. Type of data (Oracle/Sybase/any database, Mail server, development stuff... ) depending on recovery requirements.
3. How frequently your data is changing or what is the daily rate of these changes. Categorizing your data on that basis would be very helpful.
4. What is your downtime window (if any) your business can afford on daily or weekly basis.
5. Do you have intensive data update through off-hour batch processings ?
6. For how long you are required to keep your data. This may be different for different data categories you want to backup.

Without taking above factors into account it's very hard to talk about "Ideal" backup strategy.

Generally speaking,

1. Weekly Full backups for flat file data and cold backup for database (if possible)

2. Daily incremental backups for flat file data and hot backups for database.

3. keeping backups for two months at least.

would make sence in most cases. However, to make it ideal for your business you need to "fine tune" this strategy based on the factors I talked in the begining of my post.

of course, storing some backup volumes off-site is very important.

Last edited by Phantom; 02-12-2005 at 06:30 AM..
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

Strategy to concatenate and backup files

I need to be able to concatenate all the files in a directory into a new filename and a different directory. I want to append the date in YYYYMMDD format to the new filename (ie, newfilename_20090207). The original files will have different filenames so I will need to be able to loop thru each... (1 Reply)
Discussion started by: Ryan2786
1 Replies

2. Solaris

what is ideal temp for US-III+

Hi all, is it okay for US-III+ running at 1200 MHZ to excced 75° C on sun fire 880 here's the output when i ran prtdiag -v on sunfire 880 running solaris10 bash-3.00# prtdiag -v System Configuration: Sun Microsystems sun4u Sun Fire 880 System clock frequency: 150 MHz Memory size: 8192... (2 Replies)
Discussion started by: h@foorsa.biz
2 Replies

3. Red Hat

max/ideal value of items in limits.conf in rhel5?

i want to set limits in /etc/security/limits.conf.My os is rhel 5.2. It was giving continuous messages in in /var/log/secure like : continuously. I have changed values of priority and nice to "0" from unlimited and messages are not comming. But i want to know what is the ideal/maximum... (3 Replies)
Discussion started by: pankajd
3 Replies

4. AIX

How do I killed ideal users from AIX 5.3 smit?

Hi, I'm newbee to AIX and would like to setup a process which kills 1 Hr. ideal users from smit. Please advise for making it work. :) Thanks, Sumit (2 Replies)
Discussion started by: sumit30
2 Replies

5. Shell Programming and Scripting

rsync backup mode(--backup) Are there any options to remove backup folders on successful deployment?

Hi Everyone, we are running rsync with --backup mode, Are there any rsync options to remove backup folders on successful deployment? Thanks in adv. (0 Replies)
Discussion started by: MVEERA
0 Replies

6. Slackware

Ideal partition sizes of 17 gb space.

I am planning to install slack 13.37 on an old stand-alone PIII (512 mb ram) with 17 gb disk space. I need to keep lotsa pdf, chm type e-books for programming with few other misc. documents. I'm going to use this system for my personal use. It has no network but I browse internet with cable... (0 Replies)
Discussion started by: vectrum
0 Replies
nisbackup(1M)                                             System Administration Commands                                             nisbackup(1M)

NAME
nisbackup - backup NIS+ directories SYNOPSIS
nisbackup [-v] backup-dir directory... nisbackup [-v] -a backup-dir DESCRIPTION
nisbackup backs up a NIS+ directory object on a NIS+ master server. Updates to the NIS+ database will be temporarily disabled while nis- backup is running. The backup-dir is a UNIX directory that must exist prior to running nisbackup. The nisbackup command can be used to backup an individual NIS+ directory object or all ( -a) of the NIS+ directory objects served by a master server. The NIS+ directory objects being backed up will be placed into subdirectories under the backup-dir directory. These subdirectories are named according to the NIS+ directory object they contain. nisbackup operates on individual NIS+ directory objects (for example, org_dir.wiz.com). This allows an administrator to selectively backup specific directories. The rpc.nisd(1M) process must be running on the master server with a stable NIS+ database for nisbackup to complete. nisbackup will not attempt to correct any corruption in the NIS+ database, so it is important that backups be done regularly as part of the NIS+ administra- tion. The first synopsis is used to backup a single NIS+ directory object or a list of NIS+ directory objects. The objects can be partially qual- ified or fully qualified. The machine on which the command is executing must be the master for the NIS+ directory objects specified. The second synopsis will backup all of the NIS+ directory objects that are served by this master. The -a option is the recommended method of backing up a master server, since it will backup all NIS+ directory objects that are served by this master. If this server is a master server for more than one domain, the backup will include NIS+ directories that belong to all of the domains served. Individual NIS+ direc- tory objects can be selected for restoring from a backup-dir created with the -a option. See nisrestore(1M). The -a option only includes directory objects for which this server is the master. It is possible, but not recommended, to configure a master server as a replica for other domains. The objects belonging to those replicated domains will not be backed up with the -a option. The backup of replicated objects must be run on the master server for those objects. Do not use the same backup-dir to backup different master servers. Each master server must have its own backup-dir. nisbackup will set the rpc.nisd(1M) to read only mode, which will disable updates to the NIS+ database. This is neccessary to ensure the consistency of the backup. For this reason, nisbackup should not be run while large numbers of updates are being applied to the NIS+ data- base. Update utilities such as nisaddent(1M) should not be run simultaneously with nisbackup. OPTIONS
-a Creates a backup of all NIS+ directory objects for which this server is a master. -v Verbose option. Additional output will be produced and sent to syslog(3C) upon execution of the command (see syslog.conf(4)). OPERANDS
backup-dir The directory into which the subdirectories containing the backed up objects are placed. This must be created prior to running nisbackup. directory The NIS+ directory object(s) being backed up. EXAMPLES
Example 1: Backup of the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup To backup the org_dir NIS+ directory object of the domain foo.com on a master server to a directory named /backup: master_server# nisbackup /backup org_dir.foo.com. Example 2: Backup of the entire NIS+ domain foo.com to a directory named /backup To backup the entire NIS+ domain foo.com to a directory named /backup: master_server# nisbackup /backup foo.com. org_dir.foo.com. groups_dir.foo.com. ctx_dir.foo.com. Example 3: Backup of an entire NIS+ database to a backup directory named /backup To backup an entire NIS+ database to a backup directory named /backup: master_server# nisbackup -a /backup EXIT STATUS
0 Successful completion. 1 An error occurred. FILES
/backup-dir/backup_list This ascii file contains a list of all the objects contained in this backup-dir directory. /backup-dir/directory-object A subdirectory that is created in the backup-dir that contains the NIS+ directory-object backup. /backup-dir/directory-object/data A subdirectory that contains the data files that are part of the NIS+ directory-object backup. /backup-dir/directory-object/last.upd This data file contains timestamp information about the directory-object. /backup-dir/directory-object/data.dict A NIS+ data dictionary for all of the objects contained in the NIS+ directory-object backup. ATTRIBUTES
See attributes(5) for descriptions of the following attributes: +-----------------------------+-----------------------------+ | ATTRIBUTE TYPE | ATTRIBUTE VALUE | +-----------------------------+-----------------------------+ |Availability |SUNWnisu | +-----------------------------+-----------------------------+ SEE ALSO
nis+(1), nisdefaults(1), nisrm(1), nisrestore(1M), rpc.nisd(1M), syslog(3C), nisfiles(4), syslog.conf(4), attributes(5) NOTES
NIS+ might not be supported in future releases of the SolarisTM Operating Environment. Tools to aid the migration from NIS+ to LDAP are available in the Solaris 9 operating environment. For more information, visit http://www.sun.com/directory/nisplus/transition.html. SunOS 5.10 12 Dec 2001 nisbackup(1M)
All times are GMT -4. The time now is 04:05 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy