Sponsored Content
Full Discussion: Backup and Recovery
Operating Systems Linux Ubuntu Backup and Recovery Post 303039711 by engineer2002 on Sunday 13th of October 2019 04:51:26 AM
Old 10-13-2019
Would you like to share your WhatsApp number, if you don't mind. For better understanding.
Dear neo, I am newbie of Linux, kindly guide me from scratch, if possible.

From full backup to cron job.


Regards,
Rashid Hussain.
Thanks for your precious reply.

Last edited by hicksd8; 10-13-2019 at 12:11 PM..
 

6 More Discussions You Might Find Interesting

1. UNIX for Dummies Questions & Answers

backup recovery

i have taken a backup using cpio command. Now i want to retrieve the contents. Replies appreciated. raguram (2 Replies)
Discussion started by: raguramtgr
2 Replies

2. AIX

TSM backup and recovery problem

When I use tsm command: archive -subdir=yes /dir1/ to backup file system: /dir1 After I delete the contents under /dir1 and recovery it from TSM backup, retrieve /dir1/ I found the link breaked. Such as: Before: ls -l lrwxrwxrwx 1 abc develop 8 Apr 28 16:04 bin... (1 Reply)
Discussion started by: rainbow_bean
1 Replies

3. Linux

Q: Backup and recovery in major corporations?

Hey guys, I hope this is the right place to post. As i'm not too sure where this question would go. The question is: How is backup and recovery carried out in major corporations. Even if you are not in a major corporation an answer would be great. I'm doing some research as to how it's carried... (2 Replies)
Discussion started by: LibRid
2 Replies

4. Shell Programming and Scripting

rsync backup and recovery options

Hi, Do we have any options in rsync to recover files from the backup? Please share your thoughts. Thanks in advance. (0 Replies)
Discussion started by: MVEERA
0 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. Red Hat

Redhat backup/recovery

Can you please let me know a clear step by step procedure link/doc for an effective full backup and recovery procedure for a Redhat server with 2.6.34.9-69.fc13.x86_64 ? Thanks in advance. I also have the same question for Ubuntu Enterprise 12.04 if you would ... thanks again (0 Replies)
Discussion started by: cmontr
0 Replies
queuedefs(4)							   File Formats 						      queuedefs(4)

NAME
queuedefs - queue description file for at, batch, and cron SYNOPSIS
/etc/cron.d/queuedefs DESCRIPTION
The queuedefs file describes the characteristics of the queues managed by cron(1M). Each non-comment line in this file describes one queue. The format of the lines are as follows: q.[njobj][nicen][nwaitw] The fields in this line are: q The name of the queue. a is the default queue for jobs started by at(1); b is the default queue for jobs started by batch (see at(1)); c is the default queue for jobs run from a crontab(1) file. njob The maximum number of jobs that can be run simultaneously in that queue; if more than njob jobs are ready to run, only the first njob jobs will be run, and the others will be run as jobs that are currently running terminate. The default value is 100. nice The nice(1) value to give to all jobs in that queue that are not run with a user ID of super-user. The default value is 2. nwait The number of seconds to wait before rescheduling a job that was deferred because more than njob jobs were running in that job's queue, or because the system-wide limit of jobs executing has been reached. The default value is 60. Lines beginning with # are comments, and are ignored. EXAMPLES
Example 1: A sample file. # # a.4j1n b.2j2n90w This file specifies that the a queue, for at jobs, can have up to 4 jobs running simultaneously; those jobs will be run with a nice value of 1. As no nwait value was given, if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. The b queue, for batch(1) jobs, can have up to 2 jobs running simultaneously; those jobs will be run with a nice(1) value of 2. If a job cannot be run because too many other jobs are running, cron(1M) will wait 90 seconds before trying again to run it. All other queues can have up to 100 jobs running simultaneously; they will be run with a nice value of 2, and if a job cannot be run because too many other jobs are running cron will wait 60 seconds before trying again to run it. FILES
/etc/cron.d/queuedefs queue description file for at, batch, and cron. SEE ALSO
at(1), crontab(1), nice(1), cron(1M) SunOS 5.10 1 Mar 1994 queuedefs(4)
All times are GMT -4. The time now is 06:43 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy