Backupexec, DFS and Shadow Copies

I’ve had this problem for a while now, for the best part of two years my DC has been backing up to tape quite happily, then the fateful day comes to perform a restore and what?  The file wasn’t on the backup!  Or any of the last few….very odd situation.

Well, after a little researching the subject it seems that the problem was caused by our moving from a flat file structure to a basic DFS.  Since the Lands End site suffers from such a pathetic internet connection we have a decent box there – it’s a BDC so can authenticate users, pass out DHCP, DNS, etc, and we even have a simple DFS configured to move all operating files up there.

And this is one of the problems with a decent sized network architecture – interoperability, or rather in this case lack of, between systems.

Flat file system = backup working fine

Introduce DFS = need to shift to backing up the Shadow Copy rather than the actual folders.

Granted not a massive amount of work required, but when you’re not a product specialist and have to search for the solution – that’s a post all on it’s own! Suffice it to say that it could have been nearly fatal if some significant files were lost – which just proves the adage, you’re only as good as your last backup (and restore).

Within BackupExec the fix is simple enough, you just need to edit the selection list of the job (I use a template, as the daily job remains the same each day) and select the DFS folders required, per screenshot below.

At least in all of this I did also manage to get the SMTP alerts working, so I should now have a nice email each morning telling me that my 100gb backup has been completed!

Adventures in Sharepoint – email setup

Ok, cheeky post but too much wordage for twitter – just a quick post to say that I have configured incoming/outgoing email on my SP application, and normally I’d reproduce the whole lot here but today I’ll just provide you the two excellent links that helped 100%.

http://sharepointgeorge.com/2010/configuring-incoming-email-sharepoint-2010/

And

http://sharepointgeorge.com/2010/configuring-outgoing-email-sharepoint-2010/

Many thanks must go to Sharepoint George for those!

Code that makes me smile – sql comparisons

Ok, just a brief one, but important, for me, nonetheless!

I have a page on our site that displays various special offers – the CMS part is coded so that each offer is an entry in the a database, the form contains two date variables, offer start and offer end dates. The idea being that you can input a special offer record in advance, it will appear on the day the offer starts and disappear the day following the offer ending, as the advert says…We do a similar thing on our vacancies page, the only difference being that some offers do not have end dates.

Why have this?  Isn’t it just overcomplicating? Sure, you could just enter a date far into the future, but that adds to the guesswork, so the section was designed to allow a NULL date entry on the end date field which would allow the record to stay on the site indefinitely, the problem?  Constructing the SQL statement to let that happen….well it may be simple to some, but here’s my solution!

SELECT *
FROM specialofferstable
WHERE offerenddate >= date() or offerenddate is null
ORDER BY offerstartdate ASC

The problem was having the SQL select records that were in date OR nulls, of course I was trying =null and variations thereof, until I found a simple tutorial on SQL statements that showed the way.  Hyper advanced SQL it may not be, but Dreamweaver says it’s advanced and I’m happy to have figured it out!!

http://www.firstsql.com/tutor2.htm

Adventures with Sharepoint – Document Library Setup/Permissions

Keeping things nice and simple, just the one document library but since we have several departments who will manage their documents directly it seemed the most sensible way was to add sub folders and assign permissions to each one for editors.  Rather than extend the collaboration to everyone we are keeping the majority of the users on simple read permissions.

First off set the Document Library Permissions

  • From your sites homepage click Site Actions, Site Settings
  • Under the Site Administration heading click Site Libraries & Lists
  • From the Site Libraries & Lists page click Customize “Shared Documents” (or whatever you want to call it)
  • Under Permissions and Management heading click “Permissions for this document library”
  • If “This library inherits permissions from its parent. (home site)”, disable this by clicking Stop Inheriting Permissions and then Ok
  • You should now see that”This library has unique permissions” and you can modify the permissions as you require without inherited permissions confusing things!

We have stuck with a single limited access group which permits all domain users to read the site without having to log in see; http://www.rikzblog.co.uk/?p=257 and each section administrator is added on an ad hoc basis, there’s so few and they’ll change very infrequently it was easier than using groups – for now

Once that has been completed you can now create sub folders if you choose to

  • Click Shared Documents
  • Under Library Tools, click Documents, and then New Folder.
  • Give the New Folder a name and click Save.
  • Select the folder (click the check box next to the icon) and click Document Permissions on the ribbon
  • Switch off Inheriting Permissions
  • Make permission changes as required

You can now delegate management per folder and start uploading documents!  Just be sure to remember to Publish documents otherwise you’ll be like me, spending 20 mins trying to work out what was wrong with permissions, when in actual fact the documents I’d uploaded were still drafts.

Adventures with Sharepoint – Domain user access

Out of the box SP needs users to be authorised – but what if you just want all of your domain users to be able to access the system without password entry?

For all my testing I have a domain user account that shares the same restrictions/properties as the rest of the users, RDP into a different PC logged on as him and test…

So, to grant all domain users read access try the following;

  • From your sites homepage click Site Actions, Site Settings
  • Under the Users and Permissions heading click Site Permissions
  • In our setup I’ve used Home Visitors as the default group,
  • Click New, Add Users, Type in “Authenticated Users; domain users” and click the Check Name button, the display should change to show NT_AUTHORITY\Authenticated Users; YOURDOMAIN\domain users, click Ok
  • Go back to your test users desktop and try browsing the SP site again, you should now have read access for that account and all domain users.

03/05/11

Came back in to the office today and found my domain user test account unable to access, edited the above to add in domain users also, seems to work now.

Proudly powered by WordPress
Theme: Esquire by Matthew Buchanan.