Is it the Backup Command field that has a limit of 256 characters, or is it the nsrsqlsv command itself that has the limit? If you type the nsrsqlsv command in a DOS prompt on the client, and add all databases (or snapshots) using
nsrsqlsv -s backupserver -h db1 -h db2 -h db3 ...
and so on...
There can be several reasons for this error, one is anti-virus applications. If the client has some form of anti-virus installed, try shutting it off and test a new backup. If it is successful then you could try and disable the scanning of outgoing files, if that is possible.
Another reason...
Note the jukebox name, then delete it and the tape drives
from within NetWorker. The just run a new jbconfig and give the jukebox the same name as it had before. Afterwards, just run a new inventory (nsrjb -Iv) and you should be all set.
Cheers!
The + in you skip statement will traverse the filesystem from the point specified in << XX >>, i.e the root in you case. So the "+skip: *.dbf" will skip all .dbf files found in the root as well as all subdirectories. Using only "skip: *.dbf" would skip only files found directly in << XX >>, not...
When backing up mailboxes, you can usually increase the performance a bit using wildcards in the saveset name.
You might need to increase the client parallelism to 5
or something.
MSEXCH:MB/A*
MSEXCH:MB/B*
MSEXCH:MB/C*
and so on..
This should also reduce restore times some, as you need only...
CAP (Cartridge Access Port) is the same as Mailbox, just a different term. Sometimes i´ts also referred to as an IO port.
On some jukeboxes, not sure about the Dell 136t, it sometimes becomes disabled if the jukebox is powered off for too long.
This means that you might need to use the panel on...
I´ve seen occasions when the cap has become disabled due to the library being powered off for too long (>1min). I think that might have been caused by a firmware bug though.. If you have had the lib powered off, you might need to enable the cap again using the panel on the library itself...
If this is on Windows, you can use the "mt" command in order to verify if the scsi adress has actually changed. Load (not mount) a tape in what NetWorker considers to be Tape0. Then run "mt -f \\.\Tape0 status" and if Windows does not find a tape in the drive, you will see an error at the end of...
The collectors gather data at non-peak hours to avoid putting more load on the server. I have seen just one instance where we *think* the collector might be causing some performance problems, but that is still under investigation. I have several other servers, both unix and windows, running just...
Well, we can't really write a complete script for you, that would take too long. I would however suggest that the script be written in perl as this is the best script language as far as i see it. You need to know how to user nsradmin as well as mminfo in order to write this script. Below is a...
Sorry, i missed the part with the pool being an Archive pool.
So no, you cannot clone to a pool that is not a pool of type Backup Clone. However, i agree with 605, why do you need to keep the backups in the Archive pool? I would suggest you perhaps create a new pool which you call MyArchive or...
You should use mminfo for this and create a slash (/) separated list of ssid/cloneid to use with the nsrclone command. See the examples below, you should modify them to meet your needs but that should basicly be it. For example, if the clients full backups always go to a specific pool, you...
No, they will still be available for recover. But if the browse policy for the backup has expired, and you have re-labled the tapes containing the index backups, you will not be able to easily recover the index (nsrck -L7) in order to select a certain file or folder for recover. What you have to...
Use nsradmin for this. If you know the name of the storage node it is easy. Just enter the nsradmin prompt by typing "nsradmin" and hit enter. Inside the prompt you set the query by typing ". NSR client" and hit enter. After this, print the client information using "print name: client" and...
Im not aware of any such limit, so i would guess your problem is located somewhere else. Since the client need to make so many jumps, i would suspect that the name resolution fails somehere along the line. Verify that the backupserver can reverse lookup the client and vice versa. Make sure they...
speedyx: Sure, that is possible. Here´s a before and after test i just did. If you look at the ssretent, i just increased it by 20 years =)
---
# mminfo -avr ssid,ssretent -q client=calvin
ssid retent
3967725411 12/20/06
# nsrmm -e 20-years -S `mminfo -avr ssid -q client=calvin`
#...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.