Sponsored Content
Full Discussion: Backups too CD
Special Forums UNIX Desktop Questions & Answers Backups too CD Post 37336 by mccrack_2003 on Tuesday 17th of June 2003 09:12:56 AM
Old 06-17-2003
Data Backups too CD

I've been handed the task of backing up some of our system files on a Solaris box. No probs. Zipped the logs that needed backing up but my superiors do not want it on tape, they want it spanned on CD's. The CD-Writer is available on a MS box. FTP'd the zipped logs across too the MS Machine but now i need too span this 20+ GB of data onto CD.
Problem 1. How too span this over multiple CD'z. ( Does winzip support this ? )
Problem 2. Easiest method too rebuild.

If anyone knows a better way too go about this it would be much appreciated. I know this is not a purely unix post but i'm taking a chance as i have too have this done asap.
 

9 More Discussions You Might Find Interesting

1. Filesystems, Disks and Memory

Backups

I have been using the hostdump.sh backup script for over a year now and have recently run into a problem. I'm now getting the following error at the end of my jobs; /bin/mt -f: error fsf'ing tape. This script uses the native 'ufsdump'. So, I try to go back and read the last dump on the tape... (11 Replies)
Discussion started by: Solaris
11 Replies

2. UNIX for Dummies Questions & Answers

backups

When using hostdump.sh to backup a system I can do it fine. But how can I restore what I backuped up? :) Thx in advance (2 Replies)
Discussion started by: merlin
2 Replies

3. UNIX for Advanced & Expert Users

UNIX backups

hi, how do we go for the BACK UPS on the UNIX box,using DLT tapes.i need to back up the stuff on the DLT tape. pls HELP:( (4 Replies)
Discussion started by: saood
4 Replies

4. UNIX for Dummies Questions & Answers

Backups.

Hello everyone my ? is about backups. I'am running SCO OS 505 and currently backing up the hole HD. Well the back up is taking too long and this is becoming a problem for the users since we are a 24-7 bussines, I whant stop backing up every thing on the HD. What are the most important files and... (1 Reply)
Discussion started by: kikkin
1 Replies

5. UNIX for Advanced & Expert Users

backups in background

Hi, how i can do background backup process in Unix?? I has Solaris Operating System. very much thanks!! (4 Replies)
Discussion started by: jairog
4 Replies

6. UNIX for Dummies Questions & Answers

restoring backups

okay.. pple.. say now i got an aix box. of course i could restore a backup done in aix environment. 1) now how about doing a restore from sun, hp from the aix box.? 2) can we install a sun, hp os into an aix box? 3) if (1) prohibits, then how about doing an sun, hp os installation on... (1 Reply)
Discussion started by: yls177
1 Replies

7. UNIX and Linux Applications

Oracle 9i - Backups

Is there a way to backup an Oracle 9i database without the use of OEM and OMS? (1 Reply)
Discussion started by: adelsin
1 Replies

8. AIX

AIX 6.1 Backups

Hello, I've got multiple AIX LPARs running on VIOS, within a blade environment. I need to dump a mksysb backup to backup rootvg and a couple of other volume groups. mksysb -i "destination"; works however I'd like to make sure its being done correctly. on the other volume groups, ive... (2 Replies)
Discussion started by: ollie01
2 Replies

9. Shell Programming and Scripting

Backups using rsync

Hello all, I'm using nas4free as a SAN and am having troubles getting a backup of it's data to work properly. I've posted in the nas4free forums, but haven't received much help. Here is the code I'm using: #!/bin/sh {... (1 Reply)
Discussion started by: dpatino
1 Replies
EXTATTRCTL(8)						    BSD System Manager's Manual 					     EXTATTRCTL(8)

NAME
extattrctl -- manage UFS1 extended attributes SYNOPSIS
extattrctl start path extattrctl stop path extattrctl initattr [-f] [-p path] attrsize attrfile extattrctl showattr attrfile extattrctl enable path attrnamespace attrname attrfile extattrctl disable path attrnamespace attrname DESCRIPTION
The extattrctl utility is the management utility for extended attributes over the UFS1 file system. It allows the starting and stopping of extended attributes on a file system, as well as initialization of attribute backing files, and enabling and disabling of specific extended attributes on a file system. The first argument on the command line indicates the operation to be performed. Operation must be one of the following: start path Start extended attribute support on the file system named using path. The file system must be a UFS1 file system, and the UFS_EXTATTR kernel option must have been enabled. If .attribute/user and .attribute/system exist at the filesystem root, extended attributes backed by files in these directories will be automatically enabled. Note that extended attributes can be automatically started at mount time by using the -o extattr option to mount(8). stop path Stop extended attribute support on the file system named using path. Extended attribute support must previously have been started. initattr [-f] [-p path] attrsize attrfile Create and initialize a file to use as an attribute backing file. You must specify a maximum per-inode size for the attribute in bytes in attrsize, as well as the file where the attribute will be stored, using attrfile. The -f argument may be used to indicate that it is alright to overwrite an existing attribute backing file; otherwise, if the target file exists, an error will be returned. The -p path argument may be used to preallocate space for all attributes rather than relying on sparse files to conserve space. This has the advantage of guaranteeing that space will be available for attributes when they are written, preventing low disk space condi- tions from denying attribute service. This file should not exist before running initattr. When a user attempts to set a ``user'' or ``system'' extended attribute that lacks a backing file, the kernel will attempt to auto- matically create it, provided .attribute/user or .attribute/system exist and are writable by the requesting user. showattr attrfile Show the attribute header values in the attribute file named by attrfile. enable path attrnamespace attrname attrfile Enable an attribute named attrname in the namespace attrnamespace on the file system identified using path, and backed by initialized attribute file attrfile. Available namespaces are ``user'' and ``system''. The backing file must have been initialized using initattr before its first use. Attributes must have been started on the file system prior to the enabling of any attributes. disable path attrnamespace attrname Disable the attributed named attrname in namespace attrnamespace on the file system identified by path. Available namespaces are ``user'' and ``system''. The file system must have attributes started on it, and the attribute most have been enabled using enable. EXAMPLES
extattrctl start / Start extended attributes on the root file system. extattrctl initattr 17 /.attribute/system/md5 Create an attribute backing file in /.attribute/system/md5, and set the maximum size of each attribute to 17 bytes, with a sparse file used for storing the attributes. extattrctl enable / system md5 /.attribute/system/md5 Enable an attribute named md5 on the root file system, backed from the file /.attribute/system/md5. extattrctl disable / md5 Disable the attribute named md5 on the root file system. extattrctl stop / Stop extended attributes on the root file system. SEE ALSO
getextattr(1), extattr_get_file(2), extattr(9) HISTORY
Extended attribute support was developed as part of the TrustedBSD Project, and introduced in FreeBSD 5.0 and NetBSD 4.0. It was developed to support security extensions requiring additional labels to be associated with each file or directory. Backing file autocreation was added in NetBSD 6.0. AUTHORS
Robert N M Watson BUGS
extattrctl works only on UFS1 file systems. The kernel support for extended attribute backing files and this control program should be gen- eralized for any file system that lacks native extended attribute support. BSD
June 17, 2011 BSD
All times are GMT -4. The time now is 06:48 AM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy