jinnantonnixx

A way around this would be to add '-exec rename ...' to add a flag to a resized file. e.g. lolcat_rs.jpg. Adding _rs to the file flags it as resized. Then add a condition to the find to ignore the _rs flag. e.g.( .... ! -iname "*_rs.jpg") . Just a thought....

Flexet Adminstudio. It's from the InstallShield family. Totally over the top for basic use; 'comprehensive' is an understatement. .

This thread has dyed.

They are created automatically when you make your zone(s). In a nutshell, they specify the name servers for your domain. You can add to the list manually if you want to delegate zones. Suppose you owned 'bugs.co.uk' If you wanted a subdomain called 'mystuff.bugs.co.uk' you would create NS records for 'mystuff.bugs.co.uk' in 'bugs.co.uk'. The NS records must point to the DNS servers responsible for 'mystuff.bugs.co.uk' . For simple delegations, the NS records can point to the same DNS servers for 'mystuff.bugs.co.uk' and 'bugs.co.uk'. They don't have to be different, but uk.ibm.com and us.ibm.com are very likely to be different. Something like that, anyway.

I've got a nice little Samsung i3 which runs Ubuntu nicely. It has Intel graphics, which isn't the best, but adequate enough. Certified: Ubuntu Desktop certified hardware | Ubuntu Friendly: https://friendly.ubuntu.com/ Also check the lists here: Hardware & Laptops - Ubuntu Forums

Are the zones set up as AD Integrated? If so, and it's a copy (replicated), it shouldn't be in forwarding - that just doesn't make sense. Perhaps this is the fault.

Are you setting the DNS address on the clients via DHCP? This is the best way. Also, have you got competing name-resolution services running, like WINS service?

Just spotted you have two DNS servers. Under the 'Properties' of your forward lookup zone (do this from each server in your DNS view), do the correct name servers show up? Are your dynamic updates set to 'secure only?'

Try NSLOOKUP in debug mode, NSLOOKUP >set debug >name-of-your-server (or other suitable site to check) If you have DNS suffixes appending, you'll get a few rcode=NXDOMAIN in your answers, but you should get the correct answer if all is well. It's a useful tool for tracking down where DNS is going wrong.

Anything in the DNS section of event viewer on the DNS server?

You can find some on the web.

Another terrible thread.

I'd put money on the file not being released by SIMS. Maybe they forgot a file.dispose() or a file.close(). If you reboot the server I bet the problem will go away. Other than that, use a file enumerator to release the lock.

You could try resetting the NTFS permissions icacls /reset It's not uncommon for NTFS to go wrong, but the 'in use by process' message would suggest otherwise. Can't hurt to try it though. Also, if you just list the acls for the file with 'icacls ' do you get any unresolved users associated with the file?

Good point, Vik. Backup operations in tandem, whether it's an SQL script or a third party agent like Veritas will affect the log file, and these competing backup operations are certain to ruin the backup chain. Sometimes however, you will need to make an ad-hoc backup, perhaps to test something. In this case it's possible to make a backup with the COPY_ONLY flag set either from an SQL statement or through the manager console. In either case, this 'COPY_ONLY' backup has absolutely no effect on the log files, which is very, very useful if you need to make a one-off backup without ruining your backup set. Copy Only Backup for SQL Server 2005 and SQL Server 2008 Copy-Only Backups (SQL Server)

Gold has a higher resistance than silver or copper (but resists corrosion), so unless you're installing your cables in a sauna I'd go for the plain ones.

£5 Ross cables from Sainsburys are good. For more fun, Audiophile Deathmatch: Monster Cables vs. a Coat Hanger

Are you using Virgin's DNS servers or other ones? Do the addresses resolve correctly?

SQL 2008 has database mirroring. I haven't really looked at it, but it might be worth a look. How to: Configure a Database Mirroring Session (SQL Server Management Studio)

It all depends on what you're prepared to lose. If you back up every day, worst case is you've lost a full day's work. I would write it in to your SLA. If you state that the backups are done daily, and that you can restore from the night before, then if that's in your SLA that's what you do. Personally? Id' go for a daily or weekly full with hourly log backups. If you do this, your database should be in 'full' recovery mode, not 'simple'. 'Simple' restricts you to full backups; you can't make differential backups on a 'simple' database. Doing hourly full backups are likely to generate huge amounts of backup data and stress your system. In my case, we have two (large) virtual servers - one live, hosting about 100 databases (central hosting). The other server is a warm standby, with copies of the databases in restoring mode. I set up log shipping between the two; every 15 minutes the transaction logs are shipped from the live to the standby. I wrote the scripts to do this, it was a lot of work but it means that we can fail-over a database (or 100 database) in under a minute. Worst case we lose 15 minutes of work.

I've had some success with tools like this: OpenedFilesView - View opened/locked files in your system (sharing violation issues) Once you know what you're dealing with, you're halfway there.

Perhaps the easiest way (as you have the Manager console) is to set up a scheduled job to backup your database. From here, you can move the .bak files to a safe place. And TEST IT! Make sure it works. This might be of use: How to schedule a database backup operation by using SQL Server Management Studio in SQL Server 2005

Please don't just copy the mdf and ldf files. This isn't the way to do SQL backups. At the very least you'll run into truncation problems. A proper backup is done with the SQL 'BACKUP' command, or a scheduled job which you can set up using SQL Server Manager. This way you can keep the database running, and the backup is a consistent, discrete file which you can use to restore to the same or another server. http://www.sqlteam.com/article/backup-and-restore-in-sql-server-full-backups http://msdn.microsoft.com/en-us/library/ms186865.aspx Until you properly prove your backups by restoring them to a DR system and getting the recovered system working properly, you only have 'alleged backups'

This seems so strange looking at it from wet Wales. It's rained pretty much constantly since October, with the exception of a nice week or so in March. We had some building work done over Christmas, I kept a chart, and during November, December and January, we had THREE DAYS on which it didn't rain. It's enough to strip a man of reason.

Landscape | Canonical